core-lightning/hsmd/permissions.h

#ifndef LIGHTNING_HSMD_PERMISSIONS_H
#define LIGHTNING_HSMD_PERMISSIONS_H
#include "config.h"

#define HSM_PERM_ECDH 1
#define HSM_PERM_SIGN_GOSSIP 2
#define HSM_PERM_SIGN_ONCHAIN_TX 4
#define HSM_PERM_COMMITMENT_POINT 8
#define HSM_PERM_SIGN_REMOTE_TX 16
#define HSM_PERM_SIGN_CLOSING_TX 32
#define HSM_PERM_SIGN_WILL_FUND_OFFER 64
#define HSM_PERM_SIGN_SPLICE_TX 128

#define HSM_PERM_MASTER 1024
#endif /* LIGHTNING_HSMD_PERMISSIONS_H */
hsmd: rename "capabilities" flags for hsm fds to "permissions" I obviously like the word "capabilities" since I reused it to refer to the HSM's overall features :( Suggested-by: @ksedgwic Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2023-08-07 15:21:40 +09:30			`#ifndef LIGHTNING_HSMD_PERMISSIONS_H`
			`#define LIGHTNING_HSMD_PERMISSIONS_H`
			`#include "config.h"`

			`#define HSM_PERM_ECDH 1`
			`#define HSM_PERM_SIGN_GOSSIP 2`
			`#define HSM_PERM_SIGN_ONCHAIN_TX 4`
			`#define HSM_PERM_COMMITMENT_POINT 8`
			`#define HSM_PERM_SIGN_REMOTE_TX 16`
			`#define HSM_PERM_SIGN_CLOSING_TX 32`
			`#define HSM_PERM_SIGN_WILL_FUND_OFFER 64`
hsmd: fix capability check for signing splices. The nomenclature confusion mean that we were ANDING a capability with a message number (29) which always returned non-zero. We really do need a new capability which we can hand to channeld to make these splice txs. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2023-08-07 15:21:41 +09:30			`#define HSM_PERM_SIGN_SPLICE_TX 128`
hsmd: rename "capabilities" flags for hsm fds to "permissions" I obviously like the word "capabilities" since I reused it to refer to the HSM's overall features :( Suggested-by: @ksedgwic Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2023-08-07 15:21:40 +09:30
			`#define HSM_PERM_MASTER 1024`
			`#endif /* LIGHTNING_HSMD_PERMISSIONS_H */`