From 8f818a64f2f0f3a833fc842d52a675358ec64c9c Mon Sep 17 00:00:00 2001 From: Igor Soarez Date: Wed, 18 Nov 2026 14:02:09 +0000 Subject: szecret: buckets beside the old store -- get/has/put/mv/rekey/list/check/enrol, admins from SZECRET_ADMINS_COMMAND; rotate retired (fleet hardening 12) A bucket is a directory of secrets with one set of readers: its recipients file plus the admins, the full set recorded in .szecret by rekey. put refuses when the readers or admins drift from that set, or with no admins; a plain put of a new name goes to admin-only, one still in the old store is rewritten there. The old store keeps working throughout. link/claude.sh leaves out an MCP server whose secret is in a bucket this host doesn't read. Design: cloud-setup docs/proposal-secret-roles.md. --- secrets/create-local.sh | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'secrets/create-local.sh') diff --git a/secrets/create-local.sh b/secrets/create-local.sh index ffebd9c..b72600d 100755 --- a/secrets/create-local.sh +++ b/secrets/create-local.sh @@ -56,6 +56,13 @@ if [[ "${metadata_exists}" == "true" ]]; then exit 1 fi +# An old-kind store keeps its key in the old store; with buckets that key +# would land in admin-only, which this machine can't read back. A repository +# bucket is registered in cloud-setup's szecret/repo-buckets instead. +if [[ -n "${buckets}" ]]; then + die "create-local makes an old-kind store, which can't be made on a machine with buckets; make a repository bucket instead (cloud-setup docs/proposal-secret-roles.md)" +fi + # Ensure target directory exists mkdir -p "${target_dir}" -- cgit v1.2.3