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_LOCK_OUTPOINT 256

#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 07:51:40 +02:00			`#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 07:51:41 +02:00			`#define HSM_PERM_SIGN_SPLICE_TX 128`
splice: Add hsmd_check_outpoint and hsmd_lock_outpoint In general, a validating signer may be under a different operational environment than the node, and therefore may have a different source of on-chain data. The signer may therefore temporarily disagree on whether a funding or splice transaction is locked (buried). We would like to ensure agreement between the signer and the node on how to progress a channel's state. The following message are added to provide a solution: - `check_outpoint(outpoint) -> bool` - check if the signer agrees that a funding candidate outpoint is buried - `lock_outpoint(outpoint)` - change the funding/splice state to locked Link: https://github.com/ElementsProject/lightning/issues/6722 Suggested-by: @devrandom Co-Developed-by: Ken Sedgwick <ken@bonsai.com> Changelog-Added: hsmd protocol: Added hsmd_check_outpoint and hsmd_lock_outpoint Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com> 2023-09-24 17:51:06 +02:00			`#define HSM_PERM_LOCK_OUTPOINT 256`
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 07:51:40 +02:00
			`#define HSM_PERM_MASTER 1024`
			`#endif /* LIGHTNING_HSMD_PERMISSIONS_H */`