Rusty Russell 5becfa6ee1 onion_message: don't use general secret, use per-message secret. ... We had a scheme where lightningd itself would put a per-node secret in the blinded path, then we'd tell the caller when it was used. Then it simply checks the alias to determine if the correct path was used. But this doesn't work when we start to offer multiple blinded paths. So go for a far simpler scheme, where the secret is generated (and stored) by the caller, and hand it back to them. We keep the split "with secret" or "without secret" API, since I'm sure callers who don't care about the secret won't check that it doesn't exist! And without that, someone can use a blinded path for a different message and get a response which may reveal the node. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>		2022-11-09 15:08:03 +01:00
..
capabilities.h	check: make sure all files outside contrib/ include "config.h" first.	2021-12-06 10:05:39 +10:30
hsmd_wire.csv	onion_message: don't use general secret, use per-message secret.	2022-11-09 15:08:03 +01:00
hsmd.c	hsmd: don't use point32 for bolt12, but use pubkeys (though still always 02)	2022-10-26 11:29:06 +10:30
libhsmd_status.c	check: make sure all files outside contrib/ include "config.h" first.	2021-12-06 10:05:39 +10:30
libhsmd.c	onion_message: don't use general secret, use per-message secret.	2022-11-09 15:08:03 +01:00
libhsmd.h	check: make sure all files outside contrib/ include "config.h" first.	2021-12-06 10:05:39 +10:30
Makefile	Makefile: check that hsm_version.h changes if wire/hsmd_wire.csv contents does	2022-10-26 11:29:06 +10:30