aljaz/lightning
1
0
Fork 0
mirror of https://github.com/aljazceru/lightning.git synced 2025-12-20 15:44:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

lightningd: checkmessage can intuit pubkey in some cases.

Browse Source 
*If* we know the key has signed something else (as is the case for
channel_announcement) then we can effectively trust the key derivation.

This matches how LND's VerifyMessage works, though in the next patch
we will document it exactly.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell
2019-10-13 15:48:39 +10:30
committed by neil saitug
parent 034ed1711c
commit e5d9c7effc
2 changed files with 66 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
tests/test_misc.py
View File

@@ -1649,7 +1649,7 @@ def test_relative_config_dir(node_factory):
def test_signmessage(node_factory):
l1 = node_factory.get_node()
l1, l2 = node_factory.line_graph(2, wait_for_announce=True)
corpus = [[None,
"this is a test!",
@@ -1685,3 +1685,16 @@ def test_signmessage(node_factory):
assert l1.rpc.call('checkmessage', [c[1], c[2], c[3]])['verified']
assert not l1.rpc.call('checkmessage', [c[1] + "modified", c[2], c[3]])['verified']
checknokey = l1.rpc.call('checkmessage', [c[1], c[2]])
# Of course, we know our own pubkey
if c[3] == l1.info['id']:
assert checknokey['verified']
else:
assert not checknokey['verified']
assert checknokey['pubkey'] == c[3]
# l2 knows about l1, so it can validate it.
zm = l1.rpc.call('signmessage', ["message for you"])['zbase']
checknokey = l2.rpc.call('checkmessage', ["message for you", zm])
assert checknokey['pubkey'] == l1.info['id']
assert checknokey['verified']