lightning

History

Rusty Russell 6aed936799 channeld: check option_data_loss_protect fields. Firstly, if they claim to know a future value, we ask the HSM; if they're right, we tell master what the per-commitment-secret it gave us (we have no way to validate this, though) and it will not broadcast a unilateral (knowing it will cause them to use a penalty tx!). Otherwise, we check the results they sent were valid. The spec says to do this (and close the channel if it's wrong!), because otherwise they could continually lie and give us a bad per-commitment-secret when we actually need it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>		6 years ago
..
benchmark.py	pytest: Remove test_lightningd and all the legacy testing framework	6 years ago
conftest.py	pytest: Pass result to fixtures and keep directories of failed tests	6 years ago
fixtures.py	pytest: fail if we see 'bad reestablish' in the logs.	6 years ago
requirements.txt	test: add pytest-xdist to the python test requirements	7 years ago
test_closing.py	pytest: fix race in test_closing_different_fees	6 years ago
test_connection.py	channeld: check option_data_loss_protect fields.	6 years ago
test_gossip.py	connectd: iterate through all known addresses for a peer, not just one.	6 years ago
test_invoices.py	pytest: Move invoice-related tests into their own file	6 years ago
test_misc.py	log: Append the current time to the crash log filename	6 years ago
test_pay.py	openingd: take peer before we're opening, wait for explicit funding msg.	6 years ago
utils.py	common: log when we toggle IO logging, don't edit env in tests!	6 years ago