mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-03-12 10:30:29 +01:00
Code Issues Projects Releases Wiki Activity
core-lightning/common/hsm_version.h

18 lines
526 B
C
Raw Normal View History

hsmd: introduce a simple API versioning scheme. With the rise of external HSMs like VLS, this is no longer an internal-only API. Fortunately, it doesn't change very fast so maintenance should not be a huge burden. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-10-17 11:04:08 +10:30
#ifndef LIGHTNING_COMMON_HSM_VERSION_H
#define LIGHTNING_COMMON_HSM_VERSION_H
#include "config.h"
/* We give a maximum and minimum compatibility version to HSM, to allow
* some API adaptation. */
Makefile: check that hsm_version.h changes if wire/hsmd_wire.csv contents does Otherwise I know we'll miss it. Simply check for a mention: we could well change things multiple times within a single release. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-10-17 11:05:01 +10:30
/* wire/hsmd_wire.csv contents version:
* 409cffa355ab6cc76bd298910adca9936a68223267ddc4815ba16aeac5d0acc3
*/
hsmd: introduce a simple API versioning scheme. With the rise of external HSMs like VLS, this is no longer an internal-only API. Fortunately, it doesn't change very fast so maintenance should not be a huge burden. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-10-17 11:04:08 +10:30
#define HSM_MIN_VERSION 1
Makefile: check that hsm_version.h changes if wire/hsmd_wire.csv contents does Otherwise I know we'll miss it. Simply check for a mention: we could well change things multiple times within a single release. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-10-17 11:05:01 +10:30
/* wire/hsmd_wire.csv contents version:
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 12:00:10 +10:30
* dd89bf9323dff42200003fb864abb6608f3aa645b636fdae3ec81d804ac05196
Makefile: check that hsm_version.h changes if wire/hsmd_wire.csv contents does Otherwise I know we'll miss it. Simply check for a mention: we could well change things multiple times within a single release. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-10-17 11:05:01 +10:30
*/
hsmd: don't use point32 for bolt12, but use pubkeys (though still always 02) This is the one place where we hand point32 over the wire internally, so remove it. This is also our first hsm version change! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-10-17 11:05:41 +10:30
#define HSM_MAX_VERSION 2
hsmd: introduce a simple API versioning scheme. With the rise of external HSMs like VLS, this is no longer an internal-only API. Fortunately, it doesn't change very fast so maintenance should not be a huge burden. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-10-17 11:04:08 +10:30
#endif /* LIGHTNING_COMMON_HSM_VERSION_H */
Reference in a new issue Copy permalink