Every way Skarbiec can refuse.
Every cause a Skarbiec functionality declares, as Skarbiec 0.5.0 at b65cf2d8bb982e784f0ad9ebf42a3d08279e4f08 prints it with skarbiec errors list: the step that failed, why, what the refusal shows, the fix, its code and exit status and the test that provokes it. Placeholders in braces are filled with the actual names when the refusal is raised.
skarbiec.acquisition acquisition-request-grant-ended#
verify a workload's signed proof and issue a one-use token for one field, consume that token for the field, and list the workloads whose proofs were spent. Started by skarbiec acquisition.
What failed: acquisition request. Why: {ended}: {consumer} proved its workload, but its acquire grant for {item}#{field} is no longer live. What the refusal shows: no token was issued, and neither the proof's nonce nor the workload's watermark was spent.
Fix: keep the grant {consumer} holds, with the workload key it names, until revoked (skarbiec grant keep {consumer}), register the workload's acquisition catalog again until revoked (skarbiec grant register <catalog> --workload-public-key-file <pem> --until-revoked), or issue {consumer} the grant again until revoked (skarbiec grant issue {consumer} --capabilities acquire:{item}#{field} --workload-public-key-file <pem> --until-revoked --replace-capabilities); --ttl-seconds in place of --until-revoked takes only a lifetime the operator states.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/group.sh::a_proved_workload_whose_acquire_grant_ended_is_told_when_it_ended.
skarbiec.acquisition acquisition-field-absent#
verify a workload's signed proof and issue a one-use token for one field, consume that token for the field, and list the workloads whose proofs were spent. Started by skarbiec acquisition.
What failed: acquisition request. Why: {item} keeps no field {field}, so an acquisition of {coordinate}#{field} has nothing to hand over. What the refusal shows: {consumer} proved its workload; no token was issued and its proof's nonce was not spent.
Fix: set the field on {item} (skarbiec field set {item} {field}, the value on standard input), then ask again with the same proof.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::a_proved_request_for_a_field_the_item_does_not_keep_is_refused_naming_both.
skarbiec.acquisition acquisition-read-field-gone#
verify a workload's signed proof and issue a one-use token for one field, consume that token for the field, and list the workloads whose proofs were spent. Started by skarbiec acquisition.
What failed: acquisition read. Why: {item} no longer keeps the field {field} the token was issued for. What the refusal shows: {consumer} presented a live token for {coordinate}#{field}; the token was not spent.
Fix: set the field on {item} again (skarbiec field set {item} {field}) and read with the same token, or ask for a new token with skarbiec acquisition request.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::a_token_whose_field_was_removed_is_refused_and_left_unspent.
skarbiec.acquisition acquisition-role-item-inexact#
verify a workload's signed proof and issue a one-use token for one field, consume that token for the field, and list the workloads whose proofs were spent. Started by skarbiec acquisition.
What failed: acquisition request. Why: {item} plays role {role}, and its id is not an exact name (ASCII letters, digits, '.', '_' and '-'), which every acquisition binds. What the refusal shows: {consumer} proved its workload; no token was issued and its proof's nonce was not spent.
Fix: give the item an exact id: skarbiec rename {item} <exact-id> --move-grants.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::a_role_played_by_an_item_without_an_exact_id_is_refused_naming_it.
skarbiec.acquisition acquisition-workloads-unreadable#
verify a workload's signed proof and issue a one-use token for one field, consume that token for the field, and list the workloads whose proofs were spent. Started by skarbiec acquisition.
What failed: listing the workloads the acquisition state remembers. Why: the acquisition state {path} cannot be read: {why}. What the refusal shows: nothing was listed or changed.
Fix: make {path} a regular file this account owns that only it may read or write (chmod 600 {path}); do not remove or replace it, since it is what refuses a spent proof presented again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/workloads.sh::a_state_others_may_read_is_refused_naming_the_mode_it_needs.
skarbiec.acquisition.state acquisition-state-not-regular#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: {doing} the acquisition state {path}. Why: {path} is {kind}, and the acquisition state is kept only in a regular file, so a link cannot send its tokens elsewhere. What the refusal shows: owner uid {owner}, mode {mode}; no token was issued or spent.
Fix: move {path} aside (the next request starts an empty state), or point SKARBIEC_ACQUISITION_FILE at a regular file this account owns.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::an_acquisition_state_that_is_a_link_is_refused_naming_its_kind.
skarbiec.acquisition.state acquisition-state-foreign-owner#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: {doing} the acquisition state {path}. Why: {path} belongs to uid {owner}, and this process runs as uid {uid}, so another account could have written the tokens it records. What the refusal shows: mode {mode}; no token was issued or spent.
Fix: as uid {owner}, move {path} aside or chown it to uid {uid}; or point SKARBIEC_ACQUISITION_FILE at a file this account owns.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::an_acquisition_state_another_account_owns_is_refused_naming_both.
skarbiec.acquisition.state acquisition-state-exposed#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: {doing} the acquisition state {path}. Why: {path} has mode {mode}, which lets the group or other accounts touch it, and it records which tokens are live. What the refusal shows: owner uid {owner}; no token was issued or spent.
Fix: chmod 600 {path}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::an_acquisition_state_others_may_read_is_refused_naming_its_mode.
skarbiec.acquisition.state acquisition-state-not-json#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: reading the acquisition state {path}. Why: {path} is not JSON: the reader stopped at line {line}, column {column}. What the refusal shows: {bytes} bytes; the parser said: {said}; no token was issued or spent.
Fix: restore {path} from a backup; with none, move it aside: every token it recorded is then unknown, and each workload asks for a new one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::an_acquisition_state_that_is_not_json_is_refused_naming_where.
skarbiec.acquisition.state acquisition-state-not-object#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: reading the acquisition state {path}. Why: {path} holds {found}, not the object of version and sections every acquisition state is. What the refusal shows: no token was issued or spent.
Fix: restore {path} from a backup; with none, move it aside: every token it recorded is then unknown, and each workload asks for a new one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::an_acquisition_state_that_is_no_object_is_refused_naming_what_it_holds.
skarbiec.acquisition.state acquisition-state-version-unknown#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: reading the acquisition state {path}. Why: {path} records version {version}, and this skarbiec reads only version "v1". What the refusal shows: no token was issued or spent.
Fix: run the skarbiec that wrote {path} (skarbiec --version says which this is), or move {path} aside: every token it recorded is then unknown.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::an_acquisition_state_of_another_version_is_refused_naming_it.
skarbiec.acquisition.state acquisition-state-section-unfit#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: reading the acquisition state {path}. Why: its {section} section is {found}, not the object of records every section is. What the refusal shows: no token was issued or spent.
Fix: restore {path} from a backup; with none, move it aside: every token it recorded is then unknown.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/acquisition/state.sh::an_acquisition_state_whose_section_is_no_object_is_refused_naming_it.
skarbiec.acquisition.state acquisition-token-collision#
lock the acquisition state, read the tokens, proofs and workloads it records, and replace it with an owner-only file. Started by other functionalities only.
What failed: issuing {consumer} a token for {item}#{field}. Why: the digest of the token just drawn already names a live token in {path}, which a working random source never draws twice. What the refusal shows: {live} live token(s) recorded; the proof's nonce was not spent and nothing was written.
Fix: sign a fresh proof and ask again; if it recurs, this host's random source is broken and no secret skarbiec draws on it can be trusted.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/acquisition/state.sh::a_drawn_token_that_names_a_live_one_is_refused.
skarbiec.agent agent-already-enrolled#
create the internal-authority item whose agent_auth_secret answers agent:<agent>, with a secret generated here and never printed. Started by skarbiec agent enrol, POST /v1/operator/agents/enrol.
What failed: enrolling the agent {agent}. Why: {agent} already has a signing identity in item {item}. What the refusal shows: identity item: {item}.
Fix: skarbiec route resolve agent:{agent} shows it; nothing was written.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/agent_enrol.sh::an_agent_enrolled_twice_is_refused_naming_its_identity_item.
skarbiec.agent agent-item-taken#
create the internal-authority item whose agent_auth_secret answers agent:<agent>, with a secret generated here and never printed. Started by skarbiec agent enrol, POST /v1/operator/agents/enrol.
What failed: enrolling the agent {agent}. Why: the item {item} its identity is kept in already exists and is not {agent}'s signing identity. What the refusal shows: item {item}: live, not an identity of {agent}.
Fix: rename it with skarbiec rename {item} <new-id>, or delete it, then enrol {agent}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/agent_enrol.sh::an_identity_item_id_another_item_holds_is_refused_naming_it.
skarbiec.agent agent-identity-unreadable#
create the internal-authority item whose agent_auth_secret answers agent:<agent>, with a secret generated here and never printed. Started by skarbiec agent enrol, POST /v1/operator/agents/enrol.
What failed: checking whether {agent} already has a signing identity. Why: an internal-authority item does not open with this host's keys or names its agent in no readable id field, so whether {agent} already has a signing identity cannot be told. What the refusal shows: {error}; agent identity items are opened to read the agent each names.
Fix: skarbiec readers <item> names the keys an identity item is sealed to; open it with the owner's key file and enrol again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/agent_enrol.sh::an_identity_item_that_does_not_open_here_is_refused_instead_of_read_as_absent.
skarbiec.arguments arguments-form-missing#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {command} does nothing on its own, and was given none of its forms ({forms}). What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_command_given_none_of_its_forms_is_refused_naming_them.
skarbiec.arguments arguments-form-unknown#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {given} is not one of the forms of {command} ({forms}). What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_form_the_command_does_not_have_is_refused_naming_its_forms.
skarbiec.arguments arguments-missing#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {command} needs {needed}, and the command line does not give it. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_command_missing_a_value_it_needs_is_refused_naming_it.
skarbiec.arguments arguments-extra#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {command} takes {takes}, and was given {extra} beyond it, which it would otherwise ignore. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_word_beyond_what_the_command_takes_is_refused_naming_it.
skarbiec.arguments arguments-value-unfit#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {what} must be {expects}, and {given} is not. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_value_of_the_wrong_shape_is_refused_naming_the_shape.
skarbiec.arguments arguments-conflict#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {first} and {second} were both given, and {command} takes one of them, so it cannot tell which was meant. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::two_values_where_the_command_takes_one_are_refused_naming_both.
skarbiec.arguments arguments-flag-unknown#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {command} takes no --{flag}, so it cannot do what the flag asks. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_flag_the_command_does_not_take_is_refused_naming_it.
skarbiec.arguments arguments-flag-needs#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {flag} was given without {needs}. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_flag_given_without_the_one_it_needs_is_refused_naming_both.
skarbiec.arguments arguments-flag-inapplicable#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {flag} applies only {applies}, and was given with {given}. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_flag_given_where_it_does_not_apply_is_refused_naming_where_it_does.
skarbiec.arguments arguments-same#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: {first} and {second} both name {given}, and {command} acts on two different things. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::two_values_that_must_differ_naming_one_thing_are_refused.
skarbiec.arguments arguments-flag-repeated#
read a command line into the form, values and flags a command takes, before anything is read or changed. Started by other functionalities only.
What failed: reading what skarbiec {command} does. Why: --{flag} was given more than once, and {command} reads one value of it, so every value but the last would be dropped without a word. What the refusal shows: arguments: {arguments}.
Fix: run it as skarbiec {usage}, giving --{flag} once: a list is one comma-separated value.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/arguments.sh::a_flag_given_twice_is_refused_naming_it.
skarbiec.alert alert-not-set#
post a failed unattended pass to the chat webhook an item keeps, and set, read, test or remove which item that is. Started by skarbiec alert set, skarbiec alert status, skarbiec alert test, skarbiec alert unset, POST /v1/operator/alert/status, POST /v1/operator/alert/set, POST /v1/operator/alert/test, POST /v1/operator/alert/unset, Desktop: Settings → Policy → Alerts.
What failed: {doing} this host's alert. Why: no alert is set on this host. What the refusal shows: no setting at {setting}.
Fix: set one: skarbiec alert set <id> --field <field>, naming the item that keeps the webhook address.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/alert/alert_webhook.sh::testing_or_removing_an_alert_that_is_not_set_is_refused_naming_alert_set.
skarbiec.alert alert-setting-not-json#
post a failed unattended pass to the chat webhook an item keeps, and set, read, test or remove which item that is. Started by skarbiec alert set, skarbiec alert status, skarbiec alert test, skarbiec alert unset, POST /v1/operator/alert/status, POST /v1/operator/alert/set, POST /v1/operator/alert/test, POST /v1/operator/alert/unset, Desktop: Settings → Policy → Alerts.
What failed: reading this host's alert setting {setting}. Why: {setting} is not the JSON object of item and field alert set writes, so which item keeps the webhook address cannot be read. What the refusal shows: the JSON reader said: {said}.
Fix: set the alert again with skarbiec alert set <id> --field <field>, which writes the setting anew.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/alert/alert_webhook.sh::an_alert_setting_that_is_not_the_item_and_field_is_refused_naming_it.
skarbiec.alert alert-setting-field-missing#
post a failed unattended pass to the chat webhook an item keeps, and set, read, test or remove which item that is. Started by skarbiec alert set, skarbiec alert status, skarbiec alert test, skarbiec alert unset, POST /v1/operator/alert/status, POST /v1/operator/alert/set, POST /v1/operator/alert/test, POST /v1/operator/alert/unset, Desktop: Settings → Policy → Alerts.
What failed: reading this host's alert setting {setting}. Why: {setting} names no {name} as text, and the setting names the item and the field that keep the webhook address. What the refusal shows: setting: {held}.
Fix: set the alert again with skarbiec alert set <id> --field <field>, which writes the setting anew.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/alert/alert_webhook.sh::an_alert_setting_naming_no_item_is_refused_naming_the_member.
skarbiec.alert alert-address-not-https#
post a failed unattended pass to the chat webhook an item keeps, and set, read, test or remove which item that is. Started by skarbiec alert set, skarbiec alert status, skarbiec alert test, skarbiec alert unset, POST /v1/operator/alert/status, POST /v1/operator/alert/set, POST /v1/operator/alert/test, POST /v1/operator/alert/unset, Desktop: Settings → Policy → Alerts.
What failed: reading the webhook address {item} keeps in {field}. Why: {item}'s {field} is not an https:// address, and an alert carries what failed, which is posted only over TLS. What the refusal shows: the address is not shown: it lets anyone post to the channel.
Fix: keep the channel's https:// incoming webhook address in {item}'s {field} (skarbiec field set {item} {field}), then run the same command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/alert/alert_webhook.sh::an_address_that_is_not_https_is_refused_and_nothing_written.
skarbiec.alert alert-address-character#
post a failed unattended pass to the chat webhook an item keeps, and set, read, test or remove which item that is. Started by skarbiec alert set, skarbiec alert status, skarbiec alert test, skarbiec alert unset, POST /v1/operator/alert/status, POST /v1/operator/alert/set, POST /v1/operator/alert/test, POST /v1/operator/alert/unset, Desktop: Settings → Policy → Alerts.
What failed: reading the webhook address {item} keeps in {field}. Why: {item}'s {field} holds a quote, backslash, space or control character, which no webhook address carries, so the value is not the address alone. What the refusal shows: the address is not shown: it lets anyone post to the channel.
Fix: keep the channel's webhook address alone, with nothing around it, in {item}'s {field} (skarbiec field set {item} {field}).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/alert/alert_webhook.sh::an_address_holding_a_space_is_refused_and_nothing_written.
skarbiec.audit.epoch audit-epoch-intact#
start a new, signed chain in the journal after acknowledging that the old one is broken. Started by skarbiec audit epoch.
What failed: starting a new chain in the audit journal at {path}. Why: the journal's chain is intact, and an epoch acknowledges a broken one. What the refusal shows: audit verify finds no fault in {path}.
Fix: nothing to acknowledge; skarbiec audit verify reports the chain.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::an_epoch_over_an_intact_journal_is_refused.
skarbiec.audit.epoch audit-epoch-no-signer#
start a new, signed chain in the journal after acknowledging that the old one is broken. Started by skarbiec audit epoch.
What failed: signing the epoch checkpoint of the audit journal at {path}. Why: the vault records no key for its owner {owner}, so nothing signs as the owner. What the refusal shows: vault file: {vault}; nothing was written.
Fix: register the owner's key: skarbiec owner key import <file>, then run audit epoch again; skarbiec owner key show {owner} names the key the key file holds.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::an_epoch_whose_vault_records_no_owner_key_is_refused_naming_the_owner.
skarbiec.audit.journal audit-journal-block-size#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: reading the newest lines of the audit journal file {file}. Why: the file system reports no I/O block size for it, the first window its tail is read in. What the refusal shows: audit journal: {path}.
Fix: keep the journal on a local file system: SKARBIEC_AUDIT_FILE names where it is.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::a_journal_on_a_file_system_with_no_block_size_is_refused.
skarbiec.audit.journal audit-segment-stray#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: reading the closed audit segments in {directory}. Why: {directory} holds {file}, which is not a closed audit segment (NNNNNN.jsonl), so the journal cannot be read with everything in it accounted for. What the refusal shows: audit journal: {path}.
Fix: move that file out of {directory}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/appends/segments.sh::a_stray_file_in_the_segment_directory_is_refused_naming_it.
skarbiec.audit.journal audit-segment-missing#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: reading the closed audit segments in {directory}. Why: closed audit segment {missing} is missing from {directory} (the next present is {present}), so the chain cannot be followed through it. What the refusal shows: audit journal: {path}.
Fix: restore it from where the closed segments are kept: {missing} goes back into {directory}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/appends/segments.sh::a_missing_closed_segment_is_refused_naming_it.
skarbiec.audit.journal audit-segment-taken#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: closing the open audit journal {path} as a segment. Why: {target} already exists, so the open journal is not moved over it. What the refusal shows: the open file is kept as it was.
Fix: move {target} out of {directory}, then skarbiec audit rotate closes the segment again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/appends/segments.sh::a_segment_written_between_listing_and_closing_is_not_overwritten.
skarbiec.audit.journal audit-journal-tail-not-entry#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: chaining onto the last line of the audit journal file {file}. Why: the file ends with a line that is not an entry: it is not JSON (it stops being JSON at column {column} of {length}). What the refusal shows: audit journal: {path}; the parser said: {said}; nothing was chained onto that line.
Fix: skarbiec audit verify names the line, and skarbiec audit epoch --reason <text> starts a new chain after it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/appends/damaged_tail.sh::a_damaged_last_line_refuses_the_next_entry_and_stays_last.
skarbiec.audit.journal audit-journal-tail-not-text#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: chaining onto the last line of the audit journal file {file}. Why: the file ends with a line that is not an entry: it is not UTF-8 text, so no hash can be read from it. What the refusal shows: audit journal: {path}; the decoder said: {said}; nothing was chained onto that line.
Fix: skarbiec audit verify names the line, and skarbiec audit epoch --reason <text> starts a new chain after it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/appends/damaged_tail.sh::a_last_line_that_is_not_text_refuses_the_next_entry_and_stays_last.
skarbiec.audit.journal audit-journal-tail-unhashed#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: chaining onto the last line of the audit journal file {file}. Why: its last entry carries no hash. What the refusal shows: audit journal: {path}; nothing was chained onto that line.
Fix: skarbiec audit verify names the line, and skarbiec audit epoch --reason <text> starts a new chain after it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/appends/damaged_tail.sh::a_last_entry_without_a_hash_refuses_the_next_entry_and_stays_last.
skarbiec.audit.journal audit-journal-clock#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: stating the time of an entry in the audit journal {path}. Why: the clock reads a time no RFC 3339 line can carry: past the year 9999. What the refusal shows: the time library said: {said}; nothing was written.
Fix: set this host's clock to the present time (date -u says what it reads) and run the command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::a_clock_past_the_year_9999_is_refused.
skarbiec.audit.journal audit-journal-retired-line#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: reading the loopback ports retired units answered on from the audit journal {path}. Why: the unit-retired line {line} of segment {segment} holds no list of ports, which every such line records. What the refusal shows: line: {text}.
Fix: skarbiec audit verify names the line; put back the segment from where the journal is kept, so no retired port goes unanswered.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::a_unit_retired_line_without_its_ports_is_refused_naming_it.
skarbiec.audit.journal audit-journal-retired-line-not-json#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: reading the loopback ports retired units answered on from the audit journal {path}. Why: the unit-retired line {line} of segment {segment} is not JSON (it stops being JSON at column {column}), so the ports it retired cannot be read. What the refusal shows: the parser said: {said}; line: {text}.
Fix: skarbiec audit verify names the line; put back the segment from where the journal is kept, so no retired port goes unanswered.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::a_unit_retired_line_that_is_not_json_is_refused_naming_it.
skarbiec.audit.journal audit-journal-retired-port-unfit#
find, read, lock, close and write the files of the hash-chained audit journal. Started by other functionalities only.
What failed: reading the loopback ports retired units answered on from the audit journal {path}. Why: the unit-retired line {line} of segment {segment} lists {port}, which is no TCP port (a whole number from 0 to 65535). What the refusal shows: line: {text}.
Fix: skarbiec audit verify names the line; put back the segment from where the journal is kept, so no retired port goes unanswered.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::a_unit_retired_line_listing_no_port_is_refused_naming_it.
skarbiec.backup backup-directory-absent#
copy the vault file owner-only into a directory the owner chooses and read the copy back as a vault, or say what a copy holds and whether it would restore. Started by skarbiec backup, skarbiec backup check, skarbiec backup diff, skarbiec backup schedule, skarbiec backup unschedule, skarbiec maintain.
What failed: keeping a copy of the vault in {directory}. Why: nothing is at {directory}, and backup writes its copy into a directory that exists rather than making one where a mistyped path points. What the refusal shows: nothing was copied.
Fix: create the directory (mkdir -p {directory}) or name the one meant, such as a mounted external disk.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/backup/backup.sh::a_backup_into_a_directory_that_does_not_exist_is_refused_naming_it.
skarbiec.backup backup-directory-not-directory#
copy the vault file owner-only into a directory the owner chooses and read the copy back as a vault, or say what a copy holds and whether it would restore. Started by skarbiec backup, skarbiec backup check, skarbiec backup diff, skarbiec backup schedule, skarbiec backup unschedule, skarbiec maintain.
What failed: keeping a copy of the vault in {directory}. Why: {directory} is a file, not a directory, and backup writes its copy into a directory. What the refusal shows: nothing was copied.
Fix: name the directory the copy goes in, not a file.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/backup/backup.sh::a_backup_into_a_file_is_refused_naming_it.
skarbiec.backup backup-vault-unnamed#
copy the vault file owner-only into a directory the owner chooses and read the copy back as a vault, or say what a copy holds and whether it would restore. Started by skarbiec backup, skarbiec backup check, skarbiec backup diff, skarbiec backup schedule, skarbiec backup unschedule, skarbiec maintain.
What failed: naming the copy of the vault {source}. Why: the vault path {source} ends in no file name, and a copy is named after the vault file it keeps. What the refusal shows: nothing was copied.
Fix: name the vault by its file path with SKARBIEC_VAULT_FILE.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/backup/backup.sh::a_vault_path_with_no_file_name_is_refused.
skarbiec.backup backup-schedule-empty#
copy the vault file owner-only into a directory the owner chooses and read the copy back as a vault, or say what a copy holds and whether it would restore. Started by skarbiec backup, skarbiec backup check, skarbiec backup diff, skarbiec backup schedule, skarbiec backup unschedule, skarbiec maintain.
What failed: reading which directory this host backs up to. Why: the backup schedule {path} is empty, and it holds the one directory the rolling copy goes in. What the refusal shows: schedule: {path}.
Fix: name the directory again with skarbiec backup schedule <directory>, or stop the schedule with skarbiec backup unschedule.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/backup/schedule.sh::an_empty_schedule_is_refused_naming_it.
skarbiec.backup backup-scheduled-directory-gone#
copy the vault file owner-only into a directory the owner chooses and read the copy back as a vault, or say what a copy holds and whether it would restore. Started by skarbiec backup, skarbiec backup check, skarbiec backup diff, skarbiec backup schedule, skarbiec backup unschedule, skarbiec maintain.
What failed: refreshing the rolling copy of the vault in {directory}. Why: the scheduled backup directory {directory} is not there: a disk unplugged, a folder moved. What the refusal shows: the last rolling copy, wherever the disk is, is kept as it was.
Fix: reconnect it, or name another with skarbiec backup schedule <directory>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/backup/schedule.sh::a_scheduled_directory_that_is_gone_is_refused_naming_it.
skarbiec.backup.restore copy-unreadable#
put a copy of the vault in place of the live vault, keeping the live one beside it. Started by skarbiec backup restore, POST /v1/operator/backup/restore, Desktop: Backups → Restore a backup → Put it in place.
What failed: reading the copy {backup} to put in place of the vault. Why: {backup} does not read as a Skarbiec vault. What the refusal shows: copy: {backup}; reading it said: {error}; nothing was restored.
Fix: skarbiec backup check {backup} says what the copy holds and why it does not open; name a copy skarbiec backup made.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/backup/backup.sh::restoring_a_file_that_is_not_a_vault_restores_nothing.
skarbiec.backup.restore aside-unwritten#
put a copy of the vault in place of the live vault, keeping the live one beside it. Started by skarbiec backup restore, POST /v1/operator/backup/restore, Desktop: Backups → Restore a backup → Put it in place.
What failed: keeping the live vault aside at {aside} before the copy replaces it. Why: the live vault cannot be moved aside, so the copy has nowhere to go without losing it. What the refusal shows: live vault: {live}; the file system answered: {error}; nothing was restored.
Fix: free the disk or let this account write the vault's directory, then restore again; the copy goes in place only after the live vault is kept.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/backup/backup.sh::a_restore_that_cannot_keep_the_live_vault_restores_nothing.
skarbiec.backup.restore-item copy-unreadable#
put back one item a copy of the vault holds and the live vault lost, as the copy keeps it. Started by skarbiec backup restore <file> --item <id>, POST /v1/operator/backup/restore (item), Desktop: Backups → Restore a backup → Put back one item.
What failed: reading the copy {backup} to put in place of the vault. Why: {backup} does not read as a Skarbiec vault. What the refusal shows: copy: {backup}; reading it said: {error}; nothing was restored.
Fix: skarbiec backup check {backup} says what the copy holds and why it does not open; name a copy skarbiec backup made.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/backup/backup.sh::restoring_a_file_that_is_not_a_vault_restores_nothing.
skarbiec.backup.restore-item item-not-in-copy#
put back one item a copy of the vault holds and the live vault lost, as the copy keeps it. Started by skarbiec backup restore <file> --item <id>, POST /v1/operator/backup/restore (item), Desktop: Backups → Restore a backup → Put back one item.
What failed: taking {id} from the copy {backup}. Why: the copy {backup} holds no item {id}. What the refusal shows: copy: {backup}; nothing was restored.
Fix: skarbiec backup check {backup} lists what the copy holds; name an item it keeps, or a copy taken while the item was there.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/backup/item_restore.sh::an_item_the_copy_does_not_hold_is_refused_and_nothing_changes.
skarbiec.backup.restore-item item-held#
put back one item a copy of the vault holds and the live vault lost, as the copy keeps it. Started by skarbiec backup restore <file> --item <id>, POST /v1/operator/backup/restore (item), Desktop: Backups → Restore a backup → Put back one item.
What failed: putting {id} back from the copy {backup}. Why: the live vault {live} holds {id} already ({state}); restoring one item puts back only an item the vault lost, never over one it keeps. What the refusal shows: live vault: {live}; {id}: {state}; nothing was restored.
Fix: skarbiec restore {id} brings a trashed item back and skarbiec restore {id} --at <at> rolls a live one back to a saved version; skarbiec backup diff {backup} names how the copy's {id} differs.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/backup/item_restore.sh::an_item_the_vault_still_holds_is_refused_naming_its_state.
skarbiec.backup.restore-item copy-owner-differs#
put back one item a copy of the vault holds and the live vault lost, as the copy keeps it. Started by skarbiec backup restore <file> --item <id>, POST /v1/operator/backup/restore (item), Desktop: Backups → Restore a backup → Put back one item.
What failed: putting {id} back from the copy {backup}. Why: the copy {backup} is owned by {copy_owner} and the live vault {live} by {live_owner}, so the copy's ciphertext is sealed to keys the live vault does not keep. What the refusal shows: copy owner: {copy_owner}; live owner: {live_owner}; nothing was restored.
Fix: skarbiec migrate --from {backup} --to {live} copies items between vaults of different owners, opening and sealing each again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/backup/item_restore.sh::a_copy_of_another_owners_vault_is_refused_naming_both_owners.
skarbiec.bond bond-exists#
add, edit, list or remove the replication bonds a vault holds, and report each one's state. Started by skarbiec bond add, skarbiec bond edit, skarbiec bond list, skarbiec bond remove, skarbiec bond status, POST /v1/operator/bonds.
What failed: adding the bond {name}. Why: bond {name} is already configured (mode {mode}, role {role}). What the refusal shows: bond {name}: mode {mode}, role {role}.
Fix: change it with skarbiec bond edit {name}, or name a new bond.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/refusals.sh::adding_a_bond_that_is_configured_is_refused_naming_its_mode_and_role.
skarbiec.bond bond-unknown#
add, edit, list or remove the replication bonds a vault holds, and report each one's state. Started by skarbiec bond add, skarbiec bond edit, skarbiec bond list, skarbiec bond remove, skarbiec bond status, POST /v1/operator/bonds.
What failed: {doing} the bond {name}. Why: no bond is named {name}. What the refusal shows: configured bonds: {bonds}.
Fix: name one of the bonds above; skarbiec bond list lists them.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/refusals.sh::editing_or_removing_a_bond_that_is_not_configured_is_refused_naming_the_bonds.
skarbiec.bond bond-field-damaged#
add, edit, list or remove the replication bonds a vault holds, and report each one's state. Started by skarbiec bond add, skarbiec bond edit, skarbiec bond list, skarbiec bond remove, skarbiec bond status, POST /v1/operator/bonds.
What failed: reading the bond {name} as the vault holds it. Why: bond {name} holds {field} as {held}, not {expected}, so it cannot be carried into the edited bond. What the refusal shows: vault file: {path}; the bond was left as recorded.
Fix: write the bond again with skarbiec bond remove {name} and bond add {name}, or restore the vault from a backup.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/refusals.sh::a_bond_the_vault_holds_in_another_shape_is_refused_naming_the_field.
skarbiec.bond bond-section-damaged#
add, edit, list or remove the replication bonds a vault holds, and report each one's state. Started by skarbiec bond add, skarbiec bond edit, skarbiec bond list, skarbiec bond remove, skarbiec bond status, POST /v1/operator/bonds.
What failed: {doing} the vault's bonds. Why: the vault's bond section is not an object of bonds by name: it holds {held}. What the refusal shows: vault file: {path}; no bond was read or written.
Fix: restore the vault from a backup taken before the damage; skarbiec backup check <file> says whether a copy restores.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/refusals.sh::a_bond_section_held_in_another_shape_is_refused_naming_it.
skarbiec.bond bond-pull-unconfigured#
add, edit, list or remove the replication bonds a vault holds, and report each one's state. Started by skarbiec bond add, skarbiec bond edit, skarbiec bond list, skarbiec bond remove, skarbiec bond status, POST /v1/operator/bonds.
What failed: pulling the bond {name}. Why: bond {name} is a pulled serve bond, but its channel records no {field} as text, and a pull needs {needed}. What the refusal shows: channel: {channel}; vault file: {path}; nothing was pulled and replication-failed was not journalled.
Fix: write it with skarbiec bond edit {name} --channel serve:<http://host:port> --token-file <path>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/maintain/refusals.sh::a_pulled_bond_whose_channel_records_no_address_is_refused_naming_it.
skarbiec.enroll enroll-no-key#
register this replica's owner key with a source serve, and request the items it names. Started by skarbiec enroll, POST /v1/operator/bonds/enroll.
What failed: enrolling this replica with {to}. Why: this vault's owner {owner} has no registered key, so there is no identity a source could verify. What the refusal shows: owner: {owner}.
Fix: register the owner's key first: skarbiec owner key import <file>, then enroll again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/refusals.sh::an_enrolment_from_a_vault_whose_owner_has_no_key_is_refused.
skarbiec.enroll enroll-refused#
register this replica's owner key with a source serve, and request the items it names. Started by skarbiec enroll, POST /v1/operator/bonds/enroll.
What failed: enrolling this replica with {to}. Why: the source read the enrolment and refused it: it does not admit this consumer, or this key, to enrol. What the refusal shows: the source answered {status}: {said}; nothing was enrolled.
Fix: the source's owner grants this consumer enrolment (skarbiec grant on the source), then enroll again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/refusals.sh::an_enrolment_the_source_refuses_is_refused_naming_its_answer.
skarbiec.donation donation-unknown#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: {doing} the donation {id}. Why: no donation {id} is pending. What the refusal shows: pending donations: {pending}.
Fix: name one of the donations above; skarbiec donation list lists them.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::a_donation_that_is_not_pending_is_refused_naming_the_pending_ones.
skarbiec.donation donation-inbox-damaged#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: reading the donation inbox {inbox}. Why: it holds no list of donations under donations: that member is {held}. What the refusal shows: inbox: {inbox}; members: {members}; nothing was read or written.
Fix: restore {inbox} from a backup, or remove it to start an empty inbox; the donors can donate again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::an_inbox_that_is_not_a_list_of_donations_is_refused_naming_it.
skarbiec.donation donation-inbox-not-json#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: reading the donation inbox {inbox}. Why: it is not JSON, so none of the donations in it can be read. What the refusal shows: {bytes} bytes, not shown as they hold sealed donations; the JSON reader said: {error}.
Fix: restore {inbox} from a backup, or remove it to start an empty inbox; the donors can donate again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::an_inbox_that_is_not_json_is_refused_naming_where_it_stops.
skarbiec.donation donation-record-incomplete#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: accepting the donation {id}. Why: the inbox's record of donation {id} holds no {field} as text, so the donation cannot be merged. What the refusal shows: inbox: {inbox}; the record holds {members}; the donation stays in the inbox.
Fix: reject it with skarbiec donation reject {id} and ask the donor to donate again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::a_donation_record_missing_a_field_is_refused_naming_it.
skarbiec.donation donation-admission-refused#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: accepting the donation {id} for {item} from {from}. Why: the admission rule refuses it now: {rule}. What the refusal shows: the donation is removed from the inbox.
Fix: ask {from} to donate under a new item id, or write {item} yourself if its value should change.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::a_donation_the_admission_rule_refuses_at_merge_is_refused_and_dropped.
skarbiec.donation donation-unreadable#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: opening the donation {id} for {item}. Why: its sealed value does not open with the keys this host holds. What the refusal shows: the donation stays in the inbox; opening it said: {error}.
Fix: reject it with skarbiec donation reject {id} and ask the donor to donate again; skarbiec keys names the keys this host opens with.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::a_donation_that_does_not_open_is_refused_and_kept.
skarbiec.donation donation-payload-not-json#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: opening the donation {id} for {item}. Why: its sealed value opens, but what it holds is not JSON, so it is no item payload. What the refusal shows: {bytes} bytes, not shown as they are the donated value; the JSON reader said: {error}; the donation stays in the inbox.
Fix: reject it with skarbiec donation reject {id} and ask the donor to donate again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::a_donation_whose_value_is_not_json_is_refused_and_kept.
skarbiec.donation donation-kind-unnamed#
list the pending donations without opening them, merge one after rechecking its admission rule, or drop one. Started by skarbiec donation list, skarbiec donation accept, skarbiec donation reject, POST /v1/operator/donations, POST /v1/operator/donations/accept, POST /v1/operator/donations/reject.
What failed: accepting the donation {id} for {item}. Why: it names no item kind, and this vault holds no item {item} whose kind it could take. What the refusal shows: the donation stays in the inbox.
Fix: reject it with skarbiec donation reject {id} and ask the donor to donate again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donations.sh::a_donation_naming_no_kind_for_a_new_item_is_refused_and_kept.
skarbiec.donate donate-refused#
seal one item's value to a remote vault owner's key and leave it in that vault's donation inbox, where its owner accepts or rejects it. Started by skarbiec donate, POST /v1/operator/items/donate.
What failed: {step} for the donation of {item} to {to}. Why: the remote serve read the donation and refused it: it does not admit {consumer} to donate {item} there. What the refusal shows: the remote serve answered {status}: {said}; {item} is as it was in this vault.
Fix: the remote vault's owner grants {consumer} the donate action on {item} (skarbiec grant on that vault), then donate again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/donate.sh::a_donation_the_remote_serve_refuses_is_refused_naming_its_answer.
skarbiec.browser browser-binary-unplaced#
connect, disconnect, inspect and widen the autofill extension's grant on this machine. Started by skarbiec browser, POST /v1/operator/browser-host, POST /v1/operator/browser-host/install, POST /v1/operator/browser-host/uninstall, POST /v1/operator/browser-host/cover.
What failed: naming the binary the browsers start as the host. Why: the operating system does not tell this process the path of its own binary, which the manifests name when --binary does not. What the refusal shows: the operating system said: {said}; nothing was changed.
Fix: name the skarbiec binary itself with --binary <path>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/refusals.sh::a_running_binary_whose_path_the_system_does_not_tell_is_refused.
skarbiec.browser browser-binary-not-file#
connect, disconnect, inspect and widen the autofill extension's grant on this machine. Started by skarbiec browser, POST /v1/operator/browser-host, POST /v1/operator/browser-host/install, POST /v1/operator/browser-host/uninstall, POST /v1/operator/browser-host/cover.
What failed: naming the binary the browsers start as the host. Why: {binary} is not a regular file, and a browser starts the host by running the program file the manifest names. What the refusal shows: binary: {binary}; nothing was changed.
Fix: name the skarbiec binary itself with --binary, or leave it out to use the running one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/refusals.sh::an_install_naming_a_binary_that_is_not_a_file_is_refused_naming_it.
skarbiec.browser browser-no-logins#
connect, disconnect, inspect and widen the autofill extension's grant on this machine. Started by skarbiec browser, POST /v1/operator/browser-host, POST /v1/operator/browser-host/install, POST /v1/operator/browser-host/uninstall, POST /v1/operator/browser-host/cover.
What failed: granting the browser host its login fields. Why: this vault holds no live login, so the grant would reach nothing. What the refusal shows: nothing was changed.
Fix: add a login (skarbiec login new, or import one), then run browser install again.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/browser/refusals.sh::an_install_on_a_vault_without_logins_is_refused.
skarbiec.browser browser-no-grant#
connect, disconnect, inspect and widen the autofill extension's grant on this machine. Started by skarbiec browser, POST /v1/operator/browser-host, POST /v1/operator/browser-host/install, POST /v1/operator/browser-host/uninstall, POST /v1/operator/browser-host/cover.
What failed: covering the logins added since browser install. Why: the browser host holds no grant here, so there is no grant to widen. What the refusal shows: nothing was changed.
Fix: run skarbiec browser install first.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/browser/refusals.sh::cover_before_install_is_refused_naming_install.
skarbiec.browser browser-platform-unsupported#
connect, disconnect, inspect and widen the autofill extension's grant on this machine. Started by skarbiec browser, POST /v1/operator/browser-host, POST /v1/operator/browser-host/install, POST /v1/operator/browser-host/uninstall, POST /v1/operator/browser-host/cover.
What failed: connecting the autofill extension on this machine. Why: the native messaging manifests are written where macOS browsers read them, and this machine runs {platform}. What the refusal shows: platform: {platform}; nothing was written.
Fix: run skarbiec browser install on a Mac; on this machine use skarbiec login list <site> instead of the extension.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/refusals.sh::connecting_the_extension_off_macos_is_refused_naming_the_platform.
skarbiec.browser browser-extension-manifest-unusable#
connect, disconnect, inspect and widen the autofill extension's grant on this machine. Started by skarbiec browser, POST /v1/operator/browser-host, POST /v1/operator/browser-host/install, POST /v1/operator/browser-host/uninstall, POST /v1/operator/browser-host/cover.
What failed: reading the Firefox extension id from browser/manifest.json built into this binary. Why: the extension manifest this binary was built with {why}, where it is JSON declaring browser_specific_settings.gecko.id. What the refusal shows: nothing was written.
Fix: install a skarbiec build whose browser/manifest.json names the extension's gecko id (the skarbiec release installer at stado://releases/skarbiec/<version>/<platform>/install.sh).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/refusals.sh::a_build_whose_extension_manifest_names_no_firefox_id_is_refused.
skarbiec.browser browser-grant-unanswered#
connect, disconnect, inspect and widen the autofill extension's grant on this machine. Started by skarbiec browser, POST /v1/operator/browser-host, POST /v1/operator/browser-host/install, POST /v1/operator/browser-host/uninstall, POST /v1/operator/browser-host/cover.
What failed: asking grant {verb} for the browser host's grant. Why: grant {verb} answered {found}, where it answers {expected}. What the refusal shows: the manifests and the token file are as the steps before left them.
Fix: run skarbiec grant list to see whether skarbiec-browser-host holds a grant, then run the same skarbiec browser command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/refusals.sh::a_grant_command_answering_nothing_is_refused.
skarbiec.capability capability-status-no-socket#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: asking the capability broker for its status. Why: neither --socket nor SKARBIEC_CAP_SOCKET names the socket it serves, and none is guessed. What the refusal shows: nothing was asked.
Fix: name the socket skarbiec serve --socket serves, with --socket <unix-socket-path> or SKARBIEC_CAP_SOCKET.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_with_no_socket_named_is_refused_naming_both_ways_to_name_one.
skarbiec.capability capability-status-path-empty#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: making {path} absolute to ask the capability broker for its status. Why: the path is empty, and an empty path names no file. What the refusal shows: it names the {what}; nothing was asked.
Fix: name the socket and the state files by absolute paths (--socket, SKARBIEC_VAULT_FILE, SKARBIEC_CAPABILITY_FILE, SKARBIEC_CAPABILITY_ROUTES_FILE).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::an_empty_socket_path_is_refused_naming_why_it_cannot_be_resolved.
skarbiec.capability capability-status-path-no-directory#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: making {path} absolute to ask the capability broker for its status. Why: the path is relative, and this process's working directory cannot be read: it was removed, or a directory on its way may not be searched. What the refusal shows: it names the {what}; the system said: {said}; nothing was asked.
Fix: name the socket and the state files by absolute paths, or run skarbiec from a working directory that exists.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::a_relative_socket_from_a_removed_directory_is_refused_naming_why.
skarbiec.capability capability-status-path-long#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: asking the capability broker at {socket} for its status. Why: the path is {length} bytes, and a Unix socket's address holds a path of at most {most} bytes, so no broker can serve it. What the refusal shows: nothing was asked.
Fix: name the socket the broker serves (skarbiec serve refuses a longer one) with --socket or SKARBIEC_CAP_SOCKET.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_on_a_socket_path_longer_than_a_socket_holds_is_refused.
skarbiec.capability capability-status-absent#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: asking the capability broker at {socket} for its status. Why: nothing is at {socket}, or a directory on its way does not exist, so no broker serves it. What the refusal shows: the system said: {said}; no broker answered.
Fix: start the host's one process with skarbiec serve --socket {socket}, or name the socket it serves.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_on_a_socket_nothing_serves_is_refused_naming_it.
skarbiec.capability capability-status-stale#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: asking the capability broker at {socket} for its status. Why: a file is at {socket}, but no process listens on it: the broker that made it has ended, or it is no socket. What the refusal shows: the system said: {said}; no broker answered.
Fix: start the host's one process with skarbiec serve --socket {socket}, which replaces a socket no process listens on.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_on_a_socket_no_process_listens_on_is_refused_naming_it.
skarbiec.capability capability-status-denied#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: asking the capability broker at {socket} for its status. Why: this account may not connect to {socket}: the socket's mode, or a directory's on its way, does not let it. What the refusal shows: the system said: {said}; no broker was asked.
Fix: ls -ld {socket} {parent} names their owner and mode; ask as the account the broker serves (it makes its socket owner-only).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_on_a_socket_this_account_may_not_reach_is_refused_naming_it.
skarbiec.capability capability-status-unconnected#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: asking the capability broker at {socket} for its status. Why: the system refused the connection with errno {errno}, which is neither an absent socket, one no process listens on, nor one this account may not use. What the refusal shows: the system said: {said}; no broker answered.
Fix: ls -l {socket} says what is there; start the host's one process with skarbiec serve --socket {socket}.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_on_a_socket_the_system_will_not_connect_is_refused.
skarbiec.capability capability-status-connection-lost#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: asking the capability broker at {socket} for its status. Why: the connection failed while {step} (errno {errno}): the broker closed or reset it. What the refusal shows: the system said: {said}; no status was read.
Fix: ask again; stado service status skarbiec says whether the broker is still running.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::a_broker_that_drops_the_status_request_is_refused_naming_the_step.
skarbiec.capability capability-status-incomplete#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading the status the capability broker at {socket} answered. Why: the connection ended after {length} bytes, before a whole status line, so what answers there is no broker of this release, or one that ended mid-answer. What the refusal shows: answer: {answer}.
Fix: run the broker and this client from one release: skarbiec version on both names it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_answered_by_something_that_is_no_broker_is_refused.
skarbiec.capability capability-status-not-text#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading the status the capability broker at {socket} answered. Why: its answer is not UTF-8 text, and every broker of this release answers a JSON line, so what answers there is no broker. What the refusal shows: the system said: {said}.
Fix: lsof {socket} names the process that answers; run the broker and this client from one release (skarbiec version on both names it).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_answered_with_bytes_that_are_not_text_is_refused.
skarbiec.capability capability-status-not-json#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading the status the capability broker at {socket} answered. Why: its status line of {length} bytes is not JSON (column {column}), so what answers there is no broker of this release. What the refusal shows: answer: {answer}; the parser said: {said}.
Fix: run the broker and this client from one release: skarbiec version on both names it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_answered_with_a_line_that_is_not_json_is_refused.
skarbiec.capability capability-status-not-status#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading the status the capability broker at {socket} answered. Why: it answered JSON that is no {version} listening status with a process id: {wrong}. What the refusal shows: answer: {answer}.
Fix: run the broker and this client from one release: skarbiec version on both names it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::status_answered_with_json_of_another_shape_is_refused.
skarbiec.capability capability-status-paths-differ#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: checking the capability broker at {socket} reads what this client reads. Why: the broker uses different state paths: expected {expected}; observed {observed_paths}. What the refusal shows: capabilities issued here would land in a file the broker never reads.
Fix: run this client with the vault, capability and route files the broker was started with, or restart the broker with these.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::a_broker_reading_other_state_paths_is_refused_naming_both.
skarbiec.capability capability-state-damaged#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading the capability state. Why: the capability state holds {held} where the capabilities map belongs. What the refusal shows: capability state: {state}; nothing was stored.
Fix: restore the capability file from a backup taken before the damage; skarbiec doctor names what else is wrong.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::a_damaged_capability_state_is_refused_naming_what_it_holds.
skarbiec.capability capability-refusal-unknown#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading why the broker refused redemption {id}. Why: the audit journal {journal} holds no capability-redemption-denied entry with refusal id {id}. What the refusal shows: journal: {journal}.
Fix: read the refusal id from the broker's answer on the host whose broker gave it, with SKARBIEC_AUDIT_FILE naming that broker's journal; skarbiec audit list --op capability-redemption-denied lists every refusal journalled here.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_redeem_refusals.sh::an_unknown_refusal_id_is_refused_naming_the_journal.
skarbiec.capability capability-challenge-empty#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading the challenge code for {resource} from stdin. Why: stdin held nothing but whitespace, and a challenge code is the digits the provider sent. What the refusal shows: 0 characters read; nothing was stored.
Fix: pipe the digits on stdin: printf '%s' <digits> | skarbiec capability challenge {resource}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::a_challenge_with_no_code_on_stdin_is_refused.
skarbiec.capability capability-challenge-not-digits#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: reading the challenge code for {resource} from stdin. Why: a challenge code is digits only, and character {position} of the {length} read is not a digit. What the refusal shows: {length} characters read, none of them shown; nothing was stored.
Fix: pipe only the digits the provider sent, with no spaces or dashes: printf '%s' <digits> | skarbiec capability challenge {resource}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_command.sh::a_challenge_code_that_is_not_digits_is_refused_naming_where_it_stops.
skarbiec.capability capability-reply-peer-gone#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: answering a redemption on the capability socket. Why: the workload closed or reset the connection before the answer was {step} (errno {errno}). What the refusal shows: the system said: {said}; the workload received no complete answer; the broker names the request on stderr and keeps serving.
Fix: redeem again from the workload; a use the broker spent before the answer failed is not given back, so issue another capability with skarbiec grant capability when none is left.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/access/capabilities/capability_redeem_refusals.sh::a_workload_that_drops_the_connection_before_its_answer_is_named_on_stderr.
skarbiec.capability capability-reply-undelivered#
ask the running capability broker whether it reads what this client reads, store the digits an authorized challenge was sent, and read why it refused a redemption. Started by skarbiec capability status, POST /v1/operator/capability/status, skarbiec capability challenge, skarbiec capability refusal.
What failed: answering a redemption on the capability socket. Why: the system refused the answer while it was {step} with errno {errno}, which is not the workload leaving. What the refusal shows: the system said: {said}; the workload received no complete answer; the broker names the request on stderr and keeps serving.
Fix: redeem again from the workload; a use the broker spent before the answer failed is not given back, so issue another capability with skarbiec grant capability when none is left.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/access/capabilities/capability_redeem_refusals.sh::an_answer_the_system_will_not_write_is_named_on_stderr.
skarbiec.capability.state capability-state-unparsed#
lock the capability state, replay it from its journal, and append to or replace it in owner-only files. Started by other functionalities only.
What failed: reading the capability state {path}. Why: it holds no complete JSON value: the first one stops being JSON at line {line}, column {column}. What the refusal shows: {bytes} bytes; the parser said: {said}; nothing was read or changed.
Fix: restore {path} from a backup; with none, move it aside, and every capability is issued again with skarbiec grant capability.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_state.sh::a_state_holding_no_complete_value_is_refused.
skarbiec.capability.state capability-journal-entry-damaged#
lock the capability state, replay it from its journal, and append to or replace it in owner-only files. Started by other functionalities only.
What failed: replaying the capability state {path}. Why: the value at position {position} is neither a snapshot (capabilities), a capability entry (capability and record) nor a nonce entry (nonce and seen_at). What the refusal shows: value: {value}; nothing was read or changed.
Fix: restore {path} from a backup; with none, remove that line, and a capability it recorded is issued again with skarbiec grant capability.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_state.sh::a_journal_entry_of_another_shape_is_refused_naming_its_position.
skarbiec.capability.state capability-journal-record-unfit#
lock the capability state, replay it from its journal, and append to or replace it in owner-only files. Started by other functionalities only.
What failed: replaying the capability state {path}. Why: the value at position {position} is the entry of capability {id}, and its record is {record}, not the object every entry records. What the refusal shows: nothing was read or changed.
Fix: restore {path} from a backup; with none, remove that line, and the capability is issued again with skarbiec grant capability.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_state.sh::a_capability_entry_whose_record_is_no_object_is_refused_naming_its_position.
skarbiec.capability.state capability-journal-seen-unfit#
lock the capability state, replay it from its journal, and append to or replace it in owner-only files. Started by other functionalities only.
What failed: replaying the capability state {path}. Why: the value at position {position} is the entry of nonce {nonce}, and its seen_at is {seen}, not the number of seconds every nonce entry records. What the refusal shows: nothing was read or changed.
Fix: restore {path} from a backup; with none, remove that line: the nonce counts as unseen again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/capabilities/capability_state.sh::a_nonce_entry_whose_time_is_no_number_is_refused_naming_its_position.
skarbiec.capability.state capability-journal-entry-unheld#
lock the capability state, replay it from its journal, and append to or replace it in owner-only files. Started by other functionalities only.
What failed: recording {what} in the capability journal. Why: the state this process just changed holds no {what}. What the refusal shows: nothing was written.
Fix: run the command again; skarbiec doctor says whether the capability state reads.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/access/capabilities/capability_state.sh::a_change_the_state_does_not_hold_is_not_journalled.
skarbiec.certificates.read certificate-text-absent#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading the certificate of {id}. Why: {id} holds no text in its certificate field. What the refusal shows: its certificate field is {found}.
Fix: put the whole PEM certificate in it: skarbiec field set {id} certificate < cert.pem (openssl x509 -in cert.der -inform der -out cert.pem makes one of a DER file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_certificate_item_without_certificate_text_is_listed_unreadable.
skarbiec.certificates.read certificate-pem-absent#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading the certificate of {id}. Why: the certificate field of {id} holds no -----BEGIN CERTIFICATE----- line, so it is not a PEM certificate. What the refusal shows: {bytes} bytes of text, beginning {start}.
Fix: put the whole PEM certificate in it: skarbiec field set {id} certificate < cert.pem (openssl x509 -in cert.der -inform der -out cert.pem makes one of a DER file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_certificate_without_its_begin_line_is_listed_unreadable.
skarbiec.certificates.read certificate-pem-cut#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading the certificate of {id}. Why: the certificate of {id} has its BEGIN line and no -----END CERTIFICATE----- line after it, so it was cut short. What the refusal shows: {bytes} bytes follow the BEGIN line.
Fix: put the whole PEM certificate in it: skarbiec field set {id} certificate < cert.pem (openssl x509 -in cert.der -inform der -out cert.pem makes one of a DER file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_certificate_without_its_end_line_is_listed_unreadable.
skarbiec.certificates.read certificate-base64-unfit#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading the certificate of {id}. Why: the text between its BEGIN and END lines holds {character} at character {position}, which base64 has not. What the refusal shows: {length} characters between the lines, spaces left out.
Fix: put the whole PEM certificate in it: skarbiec field set {id} certificate < cert.pem (openssl x509 -in cert.der -inform der -out cert.pem makes one of a DER file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_certificate_whose_body_is_not_base64_is_listed_unreadable.
skarbiec.certificates.read certificate-der-short#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading the certificate of {id} (RFC 5280 DER). Why: its DER ends inside the {what}, before {lacks}. What the refusal shows: {bytes} bytes decoded; nothing was read past the {what}.
Fix: put the whole PEM certificate in it: skarbiec field set {id} certificate < cert.pem (openssl x509 -in cert.der -inform der -out cert.pem makes one of a DER file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_certificate_whose_der_ends_early_is_listed_unreadable.
skarbiec.certificates.read certificate-der-length#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading the certificate of {id} (RFC 5280 DER). Why: the {what} states its length in {count} bytes, where DER takes 1 to 4. What the refusal shows: {bytes} bytes decoded.
Fix: put the whole PEM certificate in it: skarbiec field set {id} certificate < cert.pem (openssl x509 -in cert.der -inform der -out cert.pem makes one of a DER file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_certificate_with_a_der_length_of_no_bytes_is_listed_unreadable.
skarbiec.certificates.read certificate-der-tag#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading the certificate of {id} (RFC 5280 DER). Why: the {what} has DER tag {found}, not the {tag} RFC 5280 puts there, so it is no X.509 certificate. What the refusal shows: {bytes} bytes decoded.
Fix: put the whole PEM certificate in it: skarbiec field set {id} certificate < cert.pem (openssl x509 -in cert.der -inform der -out cert.pem makes one of a DER file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_pem_block_holding_no_certificate_is_listed_unreadable.
skarbiec.certificates.read certificate-time-unfit#
read the PEM text of one certificate item and the subject, issuer and notAfter of its RFC 5280 DER, verifying nothing. Started by other functionalities only.
What failed: reading when the certificate of {id} ends. Why: its notAfter time {text} is neither a UTCTime (YYMMDDHHMMSSZ) nor a GeneralizedTime (YYYYMMDDHHMMSSZ) in UTC, as RFC 5280 requires. What the refusal shows: DER tag {tag}, {length} bytes.
Fix: issue the certificate again with an RFC 5280 notAfter, then put it in: skarbiec field set {id} certificate < cert.pem.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/review/certificates.sh::a_certificate_whose_end_is_no_rfc_5280_time_is_listed_unreadable.
skarbiec.errors form-unknown#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: reading what skarbiec errors is asked. Why: errors {given} is not one of its forms. What the refusal shows: arguments: {given}.
Fix: run skarbiec errors list, skarbiec errors show <functionality> or skarbiec errors check.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::an_unknown_errors_form_is_refused_with_its_usage.
skarbiec.errors functionality-unknown#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: showing the failure catalogue of {id}. Why: no functionality of this skarbiec declares a catalogue under {id}. What the refusal shows: declared functionalities: {declared}.
Fix: name one of the declared functionalities; skarbiec errors list prints them.
Code not_found, exit status 2, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::an_undeclared_functionality_is_refused_listing_the_declared_ones.
skarbiec.errors baseline-unreadable#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: reading the uncatalogued-command baseline {path}. Why: the file could not be read. What the refusal shows: --baseline {path}; the file system answered: {error}.
Fix: name the baseline file the repository holds, ci/errors-baseline.json.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::a_baseline_that_cannot_be_read_is_refused_naming_it.
skarbiec.errors baseline-malformed#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: reading the uncatalogued-command baseline {path}. Why: it is not a JSON list of command names. What the refusal shows: --baseline {path}; the JSON reader said: {error}.
Fix: write it as a JSON list of the command names still uncatalogued, e.g. ["status", "doctor"]; skarbiec errors check prints them as uncatalogued_commands.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::a_baseline_that_is_not_a_list_is_refused.
skarbiec.errors untested-unreadable#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: reading the untested-cause list {path}. Why: the file could not be read. What the refusal shows: the file system answered: {error}; --repository names the checkout whose list it is.
Fix: let this account read {path}, or name the checkout root with --repository.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::an_untested_list_that_cannot_be_read_is_refused_naming_it.
skarbiec.errors untested-malformed#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: reading the untested-cause list {path}. Why: it is not a JSON object from a declared test to why it cannot be provoked locally. What the refusal shows: the JSON reader said: {error}; --repository names the checkout whose list it is.
Fix: write {path} as one JSON object whose keys are declared tests (tests/<area>/<file>::<test>) and whose values say why each cannot be provoked locally.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::an_untested_list_that_is_not_an_object_is_refused.
skarbiec.errors findings#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: checking the failure catalogue. Why: {count} finding(s): a malformed declaration, a declared test the repository neither holds nor lists as untested, an untested-list entry the catalogue does not excuse, a command no functionality names, or a baseline entry no longer needed. What the refusal shows: the findings, each listed in the answer printed above.
Fix: fix each finding as it says: correct the declaration in src/failures, write the declared test or list it in tests/untested-causes.json with why, declare the command's failures, or remove it from the baseline.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::a_baseline_allowing_a_catalogued_command_is_a_finding.
skarbiec.errors errors-declaration-unreadable#
list, show and check every declared way a Skarbiec functionality fails. Started by skarbiec errors list, skarbiec errors show, skarbiec errors check, POST /v1/operator/errors, Desktop: Settings → Errors.
What failed: listing how {id} fails. Why: wisent-errors rendered the declaration of {id} as text that does not read as JSON, which it always writes. What the refusal shows: the JSON reader said: {error}.
Fix: install a skarbiec build whose wisent-errors renders declarations as JSON (the skarbiec release installer at stado://releases/skarbiec/<version>/<platform>/install.sh).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/errors/catalogue.sh::a_declaration_rendered_as_no_json_is_refused_naming_it.
skarbiec.clock clock-before-epoch#
read this host's clock as whole seconds since the Unix epoch, the unit every expiry and signature time is stated in. Started by other functionalities only.
What failed: reading this host's clock in seconds since the Unix epoch. Why: the system clock reads {behind} second(s) before 1970-01-01T00:00:00Z, and no expiry or signature time is computed from a time before the epoch. What the refusal shows: nothing was read, issued or written.
Fix: set this host's clock to the present time (date -u says what it reads) and run the command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/audit/commands.sh::a_clock_before_the_unix_epoch_is_refused.
skarbiec.command command-unknown#
find the command the first word names, before anything is read or written. Started by skarbiec <command>, skarbiec help <command>.
What failed: reading which skarbiec command to run. Why: unknown command: {command}; skarbiec has no command of that name. What the refusal shows: arguments: {arguments}; nothing was read or written.
Fix: run one of skarbiec's commands: {commands}; `skarbiec <command> --help` prints one's usage.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/completions/help.sh::an_unknown_command_is_refused_naming_the_inventory.
skarbiec.command command-group-spelled#
find the command the first word names, before anything is read or written. Started by skarbiec <command>, skarbiec help <command>.
What failed: reading which skarbiec command to run. Why: unknown command: {command}; {group} is a group, so this is `skarbiec {group} {verb}`. What the refusal shows: arguments: {arguments}; nothing was read or written.
Fix: run skarbiec {group} {verb}; `skarbiec {group} help` lists its verbs.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/completions/help.sh::a_spelled_group_verb_is_refused_naming_its_group_form.
skarbiec.command command-no-form#
find the command the first word names, before anything is read or written. Started by skarbiec <command>, skarbiec help <command>.
What failed: reading what skarbiec {command} does. Why: {command} {words} is not a form of {command}. What the refusal shows: arguments: {arguments}; nothing was read or written.
Fix: run it as {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/cli/completions/help.sh::words_that_are_no_form_of_a_command_are_refused_with_its_usage.
skarbiec.ci.set form-unknown#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: reading what skarbiec ci is asked. Why: ci {given} is not one of its forms. What the refusal shows: arguments: {given}.
Fix: skarbiec ci set|keep github <owner/repo> --env-from <file> [--environment <name>] [--yes] | ci set|keep kubernetes <namespace>/<name> --env-from <file> [--context <name>] [--yes] | ci set|keep vercel <project> --env-from <file> [--environment <name>[,<name>...]] [--team <slug>] [--yes] | ci set|keep cloudflare <worker> --env-from <file> [--environment <name>] [--yes] | ci kept | ci forget <target> <place>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/ci/set.sh::an_unknown_ci_form_is_refused_with_its_usage.
skarbiec.ci.set bindings-missing#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: reading which values skarbiec ci set puts on {target} {place}. Why: no --env-from bindings file was given. What the refusal shows: flags: {flags}.
Fix: name the NAME=<id>:<field> file with --env-from <file>; skarbiec bindings check <file> says whether each line reads.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/ci/set.sh::ci_set_without_bindings_is_refused.
skarbiec.ci.set target-unknown#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: setting secrets on {target} {place}. Why: ci sets GitHub Actions, Kubernetes, Vercel or Cloudflare Workers secrets, and {target} is none of them. What the refusal shows: target: {target}.
Fix: name github <owner/repo>, kubernetes <namespace>/<name>, vercel <project> or cloudflare <worker>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/ci/set.sh::ci_set_on_an_unknown_target_is_refused.
skarbiec.ci.set place-malformed#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: setting secrets on {target} {place}. Why: {place} is not {shape} as {target} names it. What the refusal shows: place: {place}.
Fix: name it as {shape}, each part letters, digits, '-', '_' or '.'.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/ci/set.sh::ci_set_on_a_malformed_place_is_refused.
skarbiec.ci.set scope-empty#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: setting secrets on {target} {place}. Why: {flag} was given with no name. What the refusal shows: {flag}: empty.
Fix: name the {what} with {flag} <name>, or leave {flag} out.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/ci/set.sh::ci_set_with_an_empty_scope_is_refused.
skarbiec.ci.set ci-field-not-text#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: reading the value of the secret {secret} from {item}#{field}. Why: {item}'s field {field} is {found}, not the text a secret is set to. What the refusal shows: fields {item} holds: {fields}; no secret was set.
Fix: bind {secret} to a text field of {item} in the bindings file, or set the field with skarbiec field set {item} {field}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ci/kept.sh::a_binding_naming_a_field_the_item_does_not_hold_is_refused_naming_its_fields.
skarbiec.ci.set ci-kept-not-json#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: reading the kept CI targets in {path}. Why: {path} is not a JSON list of kept targets: the reader stopped at line {line}, column {column}. What the refusal shows: the parser said: {said}; nothing was set or kept.
Fix: restore {path} from a backup, or move it aside and keep each target again with skarbiec ci keep <target> <place> --env-from <file> --yes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ci/kept.sh::a_kept_list_that_is_not_json_is_refused_naming_where.
skarbiec.ci.set ci-kept-entry-damaged#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: setting the kept CI target {position} of {path} again. Why: its {member} is {found}, where every kept target records it as text. What the refusal shows: target {target} {place}; nothing was set for it.
Fix: skarbiec ci forget <target> <place> drops it, and skarbiec ci keep <target> <place> --env-from <file> --yes keeps it again whole.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ci/kept.sh::a_kept_target_without_its_bindings_is_named_failed_by_its_position.
skarbiec.ci.set ci-kept-set-refused#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: setting the secrets of {target} {place}. Why: {count} of its secrets were refused ({secrets}), so {target} {place} {kept}. What the refusal shows: each refusal: {refused}.
Fix: repair what each refusal names, then run skarbiec ci keep {target} {place} --env-from <file> --yes again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/ci/kept.sh::a_target_whose_secrets_are_refused_is_not_kept.
skarbiec.ci.set ci-kept-unknown#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: forgetting the kept CI target {target} {place}. Why: {target} {place} is not kept on this host. What the refusal shows: kept in {path}: {kept}.
Fix: name one skarbiec ci kept lists.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/ci/kept.sh::forgetting_a_target_not_kept_is_refused_naming_the_kept_ones.
skarbiec.ci.set ci-directory-unread#
set GitHub Actions secrets, one Kubernetes Secret, Vercel environment variables or Cloudflare Workers secrets from the values a bindings file names. Started by skarbiec ci set, skarbiec ci keep, POST /v1/operator/ci-secrets, POST /v1/operator/ci-secrets/keep, Desktop: CI → Actions secrets → Set them, Desktop: CI → Actions secrets → Set and keep them.
What failed: naming the bindings file {given} to keep for {target} {place}. Why: the directory this command runs in could not be read, so the relative path {given} names no file to keep. What the refusal shows: the system said: {said}; nothing was set or kept.
Fix: pass --env-from as an absolute path, or run the command from a directory that exists.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ci/kept.sh::keeping_from_a_removed_directory_is_refused_naming_the_path.
skarbiec.copy copy-target-exists#
make a new item from an existing one with its kind, tags and recipients, leaving out the fields named. Started by skarbiec copy, POST /v1/operator/items/copy, Desktop: Items → a selected item → Copy to a new item.
What failed: copying {from} to {to}. Why: {to} is already an item of this vault ({state}), and copy creates an item, never replaces one. What the refusal shows: item {to}: {state}.
Fix: name a new id; skarbiec list --trashed lists the ids the trash still holds.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/copies/copy.sh::a_copy_onto_an_existing_item_is_refused_and_both_are_kept.
skarbiec.copy copy-would-duplicate#
make a new item from an existing one with its kind, tags and recipients, leaving out the fields named. Started by skarbiec copy, POST /v1/operator/items/copy, Desktop: Items → a selected item → Copy to a new item.
What failed: copying {from} to {to}. Why: a copy with every field of {from} would hold exactly its value, and the vault refuses an exact duplicate. What the refusal shows: fields of {from}: {fields}.
Fix: leave out what the copy will hold differently: skarbiec copy {from} {to} --without <field,...>, then set the copy's own value.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/copies/copy.sh::a_copy_with_every_field_is_refused_naming_without.
skarbiec.copy copy-field-missing#
make a new item from an existing one with its kind, tags and recipients, leaving out the fields named. Started by skarbiec copy, POST /v1/operator/items/copy, Desktop: Items → a selected item → Copy to a new item.
What failed: leaving {field} out of the copy of {from}. Why: {from} has no field {field}. What the refusal shows: fields of {from}: {fields}.
Fix: name in --without only fields {from} holds.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/items/copies/copy.sh::a_field_the_item_does_not_hold_is_refused_naming_the_ones_it_does.
skarbiec.credential.command command-missing#
read which credential command was asked for and whether it may run here. Started by skarbiec credential.
What failed: reading which credential command to run. Why: skarbiec credential was given no command. What the refusal shows: arguments: none.
Fix: name one: skarbiec credential help lists them.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/nouns.sh::credential_alone_is_refused_naming_the_help.
skarbiec.credential.command noun-without-verb#
read which credential command was asked for and whether it may run here. Started by skarbiec credential.
What failed: reading which credential command to run. Why: credential {noun} needs a verb. What the refusal shows: arguments: {noun}.
Fix: name the verb, e.g. credential directory seal, credential quarantine resolve or credential endpoint declare; skarbiec credential help lists them.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/nouns.sh::a_noun_alone_is_refused_naming_the_missing_verb.
skarbiec.credential.command local-only#
read which credential command was asked for and whether it may run here. Started by skarbiec credential.
What failed: running credential {command} against the canonical Skarbiec. Why: credential {command} runs against the vault file it owns, never one hop away. What the refusal shows: flags given: no --local.
Fix: rerun it with --local on the canonical Skarbiec host.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/nouns.sh::directory_seal_outside_local_is_refused_naming_the_command.
skarbiec.credential.command command-unknown#
read which credential command was asked for and whether it may run here. Started by skarbiec credential.
What failed: reading which credential command to run. Why: {command} is not a credential command. What the refusal shows: command: {command}.
Fix: run one skarbiec credential help lists.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/nouns.sh::the_retired_spelling_is_an_unknown_credential_command.
skarbiec.credential.role role-missing#
name the credential a lifecycle command acts on by the role it plays. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, skarbiec credential resume, skarbiec credential status, skarbiec credential directory seal, skarbiec credential directory reseal, skarbiec credential quarantine resolve, POST /v1/credential/operations, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status, Resume operation and Rotate.
What failed: naming the credential credential {command} acts on. Why: no argument names it. What the refusal shows: arguments: none; usage: {usage}.
Fix: run skarbiec credential {command} role:<role>, naming the role the credential plays.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/role_addressing.sh::a_credential_command_naming_nothing_is_refused_with_its_usage.
skarbiec.credential.role item-named#
name the credential a lifecycle command acts on by the role it plays. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, skarbiec credential resume, skarbiec credential status, skarbiec credential directory seal, skarbiec credential directory reseal, skarbiec credential quarantine resolve, POST /v1/credential/operations, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status, Resume operation and Rotate.
What failed: naming the credential credential {command} acts on. Why: {named} is an item id, and a credential is named by the role it plays, never by an item's name. What the refusal shows: argument: {named}.
Fix: tag the item with `skarbiec retag --add stado:role:<role> {named}` and run skarbiec credential {command} role:<role>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/role_addressing.sh::an_item_id_is_refused_naming_the_retag.
skarbiec.credential.role role-malformed#
name the credential a lifecycle command acts on by the role it plays. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, skarbiec credential resume, skarbiec credential status, skarbiec credential directory seal, skarbiec credential directory reseal, skarbiec credential quarantine resolve, POST /v1/credential/operations, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status, Resume operation and Rotate.
What failed: naming the credential credential {command} acts on. Why: role:{role} is not one role name: a role is non-empty and holds only ASCII letters, digits, '.', '_' and '-'. What the refusal shows: argument: role:{role}.
Fix: name the role exactly as the item's stado:role:<role> tag carries it.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/role_addressing.sh::a_role_with_a_character_outside_the_role_alphabet_is_refused.
skarbiec.credential.role several-holders#
name the credential a lifecycle command acts on by the role it plays. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, skarbiec credential resume, skarbiec credential status, skarbiec credential directory seal, skarbiec credential directory reseal, skarbiec credential quarantine resolve, POST /v1/credential/operations, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status, Resume operation and Rotate.
What failed: finding the item that plays role {role}. Why: {count} live items carry stado:role:{role}, and exactly one item may play a role. What the refusal shows: items carrying stado:role:{role}: {items}.
Fix: keep one: run skarbiec retag --remove stado:role:{role} <item> for each of the others.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/role_addressing.sh::a_role_two_items_play_is_refused_naming_the_count.
skarbiec.credential.role no-holder#
name the credential a lifecycle command acts on by the role it plays. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, skarbiec credential resume, skarbiec credential status, skarbiec credential directory seal, skarbiec credential directory reseal, skarbiec credential quarantine resolve, POST /v1/credential/operations, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status, Resume operation and Rotate.
What failed: finding the item that plays role {role} for credential {command}. Why: no live item carries stado:role:{role}, and only an acquisition may start before its item exists. What the refusal shows: items carrying stado:role:{role}: none.
Fix: tag the item holding this credential with `skarbiec retag --add stado:role:{role} <item>`, or create it with `skarbiec credential acquire role:{role}`.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/role_addressing.sh::a_role_no_item_plays_is_refused_for_a_rotation.
skarbiec.credential.submission unknown-flag#
read and check a credential lifecycle request before it is recorded. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, POST /v1/credential/operations, POST /v1/operator/credential, Desktop: Lifecycle → Rotate, skarbiec rotation run.
What failed: reading the flags of credential {command}. Why: --{flag} is not a flag credential {command} takes. What the refusal shows: flags given: {given}; usage: {usage}.
Fix: drop --{flag}; the usage line lists every flag credential {command} takes.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::an_unknown_flag_is_refused_naming_it.
skarbiec.credential.submission adopt-without-password-stdin#
read and check a credential lifecycle request before it is recorded. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, POST /v1/credential/operations, POST /v1/operator/credential, Desktop: Lifecycle → Rotate, skarbiec rotation run.
What failed: reading the current password credential adopt brings under management. Why: --password-stdin is absent, and the password is read from standard input only, never from an argument. What the refusal shows: flags given: {given}.
Fix: pipe the current password in and pass --password-stdin: printf '%s' '<password>' | skarbiec credential adopt role:<role> --password-stdin ….
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::adopt_without_password_stdin_is_refused.
skarbiec.credential.submission password-stdin-outside-adopt#
read and check a credential lifecycle request before it is recorded. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, POST /v1/credential/operations, POST /v1/operator/credential, Desktop: Lifecycle → Rotate, skarbiec rotation run.
What failed: reading the flags of credential {command}. Why: --password-stdin carries an operator-supplied password, which only credential adopt takes. What the refusal shows: command: credential {command}.
Fix: drop --password-stdin, or run credential adopt to bring a password you hold under management.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::password_stdin_outside_adopt_is_refused.
skarbiec.credential.submission flag-missing#
read and check a credential lifecycle request before it is recorded. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, POST /v1/credential/operations, POST /v1/operator/credential, Desktop: Lifecycle → Rotate, skarbiec rotation run.
What failed: reading the flags of credential {command}. Why: --{flag} is required and was not given. What the refusal shows: flags given: {given}; usage: {usage}.
Fix: pass --{flag} <{flag}>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::a_lifecycle_command_without_provider_is_refused_naming_it.
skarbiec.credential.submission name-malformed#
read and check a credential lifecycle request before it is recorded. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, POST /v1/credential/operations, POST /v1/operator/credential, Desktop: Lifecycle → Rotate, skarbiec rotation run.
What failed: reading --{flag} of credential {command}. Why: {value} is not one name: a {flag} is non-empty and holds only ASCII letters, digits, '.', '_' and '-'. What the refusal shows: --{flag} {value}.
Fix: pass the {flag} exactly as it is declared, e.g. the provider slug `skarbiec credential help` names.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::a_provider_outside_the_name_alphabet_is_refused.
skarbiec.credential.submission adopt-dry-run#
read and check a credential lifecycle request before it is recorded. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, POST /v1/credential/operations, POST /v1/operator/credential, Desktop: Lifecycle → Rotate, skarbiec rotation run.
What failed: planning credential adopt without running it. Why: adopt stages the password you supply and asks the provider to accept it, so there is nothing to plan without doing it. What the refusal shows: flags given: --dry-run.
Fix: drop --dry-run; credential status role:<role> --local shows what an adoption would act on.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::adopt_with_dry_run_is_refused.
skarbiec.credential.submission holder-id-unsendable#
read and check a credential lifecycle request before it is recorded. Started by skarbiec credential acquire, skarbiec credential adopt, skarbiec credential rotate, skarbiec credential reset, skarbiec credential verify, skarbiec credential remove, POST /v1/credential/operations, POST /v1/operator/credential, Desktop: Lifecycle → Rotate, skarbiec rotation run.
What failed: sending the item that plays role {role} to Weles for credential {command}. Why: its id {item} is not one the credential-operation wire carries: ASCII letters, digits, '.', '_' and '-', and at least one of them. What the refusal shows: item playing role {role}: {item}.
Fix: rename the item with `skarbiec rename {item} <new-id>` to an id of letters, digits, '.', '_' and '-'; its role tag moves with it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::a_role_played_by_an_item_whose_id_the_wire_cannot_carry_is_refused.
skarbiec.credential.item-role item-plays-no-role#
read the one role an item plays, where an item is what was named. Started by skarbiec rotation set, POST /v1/operator/rotation/set, PUT /v1/items (mode stage, by item id).
What failed: finding the role {item} plays. Why: {item} carries no stado:role:<role> tag, and a credential is operated on by the role it plays. What the refusal shows: roles {item} plays: none.
Fix: give it one with `skarbiec retag --add stado:role:<role> {item}`.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/role_addressing.sh::a_rotation_policy_for_an_item_playing_no_role_is_refused_naming_the_retag.
skarbiec.credential.item-role item-plays-several-roles#
read the one role an item plays, where an item is what was named. Started by skarbiec rotation set, POST /v1/operator/rotation/set, PUT /v1/items (mode stage, by item id).
What failed: finding the role {item} plays. Why: {item} carries {count} stado:role: tags, and a credential is operated on by exactly one. What the refusal shows: roles {item} plays: {roles}.
Fix: keep one: run `skarbiec retag --remove stado:role:<role> {item}` for each of the others.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/role_addressing.sh::a_rotation_policy_for_an_item_playing_two_roles_is_refused_naming_them.
skarbiec.credential.token-file token-in-argv#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer {command} presents. Why: --token puts the bearer in argv, where every process on this host and the shell history can read it. What the refusal shows: flags given: --token.
Fix: write the bearer to an owner-only file (chmod 600) and pass --token-file <absolute path>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::a_bearer_in_argv_is_refused.
skarbiec.credential.token-file token-file-missing#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer {command} presents. Why: neither --token-file nor {env} names the owner-only file holding it. What the refusal shows: flags given: no --token-file; {env}: unset.
Fix: pass --token-file <absolute path to an owner-only file holding the bearer>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::a_command_without_its_token_file_is_refused_naming_the_flag.
skarbiec.credential.token-file token-file-relative#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer from {path}. Why: the path is relative, so which file it names depends on the directory the command runs in. What the refusal shows: token file: {path}.
Fix: pass the absolute path, e.g. --token-file "$PWD/{path}".
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::a_relative_token_file_is_refused.
skarbiec.credential.token-file token-file-absent#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer from {path}. Why: nothing is at {path}, so no bearer can be read from it. What the refusal shows: token file: {path}; the operating system said: {error}.
Fix: write the bearer to {path} (chmod 600), or name the file that holds it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::an_absent_token_file_is_refused_with_the_operating_systems_cause.
skarbiec.credential.token-file token-file-unreadable#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer from {path}. Why: {path} is there but this account cannot {doing} it, so no bearer can be read from it. What the refusal shows: token file: {path}; {doing}: {error}.
Fix: make {path} readable by its owner, this account (chmod 600 {path}), or name a file this account can read.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/admission_in_process.mjs::a_bearer_file_this_account_cannot_read_is_recorded_naming_it.
skarbiec.credential.token-file token-file-not-owner-only#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer from {path}. Why: {path} is {found}, where a token file must be an owner-only regular file: no symbolic link, owned by this account, and neither group nor others may read or write it. What the refusal shows: {kind}, owner uid {owner} (this process runs as {uid}), mode {mode}.
Fix: chmod 600 {path} as its owner, or write the bearer to a new owner-only regular file.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/owner_only_files.sh::a_token_file_others_may_read_is_refused_by_name.
skarbiec.credential.token-file token-file-not-one-token#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer from {path}. Why: the file holds nothing but whitespace, so it is not exactly one bearer token. What the refusal shows: {bytes} byte(s) in the file, none of them a bearer.
Fix: write exactly the bearer, on one line, to {path}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::an_empty_token_file_is_refused.
skarbiec.credential.token-file token-file-control-character#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: reading the bearer from {path}. Why: the bearer in the file holds a control character ({character}) at byte {at}, so it is not exactly one bearer token. What the refusal shows: {bytes} byte(s) after trimming surrounding whitespace.
Fix: write exactly the bearer, on one line and with no control character, to {path}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::a_token_file_holding_a_control_character_is_refused_naming_it.
skarbiec.credential.token-file caller-missing#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: naming the consumer that calls the canonical Skarbiec. Why: --as is required: the canonical Skarbiec checks the bearer against the consumer it was granted to. What the refusal shows: flags given: no --as.
Fix: pass --as <consumer>, the consumer the bearer in --token-file was granted to.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::a_remote_command_without_as_is_refused.
skarbiec.credential.token-file caller-malformed#
read the bearer a command presents from an owner-only file, and the consumer it is presented as. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential resume --as, skarbiec credential status --as, skarbiec credential directory reseal, skarbiec credential quarantine resolve.
What failed: naming the consumer that calls the canonical Skarbiec. Why: {value} is not one consumer name: ASCII letters, digits, '.', '_' and '-'. What the refusal shows: --as {value}.
Fix: pass the consumer exactly as it was granted, e.g. --as weles-writer.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/token_file.sh::a_malformed_consumer_is_refused.
skarbiec.credential.adopt adopt-password-unread#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: reading the password credential adopt brings under management. Why: standard input could not be read to its end, so the password is not known whole. What the refusal shows: the system said: {said}; nothing was staged or sent.
Fix: pipe the password from a file or a command that reads to its end: skarbiec credential adopt role:<role> --password-stdin … < password.txt.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::adopt_whose_password_input_is_a_directory_is_refused.
skarbiec.credential.adopt adopt-password-not-text#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: reading the password credential adopt brings under management. Why: the password stops being UTF-8 text at byte {offset}. What the refusal shows: standard input: {length} bytes; nothing was staged or sent.
Fix: pipe the password as UTF-8 text on standard input.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::adopt_whose_password_is_not_text_is_refused.
skarbiec.credential.adopt adopt-password-not-one-line#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: reading the password credential adopt brings under management. Why: the password {why}, and a password is one non-empty line with no control character. What the refusal shows: {length} character(s) after the trailing line breaks were taken off; nothing was staged or sent.
Fix: pipe exactly the password, on one line: printf '%s' '<password>' | skarbiec credential adopt role:<role> --password-stdin ….
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::adopt_with_an_empty_password_is_refused.
skarbiec.credential.adopt adopt-shape-unknown#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: resuming the adopt request {request}. Why: the request records the staging shape {shape}, where an adopt is staged (into an existing item) or created (a new item). What the refusal shows: request record: {record}; nothing was staged or sent.
Fix: skarbiec credential status role:{role} shows the request; skarbiec history operation:role/{role} names who wrote the record, which only a Skarbiec adopt writes with a shape.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::a_resumed_adopt_whose_shape_is_unknown_is_refused_naming_it.
skarbiec.credential.adopt adopt-field-kind-unknown#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: creating the item credential adopt stages {field} into. Why: adopt creates a login for a password and an api-key item for an api_key, and has no kind for the field {field}. What the refusal shows: nothing was staged or sent.
Fix: adopt the password or api_key field, or create the item first and adopt into it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::adopt_of_a_field_no_kind_holds_is_refused_naming_it.
skarbiec.credential.adopt adopt-account-unknown#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: creating the login {credential} credential adopt stages its password into. Why: a login names its account, and neither --account nor the sealed directory contract (account_upn) gives one. What the refusal shows: nothing was staged or sent.
Fix: pass --account <address>, or seal the directory contract with skarbiec credential directory seal role:<role> … --account-upn <address>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::adopt_creating_a_login_without_its_account_is_refused.
skarbiec.credential.adopt adopt-item-foreign#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: {doing} {credential} for the adopt request {request}. Why: {credential} exists and was not created by this adopt request: its lifecycle records the request {recorded}. What the refusal shows: {credential} is as it was; nothing was staged, sent or trashed.
Fix: resolve {credential} by hand: skarbiec history {credential} shows its revisions, and skarbiec rename moves it aside.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::adopt_into_an_item_another_request_created_is_refused_naming_it.
skarbiec.credential.adopt adopt-item-gone#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: {doing} {credential} for the adopt request {request}. Why: {credential} is no live item now, though the adopt found it under the credential operation lock. What the refusal shows: nothing was sent to Weles.
Fix: skarbiec list --all names whether it was trashed; run the adopt again once it is live.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::adopt_whose_item_went_away_is_refused.
skarbiec.credential.adopt adopt-item-changed#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: trashing {credential}, which the failed adopt request {request} created. Why: {credential} has been written since the adopt created it, so trashing it would drop a change the adopt did not make. What the refusal shows: {credential}: revision {revision}, {history} earlier revision(s), current revision written by operation {operation}; it is as it was and nothing was trashed.
Fix: resolve {credential} by hand: skarbiec history {credential} shows who wrote each revision, and skarbiec delete {credential} moves it to the trash once you are sure.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::a_rollback_of_an_adopted_item_written_since_is_refused_naming_it.
skarbiec.credential.adopt adopt-staged-incomplete#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: reading {field} from the staged adopt candidate of {credential}. Why: the staged revision of {credential} records no {what}, so the adopt candidate cannot be read. What the refusal shows: vault file: {path}; the staged revision holds {members}; nothing was read or written.
Fix: restore the vault from a backup taken before the damage (skarbiec backup check <file> says whether a copy restores), then adopt again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::a_staged_adopt_candidate_missing_its_envelope_is_refused_naming_it.
skarbiec.credential.adopt adopt-staged-not-json#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: reading {field} from the staged adopt candidate of {credential}. Why: the staged revision of {credential} opens, but what it holds is not a JSON item payload. What the refusal shows: {bytes} bytes, not shown as they are the staged password; the JSON reader said: {error}.
Fix: restore the vault from a backup taken before the damage (skarbiec backup check <file> says whether a copy restores), then adopt again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::a_staged_adopt_candidate_that_is_not_json_is_refused.
skarbiec.credential.adopt adopt-record-request-id-absent#
read the operator's password from standard input and stage it into the item playing the role, or create that item, until the provider confirms it. Started by other functionalities only.
What failed: checking whether an adopt of {credential} is in flight for {consumer}. Why: {record} records an adopt in flight without its request_id, so whose candidate is staged cannot be told. What the refusal shows: record: {record}; it holds {members}; the candidate stays hidden.
Fix: settle the adopt with skarbiec credential status role:<role>, or resolve it with skarbiec credential quarantine resolve.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/submission_refusals.sh::an_adopt_record_without_its_request_id_is_refused_naming_it.
skarbiec.credential-enrol credential-enrol-no-security-page#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: enrolling an authenticator for role {role}. Why: {holder} names no page where the account shows its two-step settings, so no site is known to enrol the authenticator at. What the refusal shows: {holder}: context.security_page absent.
Fix: skarbiec login factor page {login} --set <https address of the account's two-step settings>, then run the enrolment again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::an_account_naming_no_security_page_is_refused_naming_the_fix.
skarbiec.credential-enrol credential-enrol-role-unheld#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: enrolling an authenticator for role {role}. Why: no live item plays role {role}, so there is no account to enrol. What the refusal shows: items tagged stado:role:{role}: none.
Fix: skarbiec login identity link --account <address> --role {role} --yes makes the account's identity with that role.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::a_role_no_item_plays_is_refused_naming_the_role.
skarbiec.credential-enrol credential-enrol-holder-kind#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: enrolling an authenticator for role {role}. Why: role {role} is played by {holder}, a {kind}, and an authenticator is enrolled for an identity or a login. What the refusal shows: {holder} is a {kind}.
Fix: give the role to the account's identity: skarbiec login identity list --accounts names it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::a_role_played_by_another_kind_is_refused_naming_it.
skarbiec.credential-enrol credential-enrol-no-login#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: enrolling an authenticator for role {role}. Why: role {role} is played by identity {holder}, and no live login signs in as it, so the provider has no password to sign in with before it enrols. What the refusal shows: logins whose context.identity is {holder}: none.
Fix: skarbiec login identity set <login> role:{role} names the identity on the account's login, or skarbiec login identity link --account <address> --role {role} --yes on every login of the account.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::an_identity_no_login_signs_in_as_is_refused.
skarbiec.credential-enrol credential-enrol-seed-working#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: enrolling an authenticator for role {role}. Why: {holder} keeps a working seed the account {verification}, and an account has one authenticator, so a new enrolment would make that seed stop answering. What the refusal shows: {holder}: seed present, verification {verification}.
Fix: keep the seed; skarbiec totp seed {holder} says how the account answered it. Only once it is rejected, take it out with skarbiec field unset {holder} totp_secret and enrol again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::an_account_keeping_a_working_seed_is_refused.
skarbiec.credential-enrol credential-enrol-none-started#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: {doing} for role {role}. Why: no enrolment was started for {holder}, so there is no run to answer or read. What the refusal shows: enrolments the audit journal records started for {holder}: none.
Fix: start it with skarbiec credential enrol role:{role}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::answering_without_an_enrolment_is_refused.
skarbiec.credential-enrol credential-enrol-weles-refused#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: {doing} for role {role}. Why: Weles answered {status}. What the refusal shows: its message: {message}; code {code}, phase {phase}.
Fix: the message names Weles's own fix; weles errors show credentials lists every cause of its admission.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::a_refusal_of_weles_is_named_with_its_code.
skarbiec.credential-enrol credential-enrol-verify-no-seed#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: verifying the authenticator seed of role {role}. Why: {holder} keeps no seed that computes a code, so a sign-in has nothing to answer the provider with. What the refusal shows: {holder}: seed not present.
Fix: enrol one with skarbiec credential enrol role:{role}, or store the one the provider shows with skarbiec totp set {holder}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::verifying_an_account_without_a_seed_is_refused.
skarbiec.credential-enrol credential-enrol-verify-locked#
start the authenticator enrolment of the account a role names, at the site whose two-step settings page the account names, through Weles's credential admission (the run asks the owner for nothing unless a step would reach his phone, waits for his ready before it, and writes the seed and recovery codes to the account's item once the provider took the first code), tell the run the owner is ready or got no prompt, read where it stands with the item's seed and verification, and verify the seed with a sign-in that answers the provider's code request (Weles records what the provider answered). Started by skarbiec credential enrol role:<role>, skarbiec credential enrol role:<role> --answer ready|not-received, skarbiec credential enrol role:<role> --status, skarbiec credential enrol role:<role> --verify, POST /v1/operator/credential (operation enrol), Desktop: Settings → Policy → Authenticator enrolment → Enrol an authenticator.
What failed: verifying the authenticator seed of role {role}. Why: the provider locked the authenticator method of {holder} after refused codes, and another code would extend the lock. What the refusal shows: {holder}: verification locked.
Fix: wait until the provider unlocks the method, sign in once by hand, and record it with skarbiec totp verified {holder} --outcome accepted --by owner.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/enrol.sh::verifying_a_locked_account_is_refused.
skarbiec.credential.directory seal-flag-unknown#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: reading the flags of credential {command}. Why: --{flag} is not a flag credential {command} takes. What the refusal shows: usage: {usage}.
Fix: drop --{flag}; the usage line lists every flag it takes.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::a_seal_with_an_unknown_flag_is_refused.
skarbiec.credential.directory seal-flag-missing#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: reading the directory identity credential {command} seals. Why: --{flag} is required: a seal names the provider, tenant, principal object and account together. What the refusal shows: --{flag}: absent; usage: {usage}.
Fix: pass --{flag} <{flag}>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::a_seal_without_tenant_is_refused_naming_it.
skarbiec.credential.directory uuid-malformed#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: reading {flag}. Why: {value} is not a lowercase 8-4-4-4-12 hexadecimal UUID. What the refusal shows: {flag} {value}.
Fix: pass the identifier exactly as the directory shows it, lowercase, e.g. {flag} 11111111-2222-4333-8444-555555555555.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::an_uppercase_tenant_is_refused.
skarbiec.credential.directory already-sealed#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: sealing the directory identity of role {role}. Why: role {role} already carries a sealed directory contract, and a seal is never replaced silently. What the refusal shows: sealed directory contract of role {role}: present.
Fix: change it with skarbiec credential directory reseal role:{role} … --as <consumer> --token-file <path>, holding reseal:role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::sealing_a_sealed_role_again_is_refused_naming_reseal.
skarbiec.credential.directory reseal-not-granted#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: resealing the directory identity of role {role} as {consumer}. Why: {consumer} holds no reseal:role:{role} capability for the bearer it presented. What the refusal shows: consumer: {consumer}; capability asked: reseal:role:{role}.
Fix: add reseal:role:{role} to {consumer}'s grant: skarbiec grant list shows its capabilities; issue them again with reseal:role:{role} added (skarbiec grant issue {consumer} --capabilities <its capabilities>,reseal:role:{role} --replace-capabilities …), then present that grant's bearer.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::a_reseal_without_the_capability_is_refused.
skarbiec.credential.directory seal-unreadable#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: reading the sealed directory contract of role {role}. Why: the record {record} exists but could not be opened. What the refusal shows: record: {record}; opening it said: {error}.
Fix: run skarbiec doctor to see why the vault cannot open it; reseal the role once it can be read.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::an_unreadable_seal_is_refused_naming_the_record.
skarbiec.credential.directory seal-malformed#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: reading the sealed directory contract of role {role}. Why: {why}. What the refusal shows: sealed contract keys: provider, tenant_id, principal_object_id, account_upn.
Fix: reseal the role with skarbiec credential directory reseal role:{role} …, which writes a whole contract.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::a_seal_missing_its_tenant_is_refused_naming_the_key.
skarbiec.credential.directory contract-diverged#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: reading the sealed directory contract of role {role}. Why: DIRECTORY_CONTRACT_DIVERGED: the item playing role {role} ({item}) carries another directory identity than the role's sealed record. What the refusal shows: sealed record and item {item} name different identities.
Fix: reseal the role with skarbiec credential directory reseal role:{role} …, which writes both copies.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::a_seal_and_an_item_copy_that_diverge_are_refused.
skarbiec.credential.directory expectation-mismatch#
seal, reseal and read a role's directory identity, and hold operations to it. Started by skarbiec credential directory seal, skarbiec credential directory reseal.
What failed: holding credential {command} of role {role} to {flag}. Why: DIRECTORY_EXPECTATION_MISMATCH: the role's sealed directory contract does not name what {flag} expects. What the refusal shows: {flag} {expected}; sealed: {sealed}.
Fix: check which identity the role should hold: credential status role:{role} --local shows the seal; reseal it if the seal is wrong, else correct {flag}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/directory_seal.sh::an_expectation_the_seal_does_not_meet_is_refused_naming_both.
skarbiec.doctor doctor-revision-unrecorded#
run every check of this host's vault, journal, endpoint, grants, helpers, keys and logins' sign-in factors, or the one named, held to the revision asked, and alert where a check failed. Started by skarbiec doctor, skarbiec doctor --check <check>, POST /v1/operator/doctor, POST /v1/operator/doctor/check, POST /v1/operator/doctor/alert, MCP skarbiec_doctor_check, Desktop: Overview, Desktop: Settings → Policy → Sign-in factors.
What failed: holding doctor's answer to revision {asked}. Why: this skarbiec was built without recording the commit it was built from, so it cannot say its answer is revision {asked}'s. What the refusal shows: skarbiec version: commit none.
Fix: run a released skarbiec, whose skarbiec version names the commit it was built from, or run doctor without --revision.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/sign_in_factors.sh::a_revision_a_program_built_without_one_cannot_hold_is_refused.
skarbiec.doctor doctor-revision-other#
run every check of this host's vault, journal, endpoint, grants, helpers, keys and logins' sign-in factors, or the one named, held to the revision asked, and alert where a check failed. Started by skarbiec doctor, skarbiec doctor --check <check>, POST /v1/operator/doctor, POST /v1/operator/doctor/check, POST /v1/operator/doctor/alert, MCP skarbiec_doctor_check, Desktop: Overview, Desktop: Settings → Policy → Sign-in factors.
What failed: holding doctor's answer to revision {asked}. Why: this skarbiec was built from {built}, not from {asked}, so its answer is not that revision's. What the refusal shows: skarbiec version: commit {built}.
Fix: run doctor with the skarbiec built from {asked}, or ask with --revision {built}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/sign_in_factors.sh::a_revision_another_program_was_built_from_is_refused.
skarbiec.path-placing files-cwd-unreadable#
place a relative path a command was given in the working directory. Started by other functionalities only.
What failed: placing {path} for {command}. Why: the working directory this command runs in no longer exists or cannot be read, so the relative path has no directory to be placed in. What the refusal shows: path given: {path}; the system said: {error}.
Fix: run the command from a directory that exists, or name the file by an absolute path.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/files.sh::a_relative_path_from_a_removed_working_directory_is_refused_naming_it.
skarbiec.attach attach-exists#
keep a file in the vault as a new bundle item, encrypted like any value. Started by skarbiec attach, POST /v1/operator/items/attach, Desktop: Items → a selected item → Attach a file.
What failed: attaching a file as {id}. Why: {id} already exists, and attach creates an item and never replaces one. What the refusal shows: the vault holds an item {id}.
Fix: name a new id for the file.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/files.sh::attaching_over_an_existing_item_is_refused_and_the_item_is_kept.
skarbiec.detach detach-target-exists#
write the file an item holds to a new path, owner-only from its first byte. Started by skarbiec detach, POST /v1/operator/items/detach, Desktop: Items → a selected item → Save the file.
What failed: writing the file {id} holds to {path}. Why: {path} already exists, and detach never writes over a file. What the refusal shows: {path} is present.
Fix: name a path that does not exist yet.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/files.sh::detaching_onto_an_existing_file_is_refused_and_the_file_is_kept.
skarbiec.detach detach-no-file#
write the file an item holds to a new path, owner-only from its first byte. Started by skarbiec detach, POST /v1/operator/items/detach, Desktop: Items → a selected item → Save the file.
What failed: writing the file {id} holds to {path}. Why: {id} holds no content_base64, so it holds no file. What the refusal shows: {id}'s fields: {fields}.
Fix: name an item attach or an import made from a file; skarbiec get {id} reads this one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/files.sh::detaching_an_item_that_holds_no_file_is_refused_naming_its_fields.
skarbiec.detach detach-content-damaged#
write the file an item holds to a new path, owner-only from its first byte. Started by skarbiec detach, POST /v1/operator/items/detach, Desktop: Items → a selected item → Save the file.
What failed: writing the file {id} holds to {path}. Why: {id}'s content_base64 is not Base64: {reason}, so the file it held cannot be written back. What the refusal shows: content_base64: {length} characters; nothing was written to {path}.
Fix: attach the file again as a new item; skarbiec history {id} lists its saved versions, one of which may still hold it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/files.sh::a_file_whose_content_is_not_base64_is_refused_and_nothing_is_written.
skarbiec.emergency emergency-grantee-unknown#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: recording an emergency grant for {grantee}. Why: {grantee} is not a recipient of this vault, so activation would have no key to share to. What the refusal shows: registered recipients: {recipients}.
Fix: register them with skarbiec recipient add {grantee}, then grant again.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::a_grant_for_someone_who_is_not_a_recipient_is_refused_naming_the_recipients.
skarbiec.emergency emergency-no-grant#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: {verb} the emergency grant for {grantee}. Why: the vault holds no emergency grant for {grantee}. What the refusal shows: grants held for: {held}.
Fix: name a grantee above, or record one with skarbiec emergency grant {grantee} --activate-after <iso8601>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::a_grantee_with_no_grant_is_refused_naming_the_grants_held.
skarbiec.emergency emergency-already-activated#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: {verb} the emergency grant for {grantee}. Why: it is already activated, and replacing or dropping its record would forget which items it shared. What the refusal shows: grant for {grantee}: activated at {activated_at}.
Fix: skarbiec emergency revoke {grantee} takes back the items its activation shared; then grant again if needed.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::an_activated_grant_is_refused_for_grant_and_cancel_naming_revoke.
skarbiec.emergency emergency-not-due#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: activating the emergency grant for {grantee}. Why: its delay has not passed: it activates at {activate_after}, and it is {now}. What the refusal shows: grant for {grantee}: pending until {activate_after}.
Fix: activate it at or after {activate_after}; skarbiec emergency list says when each grant is due.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::activating_before_the_delay_passes_is_refused_naming_when_it_is_due.
skarbiec.emergency emergency-not-activated#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: revoking the emergency grant for {grantee}. Why: the grant is {status}, so it has shared nothing to revoke. What the refusal shows: grant for {grantee}: {status}.
Fix: skarbiec emergency cancel {grantee} withdraws a grant that is still waiting.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::revoking_a_grant_that_is_not_activated_is_refused_naming_cancel.
skarbiec.emergency emergency-unrecorded-activation#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: revoking the emergency grant for {grantee}. Why: it was activated by a release that did not record which items it shared, so taking back exactly those cannot be done without guessing; nothing was revoked. What the refusal shows: {grantee} reads: {reads}.
Fix: skarbiec revoke <item-id> {grantee} takes back one item, and skarbiec recipient remove {grantee} --yes takes back every item.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::an_activation_that_recorded_no_items_is_refused_naming_the_items_the_grantee_reads.
skarbiec.emergency emergency-section-damaged#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: reading the vault's emergency grants. Why: the vault document's emergency section is not an object of grants: it holds {held}. What the refusal shows: vault file: {path}; no grant was read or written.
Fix: restore the vault from a backup taken before the damage; skarbiec backup check <file> says whether a copy restores.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::an_emergency_section_held_in_another_shape_is_refused_naming_it.
skarbiec.emergency emergency-grant-damaged#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: {verb} the emergency grant for {grantee}. Why: the emergency grant for {grantee} is not an object of its activate_after, status and stamps: it holds {held}. What the refusal shows: vault file: {path}; the grant was left as recorded.
Fix: restore the vault from a backup taken before the damage; skarbiec backup check <file> says whether a copy restores.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::a_grant_held_in_another_shape_is_refused_naming_it.
skarbiec.emergency emergency-grant-undated#
record a grant that waits out its delay in the open, cancel it while it waits, share every live item with the grantee once it is due, and take back exactly what that activation shared. Started by skarbiec emergency list, skarbiec emergency grant, skarbiec emergency cancel, skarbiec emergency activate, skarbiec emergency revoke, POST /v1/operator/emergency, POST /v1/operator/emergency/grant, POST /v1/operator/emergency/cancel, POST /v1/operator/emergency/activate, POST /v1/operator/emergency/revoke.
What failed: activating the emergency grant for {grantee}. Why: the emergency grant for {grantee} records no activate_after time, so the moment it may be activated is unknown. What the refusal shows: grant for {grantee}: {grant}; vault file: {path}; nothing was shared.
Fix: record it again with its moment: skarbiec emergency cancel {grantee}, then skarbiec emergency grant {grantee} --activate-after <iso8601>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/emergency.sh::a_grant_recording_no_activate_after_is_refused_naming_cancel.
skarbiec.upgrade-envelope envelope-section-damaged#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: reading the {section} of the vault to move it to the v2 envelope. Why: the vault holds its {section} as {held}, where it keeps one JSON object. What the refusal shows: the vault is as it was; nothing was written.
Fix: restore the vault from a backup taken before the damage (skarbiec backup restore <backup-file>), then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_vault_whose_grants_are_not_an_object_is_refused_naming_them.
skarbiec.upgrade-envelope envelope-legacy-item-damaged#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: moving the legacy item {id} to the v2 envelope. Why: it records {why}, and a v1 item records its type and current ciphertext as text, its recipients, tags and history as lists, its deleted flag as true or false, and its times. What the refusal shows: the vault is as it was; nothing was written.
Fix: correct {id} in the vault file as v1 recorded it, or put it back from a backup with skarbiec backup restore <backup-file> --item {id}, then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_legacy_item_missing_what_v1_records_is_refused_naming_it.
skarbiec.upgrade-envelope envelope-revision-not-json#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: reading {revision} of the legacy item {id}. Why: {revision} of {id} opens, and a v1 revision must open to one JSON document of the item's fields, which it does not. What the refusal shows: the JSON reader said: {error}; the vault is as it was; nothing was written.
Fix: put {id} back from a backup taken before the damage with skarbiec backup restore <backup-file> --item {id}, then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_legacy_revision_that_opens_to_no_json_is_refused_naming_it.
skarbiec.upgrade-envelope envelope-no-recipient#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: sealing the legacy item {id} in the v2 envelope. Why: none of the recipients it lists ({listed}) nor the owner {owner} has a key the vault holds, so nothing could open it once moved. What the refusal shows: the vault is as it was; nothing was written.
Fix: register the owner's key again with skarbiec recipient add {owner}, then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_legacy_item_no_registered_key_can_open_is_refused.
skarbiec.upgrade-envelope envelope-id-collision#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: moving the legacy item {second} to the v2 envelope. Why: {first} and {second} both become {canonical}, a credential request taking the id of the credential operation it names. What the refusal shows: the vault is as it was; nothing was written.
Fix: keep one of {first} and {second}: delete the other in the legacy vault, then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::two_legacy_items_becoming_one_id_are_refused_naming_both.
skarbiec.upgrade-envelope envelope-grant-damaged#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: moving the grant of {consumer} to the v2 envelope. Why: it records {why}, and a legacy grant is an object whose capabilities name an action and an item, whose scopes are text and whose acquisition scopes name an item and a field. What the refusal shows: the vault is as it was; nothing was written.
Fix: correct the grant of {consumer} in the vault file's tokens, or remove it there and grant it again after the upgrade.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_legacy_grant_of_another_shape_is_refused_naming_it.
skarbiec.upgrade-envelope envelope-grant-action-unknown#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: moving the grant of {consumer} to the v2 envelope. Why: it grants {action} on {target}, an action no legacy grant was written with. What the refusal shows: the vault is as it was; nothing was written.
Fix: correct the action in the grant of {consumer} to one a legacy grant took ({actions}), or remove the grant from the vault file's tokens and grant it again after the upgrade.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_legacy_grant_naming_an_unknown_action_is_refused_naming_it.
skarbiec.upgrade-envelope envelope-grant-context-mutation#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: moving the grant of {consumer} to the v2 envelope. Why: it grants {action} on the context metadata of {item}, and only a read capability may name context. What the refusal shows: the vault is as it was; nothing was written.
Fix: change that capability of {consumer} to read, or remove it, then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_legacy_grant_changing_context_metadata_is_refused.
skarbiec.upgrade-envelope envelope-grant-mixed#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: moving the grant of {consumer} to the v2 envelope. Why: it grants acquisition beside direct reads or writes, and a v2 grant is either a workload's acquisition grant or a direct one. What the refusal shows: the vault is as it was; nothing was written.
Fix: split the grant of {consumer}: keep its acquisition scopes, remove the direct ones, and grant them to another consumer after the upgrade.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::a_legacy_grant_mixing_acquisition_and_direct_access_is_refused.
skarbiec.upgrade-envelope envelope-readback-refused#
move every legacy item, each of its revisions re-sealed, and every legacy grant to the v2 envelope, read the result back and write it once. Started by skarbiec upgrade --apply, POST /v1/operator/upgrade/apply.
What failed: reading the migrated vault back as v2 before writing it. Why: {record} {why}. What the refusal shows: the vault is as it was; nothing was written.
Fix: correct {record} in the vault file as the v2 envelope records it, or restore the vault from a backup with skarbiec backup restore <backup-file>, then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/envelope.sh::an_item_already_in_v2_that_does_not_read_back_is_refused_naming_it.
skarbiec.credential.endpoint declare-without-url#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: declaring the canonical Skarbiec's address. Why: no URL was given. What the refusal shows: usage: credential endpoint declare <url>: the canonical Skarbiec's address from this machine.
Fix: run skarbiec credential endpoint declare http://127.0.0.1:<port>, or let `stado service directory publish` write the same marker from the fleet's declaration.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/nouns.sh::a_declaration_without_an_address_is_refused_with_its_usage.
skarbiec.credential.endpoint forwards-dir-unknown#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: finding the Stado forwards directory. Why: SKARBIEC_ENDPOINT_UNRESOLVED: neither STADO_FORWARDS_DIR nor HOME is set, so no directory names where the forward is. What the refusal shows: STADO_FORWARDS_DIR: unset; HOME: unset.
Fix: set HOME, or STADO_FORWARDS_DIR to the directory holding the forward files.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::no_home_and_no_forwards_directory_is_refused_naming_both.
skarbiec.credential.endpoint forward-absent#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reading where the canonical Skarbiec is. Why: SKARBIEC_ENDPOINT_UNRESOLVED: no canonical forward is at {path}, so nothing names where the canonical Skarbiec is. What the refusal shows: forward: {path}; the file system said: {error}.
Fix: declare it with `skarbiec credential endpoint declare <url>`.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/owner_only_files.sh::an_owner_only_token_file_passes_the_ownership_check_and_the_call_reaches_the_forward_lookup.
skarbiec.credential.endpoint forward-not-owner-only#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reading where the canonical Skarbiec is. Why: SKARBIEC_ENDPOINT_UNRESOLVED: {path} must be an owner-owned regular file without group or world write, since whoever may write it chooses where bearers are sent. What the refusal shows: {kind}, owner uid {owner} (this process runs as {uid}), mode {mode}.
Fix: chmod go-w {path} as its owner, or declare it again with `skarbiec credential endpoint declare <url>`.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/owner_only_files.sh::a_forward_others_may_write_is_refused_by_name.
skarbiec.credential.endpoint forward-not-text#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reading where the canonical Skarbiec is. Why: SKARBIEC_ENDPOINT_UNRESOLVED: {path} is not UTF-8 text, so it names no address. What the refusal shows: forward: {path}; {bytes} byte(s), the first that is not UTF-8 at byte {offset}.
Fix: declare it again with `skarbiec credential endpoint declare <url>`.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_forward_that_is_not_text_is_refused.
skarbiec.credential.endpoint forward-not-one-url#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reading where the canonical Skarbiec is. Why: SKARBIEC_ENDPOINT_UNRESOLVED: {path} must hold exactly one URL, and it holds none or a control character inside one. What the refusal shows: {bytes} byte(s) after trimming surrounding whitespace.
Fix: declare it again with `skarbiec credential endpoint declare <url>`.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::an_empty_forward_is_refused.
skarbiec.credential.endpoint endpoint-not-url#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reading the canonical Skarbiec's address {endpoint}. Why: SKARBIEC_ENDPOINT_UNRESOLVED: it is not an absolute URL: no scheme:// before the host. What the refusal shows: address: {endpoint}.
Fix: declare it as http://127.0.0.1:<port> with `skarbiec credential endpoint declare <url>`.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::an_address_without_a_scheme_is_refused.
skarbiec.credential.endpoint endpoint-port#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reading the canonical Skarbiec's address {endpoint}. Why: SKARBIEC_ENDPOINT_UNRESOLVED: it must name an exact numeric port after the host. What the refusal shows: address: {endpoint}.
Fix: declare it with the port the canonical Skarbiec listens on, e.g. http://127.0.0.1:8737.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::an_address_without_a_port_is_refused.
skarbiec.credential.endpoint endpoint-tls-unsupported#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reaching the canonical Skarbiec at {endpoint}. Why: SKARBIEC_ENDPOINT_TLS_UNSUPPORTED: an https address needs a TLS client this binary does not carry. What the refusal shows: address: {endpoint}.
Fix: publish the canonical Skarbiec through a loopback Stado forward and declare that http://127.0.0.1:<port> address.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::an_https_address_is_refused_naming_the_loopback_forward.
skarbiec.credential.endpoint endpoint-not-loopback#
find and declare the canonical Skarbiec's address in the owner-only Stado forward. Started by skarbiec credential endpoint declare.
What failed: reaching the canonical Skarbiec at {endpoint}. Why: SKARBIEC_ENDPOINT_UNRESOLVED: plain http is accepted only on the loopback interface, where no other machine can read the bearer. What the refusal shows: address: {endpoint}.
Fix: declare the loopback forward Stado publishes for it, http://127.0.0.1:<port>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::an_http_address_off_the_loopback_is_refused.
skarbiec.credential.remote-call canonical-not-listening#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: asking the canonical Skarbiec at {authority}. Why: nothing listens at {authority}: the connection was refused, so neither a skarbiec serve nor its Stado forward is up there. What the refusal shows: address {authority}, declared by {forward}; the system said: {error}; nothing was sent.
Fix: start the canonical Skarbiec (skarbiec serve) or its Stado forward; if the address is wrong, run skarbiec credential endpoint declare <url>.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_canonical_address_nothing_listens_on_is_refused_as_unanswered.
skarbiec.credential.remote-call canonical-connection-broken#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: asking the canonical Skarbiec at {authority}. Why: the connection to {authority} broke before its reply ended, so whether the request was carried out is not known. What the refusal shows: address {authority}, declared by {forward}; the system said: {error}.
Fix: read the canonical Skarbiec's audit (skarbiec audit list there) for the request, then run the same command again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_connection_the_canonical_skarbiec_breaks_is_refused_naming_it.
skarbiec.credential.remote-call canonical-unanswered#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: asking the canonical Skarbiec at {authority}. Why: {authority} could not be reached: the system found no route or address to it, or it did not answer in time. What the refusal shows: address {authority}, declared by {forward}; the system said: {error}; nothing was sent.
Fix: start the canonical Skarbiec (skarbiec serve) or its Stado forward; if the address is wrong, run skarbiec credential endpoint declare <url>.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_canonical_address_that_cannot_be_reached_is_refused_naming_it.
skarbiec.credential.remote-call canonical-reply-not-text#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: reading the canonical Skarbiec's reply from {authority}. Why: the reply holds bytes that are not UTF-8, which no Skarbiec sends, so none of it is read. What the refusal shows: {bytes} bytes received and erased; the first that is not UTF-8 is at byte {offset}.
Fix: check what listens on {authority} is a Skarbiec of this release (skarbiec --version there); declare the right address with skarbiec credential endpoint declare <url>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_reply_that_is_not_text_is_refused_naming_where_it_stops.
skarbiec.credential.remote-call canonical-reply-headers-unended#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: reading the canonical Skarbiec's reply from {authority}. Why: the connection closed after {bytes} bytes, before a blank line ended the reply's headers. What the refusal shows: address {authority}, declared by {forward}.
Fix: check what listens on {authority} is a Skarbiec of this release (skarbiec --version there); declare the right address with skarbiec credential endpoint declare <url>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_reply_whose_headers_never_end_is_refused_naming_its_length.
skarbiec.credential.remote-call canonical-reply-no-status-line#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: reading the canonical Skarbiec's reply from {authority}. Why: the reply's first line is empty, so it carries no HTTP status line. What the refusal shows: address {authority}, declared by {forward}; {bytes} bytes received.
Fix: check what listens on {authority} is a Skarbiec of this release (skarbiec --version there); declare the right address with skarbiec credential endpoint declare <url>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_reply_without_a_status_line_is_refused.
skarbiec.credential.remote-call canonical-reply-not-json#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: reading the canonical Skarbiec's reply from {authority}. Why: the reply body is not JSON, and every answer of a Skarbiec is. What the refusal shows: status line: {status}; {bytes} body bytes, not shown as they may hold a credential; the JSON reader said: {error}.
Fix: check what listens on {authority} is a Skarbiec of this release (skarbiec --version there); declare the right address with skarbiec credential endpoint declare <url>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_reply_that_is_not_json_is_refused_naming_its_status_line.
skarbiec.credential.remote-call service-directory-stale#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: asking the canonical Skarbiec at {authority}. Why: SERVICE_DIRECTORY_STALE: it reports this host's service directory is stale. What the refusal shows: reply: 409 service_directory_stale.
Fix: refresh the forwards with stado service directory publish, then retry.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_stale_service_directory_is_refused_naming_the_refresh.
skarbiec.credential.remote-call canonical-refused#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: the credential operation {method} {path} on the canonical Skarbiec at {authority}. Why: it refused the request with {status}. What the refusal shows: it said: {detail}; its cause: {remote_cause}; its fix: {remote_fix}.
Fix: act on the canonical Skarbiec's fix above; skarbiec errors list there names the cause {remote_cause}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_refusal_by_the_canonical_skarbiec_carries_its_own_words.
skarbiec.credential.remote-call canonical-status-not-object#
send one credential request to the canonical Skarbiec and read its reply. Started by skarbiec credential acquire --as, skarbiec credential adopt --as, skarbiec credential rotate --as, skarbiec credential reset --as, skarbiec credential verify --as, skarbiec credential remove --as, skarbiec credential status --as, skarbiec credential resume --as.
What failed: reading the status of {role} the canonical Skarbiec answered for GET {path}. Why: it answered {shape} where a credential status object belongs. What the refusal shows: members: {members}; nothing was changed here.
Fix: check the canonical Skarbiec is of this release (skarbiec --version there), and its status of {role} with skarbiec credential status role:{role} there.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/endpoint.sh::a_status_that_is_not_an_object_is_refused_naming_its_shape.
skarbiec.env-import env-import-line-not-assignment#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: reading the variables {source} sets. Why: line {line} is not NAME=value, a comment or blank, so what it holds would be left behind in the file unread. What the refusal shows: {source}: line {line}; nothing was stored.
Fix: make line {line} of {source} NAME=value, a # comment or blank.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_env_line_that_is_not_name_value_is_refused_naming_the_line.
skarbiec.env-import env-import-line-name-unfit#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: reading the variables {source} sets. Why: line {line} sets {name}, which is not a variable name a shell reads back: a letter or underscore, then letters, digits and underscores. What the refusal shows: {source}: line {line}, name {name}; nothing was stored.
Fix: rename the variable on line {line} of {source}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_env_line_whose_name_is_not_a_variable_is_refused_naming_it.
skarbiec.env-import env-import-line-set-again#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: reading the variables {source} sets. Why: line {line} sets {name} again, first set on line {first}, and which value a loader keeps differs between loaders. What the refusal shows: {source}: {name} on lines {first} and {line}; nothing was stored.
Fix: keep one of the two lines in {source}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_env_variable_set_twice_is_refused_naming_both_lines.
skarbiec.env-import env-import-line-quote-open#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: reading the variables {source} sets. Why: the {quote}-quoted value on line {line} does not end on its line, and a value across lines is not read. What the refusal shows: {source}: line {line}; nothing was stored.
Fix: close the quote on line {line} of {source}, or write the newline as \n inside double quotes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_env_quoted_value_left_open_is_refused_naming_its_line.
skarbiec.env-import env-import-empty#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: reading the variables {source} sets. Why: {source} sets no variable: every one of its {lines} lines is blank or a comment. What the refusal shows: {lines} lines, none NAME=value; nothing was stored.
Fix: name the .env file that holds the project's secrets.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_env_file_setting_nothing_is_refused_naming_it.
skarbiec.env-import env-import-ids-collide#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: naming the items the variables of {source} become. Why: {first} and {second} would both be stored as {id}, since an id is the prefix and the name in lower case with _ as -. What the refusal shows: {first} and {second} -> {id}; nothing was stored.
Fix: rename one of the two variables in {source}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::variables_that_would_become_the_same_or_an_existing_item_are_refused_naming_them.
skarbiec.env-import env-import-ids-taken#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: naming the items the variables of {source} become. Why: {taken} already exist, and env import never replaces an item. What the refusal shows: --prefix {prefix}; nothing was stored.
Fix: choose another --prefix, or delete those items first (skarbiec delete <id>).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::variables_whose_items_already_exist_are_refused_naming_them.
skarbiec.env-import env-import-bindings-present#
store each variable a .env file sets as a token item, and with --bindings write the file exec --env-from reads. Started by skarbiec env import.
What failed: writing the bindings file {bindings}. Why: {bindings} already exists, and env import never writes over a file unasked. What the refusal shows: nothing was stored.
Fix: add --replace to write the bindings over it, or name another file.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::an_existing_bindings_file_without_replace_is_refused_and_nothing_stored.
skarbiec.env-input env-input-not-text#
read one environment variable Skarbiec declares, as the operating system hands it over, or this account's home. Started by other functionalities only.
What failed: reading the environment variable {name} ({meaning}). Why: {name} is set to {bytes} bytes that are not UTF-8 text, so its value cannot be read, and it is not taken as unset. What the refusal shows: {name} is delivered by {source}; nothing was read or written.
Fix: set {name} to the value as UTF-8 text, or unset it to keep the default its meaning names (skarbiec doctor lists every input this process was given).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/core/env_input.sh::a_variable_that_is_not_text_is_refused_naming_it.
skarbiec.env-input home-blank#
read one environment variable Skarbiec declares, as the operating system hands it over, or this account's home. Started by other functionalities only.
What failed: finding this account's home directory (uid {uid}). Why: HOME is set to nothing but blanks, so the paths Skarbiec keeps under the home (the default vault, its journal, the resolver state, the browsers' manifests) cannot be found, and the user database is not asked behind that choice. What the refusal shows: HOME: blank; uid: {uid}; nothing was read or written.
Fix: set HOME to this account's home directory, or unset it so the home the user database records is used.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/core/env_input.sh::a_blank_home_is_refused_naming_it.
skarbiec.env-input home-unrecorded#
read one environment variable Skarbiec declares, as the operating system hands it over, or this account's home. Started by other functionalities only.
What failed: finding this account's home directory (uid {uid}). Why: HOME is unset and the user database records no home for uid {uid}, so the paths Skarbiec keeps under the home (the default vault, its journal, the resolver state, the browsers' manifests) cannot be found. What the refusal shows: HOME: unset; uid: {uid}; nothing was read or written.
Fix: set HOME to this account's home directory (id -P names the account the database records).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/core/env_input.sh::an_account_the_user_database_gives_no_home_is_refused_naming_it.
skarbiec.inject inject-out-exists#
write a configuration file from a template whose skarbiec:<id>:<field> references are filled from the vault. Started by skarbiec inject.
What failed: writing the filled file {out}. Why: {out} exists, and inject never writes over a file unasked. What the refusal shows: {out} is present.
Fix: add --replace to overwrite it, or name a new file.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::filling_onto_an_existing_file_is_refused_and_the_file_kept.
skarbiec.inject inject-reference-malformed#
write a configuration file from a template whose skarbiec:<id>:<field> references are filled from the vault. Started by skarbiec inject.
What failed: reading the references in {template}. Why: line {line}: the reference {reference} is not skarbiec:<id>:<field>. What the refusal shows: nothing was written.
Fix: write each reference as skarbiec:<id>:<field> between double braces.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_reference_that_names_no_item_or_field_is_refused_naming_its_line.
skarbiec.inject inject-nothing#
write a configuration file from a template whose skarbiec:<id>:<field> references are filled from the vault. Started by skarbiec inject.
What failed: filling {template}. Why: {template} holds no skarbiec:<id>:<field> reference between double braces, so there is nothing to fill. What the refusal shows: nothing was written.
Fix: add a reference where each value goes, or copy the file as it is.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_template_with_no_reference_is_refused.
skarbiec.bindings bindings-failing#
say whether every line of a bindings file gives its program a value, and keep the files this host knows of. Started by skarbiec bindings check, skarbiec bindings list, skarbiec bindings remember, skarbiec bindings forget.
What failed: checking the bindings in {file}. Why: exec would give {variables} nothing, since the item or field each line names is not a live item's text field. What the refusal shows: why each fails: {problems}.
Fix: point each failing line at a live item's text field, or restore the item (skarbiec restore <id>).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_bindings_check_with_refuse_over_a_line_that_would_fail_is_refused_naming_it.
skarbiec.bindings bindings-unknown#
say whether every line of a bindings file gives its program a value, and keep the files this host knows of. Started by skarbiec bindings check, skarbiec bindings list, skarbiec bindings remember, skarbiec bindings forget.
What failed: forgetting the bindings file {file}. Why: {file} is not a bindings file this host knows of. What the refusal shows: known bindings files are kept in {store}.
Fix: skarbiec bindings list names those it does.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::forgetting_a_file_this_host_does_not_know_is_refused.
skarbiec.bindings bindings-store-damaged#
say whether every line of a bindings file gives its program a value, and keep the files this host knows of. Started by skarbiec bindings check, skarbiec bindings list, skarbiec bindings remember, skarbiec bindings forget.
What failed: {doing} the known bindings files in {store}. Why: {store}, the list of bindings files this host knows of, does not read as a JSON list of file paths. What the refusal shows: the JSON reader stopped at line {line}, column {column}: {said}.
Fix: make {store} a JSON list of file paths again, or remove it and remember each file anew.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_known_bindings_store_that_is_not_a_list_is_refused_naming_it.
skarbiec.bindings-file bindings-line-not-binding#
read the NAME=<id>:<field> lines of a bindings file. Started by other functionalities only.
What failed: reading the bindings file {file}. Why: line {line} is not NAME=<id>:<field>: it has no '=', no ':' after it, or an empty item or field. What the refusal shows: line {line}: {text}.
Fix: write one NAME=<id>:<field> a line in {file}; # starts a comment.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_bindings_file_with_a_line_that_is_not_a_binding_is_refused_naming_the_line.
skarbiec.bindings-file bindings-line-name-unfit#
read the NAME=<id>:<field> lines of a bindings file. Started by other functionalities only.
What failed: reading the bindings file {file}. Why: line {line} binds {name}, which is not a variable name a shell reads back: a letter or underscore, then letters, digits and underscores. What the refusal shows: line {line}: {text}.
Fix: rename the variable on line {line} of {file}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_bindings_line_whose_name_is_not_a_variable_is_refused_naming_it.
skarbiec.bindings-file bindings-file-empty#
read the NAME=<id>:<field> lines of a bindings file. Started by other functionalities only.
What failed: reading the bindings file {file}. Why: {file} lists no NAME=<id>:<field>: every one of its {lines} lines is blank or a comment. What the refusal shows: {lines} lines, none a binding; nothing was started.
Fix: write one NAME=<id>:<field> a line in {file}, or bind with --env.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_bindings_file_listing_no_binding_is_refused_naming_it.
skarbiec.exec exec-item-no-text#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: putting every text field of {item} into the environment. Why: {item} holds no text field. What the refusal shows: {item}'s fields: {fields}.
Fix: bind the fields one at a time with --env NAME={item}:<field>, or name another item.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::an_item_with_no_text_field_is_refused_naming_its_fields.
skarbiec.exec exec-tag-unheld#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: putting the items tagged {tag} into the environment. Why: no live item carries the tag {tag}, so nothing would go into the environment. What the refusal shows: live items tagged {tag}: none.
Fix: tag the items the program needs: skarbiec retag --add {tag} <id>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_tag_no_live_item_carries_is_refused_naming_retag.
skarbiec.exec exec-tag-prefix#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: putting the items tagged {tag} into the environment. Why: {id}, tagged {tag}, gives the prefix {prefix}, which is not a variable name. What the refusal shows: {id} is tagged {tag}.
Fix: bind it with --env-item <PREFIX>={id}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_tagged_item_whose_id_makes_no_variable_name_is_refused_naming_env_item.
skarbiec.exec exec-field-absent#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: putting {item}'s {field} into {variable}. Why: {item} has no text field {field}. What the refusal shows: {item}'s fields: {fields}.
Fix: bind {variable} to one of the fields above.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_binding_to_a_field_the_item_does_not_hold_is_refused_naming_its_fields.
skarbiec.exec exec-program-not-found#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: starting {program}. Why: no program {program} is on PATH, or at the path given. What the refusal shows: the system said: {said}; no value left the vault.
Fix: name a program on PATH, or give its path (command -v {program} says whether PATH has it).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_program_that_cannot_start_is_refused_naming_it.
skarbiec.exec exec-program-not-executable#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: starting {program}. Why: {program} is there, but this account may not execute it. What the refusal shows: the system said: {said}; no value left the vault.
Fix: make it executable (chmod u+x {program}) or name the program it should be.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_program_this_account_may_not_execute_is_refused_naming_it.
skarbiec.exec exec-program-unstarted#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: starting {program}. Why: the system would not start {program} ({kind}): it is found and executable, and starting it failed. What the refusal shows: the system said: {said}; no value left the vault.
Fix: run {program} on its own to see why it does not start (a file that is not a program, a missing interpreter), then run exec again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_file_that_is_no_program_is_refused_naming_it.
skarbiec.exec exec-program-signalled#
run one program with vault values in its environment, ending with the program's exit status. Started by skarbiec exec.
What failed: running {program}. Why: {program} was ended by signal {signal}. What the refusal shows: {program} gave no exit status ({status}).
Fix: the signal came from outside skarbiec; run the program again, and find what sent the signal if it recurs.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/exec/refusals.sh::a_program_ended_by_a_signal_is_refused_naming_the_signal.
skarbiec.fence fence-no-vault#
record beside the vault the move whose steps alone may write it, read that record, or end it. Started by skarbiec fence arm, skarbiec fence lift, skarbiec fence show, POST /v1/operator/fence, POST /v1/operator/fence/arm, POST /v1/operator/fence/lift.
What failed: arming the write fence for transaction {transaction}. Why: there is no vault at {path} to hold writes on. What the refusal shows: vault file: {path}.
Fix: name the vault being moved with SKARBIEC_VAULT_FILE.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/vault/fence.sh::arming_a_fence_where_no_vault_is_is_refused_naming_the_file.
skarbiec.fence fence-other-move#
record beside the vault the move whose steps alone may write it, read that record, or end it. Started by skarbiec fence arm, skarbiec fence lift, skarbiec fence show, POST /v1/operator/fence, POST /v1/operator/fence/arm, POST /v1/operator/fence/lift.
What failed: {doing} the write fence for transaction {transaction}. Why: the fence stands for transaction {standing} since {since}, and only the move that armed it {owns} it. What the refusal shows: fence: transaction {standing}, since {since}.
Fix: finish or abandon that move first; skarbiec fence lift --transaction {standing} ends it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/vault/fence.sh::a_fence_standing_for_another_move_is_refused_naming_its_transaction.
skarbiec.field field-empty#
set one field of an item from standard input or a request body, or remove an optional one, keeping every other field. Started by skarbiec field set, skarbiec field unset, POST /v1/operator/items/field/set, POST /v1/operator/items/field/unset, Desktop: Items → a selected item → Set a field….
What failed: setting {field} of {id}. Why: standard input held no value, and an empty field would read as a value nobody gave. What the refusal shows: nothing was written to {id}.
Fix: give the value on standard input; skarbiec field unset {id} {field} removes the field.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/field.sh::an_empty_value_is_refused_naming_unset.
skarbiec.field field-body-empty#
set one field of an item from standard input or a request body, or remove an optional one, keeping every other field. Started by skarbiec field set, skarbiec field unset, POST /v1/operator/items/field/set, POST /v1/operator/items/field/unset, Desktop: Items → a selected item → Set a field….
What failed: setting {field} of {id}. Why: the request body's value was missing, not text or empty, and an empty field would read as a value nobody gave. What the refusal shows: nothing was written to {id}.
Fix: send the new value as the body's value; POST /v1/operator/items/field/unset, as skarbiec field unset {id} {field}, removes the field.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/field.sh::the_route_refuses_a_missing_non_text_or_empty_value_naming_unset.
skarbiec.field field-not-of-kind#
set one field of an item from standard input or a request body, or remove an optional one, keeping every other field. Started by skarbiec field set, skarbiec field unset, POST /v1/operator/items/field/set, POST /v1/operator/items/field/unset, Desktop: Items → a selected item → Set a field….
What failed: changing {field} of {id}. Why: {id} is a {kind}, and a {kind} takes no field {field}. What the refusal shows: nothing was written to {id}.
Fix: skarbiec kinds {kind} lists the fields a {kind} takes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/field.sh::a_field_the_kind_does_not_take_is_refused_naming_kinds.
skarbiec.field field-payload-invalid#
set one field of an item from standard input or a request body, or remove an optional one, keeping every other field. Started by skarbiec field set, skarbiec field unset, POST /v1/operator/items/field/set, POST /v1/operator/items/field/unset, Desktop: Items → a selected item → Set a field….
What failed: changing {field} of {id}. Why: {id} with that change would not be a {kind} the schema accepts: {why}. What the refusal shows: nothing was written to {id}.
Fix: keep every field a {kind} requires and one of each set it needs one of, and give {field} a value of the form the refusal names; skarbiec kinds {kind} lists the fields a {kind} requires and the sets it needs one of.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/field.sh::a_required_field_removed_is_refused_naming_what_the_kind_requires.
skarbiec.expiry expiry-moment-malformed#
record or forget when an item runs out, list the recorded dates soonest first, and read when stored tokens run out. Started by skarbiec expiry set, skarbiec expiry clear, skarbiec expiry list, skarbiec expiry tokens, POST /v1/operator/items/expiry/set, POST /v1/operator/items/expiry/clear, POST /v1/operator/items/expiry, Desktop: Items → a selected item → Expiry → Save / Clear, Desktop: Expiry → Set for every item tagged / Clear for every item tagged.
What failed: reading --{flag}. Why: {value} is not a UTC time of the form {example}. What the refusal shows: --{flag} {value}.
Fix: give --{flag} as a UTC time such as {example}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/expiry/expiry.sh::a_date_that_is_not_a_utc_time_is_refused_naming_the_form.
skarbiec.expiry expiry-item-trashed#
record or forget when an item runs out, list the recorded dates soonest first, and read when stored tokens run out. Started by skarbiec expiry set, skarbiec expiry clear, skarbiec expiry list, skarbiec expiry tokens, POST /v1/operator/items/expiry/set, POST /v1/operator/items/expiry/clear, POST /v1/operator/items/expiry, Desktop: Items → a selected item → Expiry → Save / Clear, Desktop: Expiry → Set for every item tagged / Clear for every item tagged.
What failed: recording when {id} runs out. Why: {id} is in the trash, and a date is recorded only for a live item. What the refusal shows: item {id}: trashed.
Fix: skarbiec restore {id} brings it back, then record its date.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/expiry/expiry.sh::a_date_for_a_trashed_item_is_refused_naming_the_restore.
skarbiec.expiry expiry-no-tagged-item#
record or forget when an item runs out, list the recorded dates soonest first, and read when stored tokens run out. Started by skarbiec expiry set, skarbiec expiry clear, skarbiec expiry list, skarbiec expiry tokens, POST /v1/operator/items/expiry/set, POST /v1/operator/items/expiry/clear, POST /v1/operator/items/expiry, Desktop: Items → a selected item → Expiry → Save / Clear, Desktop: Expiry → Set for every item tagged / Clear for every item tagged.
What failed: {doing} every live item tagged {tag}. Why: no live item carries the tag {tag}, so nothing was changed. What the refusal shows: live items carrying {tag}: none.
Fix: skarbiec tags lists every tag the live items carry.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/expiry/expiry.sh::a_tag_no_item_carries_is_refused.
skarbiec.expiry expiry-dates-damaged#
record or forget when an item runs out, list the recorded dates soonest first, and read when stored tokens run out. Started by skarbiec expiry set, skarbiec expiry clear, skarbiec expiry list, skarbiec expiry tokens, POST /v1/operator/items/expiry/set, POST /v1/operator/items/expiry/clear, POST /v1/operator/items/expiry, Desktop: Items → a selected item → Expiry → Save / Clear, Desktop: Expiry → Set for every item tagged / Clear for every item tagged.
What failed: reading the recorded dates of the vault at {path}. Why: its item_expiry section {why}, so which dates are recorded cannot be read and writing one would replace them. What the refusal shows: item_expiry: {found}.
Fix: restore the vault from a backup taken before the section was damaged (skarbiec backup list), or correct the item_expiry section in the vault file to map each item id to a UTC time.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/expiry/expiry.sh::a_damaged_date_section_is_refused_instead_of_being_replaced.
skarbiec.export export-recipient-unknown#
decrypt the live items list would name into one owner-only file: canonical payloads, rows import reads back, a browser or Bitwarden CSV, optionally sealed to one recipient; or, with -, the package sealed to one recipient on standard output. Started by skarbiec export, POST /v1/operator/items/export.
What failed: sealing the export to {uid}. Why: {uid} is not a recipient of this vault, so there is no key to seal the file to. What the refusal shows: registered recipients: {recipients}; nothing was written.
Fix: name a registered recipient, or register them with skarbiec recipient add {uid}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/copies/export.sh::an_export_sealed_to_someone_who_is_not_a_recipient_is_refused_and_writes_nothing.
skarbiec.export export-csv-kind-other#
decrypt the live items list would name into one owner-only file: canonical payloads, rows import reads back, a browser or Bitwarden CSV, optionally sealed to one recipient; or, with -, the package sealed to one recipient on standard output. Started by skarbiec export, POST /v1/operator/items/export.
What failed: writing the {format} export. Why: {format} holds {holds} only, and these items are another kind: {others}; leaving them out would read as a complete export. What the refusal shows: items chosen: {chosen}; nothing was written.
Fix: narrow the export with {narrow}, or export the other kinds without {format}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/copies/export.sh::a_csv_export_holding_another_kind_is_refused_naming_the_items.
skarbiec.export export-csv-field-not-text#
decrypt the live items list would name into one owner-only file: canonical payloads, rows import reads back, a browser or Bitwarden CSV, optionally sealed to one recipient; or, with -, the package sealed to one recipient on standard output. Started by skarbiec export, POST /v1/operator/items/export.
What failed: writing {id} into the {format} export. Why: {id}'s {field} is {held}, not text, so it has no {format} cell to go in. What the refusal shows: its value is not shown, as it may be secret; nothing was written.
Fix: write it as text with skarbiec field set {id} {field} (the value on standard input), then export again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/copies/export.sh::a_csv_export_of_a_field_that_is_not_text_is_refused_naming_it.
skarbiec.export export-stream-unsealed#
decrypt the live items list would name into one owner-only file: canonical payloads, rows import reads back, a browser or Bitwarden CSV, optionally sealed to one recipient; or, with -, the package sealed to one recipient on standard output. Started by skarbiec export, POST /v1/operator/items/export.
What failed: writing the export to standard output. Why: export - writes to standard output only a package sealed to one recipient, so a value never crosses a pipe in plaintext, and no --encrypt-to names one. What the refusal shows: nothing was written.
Fix: add --encrypt-to <uid> (skarbiec recipient list names the registered ones), or name an <out-file> instead of -.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/transfer/role_stream.sh::a_plaintext_export_to_standard_output_is_refused.
skarbiec.export export-stream-empty#
decrypt the live items list would name into one owner-only file: canonical payloads, rows import reads back, a browser or Bitwarden CSV, optionally sealed to one recipient; or, with -, the package sealed to one recipient on standard output. Started by skarbiec export, POST /v1/operator/items/export.
What failed: sealing the export to {uid} on standard output. Why: export - selected no live item {narrowing}, and a receiver importing nothing could not tell a missing item from an empty vault. What the refusal shows: nothing was sealed to {uid} or written.
Fix: run skarbiec list with the same narrowing to see what it selects, and write the item the receiver needs with skarbiec set before exporting it.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/role_stream.sh::a_role_the_source_holds_no_item_for_is_refused_naming_its_tag.
skarbiec.password-rules-language password-rules-value-absent#
read a site's password rules in the Password Rules language. Started by other functionalities only.
What failed: reading the password rules {rules}. Why: password rule `{rule}` names no value; rules read `name: value; ...`, a colon between a rule's name and its value. What the refusal shows: rules: {rules}.
Fix: write them in the Password Rules language: `name: value; ...` with minlength, maxlength, required, allowed or max-consecutive, and the classes lower, upper, digit, special, ascii-printable, unicode or a [set].
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::rules_the_language_does_not_read_are_refused_naming_the_rule.
skarbiec.password-rules-language password-rules-length-not-number#
read a site's password rules in the Password Rules language. Started by other functionalities only.
What failed: reading the password rules {rules}. Why: password rule {name}: {value} is not a whole number of characters, the one kind of value {name} takes. What the refusal shows: rules: {rules}.
Fix: write them in the Password Rules language: `name: value; ...` with minlength, maxlength, required, allowed or max-consecutive, and the classes lower, upper, digit, special, ascii-printable, unicode or a [set].
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::rules_the_language_does_not_read_are_refused_naming_the_rule.
skarbiec.password-rules-language password-rules-name-unknown#
read a site's password rules in the Password Rules language. Started by other functionalities only.
What failed: reading the password rules {rules}. Why: password rule {name} is not one the Password Rules language names (minlength, maxlength, required, allowed, max-consecutive). What the refusal shows: rules: {rules}.
Fix: write them in the Password Rules language: `name: value; ...` with minlength, maxlength, required, allowed or max-consecutive, and the classes lower, upper, digit, special, ascii-printable, unicode or a [set].
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::rules_the_language_does_not_read_are_refused_naming_the_rule.
skarbiec.password-rules-language password-rules-class-unknown#
read a site's password rules in the Password Rules language. Started by other functionalities only.
What failed: reading the password rules {rules}. Why: password rule class {class} is not lower, upper, digit, special, ascii-printable, unicode or a [set]. What the refusal shows: rules: {rules}.
Fix: write them in the Password Rules language: `name: value; ...` with minlength, maxlength, required, allowed or max-consecutive, and the classes lower, upper, digit, special, ascii-printable, unicode or a [set].
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::rules_the_language_does_not_read_are_refused_naming_the_rule.
skarbiec.password-rules-language password-rules-no-length#
read a site's password rules in the Password Rules language. Started by other functionalities only.
What failed: taking a length from the password rules {rules}. Why: the rules state neither minlength nor maxlength, so no length can be taken from them. What the refusal shows: rules: {rules}.
Fix: add minlength or maxlength to the rules; skarbiec generate also takes --length in their place.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::rules_with_no_length_are_refused_naming_the_missing_rule.
skarbiec.generate generate-length-under-classes#
draw a password or a passphrase, printed, or written into one field of an item without passing through stdout. Started by skarbiec generate, POST /v1/operator/items/generate, Desktop: Items → a selected item → Replace with a generated value.
What failed: drawing a password. Why: a password of {length} characters cannot hold one of each of the {count} classes chosen ({classes}), and every password generate draws holds one of each. What the refusal shows: --length {length}; classes: {classes}; nothing was drawn or stored.
Fix: ask for --length {count} or more, or choose fewer classes (skarbiec generate --length <N> [--lower] [--upper] [--digits] [--symbols]).
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/generate/refusals.sh::a_length_under_the_classes_chosen_is_refused_naming_both.
skarbiec.generate generate-symbols-all-lookalikes#
draw a password or a passphrase, printed, or written into one field of an item without passing through stdout. Started by skarbiec generate, POST /v1/operator/items/generate, Desktop: Items → a selected item → Replace with a generated value.
What failed: drawing a password. Why: every symbol of {set} is a look-alike that --unambiguous leaves out ({lookalikes}), so the symbol class it chose holds no character. What the refusal shows: --symbols-from {set} --unambiguous; nothing was drawn or stored.
Fix: name symbols that are not look-alikes in --symbols-from, or leave out --unambiguous.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/generate/refusals.sh::symbols_that_are_all_lookalikes_are_refused_with_unambiguous.
skarbiec.generate generate-words-over-pool#
draw a password or a passphrase, printed, or written into one field of an item without passing through stdout. Started by skarbiec generate, POST /v1/operator/items/generate, Desktop: Items → a selected item → Replace with a generated value.
What failed: drawing a passphrase. Why: the word pool holds {held} distinct words, fewer than the {count} requested, and a passphrase never repeats a word. What the refusal shows: words from {source}; nothing was drawn or stored.
Fix: ask for --words {held} or fewer.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/generate/refusals.sh::more_words_than_the_pool_holds_are_refused_naming_its_size.
skarbiec.generate generate-rules-absent#
draw a password or a passphrase, printed, or written into one field of an item without passing through stdout. Started by skarbiec generate, POST /v1/operator/items/generate, Desktop: Items → a selected item → Replace with a generated value.
What failed: reading the password rules {id} keeps. Why: {id} keeps no password rules. What the refusal shows: {id}'s context records no password_rules.
Fix: record the site's: skarbiec password rules {id} --set '<rules>', or --lookup to take them from Password Manager Resources.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::rules_of_a_login_keeping_none_is_refused_naming_password_rules_set.
skarbiec.generate generate-policy-uncleared#
draw a password or a passphrase, printed, or written into one field of an item without passing through stdout. Started by skarbiec generate, POST /v1/operator/items/generate, Desktop: Items → a selected item → Replace with a generated value.
What failed: storing a generated value in {id}. Why: the generated value does not clear the vault policy, so nothing was stored. What the refusal shows: policy verdict: {rules}.
Fix: generate a longer value or one with more classes; skarbiec policy get names the rules.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/generate/refusals.sh::a_value_the_policy_refuses_is_not_stored.
skarbiec.generate generate-field-undeclared#
draw a password or a passphrase, printed, or written into one field of an item without passing through stdout. Started by skarbiec generate, POST /v1/operator/items/generate, Desktop: Items → a selected item → Replace with a generated value.
What failed: storing a generated value in {id}'s {field}. Why: a {kind} item has no field {field}, so nothing was stored. What the refusal shows: {id} is a {kind}.
Fix: name a field a {kind} declares, such as password.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/refusals.sh::a_field_the_items_kind_does_not_declare_is_refused.
skarbiec.generate generate-dictionary-unreadable#
draw a password or a passphrase, printed, or written into one field of an item without passing through stdout. Started by skarbiec generate, POST /v1/operator/items/generate, Desktop: Items → a selected item → Replace with a generated value.
What failed: reading the words a passphrase is drawn from. Why: the system dictionary {path} exists and could not be read, and drawing from the small built-in list instead would give a weaker phrase than asked. What the refusal shows: the file system said: {error}; nothing was drawn or stored.
Fix: let this account read {path} (it is the system's word list), or generate a password with skarbiec generate --length <N> instead.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/refusals.sh::a_dictionary_that_cannot_be_read_is_refused_naming_it.
skarbiec.password-rules password-rules-no-site#
read, set, look up or clear the password rules a login keeps for its site. Started by skarbiec password rules, POST /v1/operator/items/password-rules, POST /v1/operator/items/password-rules/change, Desktop: Items → a selected item → Password rules.
What failed: looking up the password rules of {id}'s site. Why: {id} names no site, so no site's rules can be looked up. What the refusal shows: {id}'s context records no domain.
Fix: name the site: skarbiec sites {id} --add <domain>, then look up again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::a_lookup_for_a_login_naming_no_site_is_refused_naming_sites_add.
skarbiec.password-rules password-rules-unlisted#
read, set, look up or clear the password rules a login keeps for its site. Started by skarbiec password rules, POST /v1/operator/items/password-rules, POST /v1/operator/items/password-rules/change, Desktop: Items → a selected item → Password rules.
What failed: looking up the password rules of {id}'s site. Why: Password Manager Resources lists no password rules for {sites}. What the refusal shows: sites {id} names: {sites}.
Fix: record the site's own: skarbiec password rules {id} --set '<rules>'.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/generate/password_rules.sh::a_lookup_for_a_site_the_list_does_not_hold_is_refused_naming_set.
skarbiec.version-open version-open-missing#
open one saved version of an item without making it current. Started by other functionalities only.
What failed: reading the version of {id} saved at {at}. Why: {id} keeps no version saved at {at}. What the refusal shows: saved versions of {id}: {stamps}.
Fix: pick one of the stamps above; skarbiec history {id} lists every version with its stamp.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/get.sh::a_stamp_no_version_has_is_refused_naming_the_stamps_there_are.
skarbiec.version-open version-open-unreadable#
open one saved version of an item without making it current. Started by other functionalities only.
What failed: reading the version of {id} saved at {at}. Why: the version cannot be read. What the refusal shows: item {id}: version {at}; opening it said: {error}.
Fix: skarbiec readers {id} and skarbiec doctor name why a version does not open here; skarbiec history {id} names the other versions there are.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/get.sh::a_damaged_saved_version_is_refused_naming_why.
skarbiec.item-field get-field-missing#
read one text field of an item's opened value. Started by other functionalities only.
What failed: reading {field} of {id}. Why: {id} has no field {field}. What the refusal shows: fields of {id}: {fields}.
Fix: name one of the fields above with --field.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/get.sh::a_field_the_item_does_not_hold_is_refused_naming_its_fields.
skarbiec.item-field get-field-not-text#
read one text field of an item's opened value. Started by other functionalities only.
What failed: reading {field} of {id} as text. Why: {id}'s {field} holds {shape}, not text. What the refusal shows: field {field}: {shape}.
Fix: read the whole item with skarbiec get {id}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/get.sh::a_field_that_is_not_text_is_refused_naming_its_shape.
skarbiec.role get-role-unplayed#
find the one live item carrying stado:role:<role>, for get, an acquisition, a scoped read or a write naming the role. Started by other functionalities only.
What failed: reading the item that plays role {role}. Why: no live item carries stado:role:{role}. What the refusal shows: live items carrying stado:role:{role}: none.
Fix: tag the item that plays it: skarbiec retag --add stado:role:{role} <id>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/get.sh::a_role_no_item_plays_is_refused_naming_the_retag.
skarbiec.role get-role-namesake-untagged#
find the one live item carrying stado:role:<role>, for get, an acquisition, a scoped read or a write naming the role. Started by other functionalities only.
What failed: reading the item that plays role {role}. Why: no live item carries stado:role:{role}, and the live item {role} is named as the role but does not carry its tag. What the refusal shows: live items carrying stado:role:{role}: none; live item {role}: present, without stado:role:{role}.
Fix: give it the role: skarbiec retag --add stado:role:{role} {role}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/get.sh::a_role_its_namesake_item_does_not_carry_is_refused_naming_that_item.
skarbiec.role get-role-several#
find the one live item carrying stado:role:<role>, for get, an acquisition, a scoped read or a write naming the role. Started by other functionalities only.
What failed: reading the item that plays role {role}. Why: {count} live items carry stado:role:{role}, and exactly one item may play a role. What the refusal shows: items carrying stado:role:{role}: {items}.
Fix: take the tag off all but one: skarbiec retag --remove stado:role:{role} <id>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/get.sh::a_role_two_items_play_is_refused_naming_both.
skarbiec.list list-recipient-unknown#
list the items, narrowed by kind, tag, age, text, reader, use or pin, decrypting nothing. Started by skarbiec list, POST /v1/operator/items, Desktop: Items.
What failed: listing the items {uid} can open. Why: {uid} is not a registered recipient, so an empty list would read as shared with nobody. What the refusal shows: registered recipients: {registered}.
Fix: name one of the registered recipients the refusal lists.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/list.sh::an_unregistered_recipient_is_refused_naming_the_registered_ones.
skarbiec.git git-unstarted#
run one git command in a repository and read its answer. Started by other functionalities only.
What failed: asking git {purpose}: {command}. Why: git could not be started, so {purpose} cannot be asked: git is not on this account's PATH, or the file found there is not a program this account may run. What the refusal shows: the system said: {said}.
Fix: install git (on macOS xcode-select --install) or put it on PATH; command -v git names the one that runs.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::a_history_scan_where_git_does_not_start_is_refused_naming_the_command.
skarbiec.git git-refused#
run one git command in a repository and read its answer. Started by other functionalities only.
What failed: asking git {purpose}: {command}. Why: git exited with {status}, so {purpose} could not be read: {directory} is not inside a git repository this account can read, or git could not read it. What the refusal shows: directory: {directory}; git said: {said}.
Fix: run {command} to see git's refusal; name a directory inside a git repository this account can read.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::a_history_scan_of_a_directory_that_is_not_a_repository_is_refused_naming_it.
skarbiec.git git-answer-not-text#
run one git command in a repository and read its answer. Started by other functionalities only.
What failed: asking git {purpose}: {command}. Why: git answered {purpose} in bytes that stop being UTF-8 text at byte {offset}, and a path skarbiec writes to must be text. What the refusal shows: answer: {length} bytes.
Fix: give the repository a hooks directory whose path is UTF-8 text (git config core.hooksPath <path>), then run the same command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::a_hooks_directory_whose_path_is_not_text_is_refused_naming_the_byte.
skarbiec.scan scan-found#
name the files, or the commits, that hold a vault value in plain text, never the value. Started by skarbiec scan, POST /v1/operator/scan, POST /v1/operator/scan-history.
What failed: keeping vault values out of {paths}. Why: a vault value is in plain text: {copies}. What the refusal shows: copies found: {count}.
Fix: remove each copy, or keep the value in the vault and read it through skarbiec exec or skarbiec inject; a value that was committed is replaced with skarbiec rotate.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::a_plain_text_copy_found_with_refuse_is_refused_naming_the_file_line_item_and_field.
skarbiec.scan scan-unread#
name the files, or the commits, that hold a vault value in plain text, never the value. Started by skarbiec scan, POST /v1/operator/scan, POST /v1/operator/scan-history.
What failed: keeping vault values out of {paths}. Why: the scan could not read all it was asked to compare, so it cannot say no copy is there: {unread}. What the refusal shows: files read: {files_read}; paths unread: {paths_unread}; vault items unread: {items_unread}.
Fix: make each unread path readable by this account, or leave it out of the paths named, and open or repair each unread vault item, then scan again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::a_path_the_scan_cannot_read_with_refuse_is_refused_naming_it.
skarbiec.hook hook-present#
install, read or remove the git pre-commit hook that runs scan --refuse over every commit. Started by skarbiec hook install, skarbiec hook status, skarbiec hook uninstall.
What failed: installing the pre-commit hook {hook}. Why: {hook} already holds a pre-commit hook, and installing would write over it. What the refusal shows: {hook} is present.
Fix: add --replace to write this one over it, or keep that hook and call skarbiec scan --refuse from it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::installing_over_another_hook_is_refused_and_the_hook_kept.
skarbiec.hook hook-absent#
install, read or remove the git pre-commit hook that runs scan --refuse over every commit. Started by skarbiec hook install, skarbiec hook status, skarbiec hook uninstall.
What failed: removing the pre-commit hook {hook}. Why: {hook} holds no pre-commit hook, so there is nothing to remove. What the refusal shows: {hook} is absent.
Fix: skarbiec hook status <repo> says whether a hook is there.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::removing_a_hook_that_is_not_there_is_refused.
skarbiec.hook hook-foreign#
install, read or remove the git pre-commit hook that runs scan --refuse over every commit. Started by skarbiec hook install, skarbiec hook status, skarbiec hook uninstall.
What failed: removing the pre-commit hook {hook}. Why: {hook} was not written by skarbiec hook install, so it is left as it is. What the refusal shows: {hook} carries no line saying skarbiec wrote it.
Fix: remove it by hand if it is not wanted; skarbiec hook uninstall removes only a hook it wrote.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::removing_a_hook_another_tool_wrote_is_refused_and_the_hook_kept.
skarbiec.hook hook-binary-unfound#
install, read or remove the git pre-commit hook that runs scan --refuse over every commit. Started by skarbiec hook install, skarbiec hook status, skarbiec hook uninstall.
What failed: writing the pre-commit hook {hook}. Why: the path of the running skarbiec could not be read from the system, and the hook must name the program it runs by its absolute path. What the refusal shows: the system said: {said}; no hook was written.
Fix: run skarbiec hook install from an installed skarbiec whose file is still in place (not deleted or replaced while it runs).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::a_binary_whose_path_cannot_be_read_is_refused.
skarbiec.hook hook-binary-unnameable#
install, read or remove the git pre-commit hook that runs scan --refuse over every commit. Started by skarbiec hook install, skarbiec hook status, skarbiec hook uninstall.
What failed: writing the pre-commit hook {hook}. Why: this binary's path {binary} holds a quote the hook could not name it with. What the refusal shows: binary: {binary}.
Fix: install skarbiec where its path holds no quote, and install the hook again from there.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/scan/refusals.sh::a_binary_whose_path_holds_a_quote_is_refused_naming_it.
skarbiec.grant.record grant-none#
read a grant verb's command line and the grant the vault records for one consumer. Started by other functionalities only.
What failed: {doing} {consumer}'s grant. Why: consumer {consumer} has no grant in {vault}. What the refusal shows: nothing was changed.
Fix: grant it first with skarbiec grant issue {consumer}; skarbiec grant list names the consumers that hold one.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_keep.sh::a_consumer_with_no_grant_is_refused_naming_it.
skarbiec.grant.record grant-legacy#
read a grant verb's command line and the grant the vault records for one consumer. Started by other functionalities only.
What failed: {doing} {consumer}'s grant. Why: the grant records no capabilities list: it is a grant of an older vault version. What the refusal shows: grant: {grant}.
Fix: run skarbiec upgrade --apply, which writes every grant as this version reads it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/issue.sh::a_grant_recorded_before_capabilities_is_refused_naming_upgrade.
skarbiec.grant.record grant-damaged#
read a grant verb's command line and the grant the vault records for one consumer. Started by other functionalities only.
What failed: {doing} {consumer}'s grant. Why: the grant {why}, which every grant this version writes records. What the refusal shows: nothing was changed.
Fix: issue it again with skarbiec grant issue {consumer} --replace-capabilities, or put back the vault a backup keeps (skarbiec backup restore).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/issue.sh::a_grant_recording_no_expiry_is_refused_naming_it.
skarbiec.grant.record grant-expiry-overflow#
read a grant verb's command line and the grant the vault records for one consumer. Started by other functionalities only.
What failed: reading how long the grant lasts. Why: --ttl-seconds {ttl} ends past the last second a grant can record. What the refusal shows: nothing was granted.
Fix: state a lifetime in whole seconds that ends within this era, or --until-revoked.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/issue.sh::a_lifetime_past_the_last_second_is_refused.
skarbiec.grant grant-verify-token-in-argv#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: reading the bearer grant verify checks. Why: grant verify does not take --token: a bearer on the command line is readable by every process on this host (ps lists it), so it is never read from there. What the refusal shows: --token was given; its value is not shown, and nothing was checked.
Fix: write the bearer to an owner-only file (chmod 600) and run it as skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/issue.sh::a_bearer_given_on_the_command_line_is_refused_naming_token_file.
skarbiec.grant grant-acquire-mixed#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: issuing {consumer}'s grant. Why: acquire capabilities cannot share a grant with direct ones: an acquire grant mints no bearer and lends its lifetime to the one-use tokens a workload's proof earns, while a direct capability is spent with a bearer. What the refusal shows: --capabilities {requested}; nothing was granted.
Fix: issue the acquire capabilities to one consumer and the direct ones to another (skarbiec grant issue <consumer> --capabilities ...).
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/issue.sh::acquire_and_direct_capabilities_in_one_grant_are_refused.
skarbiec.grant grant-lifecycle-with-read#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: issuing {consumer}'s grant. Why: a lifecycle capability cannot share a grant with a read: driving a credential's rotation never authorizes reading the value it rotates, so one bearer never does both. What the refusal shows: --capabilities {requested}; nothing was granted.
Fix: issue the lifecycle capabilities to one consumer and the reads to another (skarbiec grant issue <consumer> --capabilities ...).
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/issue.sh::lifecycle_and_read_capabilities_in_one_grant_are_refused.
skarbiec.grant grant-workload-key-without-acquire#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: issuing {consumer}'s grant. Why: a workload public key is valid only for acquire capabilities, and {requested} names none. What the refusal shows: --workload-public-key-file {path}; nothing was granted.
Fix: drop --workload-public-key-file, or name acquire:<item>#<field> capabilities.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/issue.sh::a_workload_key_without_an_acquire_capability_is_refused.
skarbiec.grant grant-acquire-without-workload-key#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: issuing {consumer}'s grant. Why: the acquire capabilities {requested} need the workload's public key: the workload proves each acquisition with its key pair. What the refusal shows: no --workload-public-key-file was given; nothing was granted.
Fix: name the PEM file of the workload's public key with --workload-public-key-file <path>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/issue.sh::an_acquire_capability_without_a_workload_key_is_refused.
skarbiec.grant grant-change-unstated#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: issuing {consumer}'s grant. Why: grant issue refuses to change existing capabilities without --replace-capabilities. What the refusal shows: {consumer} holds {held}; the call names {requested}.
Fix: run it again with --replace-capabilities to replace them, or name the capabilities it holds.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/grant/issue.sh::a_changed_capability_set_without_replace_capabilities_is_refused.
skarbiec.grant grant-inactive#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: widening {consumer}'s grant. Why: consumer grant is expired or inactive: it ended at {expires_at}. What the refusal shows: nothing was changed.
Fix: make it live again with skarbiec grant keep {consumer}, or issue it again with skarbiec grant issue {consumer}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/grant/issue.sh::ensuring_a_read_on_an_ended_grant_is_refused.
skarbiec.grant grant-bearer-mismatch#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: widening {consumer}'s grant. Why: the bearer presented does not match the consumer's recorded bearer. What the refusal shows: {presented}; nothing was changed.
Fix: name the file holding the bearer {consumer} was issued, or its SHA-256 with --token-sha256, or issue it again with skarbiec grant issue {consumer}.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/grant/issue.sh::ensuring_with_another_bearer_is_refused.
skarbiec.grant grant-keep-no-workload-key#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: keeping {consumer}'s grant. Why: consumer {consumer}'s acquire grant records no workload key, so no workload can prove it. What the refusal shows: nothing was changed.
Fix: issue {consumer} the grant again with skarbiec grant issue {consumer} --capabilities <capabilities> --workload-public-key-file <pem> --until-revoked --replace-capabilities, which binds its workload key.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_keep.sh::keeping_an_acquire_grant_bound_to_no_workload_key_is_refused.
skarbiec.grant grant-keep-no-bearer#
declare a consumer's grant and its bearer, widen it by one read or narrow it by one, make it live until revoked, move it to another item, list the grants, and check one bearer against one question. Started by skarbiec grant issue, skarbiec grant ensure, skarbiec grant narrow, skarbiec grant keep, skarbiec grant retarget, skarbiec grant list, skarbiec grant verify.
What failed: keeping {consumer}'s grant. Why: consumer {consumer}'s grant records no bearer, so a consumer holds nothing it could keep presenting. What the refusal shows: nothing was changed.
Fix: issue it with skarbiec grant issue {consumer} --until-revoked.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_keep.sh::keeping_a_grant_that_records_no_bearer_is_refused.
skarbiec.grant-access grant-required#
admit a consumer's call to the local API only where a grant of the vault covers it. Started by POST /v1/items/list, POST /v1/items/read, POST /v1/items/revision, PUT /v1/items (mode stage), PUT /v1/items (mode acquire), PUT /v1/items (mode rotate), DELETE /v1/items, POST /v1/tokens/introspect, POST /v1/offers, POST /v1/donations, POST /v1/access-requests, GET /v1/vault, POST /v1/enroll, GET /list, GET /audit.
What failed: letting consumer {consumer} {action} {coordinate}. Why: no grant of this vault lets {consumer} {action} {coordinate}: the live grant {consumer} presented the bearer of holds no capability for that. What the refusal shows: consumer: {consumer}; action: {action}; coordinate: {coordinate}.
Fix: ask the vault's owner for the grant: skarbiec request file --kind secret --resource {coordinate} --action {action} --for-consumer {consumer} --agent <who asks> --reason <why>, on the vault host, or from another host with --to <this API's base URL> --consumer <name> --token-file <path>; a person with role owner or admin answers it with skarbiec request approve; skarbiec grant list shows what {consumer} holds.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_required.sh::a_call_with_no_grant_names_the_consumer_the_coordinate_and_the_request_that_asks_for_it.
skarbiec.grant-access vault-grant-required#
admit a consumer's call to the local API only where a grant of the vault covers it. Started by POST /v1/items/list, POST /v1/items/read, POST /v1/items/revision, PUT /v1/items (mode stage), PUT /v1/items (mode acquire), PUT /v1/items (mode rotate), DELETE /v1/items, POST /v1/tokens/introspect, POST /v1/offers, POST /v1/donations, POST /v1/access-requests, GET /v1/vault, POST /v1/enroll, GET /list, GET /audit.
What failed: letting consumer {consumer} {action} {target}. Why: no grant of this vault lets {consumer} {action} {target}: the live grant {consumer} presented the bearer of holds no {action}:{target} capability. What the refusal shows: consumer: {consumer}; capability it lacks: {action}:{target}.
Fix: the vault's owner adds the capability on the vault host: skarbiec grant issue {consumer} --capabilities {action}:{target},<every capability skarbiec grant list shows {consumer} holding> --replace-capabilities (--ttl-seconds <N> | --until-revoked), which rotates its bearer.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_required.sh::a_vault_call_with_no_grant_names_the_consumer_and_the_capability_it_lacks.
skarbiec.grant-access bearer-unrecognized#
admit a consumer's call to the local API only where a grant of the vault covers it. Started by POST /v1/items/list, POST /v1/items/read, POST /v1/items/revision, PUT /v1/items (mode stage), PUT /v1/items (mode acquire), PUT /v1/items (mode rotate), DELETE /v1/items, POST /v1/tokens/introspect, POST /v1/offers, POST /v1/donations, POST /v1/access-requests, GET /v1/vault, POST /v1/enroll, GET /list, GET /audit.
What failed: letting consumer {consumer} {action} {coordinate}. Why: the bearer {consumer} presented is no live grant of this vault: {consumer} holds no grant here, or its grant ended, was revoked or was issued again with another bearer. What the refusal shows: consumer: {consumer}; action: {action}; coordinate: {coordinate}; no capability was judged.
Fix: present the bearer of {consumer}'s live grant; skarbiec grant list shows whether {consumer} holds one and until when, and the vault's owner issues one with skarbiec grant issue {consumer} --capabilities <capabilities> (--ttl-seconds <N> | --until-revoked).
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_required.sh::a_bearer_that_is_no_live_grant_is_refused_naming_the_bearer_not_a_capability.
skarbiec.grant-access not-this-writer#
admit a consumer's call to the local API only where a grant of the vault covers it. Started by POST /v1/items/list, POST /v1/items/read, POST /v1/items/revision, PUT /v1/items (mode stage), PUT /v1/items (mode acquire), PUT /v1/items (mode rotate), DELETE /v1/items, POST /v1/tokens/introspect, POST /v1/offers, POST /v1/donations, POST /v1/access-requests, GET /v1/vault, POST /v1/enroll, GET /list, GET /audit.
What failed: staging {field} of {item} for consumer {consumer}. Why: stage writes only an item Weles manages that {consumer} itself wrote, and {item} is not one. What the refusal shows: {item} managed by Weles: {managed}; its writer: {writer}.
Fix: stage as the writer {item} names, or change it as its owner with skarbiec set {item}; skarbiec history {item} names who wrote each revision.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_required.sh::a_stage_of_an_item_another_writer_controls_names_the_writer_it_has.
skarbiec.grant-access lifecycle-record#
admit a consumer's call to the local API only where a grant of the vault covers it. Started by POST /v1/items/list, POST /v1/items/read, POST /v1/items/revision, PUT /v1/items (mode stage), PUT /v1/items (mode acquire), PUT /v1/items (mode rotate), DELETE /v1/items, POST /v1/tokens/introspect, POST /v1/offers, POST /v1/donations, POST /v1/access-requests, GET /v1/vault, POST /v1/enroll, GET /list, GET /audit.
What failed: {doing} {item} through the item API for consumer {consumer}. Why: {item} is a credential operation record or a sealed directory contract, which only the credential lifecycle writes. What the refusal shows: {item}: kind {kind}, controlled by the credential lifecycle.
Fix: act on the credential by its role: skarbiec credential status role:<role> reads its operation, and the lifecycle's own commands (credential acquire, rotate, reset, remove) change it.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_required.sh::a_lifecycle_record_is_refused_through_the_item_api_naming_what_changes_it.
skarbiec.grant-access browser-request#
admit a consumer's call to the local API only where a grant of the vault covers it. Started by POST /v1/items/list, POST /v1/items/read, POST /v1/items/revision, PUT /v1/items (mode stage), PUT /v1/items (mode acquire), PUT /v1/items (mode rotate), DELETE /v1/items, POST /v1/tokens/introspect, POST /v1/offers, POST /v1/donations, POST /v1/access-requests, GET /v1/vault, POST /v1/enroll, GET /list, GET /audit.
What failed: admitting {method} {path}. Why: {reason}. What the refusal shows: {method} {path}, refused before its body was read.
Fix: call Skarbiec from a local program at its loopback address (127.0.0.1 or localhost), with no Origin or Sec-Fetch-Site header and, for an operator POST, Content-Type: application/json; a web page cannot reach it.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_required.sh::a_request_a_web_page_sent_is_refused_naming_why_before_any_route_reads_it.
skarbiec.grant.capability grant-capability-expiry-overflow#
issue one capability an agent may redeem a set number of times before it expires, for a resource the vault resolves to a credential that holds a value. Started by skarbiec grant capability, POST /v1/operator/grants/capability.
What failed: reading how long the capability lives. Why: --ttl {ttl} ends past the last second a capability can record. What the refusal shows: nothing was issued.
Fix: state a lifetime in whole seconds that ends within this era.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/grants/grant_capability.sh::a_lifetime_past_the_last_second_is_refused.
skarbiec.grant.register grant-catalog-relative#
declare one workload-bound acquire grant for every consumer|item|field row of an acquisition catalog, all bound to one workload key and one lifetime. Started by skarbiec grant register.
What failed: reading the acquisition catalog {path}. Why: acquisition catalog path must be absolute, and {path} is relative. What the refusal shows: nothing was registered.
Fix: name the catalog by its absolute path, e.g. $PWD/{path}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/register.sh::a_relative_catalog_path_is_refused.
skarbiec.grant.register grant-catalog-unsafe#
declare one workload-bound acquire grant for every consumer|item|field row of an acquisition catalog, all bound to one workload key and one lifetime. Started by skarbiec grant register.
What failed: reading the acquisition catalog {path}. Why: acquisition catalog must be an owner-controlled regular file: {held}. What the refusal shows: nothing was registered.
Fix: name a regular file this account owns, not a link or a directory.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/register.sh::a_catalog_that_is_a_directory_is_refused_naming_it.
skarbiec.grant.register grant-catalog-row#
declare one workload-bound acquire grant for every consumer|item|field row of an acquisition catalog, all bound to one workload key and one lifetime. Started by skarbiec grant register.
What failed: reading line {number} of the acquisition catalog {path}. Why: the row is not consumer|item|field, each an exact name: {what}. What the refusal shows: line {number}: {line}; nothing was registered.
Fix: write each row as consumer|item|field (item may be role:<role>), each name exact, each consumer once.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/register.sh::a_catalog_row_that_is_not_consumer_item_field_is_refused_naming_its_line.
skarbiec.grant.register grant-catalog-row-duplicate#
declare one workload-bound acquire grant for every consumer|item|field row of an acquisition catalog, all bound to one workload key and one lifetime. Started by skarbiec grant register.
What failed: reading line {number} of the acquisition catalog {path}. Why: an earlier line of the catalog holds this same row, and each grant is registered once. What the refusal shows: line {number}: {line}; nothing was registered.
Fix: remove line {number} from {path}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/register.sh::a_catalog_row_given_twice_is_refused_naming_its_line.
skarbiec.grant.register grant-catalog-consumer-twice#
declare one workload-bound acquire grant for every consumer|item|field row of an acquisition catalog, all bound to one workload key and one lifetime. Started by skarbiec grant register.
What failed: reading line {number} of the acquisition catalog {path}. Why: an earlier line already names the consumer {what}, and each consumer's acquire grant names one exact field. What the refusal shows: line {number}: {line}; nothing was registered.
Fix: keep one row for {what} in {path}: grep -n '^{what}|' {path} names both.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/register.sh::a_catalog_naming_one_consumer_twice_is_refused_naming_its_line.
skarbiec.grant.register grant-catalog-empty#
declare one workload-bound acquire grant for every consumer|item|field row of an acquisition catalog, all bound to one workload key and one lifetime. Started by skarbiec grant register.
What failed: reading the acquisition catalog {path}. Why: acquisition catalog cannot be empty: it holds no row, only blank lines and # comments. What the refusal shows: nothing was registered.
Fix: write one consumer|item|field row for each workload-bound acquire grant to register.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/register.sh::an_empty_catalog_is_refused.
skarbiec.grant.register grant-register-differs#
declare one workload-bound acquire grant for every consumer|item|field row of an acquisition catalog, all bound to one workload key and one lifetime. Started by skarbiec grant register.
What failed: registering {consumer}'s acquire grant. Why: {consumer} differs from the acquisition catalog; pass --replace-capabilities to replace what it holds. What the refusal shows: {consumer} holds {held}; nothing was registered.
Fix: run grant register again with --replace-capabilities, or leave {consumer} out of the catalog.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/grant/register.sh::another_key_is_refused_without_replace_capabilities.
skarbiec.grant.declaration grant-capability-field-missing#
read the capabilities a grant names against the vault, the bearer file a consumer holds and the workload's public key, before anything is granted. Started by other functionalities only.
What failed: granting {capability}. Why: {item} holds no field {field}, and its kind does not let {action} create one. What the refusal shows: nothing was granted.
Fix: skarbiec kinds lists the fields each kind takes; name one {item} holds, or add it with skarbiec field set {item} {field}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/grant/declaration.sh::a_capability_naming_a_field_the_item_lacks_is_refused.
skarbiec.grant.declaration grant-capability-item-missing#
read the capabilities a grant names against the vault, the bearer file a consumer holds and the workload's public key, before anything is granted. Started by other functionalities only.
What failed: granting {capability}. Why: this vault holds no item {item}, and {action} reaches only an item that exists. What the refusal shows: nothing was granted.
Fix: name an item the vault holds (skarbiec list names them), or a role as role:<role> for acquire, read, stage or rotate.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/grant/declaration.sh::a_capability_naming_an_item_the_vault_lacks_is_refused.
skarbiec.grant.declaration grant-capability-tag-family-undeclared#
read the capabilities a grant names against the vault, the bearer file a consumer holds and the workload's public key, before anything is granted. Started by other functionalities only.
What failed: granting {capability}. Why: {family} is not a tag family the tag registry declares, and a grant names a family only by a registered namespace, never a pattern of its own. What the refusal shows: declared families (owner): {declared}; nothing was granted.
Fix: name one of the declared families as tag-family:<family> (skarbiec tags lists each with its owner and meaning), or name one exact tag as tag:<tag>; a new family is registered in Skarbiec's tag registry by the product that writes it.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/grant/tag_family.sh::a_capability_naming_an_undeclared_tag_family_is_refused.
skarbiec.grant.declaration grant-token-file-unsafe#
read the capabilities a grant names against the vault, the bearer file a consumer holds and the workload's public key, before anything is granted. Started by other functionalities only.
What failed: reading the token file {path}. Why: it must be a regular file this account owns that no group or other user can read. What the refusal shows: {path}: {held}.
Fix: chmod go-rwx {path}, or name a regular file this account owns.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/declaration.sh::a_token_file_others_can_read_is_refused_naming_it.
skarbiec.grant.declaration grant-token-file-malformed#
read the capabilities a grant names against the vault, the bearer file a consumer holds and the workload's public key, before anything is granted. Started by other functionalities only.
What failed: reading the token file {path}. Why: it must hold one token with no whitespace in it, and holds {held}. What the refusal shows: nothing was granted or checked.
Fix: write the one bearer to {path}, alone on its line.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/declaration.sh::a_token_file_holding_no_one_token_is_refused.
skarbiec.grant.declaration grant-workload-key-unsafe#
read the capabilities a grant names against the vault, the bearer file a consumer holds and the workload's public key, before anything is granted. Started by other functionalities only.
What failed: reading the workload public key {path}. Why: it must be a regular file this account owns that no group or other user can write or read. What the refusal shows: {path}: {held}.
Fix: chmod go-rwx {path}, or name a regular file this account owns.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/declaration.sh::a_workload_key_file_others_can_read_is_refused_naming_it.
skarbiec.grant.declaration grant-workload-key-not-pem#
read the capabilities a grant names against the vault, the bearer file a consumer holds and the workload's public key, before anything is granted. Started by other functionalities only.
What failed: reading the workload public key {path}. Why: it holds no PEM public key: no -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- lines. What the refusal shows: nothing was granted.
Fix: name the public half of the workload's Ed25519 key pair in PEM form (openssl pkey -pubout writes it).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/grant/declaration.sh::a_workload_key_file_that_is_not_pem_is_refused_naming_it.
skarbiec.helper.aws helper-aws-static-key-config#
make an AWS profile's credential_process read an access-key item, move a profile's key out of the shared credentials file into the vault, stop it, and answer AWS. Started by skarbiec helper setup aws, skarbiec helper import aws, skarbiec helper unset aws, skarbiec helper answer aws.
What failed: pointing AWS profile {profile} at this vault. Why: profile {profile} keeps a key in {file} itself, and AWS uses it before any credential_process, so the vault would never be asked. What the refusal shows: {file}: {header} sets aws_access_key_id; nothing was changed.
Fix: remove the profile's aws_access_key_id and aws_secret_access_key lines from {file}, then run skarbiec helper setup aws <id> --profile {profile} again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/aws_credential.sh::a_profile_keeping_a_key_in_the_config_file_is_refused_naming_the_lines.
skarbiec.helper.aws helper-aws-profile-absent#
make an AWS profile's credential_process read an access-key item, move a profile's key out of the shared credentials file into the vault, stop it, and answer AWS. Started by skarbiec helper setup aws, skarbiec helper import aws, skarbiec helper unset aws, skarbiec helper answer aws.
What failed: {doing} AWS profile {profile}. Why: {file} has no {header} section. What the refusal shows: profiles there: {profiles}; nothing was changed.
Fix: name a profile the file holds (skarbiec helper status aws lists the ones that read this vault).
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/aws_credential.sh::a_profile_the_file_lacks_is_refused_naming_the_profiles_it_holds.
skarbiec.helper.aws helper-aws-process-absent#
make an AWS profile's credential_process read an access-key item, move a profile's key out of the shared credentials file into the vault, stop it, and answer AWS. Started by skarbiec helper setup aws, skarbiec helper import aws, skarbiec helper unset aws, skarbiec helper answer aws.
What failed: unsetting AWS profile {profile}'s credential_process. Why: profile {profile} in {file} runs no credential_process, so there is nothing of this vault's to unset. What the refusal shows: {file}: {header}; nothing was changed.
Fix: skarbiec helper status aws lists the profiles that read this vault.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/aws_credential.sh::unsetting_a_profile_without_a_credential_process_is_refused.
skarbiec.helper.aws helper-aws-process-foreign#
make an AWS profile's credential_process read an access-key item, move a profile's key out of the shared credentials file into the vault, stop it, and answer AWS. Started by skarbiec helper setup aws, skarbiec helper import aws, skarbiec helper unset aws, skarbiec helper answer aws.
What failed: unsetting AWS profile {profile}'s credential_process. Why: profile {profile}'s credential_process in {file} is not this vault's, so it is left alone. What the refusal shows: the line: {line}; nothing was changed.
Fix: remove that line from {file} by hand when that other program is no longer wanted.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/aws_credential.sh::unsetting_another_programs_credential_process_is_refused_naming_it.
skarbiec.helper.aws helper-aws-import-key-missing#
make an AWS profile's credential_process read an access-key item, move a profile's key out of the shared credentials file into the vault, stop it, and answer AWS. Started by skarbiec helper setup aws, skarbiec helper import aws, skarbiec helper unset aws, skarbiec helper answer aws.
What failed: importing the key of AWS profile {profile}. Why: [{profile}] in {file} keeps no {key}, and an access-key item needs both the key id and its secret. What the refusal shows: [{profile}] sets: {keys}; nothing was changed.
Fix: import a profile whose section sets aws_access_key_id and aws_secret_access_key, or keep the key with skarbiec set.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/aws_credential.sh::importing_a_profile_without_its_secret_is_refused_naming_the_key.
skarbiec.helper.cargo helper-cargo-providers-set#
name this vault as Cargo's token-from-stdout provider, move a token credentials.toml keeps into the vault, stop it, and answer Cargo with the token of the login offered on the index host. Started by skarbiec helper setup cargo, skarbiec helper import cargo, skarbiec helper unset cargo, skarbiec helper answer cargo.
What failed: naming this vault in Cargo's {file}. Why: {file} already sets `{other}`, a global-credential-providers list of its own, and Cargo reads one. What the refusal shows: {file}: `{other}`; nothing was changed.
Fix: add this vault's provider to that list by hand: {line}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/cargo_credential.sh::a_config_already_setting_providers_is_refused_naming_the_line_to_add.
skarbiec.helper.cargo helper-cargo-path-not-text#
name this vault as Cargo's token-from-stdout provider, move a token credentials.toml keeps into the vault, stop it, and answer Cargo with the token of the login offered on the index host. Started by skarbiec helper setup cargo, skarbiec helper import cargo, skarbiec helper unset cargo, skarbiec helper answer cargo.
What failed: naming this skarbiec in Cargo's provider line. Why: this binary's path stops being UTF-8 text at byte {offset}, and Cargo's config.toml is text. What the refusal shows: binary path: {length} bytes; nothing was changed.
Fix: install skarbiec under a path that is UTF-8 text, then run skarbiec helper setup cargo from there.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/cargo_credential.sh::a_binary_path_that_is_not_text_is_refused_naming_the_byte.
skarbiec.helper.cargo helper-cargo-path-uncarriable#
name this vault as Cargo's token-from-stdout provider, move a token credentials.toml keeps into the vault, stop it, and answer Cargo with the token of the login offered on the index host. Started by skarbiec helper setup cargo, skarbiec helper import cargo, skarbiec helper unset cargo, skarbiec helper answer cargo.
What failed: naming this skarbiec in Cargo's provider line. Why: this binary's path {binary} holds a {what}, and Cargo splits the token-from-stdout provider's command at spaces inside one quoted string. What the refusal shows: binary path: {binary}; nothing was changed.
Fix: install skarbiec under a path without spaces or quotes (command -v skarbiec names where it runs from), then run skarbiec helper setup cargo from there.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/cargo_credential.sh::a_binary_path_holding_a_space_is_refused_naming_it.
skarbiec.helper.cargo helper-cargo-index-unnamed#
name this vault as Cargo's token-from-stdout provider, move a token credentials.toml keeps into the vault, stop it, and answer Cargo with the token of the login offered on the index host. Started by skarbiec helper setup cargo, skarbiec helper import cargo, skarbiec helper unset cargo, skarbiec helper answer cargo.
What failed: answering Cargo with a registry's token. Why: CARGO_REGISTRY_INDEX_URL names no registry index: skarbiec helper answer cargo is Cargo's provider, and Cargo sets it to the index it publishes to. What the refusal shows: CARGO_REGISTRY_INDEX_URL: unset or blank; nothing was read.
Fix: let Cargo run it (cargo publish, owner or yank), or set CARGO_REGISTRY_INDEX_URL=sparse+https://<index host>/ to ask by hand.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/cargo_credential.sh::an_answer_without_an_index_is_refused_naming_the_variable.
skarbiec.helper.cargo helper-cargo-index-not-address#
name this vault as Cargo's token-from-stdout provider, move a token credentials.toml keeps into the vault, stop it, and answer Cargo with the token of the login offered on the index host. Started by skarbiec helper setup cargo, skarbiec helper import cargo, skarbiec helper unset cargo, skarbiec helper answer cargo.
What failed: answering Cargo with a registry's token. Why: the index {url} holds no ://, so it names no host to find the registry's login by. What the refusal shows: CARGO_REGISTRY_INDEX_URL={url}; nothing was read.
Fix: set CARGO_REGISTRY_INDEX_URL to the index's address, sparse+https://<index host>/ or https://<index host>/.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/cargo_credential.sh::an_index_that_is_no_address_is_refused_naming_it.
skarbiec.helper.docker docker-config-unlocated#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: finding Docker's config.json. Why: neither DOCKER_CONFIG nor HOME names where Docker keeps it. What the refusal shows: nothing was changed.
Fix: set DOCKER_CONFIG to the directory Docker reads config.json from, or HOME to the account's home.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_docker_config_nothing_locates_is_refused_naming_both_variables.
skarbiec.helper.docker docker-config-unreadable#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: reading Docker's {file}. Why: {error}. What the refusal shows: nothing was changed.
Fix: let this account read {file}, or point DOCKER_CONFIG at the directory holding the config.json Docker uses.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_docker_config_that_cannot_be_read_is_refused_naming_it.
skarbiec.helper.docker docker-config-not-json#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: reading Docker's {file} at line {line} column {column}. Why: it is not JSON: {error}. What the refusal shows: nothing was changed.
Fix: correct {file} at line {line} column {column}; docker login writes it again when it is removed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_docker_config_that_is_not_json_is_refused_naming_its_line.
skarbiec.helper.docker docker-config-not-object#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: reading Docker's {file}. Why: {member} is {held}, where Docker keeps one JSON object. What the refusal shows: nothing was changed.
Fix: correct {member} in {file} into an object as Docker writes it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_docker_config_of_another_shape_is_refused_naming_the_member.
skarbiec.helper.docker docker-config-unwritable#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: writing Docker's {file}. Why: {error}. What the refusal shows: Docker's {file} is as it was.
Fix: let this account write {file} and its directory.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_docker_config_that_cannot_be_written_is_refused_naming_it.
skarbiec.helper.docker docker-link-dir-invalid#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: linking docker-credential-skarbiec into {dir}. Why: --link {dir} is not an existing directory named by an absolute path. What the refusal shows: nothing was changed.
Fix: name with --link an absolute directory that exists and is on PATH, such as ~/.local/bin.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_link_directory_that_is_not_an_absolute_directory_is_refused.
skarbiec.helper.docker docker-binary-unlocated#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: finding this skarbiec binary for Docker to run. Why: {error}. What the refusal shows: nothing was changed.
Fix: run skarbiec by the path it is installed at, then set the helper up again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_binary_that_cannot_name_its_own_path_is_refused.
skarbiec.helper.docker docker-link-taken#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: linking docker-credential-skarbiec into {dir}. Why: {program} is already there: {held}. What the refusal shows: nothing was changed.
Fix: remove {program} or name another directory with --link.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_link_name_another_program_holds_is_refused_naming_it.
skarbiec.helper.docker docker-link-unwritable#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: linking {program} to this skarbiec binary. Why: {error}. What the refusal shows: nothing was changed.
Fix: let this account write {dir}, or name another directory on PATH with --link.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_link_directory_this_account_cannot_write_is_refused_naming_it.
skarbiec.helper.docker docker-unset-none#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: unsetting the Docker helper for {registry}. Why: Docker's {file} names no credential helper for {registry}. What the refusal shows: nothing was changed.
Fix: name a registry skarbiec helper status lists under docker.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::unsetting_a_registry_docker_sends_nowhere_is_refused_naming_it.
skarbiec.helper.docker docker-import-no-sign-in#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: importing {registry}'s sign-in from Docker's {file}. Why: the file keeps no sign-in for {registry} under auths. What the refusal shows: nothing was changed.
Fix: sign in with docker login {registry} first, or name a registry under auths in {file}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::importing_a_registry_docker_keeps_no_sign_in_for_is_refused.
skarbiec.helper.docker docker-import-sign-in-malformed#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: importing {registry}'s sign-in from Docker's {file}. Why: its auth {why}, where Docker keeps base64 of username:password. What the refusal shows: nothing was changed.
Fix: sign in again with docker login {registry}, which writes the auth anew, then import it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_sign_in_that_is_not_base64_of_a_username_and_password_is_refused.
skarbiec.helper.docker docker-import-readback#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: checking {id} holds {registry}'s password. Why: {id} was written but reads back another password. What the refusal shows: Docker's {file} is as it was.
Fix: read {id} with skarbiec history {id} to see which write took its place, and import again under another id.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::an_import_overtaken_before_it_reads_back_is_refused.
skarbiec.helper.docker docker-import-auths-vanished#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: taking {registry}'s sign-in out of Docker's {file}. Why: the sign-in left auths while it was imported, written by something else. What the refusal shows: {id} holds it and Docker asks this vault for {registry}.
Fix: check {file} is the config.json Docker reads; nothing more is to be done.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_sign_in_removed_by_another_writer_during_import_is_named.
skarbiec.helper.docker docker-request-unreadable#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: reading Docker's request on standard input. Why: {error}. What the refusal shows: nothing was answered.
Fix: let Docker start the helper, which writes the registry on its standard input as UTF-8 text.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_request_that_is_not_text_is_refused.
skarbiec.helper.docker docker-request-empty#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: answering Docker's get. Why: the request names no registry. What the refusal shows: nothing was answered.
Fix: send the registry's address on standard input, as Docker does: echo <registry> | skarbiec helper answer docker get.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_get_naming_no_registry_is_refused.
skarbiec.helper.docker docker-store-refused#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: storing what docker login sends. Why: the vault keeps its own values, so docker login does not store into it. What the refusal shows: nothing was stored.
Fix: store the registry's token in a login offered on the registry with skarbiec set <id> --type login.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::docker_login_storing_into_the_vault_is_refused_naming_set.
skarbiec.helper.docker docker-erase-refused#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: erasing what docker logout asks. Why: the vault keeps its own values, so docker logout does not erase them. What the refusal shows: nothing was erased.
Fix: remove the registry's login with skarbiec delete <id>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::docker_logout_erasing_from_the_vault_is_refused_naming_delete.
skarbiec.helper.docker docker-list-refused#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: listing what Docker asks. Why: the helper answers one registry at a time through get and lists none. What the refusal shows: nothing was listed.
Fix: ask for one registry with get; skarbiec helper status lists the registries Docker sends here.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::docker_listing_the_vault_is_refused.
skarbiec.helper.docker docker-not-found#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: answering Docker's get for {server}. Why: {why}. What the refusal shows: stdout: credentials not found in native keychain, which Docker reads as nothing here.
Fix: offer a login on {server}: skarbiec set <id> --type login with context.domains naming {server}, or helper import docker.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_registry_no_login_is_offered_on_is_answered_not_found.
skarbiec.helper.docker docker-login-unusable#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: answering Docker's get for {server}. Why: login get answered {why}. What the refusal shows: nothing was answered.
Fix: run skarbiec login get {server} --field username to see what it answers, and install a release whose login get names its item.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_login_answer_without_its_item_is_refused.
skarbiec.helper.docker docker-answer-unwritten#
make Docker ask this vault for a registry's sign-in, move the one docker login left in config.json into a login, stop it, and answer Docker's get with the login the vault offers on the registry. Started by skarbiec helper setup docker, skarbiec helper import docker, skarbiec helper unset docker, skarbiec helper answer docker, docker-credential-skarbiec.
What failed: handing {server}'s credential to Docker. Why: {error}. What the refusal shows: Docker received no credential.
Fix: let Docker start the helper with its standard output connected; a docker command that went away asks again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::an_answer_docker_no_longer_reads_is_refused.
skarbiec.helper.git helper-git-config-refused#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: {doing} in git's global configuration. Why: git config ended with {ended} saying why: the global configuration file is not one git can read or write. What the refusal shows: command: {command}; git said: {said}; nothing was changed.
Fix: run {command} to see the line git stops at, repair ~/.gitconfig (or the file GIT_CONFIG_GLOBAL names), then run the same skarbiec helper command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_global_git_configuration_git_cannot_read_is_refused_in_gits_words.
skarbiec.helper.git helper-git-request-line-unshaped#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: reading git's credential request. Why: line {number} of the request holds no '=', and git writes every line of a request as key=value. What the refusal shows: the line: {bytes} bytes, not shown as it may hold a password; nothing was answered.
Fix: run git with GIT_TRACE=1 to see what calls the helper; only git, or a program speaking its credential protocol, may run skarbiec helper answer git.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_request_line_that_is_not_key_value_is_refused_without_showing_it.
skarbiec.helper.git helper-git-request-member-missing#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: reading git's credential request. Why: the request names no {member}, which git writes in every request for a credential over https. What the refusal shows: the request's keys: {keys}; nothing was answered.
Fix: run git with GIT_TRACE=1 to see what calls the helper; git names protocol and host in every request.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_request_naming_no_host_is_refused_naming_the_keys.
skarbiec.helper.git helper-git-protocol-insecure#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: answering git's request for {protocol}://{host}. Why: git asks for a password to send over {protocol}, and skarbiec answers only https, where it is not sent in the clear. What the refusal shows: protocol: {protocol}; host: {host}; nothing was answered.
Fix: use the https:// address of the repository (git remote set-url origin https://{host}/...).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_request_over_plain_http_is_refused_naming_https.
skarbiec.helper.git helper-git-value-uncarriable#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: answering git's request for {site} with {item}. Why: {item}'s {field} holds a {what}, and git's credential protocol carries one line per value. What the refusal shows: {field}: {length} characters, not shown; nothing was answered.
Fix: store the {field} without line breaks or NUL in {item} (skarbiec field set {item} {field} < file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_login_whose_password_holds_a_line_break_is_refused_naming_the_field.
skarbiec.helper.git helper-git-password-not-text#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: answering git's request for {site} with {item}. Why: {item}'s password is {shape}, and git takes a password as text. What the refusal shows: {item}: password {shape}; nothing was answered.
Fix: store the password as text (skarbiec field set {item} password < file).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_login_whose_password_is_not_text_is_refused_naming_its_shape.
skarbiec.helper.git helper-git-store-ambiguous#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: importing the sign-in git's store keeps for {host}. Why: git's store keeps {count} https sign-ins for {host}, as {names}, and one item takes one. What the refusal shows: files read: {files}; nothing was changed.
Fix: name one with --username <name>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::several_stored_sign_ins_for_one_host_are_refused_naming_the_usernames.
skarbiec.helper.git helper-git-store-no-password#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: reading the sign-in {file} keeps for {host}. Why: the line `{line}` names a user and no password, where git's store helper writes https://user:password@host. What the refusal shows: {file}; nothing was changed.
Fix: remove or repair that line of {file}, then run the import again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_stored_line_without_a_password_is_refused_naming_the_line.
skarbiec.helper.git helper-git-store-not-text#
point git at this vault for one forge's https credentials, move a sign-in git's store keeps into the vault, stop it, and answer git's requests. Started by skarbiec helper setup git, skarbiec helper import git, skarbiec helper unset git, skarbiec helper answer git.
What failed: reading the sign-in {file} keeps for {host}. Why: the {what} on `{line}` stops being UTF-8 text once its percent-escapes are decoded, at byte {offset}. What the refusal shows: {file}; nothing was changed.
Fix: repair that line of {file} so its {what} decodes to text, or keep the sign-in with skarbiec login new.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/exec/credentials/git_credential.sh::a_stored_password_that_is_not_text_once_decoded_is_refused.
skarbiec.helper.kube helper-kube-kubectl-absent#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: asking kubectl to {purpose}. Why: no kubectl is in any directory of PATH, and the kubeconfig is changed and read only through kubectl. What the refusal shows: command: {command}; PATH: {path}; nothing was changed.
Fix: install kubectl and put it on PATH (command -v kubectl names the one that runs), then run the same skarbiec helper command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::a_kube_helper_without_kubectl_on_path_is_refused_naming_path.
skarbiec.helper.kube helper-kube-kubectl-unstarted#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: asking kubectl to {purpose}. Why: a kubectl was found on PATH and could not be started (errno {errno}): it is not a program this account may run. What the refusal shows: command: {command}; PATH: {path}; the system said: {said}; nothing was changed.
Fix: command -v kubectl names the file that was found; make it executable or put a working kubectl before it on PATH.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::a_kubectl_that_cannot_be_started_is_refused_naming_errno.
skarbiec.helper.kube helper-kube-kubectl-refused#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: asking kubectl to {purpose}. Why: kubectl config ended with {ended} saying why: the kubeconfig is not one kubectl can read or write. What the refusal shows: command: {command}; KUBECONFIG: {kubeconfig}; kubectl said: {said}; {state}.
Fix: run {command} to see kubectl's refusal in full and repair the kubeconfig it names, then run the same skarbiec helper command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::a_kubeconfig_kubectl_cannot_read_is_refused_in_kubectls_words.
skarbiec.helper.kube helper-kube-view-not-json#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: reading the kubeconfig's users through {command}. Why: kubectl answered with status 0 and something that is not JSON, where -o json answers JSON: a kubectl release that prints another format, or a wrapper in its place on PATH. What the refusal shows: {bytes} bytes; the JSON reader stopped at line {line}, column {column}: {why}; nothing was changed.
Fix: run {command} by hand to see what it answers; command -v kubectl names the one on PATH.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::a_kubectl_answering_no_json_is_refused_naming_it.
skarbiec.helper.kube helper-kube-user-not-running#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: unsetting the exec of kubeconfig user {user}. Why: no kubeconfig user {user} runs this vault's helper answer kube, so there is nothing to unset. What the refusal shows: users that run it: {users}; nothing was changed.
Fix: kubectl config view shows the users there; skarbiec helper status kube names the ones that run this vault.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::unsetting_a_user_that_does_not_run_the_plugin_is_refused_naming_the_ones_that_do.
skarbiec.helper.kube helper-kube-user-absent#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: importing the credential of kubeconfig user {user}. Why: the kubeconfig has no user {user}. What the refusal shows: KUBECONFIG: {kubeconfig}; users: {users}; nothing was changed.
Fix: name one of the users kubectl config view lists.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::importing_a_user_the_kubeconfig_lacks_is_refused_naming_its_users.
skarbiec.helper.kube helper-kube-user-cert-files#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: importing the credential of kubeconfig user {user}. Why: kubeconfig user {user} keeps its client certificate in files it names, not inline. What the refusal shows: client-certificate: {certificate}; client-key: {key}; nothing was changed.
Fix: embed them first (kubectl config set-credentials {user} --embed-certs --client-certificate=<file> --client-key=<file>), then import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::importing_a_user_whose_certificate_is_in_files_is_refused_naming_embed_certs.
skarbiec.helper.kube helper-kube-user-nothing#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: importing the credential of kubeconfig user {user}. Why: kubeconfig user {user} keeps neither a bearer token nor an inline client certificate to import: it signs in another way. What the refusal shows: the user's members: {members}; nothing was changed.
Fix: a user signing in with another plugin stays as it is; import a user kubectl config view shows with a token or client-certificate-data.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::importing_a_user_with_nothing_inline_is_refused_naming_what_it_keeps.
skarbiec.helper.kube helper-kube-user-data-unread#
have kubectl point a kubeconfig user's exec at this vault, move the credential a user keeps into an item, stop it, and answer the ExecCredential. Started by skarbiec helper setup kube, skarbiec helper import kube, skarbiec helper unset kube, skarbiec helper answer kube.
What failed: importing the credential of kubeconfig user {user}. Why: kubeconfig user {user}'s {what} is {why}, so it is no PEM a certificate item can keep. What the refusal shows: {what}: {length} characters; nothing was changed.
Fix: set the user's certificate again from its PEM files (kubectl config set-credentials {user} --embed-certs --client-certificate=<file> --client-key=<file>), then import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/kube_credential.sh::importing_a_user_whose_certificate_data_is_not_pem_text_is_refused.
skarbiec.helper.tool helper-host-unfit#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: reading the host a credential helper answers for. Why: {host} is not a host as git names one, the shape every tool skarbiec helps names a host in: letters, digits, dots and hyphens, such as github.com, with a port of digits after a colon when the server uses one. What the refusal shows: host: {host}; nothing was read or changed.
Fix: name the host as the tool names it, e.g. github.com or registry.example.com:5000.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_host_that_is_not_a_host_name_is_refused_naming_its_shape.
skarbiec.helper.tool helper-item-kind-unfit#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: reading the credential {id} keeps for {tool}. Why: {id} is a {kind} item, and helper answer {tool} hands {program} {wants}. What the refusal shows: {id}: kind {kind}; nothing was answered or changed.
Fix: name an item of kind {kinds} (skarbiec list --kind <kind> names them).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_helper_for_an_item_of_another_kind_is_refused_naming_the_kinds.
skarbiec.helper.tool helper-item-field-empty#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: reading the credential {id} keeps for {tool}. Why: {id}, of kind {kind}, holds no {field}, which {program} needs from it. What the refusal shows: {id}: {field} is empty or absent; nothing was answered or changed.
Fix: store it with skarbiec field set {id} {field} < file.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_helper_item_without_its_credential_is_refused_naming_the_field.
skarbiec.helper.tool helper-file-not-json#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: reading {what} {file}. Why: {file} is not JSON, so the {tool} sign-ins it keeps cannot be read. What the refusal shows: {bytes} bytes; the JSON reader stopped at line {line}, column {column}: {why}; nothing was changed.
Fix: repair {file}, which is {tool}'s own file, or move it aside, then run the same skarbiec helper command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_tool_file_that_is_not_json_is_refused_naming_where_it_stops.
skarbiec.helper.tool helper-file-not-object#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: reading {what} {file}. Why: {file} holds {shape}, where {tool} keeps a JSON object of its sign-ins. What the refusal shows: {file}: {shape}; nothing was changed.
Fix: repair {file}, which is {tool}'s own file, or move it aside, then run the same skarbiec helper command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_tool_file_of_another_shape_is_refused_naming_it.
skarbiec.helper.tool helper-other-helper#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: pointing {tool} at this vault in {file}. Why: {file} already names a credentials helper, `{other}`, and {tool} takes one. What the refusal shows: {file}: `{other}`; nothing was changed.
Fix: remove that helper from {file} first, then run skarbiec helper setup {tool} again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_tool_already_naming_another_helper_is_refused_naming_it.
skarbiec.helper.tool helper-not-set-up#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: unsetting {tool}'s credential helper in {file}. Why: {file} names no skarbiec {helper}, so there is nothing to unset. What the refusal shows: {file}; nothing was changed.
Fix: skarbiec helper status {tool} says where {tool} looks for its helper.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::unsetting_a_helper_that_is_not_set_up_is_refused_naming_the_file.
skarbiec.helper.tool helper-program-taken#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: linking {tool}'s helper program {program} to this skarbiec. Why: {program} already links to {target}, another program than this skarbiec ({binary}). What the refusal shows: {program} -> {target}; nothing was changed.
Fix: remove {program} when that helper is no longer wanted (rm {program}), then run skarbiec helper setup {tool} again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_helper_program_linking_elsewhere_is_refused_naming_its_target.
skarbiec.helper.tool helper-program-not-link#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: linking {tool}'s helper program {program} to this skarbiec. Why: {program} exists and is not a link, so it is another program, not this vault's helper to replace. What the refusal shows: {program}: a file that is not a link; nothing was changed.
Fix: remove or rename {program} when that program is no longer wanted, then run skarbiec helper setup {tool} again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_helper_program_that_is_a_plain_file_is_refused_naming_it.
skarbiec.helper.tool helper-binary-unlocated#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: naming this skarbiec for {tool} to run. Why: this process cannot name the path of its own program (errno {errno}): the binary was moved or removed after it started. What the refusal shows: the system said: {said}; nothing was changed.
Fix: run skarbiec helper setup {tool} again from the installed binary (command -v skarbiec names it).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_binary_that_cannot_name_its_own_path_is_refused_for_the_tool.
skarbiec.helper.tool helper-store-refused#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: {tool} asking the vault to store a credential for {host}. Why: the vault keeps its own values, so {tool} {verb} does not store into it. What the refusal shows: {tool} {verb} {host}; nothing was changed.
Fix: keep {host}'s credential as a login offered on it: skarbiec login new <id> --username <name> --sites {host}, or skarbiec set.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_tool_storing_into_the_vault_is_refused_naming_login_new.
skarbiec.helper.tool helper-forget-refused#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: {tool} asking the vault to forget the credential for {host}. Why: the vault keeps its own values, so {tool} {verb} does not remove them. What the refusal shows: {tool} {verb} {host}; nothing was changed.
Fix: remove {host}'s login with skarbiec delete <id> (skarbiec login get {host} names it).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_tool_forgetting_from_the_vault_is_refused_naming_delete.
skarbiec.helper.tool helper-import-none#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: importing {tool}'s {what} for {host}. Why: {file} holds no {what} for {host}, so there is nothing to move into the vault. What the refusal shows: {tool}'s file {file}: {hosts}; nothing was changed.
Fix: name a host the file keeps (skarbiec helper status {tool} lists them), or keep the {what} with skarbiec set.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::importing_a_host_the_tool_keeps_nothing_for_is_refused_naming_the_file.
skarbiec.helper.tool helper-import-readback#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: reading back {id} after importing {tool}'s {what} for {host}. Why: {id} was written, and reading it back does not give the {what} that was moved: another write replaced it between the two. What the refusal shows: {file} was left as it was.
Fix: look at {id} (skarbiec history {id} names its writes), then run the same import again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::an_import_overtaken_before_it_reads_back_is_refused_for_the_tool.
skarbiec.helper.tool helper-answer-unwritten#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: handing {tool} its answer for {host}. Why: standard output could not take the answer (errno {errno}): {tool} closed it, or it is not open, before the answer was written. What the refusal shows: the system said: {said}; the read was journalled.
Fix: run the tool again; skarbiec helper answer {tool} get {host} prints the same answer in a shell.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::an_answer_the_tool_no_longer_reads_is_refused.
skarbiec.helper.tool helper-login-incomplete#
read a tool's own files, link and name its helper, refuse what the vault does not do for it, and hand it its answer. Started by other functionalities only.
What failed: choosing the login {tool} signs in to {host} with. Why: login get answered without {member}, which the answer to {tool} needs. What the refusal shows: login get's members: {members}.
Fix: run skarbiec login get {host} to see what it answers, and report it with skarbiec --version.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/helper/tools.sh::a_login_answer_without_its_member_is_refused_for_the_tool.
skarbiec.http.request http-request-line-malformed#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the request line. Why: the request line {line} names no method and path. What the refusal shows: nothing after the request line was read.
Fix: send <METHOD> <path> HTTP/1.1 as the first line, ended by CRLF.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_request_line_naming_no_path_is_answered_400.
skarbiec.http.request http-request-cut-short#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the request's {part}. Why: the connection ended in the middle of the {part}. What the refusal shows: read so far: {read}; no route was run.
Fix: send the whole request: every line ended by CRLF and the headers by an empty line.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_request_cut_in_the_middle_of_a_line_is_answered_400.
skarbiec.http.request http-head-not-utf8#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the request's {part}. Why: the {part} is not UTF-8. What the refusal shows: no route was run.
Fix: send the request line and the headers as ASCII.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_request_line_that_is_not_utf8_is_answered_400.
skarbiec.http.request http-content-length-invalid#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the request body. Why: Content-Length {length} is not a count of bytes. What the refusal shows: the number reader said: {error}; no body byte was read and no route was run.
Fix: state the body's length in bytes as a decimal number, or send no Content-Length and no body.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_content_length_that_is_not_a_number_is_answered_400.
skarbiec.http.request http-body-short#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the request body. Why: the request states a {length}-byte body and the connection closed after {read}. What the refusal shows: no route was run.
Fix: send exactly as many body bytes as Content-Length states.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_body_shorter_than_its_content_length_is_answered_400.
skarbiec.http.request http-body-not-utf8#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the request body. Why: the request body is not UTF-8. What the refusal shows: the text reader said: {error}; no route was run, and no byte was replaced.
Fix: send the body as UTF-8 JSON.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_body_that_is_not_utf8_is_answered_400.
skarbiec.http.request http-body-not-json#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the request body. Why: the request body is not JSON ({bytes} bytes). What the refusal shows: the JSON reader said: {error}; no route was run.
Fix: send one JSON object as the body, with Content-Type: application/json.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_body_that_is_not_json_is_answered_400.
skarbiec.http.request http-member-missing#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the body of {route}. Why: it names no {member}, which {route} needs as a non-empty string. What the refusal shows: members sent: {members}.
Fix: send {member} in the JSON body of {route}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_delete_naming_no_id_is_answered_400.
skarbiec.http.request http-route-unknown#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: answering {method} {path}. Why: no route of this Skarbiec answers {method} {path}. What the refusal shows: the request was read and nothing was changed.
Fix: call a route https://skarbiec.wisent.com/docs/api lists; GET /livez says the port answers as Skarbiec.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_path_no_route_answers_is_answered_404.
skarbiec.http.request http-connection-failed#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: {doing} on a loopback connection. Why: the connection failed before the request was answered. What the refusal shows: the system said: {error}; the request was not answered further.
Fix: send the request again; a client that closes or resets its connection is not answered.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_connection_reset_while_its_request_is_read_is_dropped.
skarbiec.http.request http-worker-unstarted#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: starting a thread for the request. Why: the system refused a thread for it. What the refusal shows: the system said: {error}; the request was not read.
Fix: send the request again once the host has threads to spare; ps -M {pid} lists the serving process's threads.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_request_the_system_gives_no_thread_is_answered_503.
skarbiec.http.request http-hand-written-403#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: answering a refused call. Why: a route wrote a 403 by hand, which names neither who was refused nor what would allow it. What the refusal shows: body it wrote: {body}.
Fix: answer the refusal from its declared cause through http::refused or http::answer_refusal.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_route_writing_a_403_by_hand_is_refused.
skarbiec.http.request http-supervisor-poisoned#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: waiting for a request worker's fatal failure. Why: a thread panicked while it held the failure channel's lock, so no worker's failure can be read from it any more. What the refusal shows: serve ends, and launchd starts it again.
Fix: read the serve log for the panic that came first; skarbiec doctor says whether the vault and journal are usable.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_lost_worker_supervisor_ends_serve.
skarbiec.http.request http-supervisor-closed#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: waiting for a request worker's fatal failure. Why: every request worker's end of the failure channel is gone, so no worker is left to serve. What the refusal shows: serve ends, and launchd starts it again.
Fix: read the serve log for the request workers that ended; skarbiec doctor says whether the vault and journal are usable.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_supervisor_whose_workers_are_all_gone_ends_serve.
skarbiec.http.request http-consumer-unnamed#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading which consumer calls the loopback API. Why: the request names no consumer, so no grant can be looked up for it; it is answered 401 before the vault is read. What the refusal shows: x-consumer header: {found}.
Fix: send the consumer the grant was issued to in the x-consumer header, beside Authorization: Bearer <token>.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_request_naming_no_consumer_is_answered_401_naming_the_header.
skarbiec.http.request http-bearer-absent#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: reading the bearer {consumer} presents to the loopback API. Why: the request from {consumer} carries no bearer, so its grant cannot be checked; it is answered 401 before the vault is read. What the refusal shows: Authorization header: {found}.
Fix: send Authorization: Bearer <token>, the token of {consumer}'s grant (skarbiec grant list shows every consumer's grants).
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/read/revision.sh::a_reader_presenting_no_bearer_is_answered_401.
skarbiec.http.request http-route-failed#
read one whole HTTP request off the loopback socket, refuse one that is not, choose the route it names, and write its answer. Started by every route of the loopback HTTP API.
What failed: answering {method} {path}. Why: this Skarbiec failed while it served the request, for a reason no cause of the route declares. What the refusal shows: the route failed with: {error}; the serve log holds the same failure; whatever the route wrote to the vault before it failed stays written.
Fix: skarbiec doctor says whether the vault and journal are usable; repair what the failure names and send the request again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_route_failing_for_an_undeclared_reason_is_answered_503_naming_it.
skarbiec.import import-export-missing#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export {path}. Why: {path} does not exist. What the refusal shows: the file system said: {said}; nothing was imported.
Fix: name the export file where the password manager or skarbiec export wrote it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_that_does_not_exist_is_refused_naming_it.
skarbiec.import import-export-not-file#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export {path}. Why: {path} is a directory or another file that is not a regular file. What the refusal shows: {path} is {kind}; nothing was imported.
Fix: name the export file itself.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_that_is_not_a_regular_file_is_refused_naming_it.
skarbiec.import import-export-denied#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export {path}. Why: {path} does not let this account read it. What the refusal shows: the file system said: {said}; nothing was imported.
Fix: give this account read permission on {path} (chmod u+r {path}), or import it as the account that owns it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_this_account_cannot_read_is_refused_naming_it.
skarbiec.import import-export-unread#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export {path}. Why: the file system failed to open or read {path}: a loop of links, a name too long, a device error or no open file left to this process. What the refusal shows: the file system said: {said}; nothing was imported.
Fix: copy the export to a short path on a working disk, then import that copy.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_the_file_system_cannot_open_is_refused_naming_it.
skarbiec.import import-stream-empty#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export from standard input. Why: import - read nothing from standard input: no package arrived. What the refusal shows: standard input ended before its first byte; nothing was imported.
Fix: pipe a sealed package into it, such as the output of skarbiec export - --encrypt-to <uid> run on the source vault.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/role_stream.sh::an_import_that_receives_nothing_is_refused.
skarbiec.import import-stream-unread#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export from standard input. Why: standard input could not be read: it is a directory or a closed or failing stream. What the refusal shows: the system said: {said}; nothing was imported.
Fix: pipe the package into import -, or name the export file instead of -.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/role_stream.sh::standard_input_that_cannot_be_read_is_refused_naming_what_it_said.
skarbiec.import import-not-json#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export {path} as JSON at line {line} column {column}. Why: {path} begins as JSON, so the whole file must be one JSON document. What the refusal shows: the JSON reader said: {said}; nothing was imported.
Fix: correct the JSON at line {line} column {column} of {path}, or export it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_that_is_not_json_is_refused_naming_its_line.
skarbiec.import import-shape-unknown#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: telling which export {path} is. Why: {shape}. What the refusal shows: {said}; nothing was imported.
Fix: import an export as its writer left it, or name its format with --format.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_of_no_known_shape_is_refused.
skarbiec.import import-format-mismatch#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export {path} as {format}. Why: {mismatch}. What the refusal shows: --format {format}; nothing was imported.
Fix: import it again with --format auto, which tells the export's format from the file itself.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_read_as_another_format_is_refused.
skarbiec.import import-empty#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing the export {path}. Why: the export holds no items. What the refusal shows: nothing was imported.
Fix: export again from a vault or account that holds items.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_holding_no_items_is_refused.
skarbiec.import import-canonical-row#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading row {row} of the canonical export {path}. Why: row {row} of {path} must be an object with a text id and a payload. What the refusal shows: row {row}: {said}; nothing was imported.
Fix: correct row {row} of {path} into an object with a text id and a payload naming its kind (tags and recipients are lists), or export it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_canonical_row_of_another_shape_is_refused_naming_it.
skarbiec.import import-1password-record#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading {place} of the 1Password export {path}. Why: {place} of {path} must be {form}. What the refusal shows: {place}: {said}; nothing was imported.
Fix: export the account again from the 1Password app as a 1PUX file, and import that file unchanged.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_1password_record_of_another_shape_is_refused_naming_it.
skarbiec.import import-bitwarden-encrypted#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the Bitwarden export {path}. Why: it is an encrypted Bitwarden export, which only Bitwarden opens. What the refusal shows: encrypted: {encrypted}; nothing was imported.
Fix: export the vault again from Bitwarden as unencrypted JSON, and import that file.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_encrypted_bitwarden_export_is_refused.
skarbiec.import import-bitwarden-item#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading {place} of the Bitwarden export {path}. Why: {place} of {path} must be {form}. What the refusal shows: {place}: {said}; nothing was imported.
Fix: export the vault again from Bitwarden as unencrypted JSON and import that file unchanged, or correct {place} into {form}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_bitwarden_item_of_another_shape_is_refused_naming_it.
skarbiec.import import-csv-line#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading line {line} of the CSV export {path}. Why: line {line} of {path} must be one line per item, with as many fields as the header names. What the refusal shows: the CSV reader said: {said}; nothing was imported.
Fix: correct line {line} of {path} (a quote opened in a field must close in it), or export it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_csv_line_that_does_not_read_is_refused_naming_it.
skarbiec.import import-sealed-not-text#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: opening the sealed export {path}. Why: {path} begins as a sealed export, so the whole file must be armored UTF-8 text. What the refusal shows: {said}; nothing was imported.
Fix: copy the sealed export again, unchanged, from where skarbiec export wrote it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_sealed_export_that_is_not_text_is_refused.
skarbiec.import import-sealed-unopened#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing {path}. Why: it is a sealed export, and no secret key this host's key file holds opens it. What the refusal shows: the sealing layer said: {error}; nothing was imported.
Fix: import the recipient's key here with skarbiec keys import, or import the export on the host that holds it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_sealed_export_no_key_here_opens_is_refused_under_the_export.
skarbiec.import import-malformed#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: reading the export {path} as {format}. Why: {why}. What the refusal shows: export: {path}; nothing was imported.
Fix: export again from the password manager, or name the format with --format; import --help names the formats read.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_that_does_not_read_as_one_is_refused_naming_what_is_wrong.
skarbiec.import import-reserved-tag#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing {id} from the export {path}. Why: the row carries managed:weles, the tag Weles alone gives the items it manages. What the refusal shows: tags: {tags}; nothing was imported.
Fix: take managed:weles off the row's tags, then import the export again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_row_carrying_the_reserved_weles_tag_is_refused.
skarbiec.import import-listed-twice#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing the export {path}. Why: the export lists {id} more than once, and one item can hold only one of them. What the refusal shows: nothing was imported.
Fix: keep one row for {id} in the export, then import it again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::an_export_listing_one_item_twice_is_refused_naming_it.
skarbiec.import import-recipient-unregistered#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing {id} from the export {path}. Why: the row is shared with {uid}, whom this vault does not register. What the refusal shows: recipients: {recipients}; nothing was imported.
Fix: skarbiec recipient add {uid} --import <their public key file>, or take {uid} off the row's recipients, then import again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_row_shared_with_an_unregistered_recipient_is_refused_naming_them.
skarbiec.import import-other-source#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing {id} from the export {path}. Why: the vault's {id} came from somewhere else ({held}), and this row is {source}. What the refusal shows: nothing was imported.
Fix: skarbiec rename {id} <new-id> to keep the vault's item beside the imported one, then import again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_row_whose_id_holds_an_item_from_another_source_is_refused.
skarbiec.import import-source-twice#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing the export {path}. Why: the vault records the import source {source} on both {first} and {second}, so a row from it cannot be told which it updates. What the refusal shows: nothing was imported.
Fix: skarbiec delete the other of {first} and {second}, the one that is not the item this source holds, then import again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_vault_recording_one_import_source_twice_is_refused_naming_both.
skarbiec.import import-row-refused#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing the export {path}. Why: {why}. What the refusal shows: nothing was imported.
Fix: change the row the refusal names in the export, or the vault item it meets, then import again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_row_the_vault_refuses_is_refused_naming_it_and_imports_nothing.
skarbiec.import import-conflict#
read a canonical, 1Password, Bitwarden or browser CSV export, from a file or (import -) standard input, opened first when it is sealed, and write every row as an item in one save, keeping, replacing or refusing an item that already holds another value. Started by skarbiec import, skarbiec onboarding --import, POST /v1/operator/items/import.
What failed: importing {id} with --conflict error. Why: {id} already holds another value, and --conflict error refuses to keep or replace it. What the refusal shows: nothing was imported.
Fix: import again with --conflict keep to leave the vault's value or --conflict replace to take the export's.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/transfer/import_refusals.sh::a_row_meeting_a_different_item_under_conflict_error_is_refused.
skarbiec.init init-exists#
create a vault whose owner and recovery recipient each have a key in this host's key file, making any key the key file does not hold. Started by skarbiec init, POST /v1/operator/vaults/create.
What failed: creating a vault at {path}. Why: a vault already exists there, and a new one would replace every item it holds. What the refusal shows: vault file: {path}.
Fix: use the vault that is there, or name a new file with SKARBIEC_VAULT_FILE.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/vault/init.sh::init_over_an_existing_vault_is_refused_naming_it.
skarbiec.history inspect-item-missing#
list every saved version of one item with the stamp restore --at takes, and with --changes which fields each changed. Started by skarbiec history, POST /v1/operator/items/history, Desktop: Items → a selected item → History.
What failed: reading the {what} of {id}. Why: this vault holds no item {id}, live or in the trash. What the refusal shows: vault file: {path}.
Fix: name an item the vault holds; skarbiec list --trashed lists them all.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/inspect.sh::the_history_and_readers_of_an_item_the_vault_does_not_hold_name_it.
skarbiec.history history-damaged#
list every saved version of one item with the stamp restore --at takes, and with --changes which fields each changed. Started by skarbiec history, POST /v1/operator/items/history, Desktop: Items → a selected item → History.
What failed: reading the saved versions of {id}. Why: {id} records its history as {found}, not a list of versions. What the refusal shows: item {id}: history {found}.
Fix: restore the vault from a backup taken before the item's history was damaged (skarbiec backup list).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/inspect.sh::an_item_whose_history_is_not_a_list_is_refused_naming_what_it_records.
skarbiec.readers inspect-item-missing#
name the keys an item's current value is sealed to and whether this host holds each, without decrypting it. Started by skarbiec readers, POST /v1/operator/items/readers, Desktop: Items → a selected item → Readers.
What failed: reading the {what} of {id}. Why: this vault holds no item {id}, live or in the trash. What the refusal shows: vault file: {path}.
Fix: name an item the vault holds; skarbiec list --trashed lists them all.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/inspect.sh::the_history_and_readers_of_an_item_the_vault_does_not_hold_name_it.
skarbiec.readers readers-ciphertext-absent#
name the keys an item's current value is sealed to and whether this host holds each, without decrypting it. Started by skarbiec readers, POST /v1/operator/items/readers, Desktop: Items → a selected item → Readers.
What failed: reading which keys {id} is encrypted to. Why: {id} records no current ciphertext, so its current value names no key it is sealed to. What the refusal shows: item {id}: revision {revision}.
Fix: skarbiec history {id} lists its saved versions, and skarbiec restore {id} --at <stamp> makes one current again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/inspect.sh::an_item_with_no_current_ciphertext_is_refused_naming_it.
skarbiec.kinds kind-unknown#
list every item kind, or one, with each field it takes, whether it is required, the set a payload needs one of, and the value it holds. Started by skarbiec kinds, skarbiec kinds <kind>, POST /v1/operator/kinds, Desktop: Items → New item…, Set a field….
What failed: listing the fields of kind {kind}. Why: this Skarbiec has no item kind {kind}. What the refusal shows: kinds: {kinds}.
Fix: name one of the kinds listed, or run skarbiec kinds to see every kind with its fields.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/kinds.sh::a_kind_that_does_not_exist_is_refused_naming_every_kind.
skarbiec.exposure exposure-unanswered#
answer for one item the keys, grants, journal entries and machine configurations that could have learned its value. Started by skarbiec exposure, POST /v1/operator/items/exposure, Desktop: Items → a selected item → Who could have learned it.
What failed: answering who could have learned {id}. Why: {command}, which exposure asks in process, answered no {expected}, which only a build whose command lost its answer produces. What the refusal shows: item {id}.
Fix: run skarbiec readers {id} and skarbiec grant list --item {id} by hand, and install a released skarbiec (the skarbiec release installer at stado://releases/skarbiec/<version>/<platform>/install.sh).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/inspect.sh::exposure_whose_inner_command_answers_nothing_is_refused_naming_it.
skarbiec.notes notes-stdin-unreadable#
read or replace the free text an item carries beside its fields. Started by skarbiec notes, POST /v1/operator/items/notes, POST /v1/operator/items/notes/set, Desktop: Items → a selected item → Save notes.
What failed: reading {id}'s new notes from standard input. Why: standard input could not be read to its end, so the new notes are not known whole. What the refusal shows: the system said: {said}; nothing was written to {id}.
Fix: give the notes on standard input from a file or a pipe that reads to its end, such as skarbiec notes {id} --set < notes.txt.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/notes.sh::notes_whose_input_cannot_be_read_are_refused.
skarbiec.notes notes-not-text#
read or replace the free text an item carries beside its fields. Started by skarbiec notes, POST /v1/operator/items/notes, POST /v1/operator/items/notes/set, Desktop: Items → a selected item → Save notes.
What failed: reading {id}'s new notes from standard input. Why: the notes stop being UTF-8 text at byte {offset}, and notes are text. What the refusal shows: standard input: {length} bytes; nothing was written to {id}.
Fix: give the notes as UTF-8 text on standard input, such as skarbiec notes {id} --set < notes.txt.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/notes.sh::notes_that_are_not_text_are_refused_and_nothing_is_written.
skarbiec.site-hosts site-not-bare#
read a list of sites as the bare hosts a login is offered on. Started by other functionalities only.
What failed: reading the sites {flag} names. Why: --{flag} {domain} is not a bare host. What the refusal shows: {domain} names the host {host}.
Fix: name it as {host}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/autofill/sites.sh::a_site_that_is_not_a_bare_host_is_refused_naming_the_host.
skarbiec.sites sites-not-login#
read, set, add, remove or relate the sites a login is offered on, or name where each changes its password. Started by skarbiec sites, POST /v1/operator/items/sites, POST /v1/operator/items/sites/set, POST /v1/operator/items/sites/change, POST /v1/operator/items/sites/change-pages, Desktop: Items → a selected item → Save sites, Add sites sharing this sign-in, Find the sites' own pages.
What failed: reading the sites of {id}. Why: {id} is a {kind} item; only a login is offered on sites. What the refusal shows: {id} is a {kind}.
Fix: name a login; skarbiec list --kind login lists them.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/sites.sh::the_sites_of_an_item_that_is_not_a_login_are_refused_naming_its_kind.
skarbiec.sites sites-none#
read, set, add, remove or relate the sites a login is offered on, or name where each changes its password. Started by skarbiec sites, POST /v1/operator/items/sites, POST /v1/operator/items/sites/set, POST /v1/operator/items/sites/change, POST /v1/operator/items/sites/change-pages, Desktop: Items → a selected item → Save sites, Add sites sharing this sign-in, Find the sites' own pages.
What failed: {doing} for {id}. Why: {id} names no site. What the refusal shows: {id}'s context records no domain.
Fix: name one: skarbiec sites {id} --add <domain>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/related_sites.sh::a_login_naming_no_site_is_refused_naming_sites_add.
skarbiec.sites sites-remove-absent#
read, set, add, remove or relate the sites a login is offered on, or name where each changes its password. Started by skarbiec sites, POST /v1/operator/items/sites, POST /v1/operator/items/sites/set, POST /v1/operator/items/sites/change, POST /v1/operator/items/sites/change-pages, Desktop: Items → a selected item → Save sites, Add sites sharing this sign-in, Find the sites' own pages.
What failed: removing {absent} from the sites of {id}. Why: {id} is not offered on {absent}, so removing it would change nothing. What the refusal shows: {id}'s sites: {sites}.
Fix: name one of the sites above.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/sites.sh::removing_a_site_the_login_is_not_offered_on_is_refused_naming_its_sites.
skarbiec.open sites-none#
open a login's site, or its change-password page, in the default browser. Started by skarbiec open, Desktop: Items → a selected item → Open <site>, Change password at <address>.
What failed: {doing} for {id}. Why: {id} names no site. What the refusal shows: {id}'s context records no domain.
Fix: name one: skarbiec sites {id} --add <domain>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/related_sites.sh::a_login_naming_no_site_is_refused_naming_sites_add.
skarbiec.open open-site-absent#
open a login's site, or its change-password page, in the default browser. Started by skarbiec open, Desktop: Items → a selected item → Open <site>, Change password at <address>.
What failed: opening {site} for {id}. Why: {id} is not offered on {site}. What the refusal shows: {id}'s sites: {sites}.
Fix: name one of the sites above with --site.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/open_site.sh::a_site_the_login_is_not_offered_on_is_refused_naming_its_sites.
skarbiec.open open-several-sites#
open a login's site, or its change-password page, in the default browser. Started by skarbiec open, Desktop: Items → a selected item → Open <site>, Change password at <address>.
What failed: opening the site of {id}. Why: {id} is offered on several sites, and nothing says which to open. What the refusal shows: {id}'s sites: {sites}.
Fix: name one with --site.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/open_site.sh::a_login_on_several_sites_is_refused_naming_them.
skarbiec.open open-opener-unstarted#
open a login's site, or its change-password page, in the default browser. Started by skarbiec open, Desktop: Items → a selected item → Open <site>, Change password at <address>.
What failed: handing {address} to the default browser with {opener}. Why: {opener} could not be started: it is not on this account's PATH, or the file found there is not a program this account may run. What the refusal shows: the system said: {said}; nothing was opened.
Fix: run it where {opener} is on PATH (command -v {opener} names it), or open {address} by hand.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/open_site.sh::an_opener_that_cannot_run_is_refused_naming_it_and_the_address.
skarbiec.open open-opener-refused#
open a login's site, or its change-password page, in the default browser. Started by skarbiec open, Desktop: Items → a selected item → Open <site>, Change password at <address>.
What failed: handing {address} to the default browser with {opener}. Why: {opener} {address} exited with {status}: this session has no default browser it can hand the address to. What the refusal shows: {opener} said: {said}; nothing was opened.
Fix: run {opener} {address} in a desktop session to see its refusal, set a default browser there, or open {address} by hand.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/open_site.sh::an_opener_that_refuses_the_address_is_refused_naming_its_status.
skarbiec.item-open item-open-missing#
open one live item's current value and hold it to its kind. Started by other functionalities only.
What failed: opening {id}. Why: this vault holds no item {id}. What the refusal shows: vault file: {path}.
Fix: name an item the vault holds; skarbiec list names them, skarbiec find <text> searches them.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/open.sh::opening_an_item_the_vault_does_not_hold_names_it.
skarbiec.item-open item-open-legacy-envelope#
open one live item's current value and hold it to its kind. Started by other functionalities only.
What failed: opening {id}. Why: {id} is still kept in envelope format {format}, which this release no longer opens. What the refusal shows: item {id}: envelope format {format}.
Fix: skarbiec upgrade --apply moves every item to the current envelope.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/open.sh::a_legacy_item_is_refused_naming_the_upgrade.
skarbiec.item-open item-open-trashed#
open one live item's current value and hold it to its kind. Started by other functionalities only.
What failed: opening {id}. Why: {id} is in the trash, and only a live item's value is opened. What the refusal shows: item {id}: trashed.
Fix: skarbiec restore {id} brings it back; skarbiec get {id} --at <stamp> reads a saved version without restoring it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/open.sh::a_trashed_item_is_refused_naming_the_restore.
skarbiec.item-open item-open-undecryptable#
open one live item's current value and hold it to its kind. Started by other functionalities only.
What failed: opening {id}. Why: its current value does not decrypt with a key this host holds. What the refusal shows: item {id}: revision {revision}; decrypting it said: {error}.
Fix: skarbiec readers {id} names the keys it is encrypted to and whether this keyring holds each; skarbiec keys check and skarbiec doctor name why this host's key does not open it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/open.sh::a_value_encrypted_to_no_key_here_is_refused_naming_the_readers_command.
skarbiec.item-open item-open-damaged#
open one live item's current value and hold it to its kind. Started by other functionalities only.
What failed: opening {id}. Why: {id}'s stored record lacks a part every item records (its kind, or an object of fields), so the vault cannot tell what it holds. What the refusal shows: {why}; item {id}: revision {revision}.
Fix: skarbiec history {id} lists its saved versions, and skarbiec restore {id} --at <stamp> makes one that opens current again; a backup taken before the damage restores the whole vault.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reads/open.sh::an_item_that_records_no_kind_is_refused_naming_what_is_wrong.
skarbiec.set set-payload-not-json#
write one item's canonical payload from stdin as a new revision, keeping its tags and recipients unless they are given, only when absent or only when unchanged when asked. Started by skarbiec set, POST /v1/operator/credential.
What failed: writing {id}. Why: the payload on stdin is not one JSON document: it stops being JSON at line {line}, column {column}. What the refusal shows: stdin: {length} bytes; the parser said: {said}; nothing was written.
Fix: send one canonical JSON payload on stdin, with schema skarbiec.item.v2, a kind, fields and context (skarbiec kinds names each kind's fields).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/set.sh::a_payload_that_is_not_a_canonical_item_is_refused_naming_what_is_wrong.
skarbiec.set set-if-unchanged-unpaired#
write one item's canonical payload from stdin as a new revision, keeping its tags and recipients unless they are given, only when absent or only when unchanged when asked. Started by skarbiec set, POST /v1/operator/credential.
What failed: writing {id} only if unchanged. Why: set --if-unchanged reads one object holding expected (the payload read) and payload (the new one), and this one holds no {missing}. What the refusal shows: nothing was written.
Fix: send one JSON object on stdin whose expected member is the payload skarbiec get {id} answered and whose payload member is the new payload.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/set.sh::an_if_unchanged_write_naming_no_expected_is_refused.
skarbiec.set set-stdin-unreadable#
write one item's canonical payload from stdin as a new revision, keeping its tags and recipients unless they are given, only when absent or only when unchanged when asked. Started by skarbiec set, POST /v1/operator/credential.
What failed: reading the payload of {id} from stdin. Why: standard input could not be read to its end, so the payload is not known whole. What the refusal shows: the system said: {said}; nothing was written.
Fix: send the payload from a file or a pipe that reads to its end, e.g. skarbiec set {id} < payload.json.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/set.sh::a_payload_whose_input_cannot_be_read_is_refused.
skarbiec.set set-stdin-not-text#
write one item's canonical payload from stdin as a new revision, keeping its tags and recipients unless they are given, only when absent or only when unchanged when asked. Started by skarbiec set, POST /v1/operator/credential.
What failed: reading the payload of {id} from stdin. Why: the payload stops being UTF-8 text at byte {offset}, and a payload is JSON text. What the refusal shows: stdin: {length} bytes; nothing was written.
Fix: send the payload as UTF-8 JSON on stdin, e.g. skarbiec set {id} < payload.json.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/set.sh::a_payload_that_is_not_utf8_text_is_refused.
skarbiec.set set-payload-changed#
write one item's canonical payload from stdin as a new revision, keeping its tags and recipients unless they are given, only when absent or only when unchanged when asked. Started by skarbiec set, POST /v1/operator/credential.
What failed: writing {id} only if unchanged. Why: item_payload_changed: its payload changed since the caller read it. What the refusal shows: nothing was written.
Fix: read {id} again (skarbiec get {id}) and send the change against what it holds now.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/set.sh::an_if_unchanged_write_over_a_changed_item_is_refused_and_writes_nothing.
skarbiec.set set-recipient-unknown#
write one item's canonical payload from stdin as a new revision, keeping its tags and recipients unless they are given, only when absent or only when unchanged when asked. Started by skarbiec set, POST /v1/operator/credential.
What failed: writing {id} for {uid}. Why: {uid} is not a recipient of this vault, so there is no key to seal {id} to. What the refusal shows: registered recipients: {recipients}.
Fix: register them with skarbiec recipient add {uid}, or leave them out of --recipients.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/set.sh::a_recipient_the_vault_does_not_register_is_refused_instead_of_left_out.
skarbiec.set create-exists#
write one item's canonical payload from stdin as a new revision, keeping its tags and recipients unless they are given, only when absent or only when unchanged when asked. Started by skarbiec set, POST /v1/operator/credential.
What failed: creating {id} with {by}. Why: {id} already exists, and {by} creates an item and never replaces one. What the refusal shows: nothing was written.
Fix: name another id, or read what {id} holds with skarbiec get {id} and remove it first (skarbiec delete {id}) when it is to be replaced.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/cloud/aws_credential.sh::an_import_onto_an_existing_item_is_refused_and_the_source_kept.
skarbiec.item-write item-record-damaged#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: reading the stored record of {id}. Why: {why}, which no write of this build leaves. What the refusal shows: nothing was written.
Fix: skarbiec backup restore <copy> --item {id} puts back the item as a kept copy holds it; skarbiec vaults names the copies kept beside the vault.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::an_item_whose_stored_history_is_not_a_list_is_refused_naming_it.
skarbiec.item-write item-identity-unknown#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: context.{field} names {reference}, and this vault holds no such item. What the refusal shows: nothing was written.
Fix: store the identity first (skarbiec set {reference} --type identity), or name one skarbiec list --kind identity lists.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_login_naming_an_identity_the_vault_lacks_is_refused_naming_it.
skarbiec.item-write item-identity-not-active#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: context.{field} names {reference}, which is not an active identity item. What the refusal shows: nothing was written.
Fix: name an identity skarbiec list --kind identity lists, or restore {reference} from the trash with skarbiec restore {reference}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_login_naming_an_item_that_is_not_an_identity_is_refused_naming_it.
skarbiec.item-write item-legacy-envelope#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: {id} still uses the legacy envelope, which this build does not write over. What the refusal shows: nothing was written.
Fix: run skarbiec upgrade --apply, then write it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::an_item_in_the_legacy_envelope_is_refused_naming_the_upgrade.
skarbiec.item-write item-protected#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: its payload and protected metadata may only change through its controlling lifecycle ({management}). What the refusal shows: nothing was written.
Fix: change it through what manages it, or take it back with skarbiec reclaim {id}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_share_that_would_change_a_managed_item_is_refused.
skarbiec.item-write item-duplicate#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: {holder} already holds exactly this payload; an exact duplicate is refused. What the refusal shows: nothing was written.
Fix: rename or delete one of them, or read skarbiec duplicates.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_payload_another_item_holds_is_refused_naming_it.
skarbiec.item-write item-salt-missing#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: fingerprinting the payload of {id}. Why: this vault has no fingerprint salt, which every write mints before it seals. What the refusal shows: nothing was written.
Fix: run skarbiec upgrade --apply, which mints the salt, then write it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_write_with_no_fingerprint_salt_is_refused.
skarbiec.item-write item-revision-full#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: it records revision {revision}, and no revision follows it. What the refusal shows: nothing was written.
Fix: copy it to a new id with skarbiec copy {id} <new-id>, which starts at revision one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::an_item_at_the_last_revision_is_refused.
skarbiec.item-write item-batch-duplicate#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing several items at once. Why: two of them are named {id}, and one would be written over the other. What the refusal shows: nothing was written.
Fix: give each item its own id; skarbiec import names a repeated source item before it writes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_batch_naming_one_id_twice_is_refused.
skarbiec.item-write item-placeholder#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: {fields} of this {kind} would hold an uppercase placeholder (capitals, digits and underscores, the way an environment variable is named) where the credential itself belongs, and every reader would hand that text to the service as the secret. What the refusal shows: nothing was written; a field that held the same text before this write keeps it, so only a placeholder this write brings is refused.
Fix: write the real credential into {fields}, or leave the field out until it is known; skarbiec kinds {kind} lists which fields the kind requires and which hold a secret, and skarbiec totp seed names an authenticator seed that is still a placeholder.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_placeholder_written_where_a_secret_belongs_is_refused_naming_the_field.
skarbiec.item-write item-factor-removed#
seal one item's payload into its stored envelope, carrying its identity, management, tags, readers and earlier versions forward. Started by other functionalities only.
What failed: writing {id}. Why: {id} records that its account asks for an authenticator code after the password (context.second_factor totp) and holds a seed that computes one, and this write would leave totp_secret {after}, so every automated sign-in of the account would stop at the second factor. What the refusal shows: totp_secret now: present; after this write: {after}; the record after this write: {record}; nothing was written.
Fix: keep the working seed in totp_secret (skarbiec totp set {id} replaces it with another that works); if the account no longer asks for a code, record that in the same write or first with skarbiec login factor set <login> --factor <what it asks now>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/write.sh::a_write_removing_the_seed_a_recorded_factor_needs_is_refused.
skarbiec.key-file key-file-not-regular#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading {what} {path}. Why: {path} is a link or a directory, not a regular file, and a link lets whoever can change it decide which keys open the vault. What the refusal shows: {what}: {path}.
Fix: put the file itself at {path} (cp the file the link names over it), owned by this account at mode 600.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_file_that_is_a_link_is_refused_naming_it.
skarbiec.key-file key-file-foreign-owner#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading {what} {path}. Why: {path} belongs to uid {owner}, not to this account (uid {uid}), and a file another account can replace decides which keys open the vault. What the refusal shows: {what}: {path}.
Fix: chown {path} to this account, or name a file of this account with the variable that names it (SKARBIEC_KEYS_FILE, SKARBIEC_UNLOCK_FILE).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_file_another_account_owns_is_refused_naming_its_owner.
skarbiec.key-file key-file-open-mode#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading {what} {path}. Why: {path} is mode {mode}, which lets another account read it, and it must be mode 0600. What the refusal shows: {what}: {path}.
Fix: chmod 600 {path}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_file_other_accounts_can_read_is_refused_naming_chmod.
skarbiec.key-file key-file-not-json#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: it is not the JSON Skarbiec writes: its text stops being JSON at line {line}, column {column}. What the refusal shows: key file: {path}, {bytes} bytes; the parser said: {said}.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_file_that_is_not_json_is_refused_naming_it.
skarbiec.key-file key-file-no-keys#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: it has no keys list, where the key file keeps every key. What the refusal shows: key file: {path}; keys holds {held}.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_file_with_no_keys_list_is_refused_naming_it.
skarbiec.key-file key-file-field-missing#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: {entry} has no {field} text, which every {part} the key file writes holds. What the refusal shows: key file: {path}; the entry was not used.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_entry_missing_a_field_is_refused_naming_it.
skarbiec.key-file key-file-field-not-hex#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: {entry}'s {field} is not hexadecimal bytes: {how}. What the refusal shows: key file: {path}; none of its characters are shown.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_entry_whose_secret_is_not_hex_is_refused_naming_where.
skarbiec.key-file key-file-field-length#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: {entry}'s {field} is {length} bytes, and it is {expected}. What the refusal shows: key file: {path}; none of its bytes are shown.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_entry_whose_secret_is_of_another_length_is_refused_naming_both.
skarbiec.key-file key-file-public-not-base64#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: {entry}'s public key text is not base64. What the refusal shows: key file: {path}; the decoder said: {said}.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_entry_whose_public_key_is_not_base64_is_refused_naming_it.
skarbiec.key-file key-file-public-unreadable#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: {entry}'s public key packets are no OpenPGP public key Skarbiec reads: they were cut or changed. What the refusal shows: key file: {path}; the key reader said: {said}.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_entry_whose_public_packets_do_not_read_is_refused_naming_it.
skarbiec.key-file key-file-public-empty#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: {entry}'s public key text decodes to packets that hold no public key. What the refusal shows: key file: {path}.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_entry_holding_no_public_key_is_refused_naming_it.
skarbiec.key-file key-file-secret-foreign#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: {entry}'s secret half is not that key's: {which}, so the file was changed or written wrongly. What the refusal shows: key file: {path}; the entry was not used.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_entry_holding_another_keys_secret_is_refused_naming_it.
skarbiec.key-file key-file-secret-opened-length#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: the secret half of {fingerprint} opens to {length} bytes, not the 64 a seed and a scalar make or the 32 of a scalar alone, so it was sealed wrongly. What the refusal shows: key file: {path}; none of its bytes are shown.
Fix: restore {path} from the backup that keeps it (skarbiec backup restore), or import the keys again with skarbiec keys import.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_sealed_secret_of_another_length_is_refused_naming_it.
skarbiec.key-file key-file-format#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key file {path}. Why: it states format {stated}, and this build reads only {format}. What the refusal shows: key file: {path}.
Fix: open it with the skarbiec build that wrote it, or restore the {format} file from the backup that keeps it (skarbiec backup restore).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_file_of_another_format_is_refused_naming_both.
skarbiec.key-file key-file-key-absent#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: finding the key {fingerprint} in the key file {path}. Why: the key file holds no key {fingerprint}. What the refusal shows: key file: {path}.
Fix: import its public key with skarbiec recipient add <uid> --import <file>, or, for a key gpg kept, run skarbiec keys import.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::sealing_to_a_key_the_key_file_lacks_is_refused_naming_it.
skarbiec.key-file key-file-secret-absent#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: using the secret half of {fingerprint}. Why: {path} holds only its public key. What the refusal shows: key file: {path}.
Fix: import the secret half here with skarbiec keys import, or run the command on the host that holds it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::signing_with_a_key_held_only_publicly_is_refused_naming_it.
skarbiec.key-file key-file-secret-no-phrase#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: unlocking the secret half of {fingerprint} in {path}. Why: it is sealed under the unlock phrase, and no unlock phrase is configured: SKARBIEC_UNLOCK is unset, and {unlock_file} is absent or empty. What the refusal shows: key file: {path}.
Fix: write the phrase it was sealed under to the owner-only file SKARBIEC_UNLOCK_FILE names (default ~/.stado/skarbiec-unlock), or set SKARBIEC_UNLOCK for one command.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::using_a_sealed_key_with_no_unlock_phrase_is_refused_naming_where_it_looked.
skarbiec.key-file key-file-secret-wrong-phrase#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: unlocking the secret half of {fingerprint} in {path}. Why: the unlock phrase does not open the secret half: it was sealed under another phrase, or the file was changed. What the refusal shows: key file: {path}; the phrase came from {source}.
Fix: configure the phrase it was sealed under: write it to the owner-only file SKARBIEC_UNLOCK_FILE names (default ~/.stado/skarbiec-unlock), or set SKARBIEC_UNLOCK for one command.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::signing_with_a_key_sealed_under_another_phrase_is_refused_naming_it.
skarbiec.key-file key-file-signing-half-absent#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: signing as {fingerprint}. Why: this host holds only the decryption half of the key; its signing half was protected when it was imported. What the refusal shows: key file: {path}.
Fix: write its passphrase to the owner-only file SKARBIEC_UNLOCK_FILE names (default ~/.stado/skarbiec-unlock) and run skarbiec keys import again, or sign on the host that holds it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::signing_with_a_key_held_for_decryption_only_is_refused_naming_it.
skarbiec.key-file key-file-no-encryption-subkey#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: sealing to the key {fingerprint}. Why: the key has no Curve25519 encryption subkey. What the refusal shows: nothing was sealed.
Fix: give its holder a new Ed25519 key with a Curve25519 encryption subkey: skarbiec recipient rekey <uid> --import <public-key-file> --yes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::sealing_to_a_key_with_no_encryption_subkey_is_refused_naming_it.
skarbiec.key-file key-file-key-not-armored#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key to add. Why: the text given is not an ASCII-armored OpenPGP public key block (-----BEGIN PGP PUBLIC KEY BLOCK----- and its checksum). What the refusal shows: the armor reader said: {said}; the key file holds what it held before.
Fix: give the public key exactly as its holder exported it (gpg --armor --export <uid>, or skarbiec recipient export <uid>).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_public_key_that_is_not_armored_is_refused_naming_it.
skarbiec.key-file key-file-key-packets-unreadable#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key to add. Why: the armored block holds bytes that are not OpenPGP packets, so it was cut or changed after it was exported. What the refusal shows: the packet reader said: {said}; the key file holds what it held before.
Fix: export the public key again from its holder (gpg --armor --export <uid>, or skarbiec recipient export <uid>) and give the whole block.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_block_whose_packets_do_not_read_is_refused.
skarbiec.key-file key-file-key-not-public#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key to add. Why: the packets hold no OpenPGP public key Skarbiec reads (an Ed25519 primary key with an X25519 encryption subkey). What the refusal shows: the key reader said: {said}; the key file holds what it held before.
Fix: export the holder's public key itself, not a signature or a secret key (gpg --armor --export <uid>); skarbiec owner key mint <uid> makes a key Skarbiec reads.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_block_holding_no_public_key_is_refused.
skarbiec.key-file key-file-key-unverified#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: reading the key to add. Why: key {fingerprint}'s own signatures do not verify, so its user ids and subkey are not shown to be its holder's. What the refusal shows: the signature check said: {said}; the key file holds what it held before.
Fix: ask the holder to export the key again (gpg --armor --export <uid>); a key whose bytes were changed after export is not added.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_whose_own_signatures_do_not_verify_is_refused.
skarbiec.key-file key-file-key-unanswered#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: making a new key for {uid}. Why: the key file writer answered no fingerprint for the one key it was given, which only a build whose writer lost its answer produces. What the refusal shows: the key may have been written; skarbiec keys lists what the key file holds.
Fix: run skarbiec keys to see whether the key for {uid} is there, and install a released skarbiec (the skarbiec release installer at stado://releases/skarbiec/<version>/<platform>/install.sh).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_key_writer_that_answers_no_fingerprint_is_refused.
skarbiec.key-file key-file-clock-out-of-range#
keep every recipient's public key and the secret halves this host holds in one owner-only file beside the vault, sealed under the unlock phrase when one is configured. Started by skarbiec recipient add, skarbiec owner key mint.
What failed: stating the time in {what}. Why: the clock reads {seconds} seconds after 1970, past what {what} can state. What the refusal shows: nothing was signed or written.
Fix: set this host's clock to the present time (date -u says what it reads) and run the command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/key_file.sh::a_clock_past_what_openpgp_states_is_refused.
skarbiec.keys.import keys-import-no-keyring#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: importing the vault's keys from {home}. Why: {home} holds no public keyring, and this host's key file {key_file} lacks keys the vault names: {missing}. What the refusal shows: looked for {database} and {keybox}; nothing was imported.
Fix: name the GnuPG home that holds the vault's keys with --gnupg-home <dir>, or bring them with skarbiec owner key import <file> or the key file from its backup.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::an_import_from_a_home_with_no_keyring_and_a_key_file_that_does_not_serve_the_vault_is_refused.
skarbiec.keys.import keys-import-no-keyring-item-unopened#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: importing the vault's keys from {home}. Why: {home} holds no public keyring, and this host's key file {key_file} holds every key the vault names, but the vault's item {item} does not open with it. What the refusal shows: looked for {database} and {keybox}; opening {item} said: {error}; nothing was imported.
Fix: name the GnuPG home that holds the vault's secret keys with --gnupg-home <dir>, or bring them with skarbiec owner key import <file> or the key file from its backup; skarbiec doctor names why {item} does not open.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::an_import_from_a_home_with_no_keyring_and_a_key_file_that_does_not_open_the_vault_is_refused.
skarbiec.keys.import keys-import-keyring-damaged#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: reading the public keys in {file}. Why: {file} is not {kind} Skarbiec reads: it was cut short, or gpg wrote it in a layout this release does not know. What the refusal shows: {bytes} bytes; the reader said: {said}; nothing was imported.
Fix: gpg --homedir {home} --list-keys says whether gpg itself reads it; if gpg is writing it now, run the import again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_keyring_that_cannot_be_read_is_refused_naming_it.
skarbiec.keys.import keys-import-key-unreadable#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: importing the key {fingerprint} from {home}. Why: its keyblock does not read as an OpenPGP public key Skarbiec reads (an Ed25519 primary key), so no item can be sealed to it. What the refusal shows: the key reader said: {said}; nothing was imported.
Fix: give its holder a new Ed25519 key with a Curve25519 encryption subkey: skarbiec recipient rekey <uid> --import <public-key-file> --yes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_key_of_another_algorithm_is_refused_naming_it.
skarbiec.keys.import keys-import-key-no-subkey#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: importing the key {fingerprint} from {home}. Why: it has no Curve25519 encryption subkey, so no item can be sealed to it. What the refusal shows: the key reader said: {said}; nothing was imported.
Fix: give its holder a new Ed25519 key with a Curve25519 encryption subkey: skarbiec recipient rekey <uid> --import <public-key-file> --yes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_key_with_no_encryption_subkey_is_refused_naming_it.
skarbiec.keys.import keys-import-secret-no-phrase#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: reading the secret half of {fingerprint} in {home}. Why: {file} is protected by a passphrase and no unlock phrase is configured. What the refusal shows: gpg-agent key file: {file}; the reader said: {said}; nothing was imported.
Fix: a key protected by a passphrase opens with the one written to the owner-only file SKARBIEC_UNLOCK_FILE names (default ~/.stado/skarbiec-unlock); otherwise gpg --homedir {home} --list-secret-keys {fingerprint} says whether gpg itself opens it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_secret_half_that_cannot_be_read_is_refused_naming_the_key.
skarbiec.keys.import keys-import-secret-wrong-passphrase#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: reading the secret half of {fingerprint} in {home}. Why: {file} does not open with the configured unlock phrase, which is not its passphrase. What the refusal shows: gpg-agent key file: {file}; the reader said: {said}; nothing was imported.
Fix: a key protected by a passphrase opens with the one written to the owner-only file SKARBIEC_UNLOCK_FILE names (default ~/.stado/skarbiec-unlock); otherwise gpg --homedir {home} --list-secret-keys {fingerprint} says whether gpg itself opens it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_secret_half_under_another_passphrase_is_refused_naming_it.
skarbiec.keys.import keys-import-secret-unsupported#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: reading the secret half of {fingerprint} in {home}. Why: {file} holds a key of a curve or a protection Skarbiec does not read. What the refusal shows: gpg-agent key file: {file}; the reader said: {said}; nothing was imported.
Fix: a key protected by a passphrase opens with the one written to the owner-only file SKARBIEC_UNLOCK_FILE names (default ~/.stado/skarbiec-unlock); otherwise gpg --homedir {home} --list-secret-keys {fingerprint} says whether gpg itself opens it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_secret_half_of_another_kind_is_refused_naming_it.
skarbiec.keys.import keys-import-secret-damaged#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: reading the secret half of {fingerprint} in {home}. Why: {file} is no gpg-agent key file Skarbiec reads: it was cut short or changed. What the refusal shows: gpg-agent key file: {file}; the reader said: {said}; nothing was imported.
Fix: a key protected by a passphrase opens with the one written to the owner-only file SKARBIEC_UNLOCK_FILE names (default ~/.stado/skarbiec-unlock); otherwise gpg --homedir {home} --list-secret-keys {fingerprint} says whether gpg itself opens it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_damaged_agent_key_file_is_refused_naming_it.
skarbiec.keys.import keys-import-agent-file-not-text#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: reading the gpg-agent key file {file}. Why: it stops being UTF-8 text at byte {offset}, so it holds no key this import reads (an RSA key, a card stub, or one written with binary values). What the refusal shows: {bytes} bytes; it is left out, and the import goes on with the other files.
Fix: nothing to do when it is no vault key's; gpg --homedir {home} --list-secret-keys names what it holds.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::an_agent_file_that_is_not_text_is_left_out_naming_it.
skarbiec.keys.import keys-import-missing#
copy the vault's keys, and the secret halves this host holds, from a GnuPG home into this host's key file. Started by skarbiec keys import.
What failed: importing the vault's keys from {home}. Why: {home} holds no public key {missing}, which was asked for. What the refusal shows: the {written} other key(s) were written to {key_file}.
Fix: import those keys' public halves into that GnuPG home, or name the home that holds them with --gnupg-home, then run keys import again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/refusals.sh::a_key_the_home_does_not_hold_is_refused_naming_it.
skarbiec.keys.check keys-check-flag-unknown#
say whether any key on this host opens the vault, which recipients' secret halves are here and whether the owner can sign. Started by skarbiec keys check.
What failed: reading the flags of keys check. Why: keys check takes only --require-readable; it was given --{flag}. What the refusal shows: flags given: {given}; nothing was read.
Fix: run skarbiec keys check, or skarbiec keys check --require-readable to fail when no key here opens the vault.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/keys/gpg/gpg_free.sh::keys_check_refuses_a_flag_it_does_not_take_naming_it.
skarbiec.keys.check keys-check-not-readable#
say whether any key on this host opens the vault, which recipients' secret halves are here and whether the owner can sign. Started by skarbiec keys check.
What failed: proving a key on this host opens {vault} before this binary serves it (keys check --require-readable). Why: no key in {key_file} opens {item}, the vault's lowest live item, so this binary would serve a vault it cannot read. What the refusal shows: opening {item}: {error}; recipients whose secret half is here: {openers}.
Fix: bring the key it is sealed to with skarbiec keys import (or the key file from its backup) before this binary serves the vault; skarbiec keys check lists every recipient and whether its secret half is here.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/gpg/gpg_free.sh::keys_check_require_readable_fails_while_no_key_here_opens_the_vault.
skarbiec.credential.lifecycle-state record-unreadable#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: checking whether role {role} is quarantined. Why: its operation record {record} exists but could not be opened, so whether the role is quarantined is not known. What the refusal shows: record: {record}; opening it said: {error}.
Fix: run skarbiec doctor to see why the vault cannot open {record}; no lifecycle operation starts on a credential whose quarantine nobody can check.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::an_unreadable_operation_record_stops_the_operation_naming_it.
skarbiec.credential.lifecycle-state item-unreadable#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: reading the {block} of {item}. Why: {item} exists but this host could not open it, so its {block} cannot be read and the operation does not go on as if it were absent. What the refusal shows: item: {item}; opening it: {error}.
Fix: run skarbiec doctor to see why the vault cannot open {item}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::an_item_that_cannot_be_opened_stops_the_operation_naming_it.
skarbiec.credential.lifecycle-state state-unknown#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: reading the lifecycle state of role {role}. Why: {item} records the lifecycle state {state}, which is none of unmanaged, managed, adopting or quarantined. What the refusal shows: context.lifecycle.state of {item}: {state}.
Fix: write a declared state back with skarbiec set {item} (context.lifecycle.state), or remove the lifecycle block; credential status role:{role} --local shows what the role holds.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::an_undeclared_lifecycle_state_is_refused_naming_it.
skarbiec.credential.lifecycle-state quarantined#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: starting credential {command} of role {role}. Why: role {role} is quarantined: an earlier operation's provider effect is uncertain, so nobody knows which password the provider accepts. What the refusal shows: quarantine of role {role}: active.
Fix: resolve it: skarbiec credential quarantine resolve role:{role} --confirm 'I know which password this provider account accepts' --as <consumer> --token-file <path> --local.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::a_quarantined_role_refuses_an_operation_naming_the_resolve_command.
skarbiec.credential.lifecycle-state field-contract-mismatch#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: holding {item} to the {provider} credential contract. Why: CREDENTIAL_FIELD_CONTRACT_MISMATCH: the contract writes {required}, and the managed item carries {carried} and no {required}; Skarbiec adds no alias and writes no second field. What the refusal shows: fields of {item}: {carried}.
Fix: move the value to {required} as your own decision (skarbiec set {item} with the field renamed), then run the operation again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::a_managed_item_without_the_contract_field_is_refused_naming_both.
skarbiec.credential.lifecycle-state operation-lock-held#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: starting a credential operation on {vault}. Why: another credential operation holds {lock}: one operation runs at a time on a vault. What the refusal shows: {lock}: {holder}.
Fix: wait for that operation to finish; if its process is gone (the pid above runs nothing), check no Weles task is active and remove {lock}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::a_held_operation_lock_is_refused_naming_its_holder.
skarbiec.credential.lifecycle-state lifecycle-metadata-item-inactive#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: writing the credential lifecycle metadata {blocks} to {id}. Why: {id} is {state}, not active, and lifecycle metadata is written only to a live item. What the refusal shows: nothing was written to {id}.
Fix: bring {id} back with skarbiec restore {id} if it was trashed by mistake, then run the operation again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::metadata_for_an_item_that_is_not_active_is_refused_naming_its_state.
skarbiec.credential.lifecycle-state lifecycle-metadata-item-staged#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: writing the credential lifecycle metadata {blocks} to {id}. Why: {id} holds a staged revision, and its metadata waits until that revision is resolved, so a staged value is never silently dropped. What the refusal shows: staged revision written by {writer}; nothing was written to {id}.
Fix: settle the operation with skarbiec credential status role:<role>, or resolve a quarantined one with skarbiec credential quarantine resolve, then run it again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::metadata_for_an_item_with_a_staged_revision_is_refused_naming_it.
skarbiec.credential.lifecycle-state lifecycle-metadata-envelope-damaged#
read a credential's quarantine, lifecycle state and field contract, take the operation lock, and write its lifecycle metadata. Started by other functionalities only.
What failed: writing the credential lifecycle metadata {blocks} to {id}. Why: {id}'s record holds no {field}, which every {which} item records, so its next revision cannot be written as the one before. What the refusal shows: vault file: {path}; nothing was written to {id}.
Fix: restore the vault from a backup taken before the damage; skarbiec backup check <file> says whether a copy restores.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/lifecycle_state.sh::metadata_for_an_item_whose_record_is_damaged_is_refused_naming_the_field.
skarbiec.lifetime lifetime-missing#
read the lifetime a grant is written with: --ttl-seconds <N> whole seconds or --until-revoked. Started by other functionalities only.
What failed: reading how long the grant lives. Why: {command} requires --ttl-seconds <N> (a lifetime in whole seconds) or --until-revoked (it lives until `grant revoke`). What the refusal shows: neither was given; nothing was written.
Fix: run {command} again with --ttl-seconds <N> or --until-revoked.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::an_approval_stating_no_lifetime_is_refused_naming_both_ways.
skarbiec.lifetime lifetime-twice#
read the lifetime a grant is written with: --ttl-seconds <N> whole seconds or --until-revoked. Started by other functionalities only.
What failed: reading how long the grant lives. Why: --ttl-seconds and --until-revoked are exclusive. What the refusal shows: --ttl-seconds {given} and --until-revoked were both given; nothing was written.
Fix: keep one of them.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_lifetime_in_seconds_beside_until_revoked_is_refused.
skarbiec.lifetime lifetime-unfit#
read the lifetime a grant is written with: --ttl-seconds <N> whole seconds or --until-revoked. Started by other functionalities only.
What failed: reading how long the grant lives. Why: --ttl-seconds {given} is not a whole number of seconds of at least one. What the refusal shows: --ttl-seconds: {given}; nothing was written.
Fix: give --ttl-seconds a whole number of at least one, or state --until-revoked.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_lifetime_that_is_not_whole_seconds_is_refused_naming_it.
skarbiec.local-file local-file-missing#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: {path}, or a directory on its way, does not exist. What the refusal shows: the file system said: {said}.
Fix: name the path where the file is, or create the directory it goes in; ls -ld {parent} says what is there.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_path_that_does_not_exist_is_refused_naming_it.
skarbiec.local-file local-file-denied#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: the owner or mode of {path}, or of a directory on its way, does not give this account the permission this step needs. What the refusal shows: the file system said: {said}.
Fix: ls -ld {path} {parent} names their owner and mode; give this account the permission (chmod or chown), or run as the account that owns them.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_path_this_account_may_not_use_is_refused_naming_it.
skarbiec.local-file local-file-not-permitted#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: the operating system permits this step on {path} to no account of its mode: it is a directory where a file is removed, or it is locked against change by an immutable flag or System Integrity Protection. What the refusal shows: the file system said: {said}.
Fix: ls -ldO {path} names its kind and flags; move a directory standing there aside, or clear the flag (chflags nouchg {path}), then run the same command again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_directory_removed_as_a_file_is_refused_naming_it.
skarbiec.local-file local-file-not-directory#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: a part of {path} that has to be a directory is a file. What the refusal shows: the file system said: {said}.
Fix: move the file that stands in the path aside, or name a path whose directories are directories.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_path_through_a_file_is_refused_naming_it.
skarbiec.local-file local-file-is-directory#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: {path} is a directory, and this step needs a file there. What the refusal shows: the file system said: {said}.
Fix: name the file itself, not the directory holding it, or move the directory aside.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_directory_where_a_file_is_needed_is_refused_naming_it.
skarbiec.local-file local-file-exists#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: {path} already exists, and this step makes it new so that nothing there is written over. What the refusal shows: the file system said: {said}.
Fix: move {path} aside or remove it if nothing needs it, then run the same command again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_path_that_already_exists_is_refused_naming_it.
skarbiec.local-file local-file-not-text#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: {path} holds bytes that are not UTF-8 text, and this step reads it as text. What the refusal shows: the file system said: {said}.
Fix: name the text file meant here; file {path} says what it holds.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_file_that_is_not_text_is_refused_naming_it.
skarbiec.local-file local-file-full#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: the file system holding {path} has no room left, this account's quota on it is spent, or the file would pass the size it may have. What the refusal shows: the file system said: {said}.
Fix: free room on the disk holding {path} (df -h {parent} names it), then run the same command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_file_system_with_no_room_is_refused_naming_it.
skarbiec.local-file local-file-read-only#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: the file system holding {path} is mounted read-only, so nothing on it can change. What the refusal shows: the file system said: {said}.
Fix: name a path on a writable file system, or mount this one writable (mount names how each is mounted).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_read_only_file_system_is_refused_naming_it.
skarbiec.local-file local-file-device-failed#
open, read, write, examine, rename or remove a file or directory on this host's disk. Started by other functionalities only.
What failed: {doing} {path}. Why: the operating system failed the step for a reason of the disk or the process rather than of the path's existence, owner or kind: a device error, a name too long, a loop of symbolic links or no open file left to this process. What the refusal shows: the file system said: {said}.
Fix: the file system's words above name which; shorten the path, break the link loop, raise the open-file limit (ulimit -n) or check the disk (diskutil verifyVolume), then run the same command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/disk/local_file.sh::a_loop_of_links_is_refused_naming_it.
skarbiec.lockdown argument-given#
withdraw every consumer grant at once, keeping only the consumers named. Started by skarbiec lockdown, POST /v1/operator/lockdown, Desktop: Grants → Withdraw every grant.
What failed: reading what skarbiec lockdown withdraws. Why: lockdown takes no positional argument, and {given} was given. What the refusal shows: arguments: {given}.
Fix: run skarbiec lockdown [--except <consumer,...>] [--yes]; --except names the consumers to keep.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/lockdown/lockdown.sh::lockdown_with_an_argument_is_refused_with_its_usage.
skarbiec.lockdown grants-unread#
withdraw every consumer grant at once, keeping only the consumers named. Started by skarbiec lockdown, POST /v1/operator/lockdown, Desktop: Grants → Withdraw every grant.
What failed: reading the consumer grants lockdown would withdraw. Why: the grants the vault records cannot be read, so what lockdown would withdraw is unknown. What the refusal shows: reading them said: {error}; nothing was withdrawn.
Fix: skarbiec grant list and skarbiec doctor name why the grants do not read; fix that, then run lockdown again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/lockdown/lockdown.sh::lockdown_of_an_absent_vault_withdraws_nothing.
skarbiec.lockdown except-unknown#
withdraw every consumer grant at once, keeping only the consumers named. Started by skarbiec lockdown, POST /v1/operator/lockdown, Desktop: Grants → Withdraw every grant.
What failed: keeping {unknown} out of the lockdown. Why: --except names {unknown}, which hold no grant, so a misspelled consumer would be withdrawn. What the refusal shows: consumers holding a grant: {consumers}; nothing was withdrawn.
Fix: name the consumers to keep as skarbiec grant list names them.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/lockdown/lockdown.sh::lockdown_keeping_an_unknown_consumer_withdraws_nothing.
skarbiec.login-new login-exists#
create a login whose password is generated, checked against the policy and stored without passing through stdout. Started by skarbiec login new, POST /v1/operator/items/new-login, Desktop: Items → New login with a generated password → Create login.
What failed: creating the login {id}. Why: {id} already exists, and login new creates an item and never replaces one. What the refusal shows: the vault holds an item {id}.
Fix: name a new id, or replace {id}'s password with skarbiec generate --into {id} --field password.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/autofill/login_new.sh::a_login_new_over_an_existing_item_is_refused_and_the_item_is_kept.
skarbiec.login-get login-none-offered#
read one field, or the current one-time code, of the login a site is signed in with, chosen as autofill chooses it. Started by skarbiec login get, POST /v1/operator/items/site-get.
What failed: choosing the login {host} signs in with. Why: no login{with} is offered on {host}. What the refusal shows: logins that would not open to tell: {unreadable}.
Fix: skarbiec login list {host} lists what is offered there; skarbiec sites <id> --add {host} offers a login there.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/read/site_get.sh::a_site_no_login_is_offered_on_is_refused_naming_login_list.
skarbiec.login-get login-several-offered#
read one field, or the current one-time code, of the login a site is signed in with, chosen as autofill chooses it. Started by skarbiec login get, POST /v1/operator/items/site-get.
What failed: choosing the login {host} signs in with. Why: {count} logins are offered on {host}, and nothing says which one. What the refusal shows: offered: {logins}.
Fix: name one with --username.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/read/site_get.sh::a_site_several_logins_are_offered_on_is_refused_naming_them.
skarbiec.login-get login-no-code#
read one field, or the current one-time code, of the login a site is signed in with, chosen as autofill chooses it. Started by skarbiec login get, POST /v1/operator/items/site-get.
What failed: computing the one-time code of {item}. Why: {item} gives no one-time code: {reason}. What the refusal shows: {item} is the login {host} signs in with.
Fix: record its seed with skarbiec totp set {item} (the Base32 seed or otpauth:// address on standard input); skarbiec totp seed {item} says what it keeps.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/read/site_get.sh::a_one_time_code_from_a_login_keeping_no_seed_is_refused_naming_totp_set.
skarbiec.login-factor-list login-factor-not-login#
say which second factor each login's sign-in demands after its password and whether the vault holds what answers it: held, undeclared, missing-seed, invalid or not-held, without a sign-in. Started by skarbiec login factor list, skarbiec login factor list <item-id>, POST /v1/operator/items/factors, MCP skarbiec_login_factors, Desktop: Settings → Policy → Sign-in factors.
What failed: {doing} {id}. Why: {id} is a {kind}, and a second factor is recorded for logins only. What the refusal shows: {id} is a {kind}.
Fix: name a login: skarbiec list --kind login lists them; skarbiec login factor list names every login's record.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/login_factor.sh::an_item_that_is_not_a_login_is_refused_naming_its_kind.
skarbiec.login-factor-set login-factor-not-login#
record which second factor one login's sign-in demands after its password, by its owner, or remove that record; and record or remove where it is asked for: the identity provider's site the login signs in through, and the page showing its account's two-step settings. Started by skarbiec login factor set, skarbiec login factor unset, skarbiec login factor via, skarbiec login factor page, POST /v1/operator/items/factor/set, POST /v1/operator/items/factor/unset, POST /v1/operator/items/factor/place, Desktop: Settings → Policy → Sign-in factors → Record, Remove the record, Signs in through, Security page.
What failed: {doing} {id}. Why: {id} is a {kind}, and a second factor is recorded for logins only. What the refusal shows: {id} is a {kind}.
Fix: name a login: skarbiec list --kind login lists them; skarbiec login factor list names every login's record.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/login_factor.sh::an_item_that_is_not_a_login_is_refused_naming_its_kind.
skarbiec.login-factor-set login-factor-none-recorded#
record which second factor one login's sign-in demands after its password, by its owner, or remove that record; and record or remove where it is asked for: the identity provider's site the login signs in through, and the page showing its account's two-step settings. Started by skarbiec login factor set, skarbiec login factor unset, skarbiec login factor via, skarbiec login factor page, POST /v1/operator/items/factor/set, POST /v1/operator/items/factor/unset, POST /v1/operator/items/factor/place, Desktop: Settings → Policy → Sign-in factors → Record, Remove the record, Signs in through, Security page.
What failed: removing the {what} recorded for {id}. Why: {holder} records no {what} for {id}, so there is nothing to remove. What the refusal shows: {holder}'s context records no {what}.
Fix: skarbiec login factor list {id} says what the second factor record holds; login factor via {id} and login factor page {id} read the other two.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/login_factor.sh::removing_a_record_a_login_does_not_keep_is_refused.
skarbiec.login-factor-observe login-factor-not-login#
have Weles read, from the page an account shows its two-step settings on (context.security_page), in the account's own browser profile and without signing in, what the account asks after its password, at any site, and record it on the item keeping its second factor. Started by skarbiec login factor observe, skarbiec login factor observe <item-id>, POST /v1/operator/items/factor/observe, Desktop: Settings → Policy → Sign-in factors → Observe every account, Observe.
What failed: {doing} {id}. Why: {id} is a {kind}, and a second factor is recorded for logins only. What the refusal shows: {id} is a {kind}.
Fix: name a login: skarbiec list --kind login lists them; skarbiec login factor list names every login's record.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/login_factor.sh::an_item_that_is_not_a_login_is_refused_naming_its_kind.
skarbiec.login-factor-observe login-factor-observe-no-page#
have Weles read, from the page an account shows its two-step settings on (context.security_page), in the account's own browser profile and without signing in, what the account asks after its password, at any site, and record it on the item keeping its second factor. Started by skarbiec login factor observe, skarbiec login factor observe <item-id>, POST /v1/operator/items/factor/observe, Desktop: Settings → Policy → Sign-in factors → Observe every account, Observe.
What failed: observing what the account of {id} asks after the password. Why: {holder} names no page where the account shows its two-step settings, so Weles has nowhere to read them. What the refusal shows: {holder}'s context.security_page: none.
Fix: skarbiec login factor page {id} --set <https address of the account's two-step settings>; or a sign-in of {id} through Weles that meets a second step records it; or skarbiec login factor set {id} --factor <none|totp|push|sms|email|security-key>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/login_factor.sh::observing_a_login_whose_account_names_no_security_page_is_refused.
skarbiec.login-factor-observe login-factor-observe-weles-refused#
have Weles read, from the page an account shows its two-step settings on (context.security_page), in the account's own browser profile and without signing in, what the account asks after its password, at any site, and record it on the item keeping its second factor. Started by skarbiec login factor observe, skarbiec login factor observe <item-id>, POST /v1/operator/items/factor/observe, Desktop: Settings → Policy → Sign-in factors → Observe every account, Observe.
What failed: {doing} {login}. Why: Weles answered {status}. What the refusal shows: its message: {message}; code {code}, phase {phase}.
Fix: the message names Weles's own fix; weles errors show credentials lists every cause of its admission, and weles worker status says whether its worker is ready.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/login_factor.sh::an_observation_weles_cannot_take_is_refused_naming_its_answer.
skarbiec.login-identity-list login-identity-not-login#
say which identity each login signs in as, which logins sign in as each identity with the identity's seed state, recovery codes left and verification, and every account the vault names (identities, sign-ins delegated to a provider, subscriptions) with what it lacks. Started by skarbiec login identity list, skarbiec login identity list <login-id>, skarbiec login identity list --accounts, POST /v1/operator/logins/identities, MCP skarbiec_login_identities, Desktop: Accounts.
What failed: {doing} {id}. Why: {id} is a {kind}, and only a login signs in as an identity. What the refusal shows: {id} is a {kind}.
Fix: name a login: skarbiec list --kind login lists them; skarbiec login identity list names the identity each one signs in as.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity.sh::an_item_that_is_not_a_login_is_refused_naming_its_kind.
skarbiec.login-identity-set login-identity-not-login#
name the identity one login signs in as, by the role it plays or the account address it records, moving the login's own seed and second-factor record onto it when the identity keeps none, or remove that name. Started by skarbiec login identity set, skarbiec login identity unset, POST /v1/operator/logins/identity/set, POST /v1/operator/logins/identity/unset, Desktop: Item → Signs in as.
What failed: {doing} {id}. Why: {id} is a {kind}, and only a login signs in as an identity. What the refusal shows: {id} is a {kind}.
Fix: name a login: skarbiec list --kind login lists them; skarbiec login identity list names the identity each one signs in as.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity.sh::an_item_that_is_not_a_login_is_refused_naming_its_kind.
skarbiec.login-identity-set login-identity-not-identity#
name the identity one login signs in as, by the role it plays or the account address it records, moving the login's own seed and second-factor record onto it when the identity keeps none, or remove that name. Started by skarbiec login identity set, skarbiec login identity unset, POST /v1/operator/logins/identity/set, POST /v1/operator/logins/identity/unset, Desktop: Item → Signs in as.
What failed: {doing} {login}. Why: {named} is held by {id}, a {kind}, and a login signs in only as an identity item. What the refusal shows: {id} is a {kind}.
Fix: name the account's identity: skarbiec list --kind identity lists them, and skarbiec login identity link --account <address> --role <role> makes one for an account that has none.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity.sh::a_target_that_is_not_an_identity_is_refused_naming_its_kind.
skarbiec.login-identity-set login-identity-role-unheld#
name the identity one login signs in as, by the role it plays or the account address it records, moving the login's own seed and second-factor record onto it when the identity keeps none, or remove that name. Started by skarbiec login identity set, skarbiec login identity unset, POST /v1/operator/logins/identity/set, POST /v1/operator/logins/identity/unset, Desktop: Item → Signs in as.
What failed: {doing} {login}. Why: no live item plays role {role}, so it names no identity. What the refusal shows: items tagged stado:role:{role}: none.
Fix: skarbiec login identity link --account <address> --role {role} makes the account's identity with that role, or skarbiec retag --add stado:role:{role} <identity-id> gives an existing one the role.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity.sh::a_role_no_item_plays_is_refused_naming_the_role.
skarbiec.login-identity-set login-identity-account-unheld#
name the identity one login signs in as, by the role it plays or the account address it records, moving the login's own seed and second-factor record onto it when the identity keeps none, or remove that name. Started by skarbiec login identity set, skarbiec login identity unset, POST /v1/operator/logins/identity/set, POST /v1/operator/logins/identity/unset, Desktop: Item → Signs in as.
What failed: {doing} {login}. Why: no identity item records {account} as its email, so the address names no identity. What the refusal shows: identities with email {account}: none.
Fix: skarbiec login identity link --account {account} --role <role> makes it and links every login of that account.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity.sh::an_account_no_identity_records_is_refused_naming_the_address.
skarbiec.login-identity-set login-identity-seeds-differ#
name the identity one login signs in as, by the role it plays or the account address it records, moving the login's own seed and second-factor record onto it when the identity keeps none, or remove that name. Started by skarbiec login identity set, skarbiec login identity unset, POST /v1/operator/logins/identity/set, POST /v1/operator/logins/identity/unset, Desktop: Item → Signs in as.
What failed: {doing}. Why: {holders} keep different working authenticator seeds, and an account has one authenticator, so the seed its identity must keep cannot be told. What the refusal shows: working seeds on: {holders}.
Fix: find which seed the account accepts (skarbiec totp code <item> beside the code the account's authenticator shows), keep it on one item, empty the others with skarbiec field unset <item> totp_secret, and run it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity_link.sh::logins_keeping_different_seeds_are_refused_naming_them.
skarbiec.login-identity-set login-identity-none-linked#
name the identity one login signs in as, by the role it plays or the account address it records, moving the login's own seed and second-factor record onto it when the identity keeps none, or remove that name. Started by skarbiec login identity set, skarbiec login identity unset, POST /v1/operator/logins/identity/set, POST /v1/operator/logins/identity/unset, Desktop: Item → Signs in as.
What failed: removing the identity {id} signs in as. Why: {id} names no identity, so there is nothing to remove. What the refusal shows: {id}'s context.identity: none.
Fix: nothing to do; skarbiec login identity list {id} says what it signs in as.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity.sh::unsetting_a_login_that_names_no_identity_is_refused.
skarbiec.login-identity-set login-identity-seed-stranded#
name the identity one login signs in as, by the role it plays or the account address it records, moving the login's own seed and second-factor record onto it when the identity keeps none, or remove that name. Started by skarbiec login identity set, skarbiec login identity unset, POST /v1/operator/logins/identity/set, POST /v1/operator/logins/identity/unset, Desktop: Item → Signs in as.
What failed: removing the identity {id} signs in as. Why: {id} keeps no seed of its own and its account's seed is on {identity}, so after the removal no sign-in of {id} could answer the authenticator code {identity} records. What the refusal shows: {identity} records {factor}; {id}'s totp_secret: none.
Fix: store the seed on {id} first (skarbiec totp uri {identity} | skarbiec totp set {id}), then remove the identity.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity.sh::unsetting_a_login_whose_seed_is_on_the_identity_is_refused.
skarbiec.login-identity-link login-identity-role-elsewhere#
find every login of one account at one identity provider (its context.account_ref, username or email; the provider --via names, or the only one its logins sign in through), make the account's identity with the role named and that provider's site when the vault has none, and, with --yes, name it on each of those logins and move their one working seed and second-factor record onto it; without --yes say what it would do and write nothing. Started by skarbiec login identity link --account <address> [--via <site>] --role <role>, POST /v1/operator/logins/identity/link, Desktop: Accounts → Link logins.
What failed: linking the logins of {account}. Why: role {role} is played by {holder}, which is {what}, so it cannot also be the role of {account}'s identity. What the refusal shows: stado:role:{role} on {holder}.
Fix: name another role for {account}, or take the role off {holder}: skarbiec retag --remove stado:role:{role} {holder}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity_link.sh::a_role_another_item_plays_is_refused_naming_it.
skarbiec.login-identity-link login-identity-seeds-differ#
find every login of one account at one identity provider (its context.account_ref, username or email; the provider --via names, or the only one its logins sign in through), make the account's identity with the role named and that provider's site when the vault has none, and, with --yes, name it on each of those logins and move their one working seed and second-factor record onto it; without --yes say what it would do and write nothing. Started by skarbiec login identity link --account <address> [--via <site>] --role <role>, POST /v1/operator/logins/identity/link, Desktop: Accounts → Link logins.
What failed: {doing}. Why: {holders} keep different working authenticator seeds, and an account has one authenticator, so the seed its identity must keep cannot be told. What the refusal shows: working seeds on: {holders}.
Fix: find which seed the account accepts (skarbiec totp code <item> beside the code the account's authenticator shows), keep it on one item, empty the others with skarbiec field unset <item> totp_secret, and run it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity_link.sh::logins_keeping_different_seeds_are_refused_naming_them.
skarbiec.login-identity-link login-identity-providers-several#
find every login of one account at one identity provider (its context.account_ref, username or email; the provider --via names, or the only one its logins sign in through), make the account's identity with the role named and that provider's site when the vault has none, and, with --yes, name it on each of those logins and move their one working seed and second-factor record onto it; without --yes say what it would do and write nothing. Started by skarbiec login identity link --account <address> [--via <site>] --role <role>, POST /v1/operator/logins/identity/link, Desktop: Accounts → Link logins.
What failed: linking the logins of {account}. Why: {account}'s logins sign in through several identity providers ({sites}), each its own account with its own second step, so which account to link cannot be told. What the refusal shows: sites named in context.sign_in_via: {sites}.
Fix: name the provider: skarbiec login identity link --account {account} --via <site> --role <role>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/identity_link.sh::an_address_at_two_providers_is_refused_until_one_is_named.
skarbiec.maintain maintain-pass-failed#
run every scheduled step of this host once: the readiness proof, bond pulls, the mirror push, ended shares, autofill cover, the scheduled backup, kept CI secrets, due rotations, due subscription sign-ins, the second factor of every account no provider has shown one for, at any site whose two-step settings page it names, and the authenticator enrolment of every account that asks for a code and keeps no seed it accepts. Started by skarbiec maintain.
What failed: running one maintenance pass. Why: {reasons}. What the refusal shows: every other step ran; {alert}.
Fix: fix each step the reasons name — its own command (mirror push, shares expire, browser cover, backup, ci keep, rotation run, subscription run, login factor observe, credential enrol) says the same with its own fix — then run skarbiec maintain again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/maintain/refusals.sh::a_pass_with_a_failing_step_is_refused_naming_the_step.
skarbiec.credential.managed-write no-active-operation#
admit Weles's write of a credential's new value for the role's active operation. Started by PUT /v1/items (mode acquire), PUT /v1/items (mode stage).
What failed: admitting a managed write for role {role}. Why: role {role} has no readable active credential operation to write for. What the refusal shows: record: {record}; reading it said: {error}.
Fix: start the operation (skarbiec credential acquire|rotate|reset role:{role} …); Weles writes only for an operation Skarbiec recorded.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_write_for_a_role_with_no_operation_is_refused.
skarbiec.credential.managed-write not-this-operation#
admit Weles's write of a credential's new value for the role's active operation. Started by PUT /v1/items (mode acquire), PUT /v1/items (mode stage).
What failed: admitting a managed write for role {role}. Why: the write's {what} is not the active operation's: it presents {presented}, the operation recorded {recorded}. What the refusal shows: operation record: {record}.
Fix: write for the operation as Skarbiec recorded it (credential status role:{role} --local shows its request id, writer, baseline and status); a write for an earlier or other operation is never admitted.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_write_presenting_another_request_id_is_refused_naming_both.
skarbiec.credential.managed-write capture-origin-mismatch#
admit Weles's write of a credential's new value for the role's active operation. Started by PUT /v1/items (mode acquire), PUT /v1/items (mode stage).
What failed: admitting the acquired value for role {role}. Why: Weles captured it at {captured}, and the operation declared the signup origin {declared}. What the refusal shows: capture_origin: {captured}; signup_origin: {declared}.
Fix: acquire again with the --signup-origin the provider's signup is actually served from.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::an_acquisition_captured_at_another_origin_is_refused_naming_both.
skarbiec.credential.managed-write write-quarantined#
admit Weles's write of a credential's new value for the role's active operation. Started by PUT /v1/items (mode acquire), PUT /v1/items (mode stage).
What failed: admitting a managed write for role {role}. Why: role {role} is quarantined, and no managed write lands until the quarantine is resolved. What the refusal shows: quarantine of role {role}: active.
Fix: resolve it: skarbiec credential quarantine resolve role:{role} --confirm '…' --local.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_write_for_a_quarantined_role_is_refused.
skarbiec.credential.managed-write baseline-stale#
admit Weles's write of a credential's new value for the role's active operation. Started by PUT /v1/items (mode acquire), PUT /v1/items (mode stage).
What failed: admitting a managed write for role {role}. Why: {why}. What the refusal shows: item {item}: revision {revision}; operation baseline: {baseline}.
Fix: start the operation again from the item as it stands; credential status role:{role} --local shows both.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_rotation_write_against_a_moved_revision_is_refused_naming_both.
skarbiec.mcp mcp-stdin-unreadable#
serve Skarbiec's read-only MCP tools, or the broker's, to an agent client over standard input and output. Started by skarbiec mcp.
What failed: reading the next request from standard input. Why: standard input answered a read with an error rather than a request or its end: it is a directory, a closed descriptor or a device that fails. What the refusal shows: the system said: {said}; the server stopped; requests answered before it stand.
Fix: start skarbiec mcp with standard input connected to the agent client's pipe, as the client's MCP server configuration does.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/refusals.sh::a_standard_input_that_cannot_be_read_stops_the_server_naming_it.
skarbiec.mcp mcp-stdout-unwritable#
serve Skarbiec's read-only MCP tools, or the broker's, to an agent client over standard input and output. Started by skarbiec mcp.
What failed: writing the answer to request {id} to standard output. Why: standard output no longer takes an answer: the client closed its end of the pipe, or the descriptor fails. What the refusal shows: the system said: {said}; the server stopped; the client is no longer reading its answers.
Fix: start skarbiec mcp with standard output connected to the agent client's pipe; a client that went away starts it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/refusals.sh::a_closed_standard_output_stops_the_server_naming_it.
skarbiec.mcp-broker mcp-broker-agent-unset#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: naming the agent a broker call is made for. Why: SKARBIEC_MCP_AGENT_ID is not set on the broker, and the agent is the operator's statement, never a tool argument. What the refusal shows: nothing was filed or issued.
Fix: start skarbiec mcp broker with SKARBIEC_MCP_AGENT_ID set to the agent's exact name.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::a_broker_without_an_agent_is_refused_naming_the_variable.
skarbiec.mcp-broker mcp-broker-agent-not-exact#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: naming the agent a broker call is made for. Why: SKARBIEC_MCP_AGENT_ID is {agent}, which is not one exact name of letters, digits, '.', '_' and '-'. What the refusal shows: nothing was filed or issued.
Fix: set SKARBIEC_MCP_AGENT_ID to the agent's exact name.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::an_agent_that_is_not_one_exact_name_is_refused.
skarbiec.mcp-broker mcp-broker-arguments-not-object#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: calling the broker tool {tool}. Why: its arguments are {held}, and a tool's arguments are one JSON object. What the refusal shows: nothing was filed or issued.
Fix: call {tool} with arguments as one object; tools/list states its input schema.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::arguments_that_are_not_an_object_are_refused.
skarbiec.mcp-broker mcp-broker-argument-undeclared#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: calling the broker tool {tool}. Why: argument {name} is not part of {tool}'s schema. What the refusal shows: nothing was filed or issued.
Fix: leave {name} out; tools/list states the arguments {tool} takes.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::an_argument_the_schema_does_not_declare_is_refused_naming_it.
skarbiec.mcp-broker mcp-broker-argument-shape#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: calling the broker tool {tool}. Why: argument {name} does not have the shape {tool}'s schema declares: {shape}. What the refusal shows: nothing was filed or issued.
Fix: give {name} as {shape}: text without surrounding space or line breaks, or a whole number at least the minimum.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::an_argument_of_another_shape_is_refused_naming_the_shape.
skarbiec.mcp-broker mcp-broker-argument-required#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: calling the broker tool {tool}. Why: argument {name} is required, and the call gives none. What the refusal shows: nothing was filed or issued.
Fix: call {tool} with {name}; tools/list states what {tool} requires.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::a_call_missing_a_required_argument_is_refused_naming_it.
skarbiec.mcp-broker mcp-broker-request-unknown#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: reporting the access request {id}. Why: {agent} filed no access request {id}; an agent reads only the requests it filed. What the refusal shows: nothing was read.
Fix: name the request_id capability_request answered with for this agent.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::a_request_this_agent_did_not_file_is_refused.
skarbiec.mcp-broker mcp-broker-request-state-unknown#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: reporting the access request {id}. Why: the register records it in the state {state}, which is none of pending, approved, denied and withdrawn. What the refusal shows: nothing was read.
Fix: read it with skarbiec request show {id}; when nothing can decide it, call capability_request again, which files a new one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::a_request_in_a_state_the_broker_does_not_know_is_refused.
skarbiec.mcp-broker mcp-broker-approved-without-capability#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: reporting the access request {id}. Why: the register records it approved with no capability issued for it. What the refusal shows: nothing was read.
Fix: ask its decider, whom skarbiec request show {id} names, and call capability_request again, which files a new one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::an_approved_request_without_a_capability_is_refused.
skarbiec.mcp-broker mcp-broker-generation-missing#
answer an agent's call of the broker's four tools: health, whether a bounded capability is available, a request for one a person decides, and that decision. Started by skarbiec mcp broker (tools/call).
What failed: reporting the broker's health. Why: the vault document records no generation as a whole number, which every save writes. What the refusal shows: vault file: {path}.
Fix: restore the vault from a backup with skarbiec backup restore <backup-file>; skarbiec doctor names what else is wrong.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/broker.sh::a_vault_recording_no_generation_is_refused.
skarbiec.mcp-tools mcp-tool-unknown#
answer an agent's call of one read-only vault tool with what the command it mirrors answers, or with the declared refusal as a JSON-RPC error. Started by skarbiec mcp (tools/call).
What failed: calling the MCP tool {tool}. Why: this server has no tool {tool}. What the refusal shows: tools this server lists: {tools}.
Fix: call one of the tools tools/list names.
Code not_found, exit status 2, not worth retrying unchanged. Provoked by tests/mcp/tools.sh::an_unknown_tool_is_refused_naming_the_tools.
skarbiec.mcp-tools mcp-argument-missing#
answer an agent's call of one read-only vault tool with what the command it mirrors answers, or with the declared refusal as a JSON-RPC error. Started by skarbiec mcp (tools/call).
What failed: calling the MCP tool {tool}. Why: {tool} needs {argument} as text, {meaning}, and the call gives none. What the refusal shows: nothing was read.
Fix: call {tool} with arguments.{argument}; tools/list states each tool's input schema.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/mcp/tools.sh::a_tool_called_without_what_it_needs_is_refused_naming_it.
skarbiec.mcp-tools mcp-path-relative#
answer an agent's call of one read-only vault tool with what the command it mirrors answers, or with the declared refusal as a JSON-RPC error. Started by skarbiec mcp (tools/call).
What failed: calling the MCP tool {tool}. Why: {argument} is {path}, a relative path, and the server's working directory is not the agent's. What the refusal shows: nothing was read.
Fix: call {tool} with {argument} as an absolute path.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/mcp/tools.sh::a_relative_bindings_file_is_refused_naming_it.
skarbiec.mcp-tools mcp-tool-unanswered#
answer an agent's call of one read-only vault tool with what the command it mirrors answers, or with the declared refusal as a JSON-RPC error. Started by skarbiec mcp (tools/call).
What failed: calling the MCP tool {tool}. Why: the command it runs, skarbiec {command}, answered nothing in this build. What the refusal shows: nothing was read.
Fix: run skarbiec {command} on the command line to see what it answers, and install a release whose MCP tools all answer (skarbiec about names this one).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/tools.sh::a_tool_whose_command_answers_nothing_is_refused_naming_it.
skarbiec.mcp-tools mcp-resolve-unconfigured#
answer an agent's call of one read-only vault tool with what the command it mirrors answers, or with the declared refusal as a JSON-RPC error. Started by skarbiec mcp (tools/call).
What failed: resolving a route over MCP. Why: skarbiec_route_resolve needs {variable} set on the MCP server ({meaning}), and it is not. What the refusal shows: nothing was resolved.
Fix: start skarbiec mcp with {variable} set in its environment.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/tools.sh::route_resolve_on_an_unconfigured_server_is_refused_naming_the_variable.
skarbiec.mcp-tools mcp-out-dir-relative#
answer an agent's call of one read-only vault tool with what the command it mirrors answers, or with the declared refusal as a JSON-RPC error. Started by skarbiec mcp (tools/call).
What failed: resolving a route over MCP. Why: SKARBIEC_MCP_OUT_DIR is {dir}, a relative path, which would put resolved credentials wherever the server was started. What the refusal shows: nothing was resolved.
Fix: start skarbiec mcp with SKARBIEC_MCP_OUT_DIR set to an absolute directory.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/tools.sh::a_relative_out_dir_is_refused_naming_it.
skarbiec.mcp-tools mcp-token-file-empty#
answer an agent's call of one read-only vault tool with what the command it mirrors answers, or with the declared refusal as a JSON-RPC error. Started by skarbiec mcp (tools/call).
What failed: reading the grant SKARBIEC_MCP_TOKEN_FILE names, {path}. Why: the file holds no grant. What the refusal shows: nothing was resolved.
Fix: write the consumer's grant into {path}, or unset SKARBIEC_MCP_TOKEN_FILE.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mcp/tools.sh::an_empty_token_file_is_refused_naming_it.
skarbiec.migrate migrate-owners-differ#
copy every live item of one vault file into another, re-encrypted to the target's recipients; skip, replace or reconcile an id both hold, and set a reconciled copy aside. Started by skarbiec migrate, POST /v1/operator/migrate.
What failed: reconciling {from} into {to}. Why: --reconcile joins two files of one owner, and {from} is owned by {source_owner} while {to} is owned by {target_owner}. What the refusal shows: nothing was written.
Fix: migrate without --reconcile to copy items between vaults of different owners.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/vault/migrations/migrate.sh::reconciling_vaults_of_different_owners_is_refused_naming_both.
skarbiec.migrate migrate-managed#
copy every live item of one vault file into another, re-encrypted to the target's recipients; skip, replace or reconcile an id both hold, and set a reconciled copy aside. Started by skarbiec migrate, POST /v1/operator/migrate.
What failed: migrating {id} into {to}. Why: {id} is managed by {controller}, and a copy would overwrite what it manages. What the refusal shows: items migrated before {id} are written; {id} and the rest are not.
Fix: change it through what manages it (skarbiec credential <operation> role:<role>), or leave it out of the source.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/vault/migrations/migrate.sh::an_item_the_target_manages_elsewhere_is_refused_naming_its_controller.
skarbiec.migrate migrate-retire-failed#
copy every live item of one vault file into another, re-encrypted to the target's recipients; skip, replace or reconcile an id both hold, and set a reconciled copy aside. Started by skarbiec migrate, POST /v1/operator/migrate.
What failed: setting the reconciled copy {from} aside as {retired}. Why: the directory of {from} did not let this account add the name {retired} beside it, so the copy is not set aside. What the refusal shows: the file system said: {error}; every item is in {to}; the copy {from} is still where it was.
Fix: let this account write the directory of {from}, then run the same migrate --reconcile again: it finds every item kept and sets the copy aside.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/migrations/migrate.sh::a_reconciled_copy_that_cannot_be_set_aside_is_refused_naming_it.
skarbiec.migrate migrate-retire-unlink-failed#
copy every live item of one vault file into another, re-encrypted to the target's recipients; skip, replace or reconcile an id both hold, and set a reconciled copy aside. Started by skarbiec migrate, POST /v1/operator/migrate.
What failed: removing the name {from} of the reconciled copy. Why: the copy is set aside as {retired}, and the directory of {from} did not let this account remove the old name (a sticky directory keeps a file another account owns). What the refusal shows: the file system said: {error}; every item is in {to}; the copy is under both {from} and {retired}.
Fix: remove {from} as the account that owns it (rm {from}); {retired} keeps the copy.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/migrations/migrate.sh::a_reconciled_copy_whose_old_name_cannot_be_removed_is_refused_naming_both.
skarbiec.mirror mirror-absent#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: {doing}. Why: there is no mirror in {sync_dir}. What the refusal shows: nothing was changed.
Fix: create it with skarbiec mirror init <remote-url>, or name the mirror with SKARBIEC_SYNC_DIR.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/refusals.sh::a_mirror_command_with_no_mirror_is_refused_naming_init.
skarbiec.mirror mirror-git-refused#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: {doing} in {sync_dir}. Why: git refused the step and ended with {ended}, so the mirror did not take it. What the refusal shows: command: {command}; git said: {said}; the live vault was not changed.
Fix: fix what git names (the remote's address, access to it, or the branch) after running {command} to see its refusal in full, then run the same skarbiec command again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/refusals.sh::a_remote_git_cannot_push_to_is_refused_in_gits_words.
skarbiec.mirror mirror-publish-unread#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: reading whether this host publishes the mirror in {sync_dir}. Why: git could not read the key skarbiec.publish and ended with {ended} saying why: {sync_dir}/.git/config is not a configuration git can read, where a key that is merely absent ends git silently. What the refusal shows: command: {command}; git said: {said}; nothing was pushed.
Fix: run {command} to see the line git stops at, repair or remove that line of {sync_dir}/.git/config, then run skarbiec mirror publish (or unpublish) again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/publish.sh::an_unreadable_mirror_config_fails_the_pass_instead_of_reading_as_a_host_that_does_not_publish.
skarbiec.mirror mirror-never-pushed#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: checking that the mirror in {sync_dir} carries the live vault. Why: the mirror has never pushed {pushed}, so no copy of the vault is published from this host. What the refusal shows: command: {command}; git said: {said}.
Fix: push it with skarbiec mirror push; skarbiec mirror publish has every maintain pass push it after that.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/publish.sh::a_mirror_that_never_pushed_fails_the_mirror_check_naming_the_branch.
skarbiec.mirror mirror-stale#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: checking that the mirror in {sync_dir} carries the live vault. Why: the live vault changed after the last push to {pushed}, at {at}, and nothing published it since. What the refusal shows: live vault {vault}: {live} bytes; the copy last pushed: {copy} bytes.
Fix: push it with skarbiec mirror push; skarbiec mirror publish has every maintain pass push it after that.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/publish.sh::a_vault_changed_after_the_last_push_fails_the_mirror_check.
skarbiec.mirror mirror-no-vault#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: pushing the vault to the mirror. Why: there is no vault at {path} to push. What the refusal shows: nothing was pushed.
Fix: name the vault with SKARBIEC_VAULT_FILE, or create one with skarbiec init <owner-uid>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/refusals.sh::a_push_with_no_vault_is_refused_naming_the_path.
skarbiec.mirror mirror-nothing-mirrored#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: pulling the vault from the mirror. Why: the mirror's branch {branch} holds no vault.enc.json. What the refusal shows: the live vault was not changed.
Fix: push a vault to the mirror from the host that holds it with skarbiec mirror push.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/refusals.sh::a_pull_from_a_mirror_holding_no_vault_is_refused.
skarbiec.mirror mirror-pull-would-lose#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: pulling the vault from the mirror. Why: {count} local item(s) are not in the mirror and would be lost: {items}. What the refusal shows: the live vault is unchanged and backed up at {backup}.
Fix: push them first with skarbiec mirror push, or run the pull again with --force to accept the loss.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/refusals.sh::a_pull_that_would_lose_local_items_is_refused_naming_them.
skarbiec.mirror mirror-pulled-not-json#
keep a Git mirror of the encrypted vault: set it up, push the vault to it, pull it back, and have maintain push it. Started by skarbiec mirror, POST /v1/operator/sync/init, POST /v1/operator/sync/push, POST /v1/operator/sync/pull, POST /v1/operator/sync/publish, POST /v1/operator/sync/unpublish.
What failed: comparing the vault pulled into {path} with the live vault. Why: the vault the mirror's branch {branch} holds is not JSON, so it is no vault skarbiec wrote and cannot replace the live one. What the refusal shows: {bytes} bytes; the JSON reader stopped at line {line}, column {column}: {said}; the live vault is unchanged and backed up at {backup}.
Fix: push a vault that reads from the host that holds it (skarbiec mirror push there), then pull again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/mirror/refusals.sh::a_pull_of_a_mirror_holding_no_json_is_refused_naming_where_it_stops.
skarbiec.browser.host.frames browser-host-stdin-unread#
read one length-prefixed JSON request from standard input and write one length-prefixed JSON answer to standard output. Started by other functionalities only.
What failed: reading a request from the browser extension. Why: standard input failed while the host read {step}. What the refusal shows: the system said: {said}; the host stops.
Fix: reload the extension, which starts the host again; skarbiec browser status says whether its manifests are installed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_request_whose_input_fails_stops_the_host_naming_the_step.
skarbiec.browser.host.frames browser-host-frame-short#
read one length-prefixed JSON request from standard input and write one length-prefixed JSON answer to standard output. Started by other functionalities only.
What failed: reading a request from the browser extension. Why: the request declared {length} bytes, and standard input ended after {got}. What the refusal shows: nothing was answered for it; the host stops.
Fix: reload the extension, which starts the host again; only a browser that closed the host mid-message sends less.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_request_shorter_than_it_declares_stops_the_host_naming_both.
skarbiec.browser.host.frames browser-host-frame-not-json#
read one length-prefixed JSON request from standard input and write one length-prefixed JSON answer to standard output. Started by other functionalities only.
What failed: reading a request from the browser extension. Why: the {length}-byte request is not JSON: the reader stopped at line {line}, column {column}. What the refusal shows: the parser said: {said}; the host stops.
Fix: send each request as one JSON object; the extension of this skarbiec's release does.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_request_that_is_not_json_stops_the_host_naming_where.
skarbiec.browser.host.frames browser-host-reply-unwritten#
read one length-prefixed JSON request from standard input and write one length-prefixed JSON answer to standard output. Started by other functionalities only.
What failed: answering the browser extension. Why: standard output refused the {bytes}-byte answer at {step}: the browser closed the host's pipe. What the refusal shows: the system said: {said}; the host stops.
Fix: reload the extension, which starts the host again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::an_answer_the_browser_no_longer_reads_stops_the_host_naming_it.
skarbiec.browser.host.frames browser-host-reply-too-long#
read one length-prefixed JSON request from standard input and write one length-prefixed JSON answer to standard output. Started by other functionalities only.
What failed: answering the browser extension. Why: the answer is {bytes} bytes, past the {limit} a native message's 32-bit length can state. What the refusal shows: nothing was written; the host stops.
Fix: narrow the request: search for a text, or list one site, instead of every login.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::an_answer_past_what_a_frame_states_stops_the_host.
skarbiec.browser.host browser-host-action-absent#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: answering a request of the browser extension. Why: the request names no action, so the host cannot tell what it asks. What the refusal shows: request keys: {keys}.
Fix: send one of the actions the host answers ({actions}) as "action"; the extension of this skarbiec's release does.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_request_naming_no_action_is_answered_naming_the_actions.
skarbiec.browser.host browser-host-action-unknown#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: answering a request of the browser extension. Why: {action} is not one of the actions the host answers ({actions}). What the refusal shows: request keys: {keys}.
Fix: update the extension and skarbiec to one release (skarbiec --version says this one), or send one of {actions}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::an_action_the_host_does_not_answer_is_answered_naming_the_actions.
skarbiec.browser.host browser-host-request-incomplete#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: answering the extension's {action} request. Why: {action} needs {needed}, and the request carries none. What the refusal shows: request keys: {keys}.
Fix: send {needed} with the {action} request.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_request_missing_what_its_action_needs_is_answered_naming_it.
skarbiec.browser.host browser-host-home-unset#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: finding the browser-host grant. Why: neither SKARBIEC_BROWSER_TOKEN_FILE nor HOME is set, so there is no place the grant file is looked for. What the refusal shows: nothing was asked of the loopback API.
Fix: start the browser from a session where HOME is set; skarbiec browser status names the grant file browser install writes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_host_without_home_is_answered_naming_both_variables.
skarbiec.browser.host browser-host-api-refused#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: asking the loopback API {path} for the browser extension. Why: the API at {base} refused the grant in {grant} with {status}. What the refusal shows: its cause: {cause}; its fix: {fix}; it said: {said}.
Fix: skarbiec browser status says whether that grant still reaches the logins; skarbiec browser cover widens it, and skarbiec browser install mints it again.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_grant_the_api_refuses_is_answered_with_the_api_s_cause.
skarbiec.browser.host browser-host-api-status#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: asking the loopback API {path} for the browser extension. Why: the API at {base} answered {status}, not 200 OK, and said no error. What the refusal shows: body: {body}.
Fix: run skarbiec serve of this skarbiec's release at {base} (skarbiec --version says which); skarbiec doctor says what answers there.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::an_api_answering_another_status_is_answered_naming_it.
skarbiec.browser.host browser-host-field-not-text#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: reading {field} of {id} for the browser extension. Why: the API answered {shape} for it, not the text a login's {field} is. What the refusal shows: no value was handed to the extension.
Fix: skarbiec get {id} --field {field} says what the item keeps there; skarbiec field set {id} {field} replaces it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_login_field_that_is_not_text_is_answered_naming_it.
skarbiec.browser.host browser-host-list-unshaped#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: listing the logins for the browser extension. Why: the API at {base} answered {shape} to /v1/items/list, not the list of items it answers. What the refusal shows: reply begins: {start}.
Fix: run skarbiec serve of this skarbiec's release at {base} (skarbiec --version says which).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::an_item_list_that_is_no_list_is_answered_naming_what_came.
skarbiec.browser.host browser-host-list-row-unnamed#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: listing the logins for the browser extension. Why: row {position} of the list /v1/items/list answered is a login with no text id. What the refusal shows: row: {row}.
Fix: run skarbiec serve of this skarbiec's release at {base} (skarbiec --version says which).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_listed_login_without_an_id_is_answered_naming_its_row.
skarbiec.browser.host browser-host-context-absent#
answer the extension's requests: list and fill logins through the loopback API with the host's grant, and pass on an offer. Started by skarbiec browser host, Browser: the autofill extension.
What failed: reading the sites {id} is offered on, for the browser extension. Why: the API's read of {id}'s context answered no value. What the refusal shows: reply keys: {keys}.
Fix: run skarbiec serve of this skarbiec's release (skarbiec --version says which); skarbiec get {id} --field context reads it here.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/browser/native_host.sh::a_context_read_without_a_value_is_answered_naming_the_item.
skarbiec.network network-address-not-dialled#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {target} is neither an https:// address nor an http:// address on this host's loopback interface, the only addresses Skarbiec dials. What the refusal shows: {observed}.
Fix: give the service's https:// address, or the http://127.0.0.1:<port> address a program on this host answers at.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::an_address_that_is_neither_https_nor_loopback_is_refused_naming_it.
skarbiec.network network-address-credentials#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {target} carries a user name or password in the address, which every log and process listing would show. What the refusal shows: {observed}.
Fix: remove user:password@ from the address and give the credential where the command takes it, as a header or an item field.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::an_address_carrying_credentials_is_refused.
skarbiec.network network-address-host#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {target} names no host to dial, or opens an IPv6 address with [ that it does not close with ]. What the refusal shows: {observed}.
Fix: give the address as https://<host>[:<port>]/<path>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::an_address_naming_no_host_is_refused.
skarbiec.network network-address-port#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {target} names a port that is not a whole number from 1 to 65535. What the refusal shows: {observed}.
Fix: give the port as digits after the host (https://<host>:8443/), or leave it out for 443.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::an_address_naming_a_port_that_is_no_number_is_refused.
skarbiec.network network-loopback-not-numeric#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {target} does not name a numeric loopback address and port (127.0.0.1:<port>, [::1]:<port> or localhost:<port>). What the refusal shows: {observed}.
Fix: give the loopback address with its port, as the program on this host prints it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_loopback_address_without_a_port_is_refused.
skarbiec.network network-loopback-off-host#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {target} is a plain http:// address off this host's loopback interface, and plain HTTP is spoken only to this host, never across a network. What the refusal shows: {observed}.
Fix: give the service's https:// address; a service on another host is reached through the route Stado's resolver answers.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_plain_http_address_off_this_host_is_refused.
skarbiec.network network-header-line-break#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the header {header} holds a line break, which would end the request early and let the value add headers of its own. What the refusal shows: {observed}.
Fix: store the value without line breaks: a token or address is one line.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_header_holding_a_line_break_is_refused_naming_it.
skarbiec.network network-schedule-unbounded#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: holding a network exchange to the run's schedule. Why: this run was started by Stado schedule {schedule} (STADO_SCHEDULE_ID), and {variable}, which a scheduled run needs to end its exchanges in time, is not set. What the refusal shows: STADO_SCHEDULE_ID={schedule}; {variable} unset.
Fix: start the run from its Stado schedule, which sets STADO_SCHEDULE_NEXT_DUE_AT and STADO_SCHEDULE_CRON, or unset STADO_SCHEDULE_ID for a run a person starts.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_scheduled_run_without_its_next_firing_is_refused_naming_it.
skarbiec.network network-schedule-moment-malformed#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: holding a network exchange to the run's schedule. Why: STADO_SCHEDULE_NEXT_DUE_AT {next_due} (schedule {schedule}) is not an RFC 3339 moment, so the exchange cannot be held to end before the next run. What the refusal shows: the time reader said: {said}.
Fix: set STADO_SCHEDULE_NEXT_DUE_AT as Stado does, such as 2026-11-09T12:00:00Z.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_schedule_moment_that_is_not_rfc3339_is_refused_naming_it.
skarbiec.network network-name-unresolved#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {host} does not resolve to an address from this host: the name does not exist, or this host's resolver does not answer. What the refusal shows: {observed}.
Fix: check the address for a typing error; when it is right, run the same command again once this host resolves names (dscacheutil -q host -a name {host}).
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::a_host_name_that_does_not_resolve_is_refused_naming_it.
skarbiec.network network-connection-refused#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: nothing listens at {authority}: the service is down, or the address names another port. What the refusal shows: {observed}.
Fix: run the same command again once the service answers at {authority}, or give the address it listens on.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::an_address_nothing_listens_at_is_refused_naming_it.
skarbiec.network network-unreachable#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: no route from this host reaches {authority}: this host is offline, or a network between drops the connection. What the refusal shows: {observed}.
Fix: run the same command again once this host reaches the network {authority} is on.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::an_address_no_route_reaches_is_refused_naming_it.
skarbiec.network network-deadline-passed#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the exchange did not end by the next firing of the Stado schedule that started this run, so it was ended for the next run to make. What the refusal shows: {observed}.
Fix: nothing to change when the service is slow only now: the next run tries again; a service always slower than the period needs a longer period.
Code timeout, exit status 69, worth retrying unchanged. Provoked by tests/net/https_in_process.sh::an_exchange_past_its_schedule_deadline_is_ended_naming_it.
skarbiec.network network-run-started-late#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: this run started after the next firing of the Stado schedule that started it, so no exchange was begun: the run is late, not the server. What the refusal shows: {observed}.
Fix: nothing to change in the service: the schedule's next run begins its exchanges in time; a run that keeps starting late waits behind other work on its host, which is where to look.
Code timeout, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::a_run_started_after_its_schedule_deadline_begins_no_exchange.
skarbiec.network network-connection-broken#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {authority} closed or reset the connection before its reply was whole. What the refusal shows: {observed}.
Fix: run the same command again; when it breaks again, the service at {authority} fails while answering.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::a_connection_closed_before_the_reply_is_refused.
skarbiec.network network-system-failed#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the operating system failed the connection to {authority} for a reason other than the name, the listener, the route or the deadline: no socket or port left to this process, or a device error. What the refusal shows: {observed}.
Fix: the system's words name which; raise the open-file limit (ulimit -n) or wait for sockets to close, then run the same command again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::a_connection_the_system_cannot_open_is_refused.
skarbiec.network network-trust-bundle-absent#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: this host keeps no trust bundle at {bundles} and SSL_CERT_FILE names none, so no server's certificate chain can be checked. What the refusal shows: {observed}.
Fix: install the system's CA certificates (ca-certificates), or name a PEM bundle of CA certificates with SSL_CERT_FILE.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_host_without_a_trust_bundle_is_refused_naming_where_it_looked.
skarbiec.network network-trust-bundle-empty#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the trust bundle {bundle} holds no PEM certificate whose key this client can use as a root. What the refusal shows: {observed}.
Fix: name a PEM bundle of CA certificates with SSL_CERT_FILE, or unset it to use this host's own.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_trust_bundle_holding_no_usable_root_is_refused_naming_it.
skarbiec.network network-tls-old-version#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {authority} speaks TLS 1.2 or older (it ended the handshake with alert 70, protocol_version), and Skarbiec's client speaks TLS 1.3 only. What the refusal shows: {observed}.
Fix: enable TLS 1.3 on the server at {authority}, or ask its operator to.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_server_speaking_only_tls_1_2_is_refused_naming_it.
skarbiec.network network-tls-alert#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: {authority} ended the TLS handshake with a fatal alert, refusing something this client offered or sent. What the refusal shows: {observed}.
Fix: the alert named above says what the server refused; a server that requires a client certificate or another cipher is not one Skarbiec's client reaches.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_server_ending_the_handshake_with_an_alert_is_refused_naming_it.
skarbiec.network network-tls-protocol#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: what answered at {authority} does not speak TLS 1.3 as RFC 8446 states it: it is no TLS server (plain HTTP on that port), or the stream was changed on the way. What the refusal shows: {observed}.
Fix: check that {target} names the service's https port; a plain-HTTP port answers no handshake.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::an_https_address_answered_by_plain_http_is_refused_naming_it.
skarbiec.network network-tls-untrusted#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the certificate {authority} sent is not trusted: its chain leads to no root in this host's trust bundle, it names another host, or it is outside its validity. What the refusal shows: {observed}.
Fix: check the address names the service itself; a service behind its own CA is trusted by naming a bundle holding that CA with SSL_CERT_FILE.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_server_whose_certificate_this_host_does_not_trust_is_refused.
skarbiec.network network-reply-malformed#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: what answered at {authority} is not HTTP/1.1: its status line, headers or body framing break the protocol. What the refusal shows: {observed}.
Fix: check that {target} names the service and not another program on that port.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_listener_that_does_not_answer_http_is_refused_naming_its_reply.
skarbiec.network network-status-not-found#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the service has nothing at the path asked for ({status}). What the refusal shows: {status}: {said}.
Fix: check the address's path; a list or API that moved is named by its publisher.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_reply_saying_the_path_is_not_there_is_refused_as_not_found.
skarbiec.network network-status-rate-limited#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the service is throttling requests from this host or credential ({status}). What the refusal shows: {status}: {said}.
Fix: run the same command again after the time the service names, or less often.
Code rate_limit, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::a_reply_throttling_the_request_is_refused_as_rate_limited.
skarbiec.network network-status-refused#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the service refused the request as sent ({status}), and it says why in its answer. What the refusal shows: {status}: {said}.
Fix: change what the answer above names (a field, a value, the request's shape) and run the command again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_reply_refusing_the_request_is_refused_naming_its_status.
skarbiec.network network-status-server-failed#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the service failed while answering ({status}), a fault on its side. What the refusal shows: {status}: {said}.
Fix: run the same command again once the service recovers; its status page says when.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/net/exchange.sh::a_reply_saying_the_service_failed_is_refused_as_retryable.
skarbiec.network network-status-unexpected#
send one HTTP/1.1 request, over Skarbiec's own TLS 1.3 client or to this host's loopback interface, and read its whole reply. Started by other functionalities only.
What failed: {what}: {method} {target}. Why: the service answered {status}, neither success nor a refusal: a redirect, which Skarbiec does not follow to an address it was not given. What the refusal shows: {status}: {said}.
Fix: give the address the redirect names, when it is the same service.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/exchange.sh::a_reply_redirecting_elsewhere_is_refused_naming_it.
skarbiec.onboarding onboarding-state-not-json#
walk the published first-use journey, writing and reading one non-secret note and showing its audit entry, or import an export during setup. Started by skarbiec onboarding.
What failed: resuming the first-use journey kept in {path}. Why: the journey state is not JSON: it stops being JSON at line {line}, column {column}. What the refusal shows: state file: {path}; the parser said: {said}.
Fix: skarbiec onboarding --reset starts a new journey; no vault item is removed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/onboarding/journey.sh::a_journey_state_that_does_not_read_as_one_is_refused_naming_the_reset.
skarbiec.onboarding onboarding-state-other#
walk the published first-use journey, writing and reading one non-secret note and showing its audit entry, or import an export during setup. Started by skarbiec onboarding.
What failed: resuming the first-use journey kept in {path}. Why: the file holds another journey's state ({found}), not skarbiec.onboarding-state.v1 of skarbiec's first-use journey. What the refusal shows: state file: {path}.
Fix: skarbiec onboarding --reset starts a new journey; no vault item is removed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/onboarding/journey.sh::a_journey_state_of_another_journey_is_refused_naming_the_reset.
skarbiec.onboarding onboarding-state-incomplete#
walk the published first-use journey, writing and reading one non-secret note and showing its audit entry, or import an export during setup. Started by skarbiec onboarding.
What failed: resuming the first-use journey kept in {path}. Why: the journey state records no {lacks}, so where the journey stands cannot be read. What the refusal shows: state file: {path}.
Fix: skarbiec onboarding --reset starts a new journey; no vault item is removed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/onboarding/journey.sh::a_journey_state_naming_no_screen_is_refused_naming_the_reset.
skarbiec.onboarding onboarding-state-screen-unknown#
walk the published first-use journey, writing and reading one non-secret note and showing its audit entry, or import an export during setup. Started by skarbiec onboarding.
What failed: resuming the first-use journey kept in {path}. Why: the journey state stands on the screen {screen}, which the journey this build ships does not publish. What the refusal shows: state file: {path}.
Fix: skarbiec onboarding --reset starts a new journey; no vault item is removed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/onboarding/journey.sh::a_journey_state_on_a_screen_the_journey_lacks_is_refused_naming_the_reset.
skarbiec.onboarding onboarding-no-evidence#
walk the published first-use journey, writing and reading one non-secret note and showing its audit entry, or import an export during setup. Started by skarbiec onboarding.
What failed: finishing the first-use journey. Why: the audit journal holds no onboarding-demo-item-read entry for the note {item} this journey recorded, so it cannot claim the note was read. What the refusal shows: recorded note: {item}.
Fix: skarbiec onboarding --reset walks the journey again and writes and reads a new note.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/onboarding/journey.sh::a_journey_whose_note_the_journal_never_saw_read_is_refused_naming_the_reset.
skarbiec.onboarding onboarding-journey-damaged#
walk the published first-use journey, writing and reading one non-secret note and showing its audit entry, or import an export during setup. Started by skarbiec onboarding.
What failed: reading the first-use journey this build ships. Why: the journey compiled into this build breaks the journey contract: {rule}. What the refusal shows: journey: {journey}; nothing was written.
Fix: install another skarbiec release (skarbiec --version names this one): this build shipped a damaged journey.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/onboarding/journey.sh::a_build_whose_journey_breaks_its_contract_is_refused_naming_the_rule.
skarbiec.onboarding onboarding-note-mismatch#
walk the published first-use journey, writing and reading one non-secret note and showing its audit entry, or import an export during setup. Started by skarbiec onboarding.
What failed: reading back the onboarding note {item} from {path}. Why: the note the vault opened is not the note just sealed into it, so a read cannot be shown as proof. What the refusal shows: members read back: {keys}; the note stays in the vault and no audit entry was written.
Fix: skarbiec doctor says whether the vault and its key file read; skarbiec onboarding --reset walks the journey again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/onboarding/journey.sh::a_note_that_reads_back_otherwise_is_refused_naming_it.
skarbiec.credential.operations-route body-not-object#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: reading a credential operation request. Why: its body is not one JSON object. What the refusal shows: body: {kind}.
Fix: send {form} as the body.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::a_body_that_is_not_an_object_is_refused.
skarbiec.credential.operations-route body-unknown-field#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: reading a credential operation request. Why: {field} is not a member a credential operation request carries. What the refusal shows: members: {members}.
Fix: send only role, operation, consumer, purpose, signup_origin, expect, approval and resume_token.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::a_body_with_an_unknown_member_is_refused_naming_it.
skarbiec.credential.operations-route body-role#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: reading which credential a request acts on. Why: role is absent or not one role name: the request names the role the credential plays, never an item. What the refusal shows: role: {value}.
Fix: send "role": "<role>", the role the credential's item is tagged stado:role:<role> with.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::a_body_naming_no_role_is_refused.
skarbiec.credential.operations-route body-member-missing#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: reading a credential operation request for role {role}. Why: {member} is required{why}. What the refusal shows: members: {members}.
Fix: send {member} with the request.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::a_body_without_a_consumer_is_refused_naming_it.
skarbiec.credential.operations-route operation-not-remote#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: starting credential {operation} of role {role} through the canonical endpoint. Why: {operation} is not available there: credential adopt reads the current password from the operator's standard input. What the refusal shows: operation: {operation}.
Fix: run skarbiec credential adopt role:{role} … --password-stdin --local on the canonical Skarbiec host.
Code refused, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::an_adopt_through_the_endpoint_is_refused_naming_the_local_command.
skarbiec.credential.operations-route operation-unknown#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: starting a credential operation of role {role}. Why: {operation} is not a credential operation. What the refusal shows: operation: {operation}.
Fix: send one of acquire, rotate, reset, verify or remove.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::an_unknown_operation_is_refused_naming_it.
skarbiec.credential.operations-route provider-unknown#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: finding the provider of role {role}. Why: role {role} has no sealed directory contract and no earlier operation names one, and only an acquisition under a role named after a generic provider slug takes the slug as its provider. What the refusal shows: seal of role {role}: none; operation record: {record}.
Fix: seal the role's directory first (skarbiec credential directory seal role:{role} …), or acquire it locally with --provider.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::a_rotation_of_a_role_whose_provider_is_unknown_is_refused.
skarbiec.credential.operations-route record-unreadable#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: finding the provider of role {role}. Why: its operation record {record} cannot be read, so its provider is unknown. What the refusal shows: record: {record}; reading it said: {error}.
Fix: run skarbiec doctor on the canonical Skarbiec to see why it cannot open {record}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::an_unreadable_record_stops_the_request_naming_it.
skarbiec.credential.operations-route account-unrecorded#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: starting credential {operation} of role {role} for provider microsoft. Why: role {role} records no account address, and a microsoft credential is bound to one. What the refusal shows: account_email: none; account_ref: none.
Fix: run it locally once with --account <email> on the canonical Skarbiec host, which records the address.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::a_microsoft_role_with_no_recorded_account_is_refused.
skarbiec.credential.operations-route lifecycle-not-granted#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: taking a credential operation of role {role} from {consumer}. Why: {consumer} holds no lifecycle:role:{role} capability for the bearer it presented. What the refusal shows: consumer: {consumer}; capability asked: lifecycle:role:{role}.
Fix: add lifecycle:role:{role} to {consumer}'s grant on the canonical Skarbiec (skarbiec grant list shows its capabilities), then present that grant's bearer.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::a_consumer_without_the_lifecycle_capability_is_refused_naming_it.
skarbiec.credential.operations-route expect-malformed#
read a credential operation request sent to the canonical Skarbiec. Started by POST /v1/credential/operations, GET /v1/credential/operations/<role>.
What failed: reading the expectations of a credential operation request. Why: {why}. What the refusal shows: expect: {value}.
Fix: send expect as an object of tenant_id, principal_object_id and account_upn only.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/routing/operations_route.sh::expectations_with_an_unknown_member_are_refused.
skarbiec.http.operator operator-not-post#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: answering {method} {path}. Why: operator routes take POST with a JSON object body, and this request is {method}. What the refusal shows: the request was read and nothing was changed.
Fix: send POST {path} with Content-Type: application/json and a JSON object body.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::an_operator_route_asked_with_get_is_refused_naming_post.
skarbiec.http.operator operator-body-not-object#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: reading the body of POST {path}. Why: the body is JSON but not an object, and every operator route reads its arguments as members of one object. What the refusal shows: body: {held}; nothing was forwarded or changed.
Fix: send POST {path} with a JSON object body whose members are the route's arguments, as skarbiec help names the command's flags.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_body_that_is_not_an_object_is_refused_naming_it.
skarbiec.http.operator operator-member-missing#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: reading the operator request's body. Why: it names no {member}, which this route needs as a non-empty string. What the refusal shows: members sent: {members}; nothing was changed.
Fix: send {member} in the JSON body, as the command the route stands for takes it.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_body_without_a_member_the_route_needs_is_refused_naming_it.
skarbiec.http.operator operator-member-shape#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: reading {member} from the operator request's body. Why: {member} is {value}, and the route takes {wanted}. What the refusal shows: nothing was changed.
Fix: send {member} as {wanted}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_member_of_another_shape_is_refused_naming_what_the_route_takes.
skarbiec.http.operator operator-path-relative#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: reading {member} from the operator request's body. Why: {member} is {path}, a relative path, and the serving process resolves no path against a working directory its caller does not see. What the refusal shows: nothing was read or written.
Fix: send {member} as an absolute path on the machine serving this API.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_relative_path_is_refused_naming_the_member.
skarbiec.http.operator operator-credential-operation-unknown#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: reading which credential operation the console asks for. Why: operation {operation} is not one this route takes. What the refusal shows: the reader said: {error}; nothing was asked or changed.
Fix: send operation as one of status, acquire, rotate, resume, get, set or totp; a field write sends the whole payload with set.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_credential_operation_the_route_does_not_take_is_refused_naming_the_set.
skarbiec.http.operator operator-credential-payload-missing#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: reading the payload a credential set writes to {item}. Why: the body names no payload, the item's whole canonical payload that set writes as its next revision. What the refusal shows: members sent: {members}; nothing was changed.
Fix: send payload as the item's canonical payload object (schema skarbiec.item.v2, its kind, fields and context) beside operation set and item {item}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_credential_set_without_a_payload_is_refused_naming_it.
skarbiec.http.operator operator-forward-loop#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: answering {path}, forwarded to this host as the vault owner. Why: this host routes to the owner {route} itself, so forwarding the request again would loop between hosts. What the refusal shows: nothing was forwarded or changed.
Fix: declare the owner's vault on this host (stado config set secrets.skarbiec.vault_file <path>) instead of secrets.skarbiec.url, or forward to the host that holds the vault.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_forwarded_request_on_a_host_that_forwards_itself_is_refused.
skarbiec.http.operator operator-caller-unproven#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: admitting the caller of POST {path}. Why: an operator route serves this host's operator, proved by the operator proof serve keeps in {proof}, or a consumer whose grant names the route; the request carried neither an X-Skarbiec-Operator proof nor an X-Consumer with its bearer. What the refusal shows: no proof and no consumer were presented; nothing was read, forwarded or changed.
Fix: a console on this host sends the content of {proof} as X-Skarbiec-Operator; any other caller, and a host Stado routes to this owner, sends X-Consumer and Authorization: Bearer of a grant the owner issued with call:skarbiec#{route} (skarbiec grant issue <consumer> --capabilities call:skarbiec#{route} --until-revoked, on the owner).
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::an_operator_request_without_a_proof_is_refused_naming_both_ways_in.
skarbiec.http.operator operator-proof-mismatch#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: admitting the caller of POST {path}. Why: the X-Skarbiec-Operator it presented is not the operator proof this serve keeps in {proof}: it is another host's or a stale one. What the refusal shows: the presented proof differs from {proof}; nothing was read, forwarded or changed.
Fix: on this host, send the content of {proof} as it is now; from another host, reach this owner as a consumer instead: run skarbiec serve there and point the console at it, so it forwards as the consumer Stado declares for that host, or send X-Consumer and the bearer of a grant naming call:skarbiec#<route>.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_request_with_another_hosts_operator_proof_is_refused.
skarbiec.http.operator operator-consumer-host-local#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the route acts on the machine it runs on (its files, keyring, agent or socket), so only that machine's operator calls it, never a consumer, whatever its grant names. What the refusal shows: consumer: {consumer}; nothing was read or changed.
Fix: run the command on the machine it is meant to act on, as that machine's operator (its console sends the operator proof); a consumer reaches the vault's content through the routes its grant names.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_asking_a_route_that_acts_on_the_owners_machine_is_refused.
skarbiec.http.operator operator-consumer-vault-named#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the body names the vault file {vault}, and only this host's operator chooses which of its files a route opens. What the refusal shows: consumer: {consumer}; vault: {vault}; nothing was read or changed.
Fix: leave the vault member out: a consumer is served from the vault this host serves.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_naming_a_vault_file_is_refused.
skarbiec.http.operator operator-consumer-item-route#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the route reaches vault items in a way no per-item grant decides, so only this host's operator calls it, whatever a call grant names. What the refusal shows: consumer: {consumer}; nothing was read or changed.
Fix: a consumer reaches items through the routes its per-item grant decides: POST /v1/items/list, /v1/items/get, /v1/items/set-json, /v1/items/retag, /v1/items/read and DELETE /v1/items (or their operator twins items/list, get, set-json, retag, trash, factors), with read, write or trash on the item, on tag:<tag> or on tag-family:<family>.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/consumer_items.sh::a_consumer_asking_an_item_route_no_item_grant_decides_is_refused.
skarbiec.http.operator operator-consumer-item-form#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving {route} to consumer {consumer}. Why: the request acts on several items at once ({form}), and a consumer's grant is judged one named item at a time. What the refusal shows: consumer: {consumer}; nothing was read or changed.
Fix: name one item per request (the item's id, as positionals or id), or run the several-item form as this host's operator.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/consumer_items.sh::a_consumer_trashing_by_tag_is_refused.
skarbiec.http.operator operator-consumer-recipients#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving {route} to consumer {consumer}. Why: the request names the item's recipients ({recipients}), the keys that decrypt it, and only the vault owner's operator decides who may decrypt an item. What the refusal shows: consumer: {consumer}; nothing was written.
Fix: leave --recipients out: an item a consumer writes is sealed to the vault's own recipients; the operator shares it (skarbiec share) when another key must read it.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/consumer_items.sh::a_consumer_naming_an_items_recipients_is_refused.
skarbiec.http.operator operator-consumer-grant-verb#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: a consumer hands on part of its own grant (issue, ensure, narrow, verify, revoke <consumer>, and keep while its own grant lives until revoked); {leaf} acts beyond any one grant it issued. What the refusal shows: consumer: {consumer}; nothing was changed.
Fix: run grant {leaf} as the vault owner's operator; a consumer issues, widens, narrows, keeps, verifies or revokes only a grant it issued itself, and never one that outlives its own.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_asking_a_grant_verb_it_may_not_use_is_refused.
skarbiec.http.operator operator-consumer-grant-self#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the request changes the grant of {consumer} itself, and a consumer's own grant is the operator's to change. What the refusal shows: consumer: {consumer}; its grant is as it was.
Fix: ask the vault owner's operator to change it (skarbiec grant issue {consumer} ... --replace-capabilities, on the owner); a consumer changes only grants it issued to other consumers.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_issuing_itself_a_grant_is_refused.
skarbiec.http.operator operator-consumer-grant-foreign#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the grant of {target} was not issued by {consumer} (issued by: {issuer}), so {consumer} may not change it. What the refusal shows: consumer: {consumer}; grant of {target}: issued by {issuer}; nothing was changed.
Fix: change it as the consumer that issued it, or as the vault owner's operator (skarbiec grant list shows issued_by); a consumer issues a new grant only under a name that holds none.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_changing_a_grant_it_did_not_issue_is_refused.
skarbiec.http.operator operator-consumer-grant-wider#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: {consumer} asked to hand on {capability}, which its own live grant does not hold, and a consumer hands on only part of what it holds. What the refusal shows: consumer: {consumer}; capability it lacks: {capability}; nothing was changed.
Fix: hand on only capabilities skarbiec grant list shows {consumer} holding, or ask the vault owner's operator to issue {capability}.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_issuing_a_capability_it_does_not_hold_is_refused.
skarbiec.http.operator operator-consumer-grant-operator-route#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: {capability} reaches an operator route of this vault, and only the vault owner's operator decides who calls one. What the refusal shows: consumer: {consumer}; nothing was changed.
Fix: leave {capability} out; the vault owner's operator issues call:skarbiec#v1/operator/<route> itself.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_handing_on_a_call_on_an_operator_route_is_refused.
skarbiec.http.operator operator-consumer-grant-longer#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the grant asked (by grant issue, or by grant keep, which makes it live until revoked) would end {asked}, after the grant of {consumer} itself ends ({held}), and a consumer hands on nothing that outlives what it holds. What the refusal shows: consumer: {consumer}; its grant ends {held}; nothing was changed.
Fix: issue it with --ttl-seconds ending no later than {held} and leave it unkept, or ask the vault owner's operator for the longer grant (skarbiec grant keep or grant issue --until-revoked on the owner).
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_issuing_a_grant_outliving_its_own_is_refused.
skarbiec.http.operator operator-consumer-grant-audience#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the grant for {target} names the audience {audience}, the identity its bearer would act under, and a consumer hands on capabilities only under the name of the consumer it issues them to. What the refusal shows: consumer: {consumer}; target: {target}; audience asked: {audience}; nothing was changed.
Fix: leave audience out (it is then {target}) or set it to {target}; only the vault owner's operator issues a grant acting under another identity.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_issuing_a_grant_under_another_identity_is_refused.
skarbiec.http.operator operator-consumer-file-named#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: serving POST {path} to consumer {consumer}. Why: the body's {member} names {value}, a file on the vault owner's machine, and only that machine's operator chooses which of its files a route opens. What the refusal shows: consumer: {consumer}; {member}: {value}; nothing was read or changed.
Fix: leave {member} out; a grant bound to a workload key is issued by the operator of the host that holds the key.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::a_consumer_naming_a_workload_key_file_on_the_owner_is_refused.
skarbiec.http.operator operator-proof-unsafe#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: reading the operator proof {proof}. Why: the file cannot be trusted as the proof this serve admits its host's operator by: {why}. What the refusal shows: {proof}: {why}; no operator request is admitted while it stands.
Fix: remove {proof} (rm {proof}): serve writes a new owner-only proof at its next start or next request, and a console reads the new one; then find what changed the old file, since another account may have read it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_caller.sh::serve_with_an_operator_proof_open_to_others_does_not_start.
skarbiec.http.operator operator-no-handler#
admit an operator request's caller (this host's operator by its proof, or a consumer: on an item route by its per-item grant, on any other route by the grant naming the route, and on a grant route only to hand on part of what it holds), read its method and body members, forward it to the vault owner or answer it here through the command it stands for, and answer that command's refusal with its cause. Started by every POST /v1/operator/ route of the loopback API.
What failed: answering an operator route through skarbiec {command}. Why: the dispatcher answered nothing for {command}, so this route stands for no command this skarbiec has. What the refusal shows: nothing was changed.
Fix: run skarbiec help to see whether {command} exists in this release, and skarbiec --version to name the release that lacks it.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/operator_routes.sh::a_route_whose_command_this_release_lacks_is_refused_naming_it.
skarbiec.owner owner-rotate-no-key#
move the vault to a new owner key, and make, read, export and import the keys a vault is opened and sealed with on this host. Started by skarbiec owner rotate, skarbiec owner key, POST /v1/operator/owner/rotate, POST /v1/operator/owner/key/mint, POST /v1/operator/owner/key/show.
What failed: moving the vault to the owner {uid}. Why: {uid} names no key in this vault's key file {key_file}, and a key made now would be one no ciphertext was ever encrypted to. What the refusal shows: nothing was changed.
Fix: import the new owner's key (skarbiec recipient add {uid} --import <public-key-file>) or make it (skarbiec owner key mint {uid}), then rotate.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/access/owner.sh::rotating_to_a_uid_with_no_key_is_refused_naming_how_to_bring_one.
skarbiec.owner owner-rotate-already-owner#
move the vault to a new owner key, and make, read, export and import the keys a vault is opened and sealed with on this host. Started by skarbiec owner rotate, skarbiec owner key, POST /v1/operator/owner/rotate, POST /v1/operator/owner/key/mint, POST /v1/operator/owner/key/show.
What failed: moving the vault to the owner {uid}. Why: {uid} is already the owner of this vault. What the refusal shows: nothing was changed.
Fix: name the uid of the key the vault should move to.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/owner.sh::rotating_to_the_current_owner_is_refused.
skarbiec.owner owner-key-mint-exists#
move the vault to a new owner key, and make, read, export and import the keys a vault is opened and sealed with on this host. Started by skarbiec owner rotate, skarbiec owner key, POST /v1/operator/owner/rotate, POST /v1/operator/owner/key/mint, POST /v1/operator/owner/key/show.
What failed: making the owner key for {uid}. Why: {uid} already names key {fingerprint} in this vault's key file, and a second key under one uid would leave which one opens the vault to the key file's order. What the refusal shows: nothing was changed.
Fix: read the key with skarbiec owner key show {uid}, or mint under another uid.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/owner.sh::minting_a_uid_that_already_names_a_key_is_refused_naming_it.
skarbiec.owner owner-key-absent#
move the vault to a new owner key, and make, read, export and import the keys a vault is opened and sealed with on this host. Started by skarbiec owner rotate, skarbiec owner key, POST /v1/operator/owner/rotate, POST /v1/operator/owner/key/mint, POST /v1/operator/owner/key/show.
What failed: reading the owner key of {uid}. Why: {uid} names no key in this vault's key file {key_file}. What the refusal shows: nothing was changed.
Fix: make it with skarbiec owner key mint {uid}, or bring it with skarbiec owner key import <file>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/access/owner.sh::showing_a_uid_with_no_key_is_refused_naming_mint.
skarbiec.owner owner-key-export-no-fingerprint#
move the vault to a new owner key, and make, read, export and import the keys a vault is opened and sealed with on this host. Started by skarbiec owner rotate, skarbiec owner key, POST /v1/operator/owner/rotate, POST /v1/operator/owner/key/mint, POST /v1/operator/owner/key/show.
What failed: exporting the keys this vault seals to. Why: the recipient {uid} records no fingerprint, so which key it is cannot be told. What the refusal shows: nothing was exported.
Fix: register the recipient's key again with skarbiec recipient rekey {uid} --import <public-key-file> --yes, or restore the vault from a backup taken before the damage.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/owner.sh::exporting_a_recipient_that_records_no_fingerprint_is_refused_naming_it.
skarbiec.owner owner-key-export-key-missing#
move the vault to a new owner key, and make, read, export and import the keys a vault is opened and sealed with on this host. Started by skarbiec owner rotate, skarbiec owner key, POST /v1/operator/owner/rotate, POST /v1/operator/owner/key/mint, POST /v1/operator/owner/key/show.
What failed: exporting the keys this vault seals to. Why: the key file lacks a key this vault seals to, and a block without it would let a destination seal writes that key could not open. What the refusal shows: exporting said: {error}; key file: {key_file}; nothing was exported.
Fix: bring the missing key with skarbiec keys import or skarbiec owner key import <file>, then export.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/access/owner.sh::exporting_while_the_key_file_lacks_a_sealing_key_is_refused_naming_it.
skarbiec.owner-forward owner-forward-usage#
send a vault command to the vault owner Stado routes this machine to, and answer with the owner's result or its declared refusal. Started by skarbiec get|list|set|status|delete|retag|login get|totp seed|grant capability|grant issue|grant ensure|grant verify, on a machine Stado routes to the vault owner, POST /v1/operator/*, on a serve whose machine Stado routes to the vault owner.
What failed: running {command} on the vault owner {route} (POST {path} at {endpoint}). Why: the vault owner judged the forwarded command malformed, as it would judge it typed on the owner. What the refusal shows: the owner answered {status}, cause {owner_cause}: {owner_error}; nothing ran on the owner or here.
Fix: {owner_remedy}; skarbiec errors show names every cause of the command.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/selection/owner_forward.sh::a_forwarded_command_the_owner_judges_malformed_exits_with_its_usage.
skarbiec.owner-forward owner-forward-denied#
send a vault command to the vault owner Stado routes this machine to, and answer with the owner's result or its declared refusal. Started by skarbiec get|list|set|status|delete|retag|login get|totp seed|grant capability|grant issue|grant ensure|grant verify, on a machine Stado routes to the vault owner, POST /v1/operator/*, on a serve whose machine Stado routes to the vault owner.
What failed: running {command} on the vault owner {route} (POST {path} at {endpoint}). Why: the vault owner refused this host's consumer the command: the grant its bearer opens does not name the route as call:skarbiec#<route>, or the bearer is not that consumer's. What the refusal shows: the owner answered {status}, cause {owner_cause}: {owner_error}; nothing ran on the owner or here.
Fix: {owner_remedy}.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_forward.sh::an_owner_that_does_not_admit_this_caller_is_refused_naming_its_answer.
skarbiec.owner-forward owner-forward-absent#
send a vault command to the vault owner Stado routes this machine to, and answer with the owner's result or its declared refusal. Started by skarbiec get|list|set|status|delete|retag|login get|totp seed|grant capability|grant issue|grant ensure|grant verify, on a machine Stado routes to the vault owner, POST /v1/operator/*, on a serve whose machine Stado routes to the vault owner.
What failed: running {command} on the vault owner {route} (POST {path} at {endpoint}). Why: the fleet vault on the owner does not hold what the command names. What the refusal shows: the owner answered {status}, cause {owner_cause}: {owner_error}; nothing was changed.
Fix: {owner_remedy}; skarbiec list, run here, lists what the owner's vault holds.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_forward.sh::a_forwarded_get_of_an_item_the_owner_does_not_hold_is_refused_naming_it.
skarbiec.owner-forward owner-forward-refused#
send a vault command to the vault owner Stado routes this machine to, and answer with the owner's result or its declared refusal. Started by skarbiec get|list|set|status|delete|retag|login get|totp seed|grant capability|grant issue|grant ensure|grant verify, on a machine Stado routes to the vault owner, POST /v1/operator/*, on a serve whose machine Stado routes to the vault owner.
What failed: running {command} on the vault owner {route} (POST {path} at {endpoint}). Why: the vault owner refused the command for a reason of its own vault, as it would refuse it typed on the owner. What the refusal shows: the owner answered {status}, cause {owner_cause}: {owner_error}; nothing ran here.
Fix: {owner_remedy}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_forward.sh::a_forwarded_set_the_owner_refuses_is_refused_with_the_owners_cause.
skarbiec.owner-forward owner-forward-answer-shape#
send a vault command to the vault owner Stado routes this machine to, and answer with the owner's result or its declared refusal. Started by skarbiec get|list|set|status|delete|retag|login get|totp seed|grant capability|grant issue|grant ensure|grant verify, on a machine Stado routes to the vault owner, POST /v1/operator/*, on a serve whose machine Stado routes to the vault owner.
What failed: reading the vault owner {route}'s answer to {path} at {endpoint}. Why: the owner answered {path} with {held}, where it answers {expected}, so the result cannot be shown; it is an older or another program than this Skarbiec. What the refusal shows: answer: {held}.
Fix: upgrade Skarbiec on the owner to this version (skarbiec version, run there, names its own), then run the command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_forward.sh::an_owner_answering_no_object_is_refused_naming_the_answer.
skarbiec.owner-forward owner-forward-input-unreadable#
send a vault command to the vault owner Stado routes this machine to, and answer with the owner's result or its declared refusal. Started by skarbiec get|list|set|status|delete|retag|login get|totp seed|grant capability|grant issue|grant ensure|grant verify, on a machine Stado routes to the vault owner, POST /v1/operator/*, on a serve whose machine Stado routes to the vault owner.
What failed: reading the payload set forwards to the vault owner {route} on standard input. Why: standard input could not be read to its end as text ({kind}), so no payload was sent. What the refusal shows: the system said: {error}; read {read} bytes before it; nothing was sent to the owner.
Fix: pipe the payload as UTF-8 JSON: skarbiec set <id> < payload.json.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_forward.sh::a_forwarded_set_whose_input_is_not_text_is_refused_and_nothing_is_sent.
skarbiec.owner-forward owner-forward-identity-undeclared#
send a vault command to the vault owner Stado routes this machine to, and answer with the owner's result or its declared refusal. Started by skarbiec get|list|set|status|delete|retag|login get|totp seed|grant capability|grant issue|grant ensure|grant verify, on a machine Stado routes to the vault owner, POST /v1/operator/*, on a serve whose machine Stado routes to the vault owner.
What failed: proving this host to the vault owner {route} before forwarding a vault command. Why: the owner serves a forwarded command only to a consumer whose grant names its route, and Stado declares no consumer or no token file for this host. What the refusal shows: Stado's skarbiec_consumer: {consumer}; skarbiec_token_file: {token_file}; nothing was sent to the owner.
Fix: declare who this host is to the owner in Stado's config: secrets.skarbiec.consumer and secrets.skarbiec.token_file (or WC_SKARBIEC_CONSUMER and WC_SKARBIEC_TOKEN_FILE for one program), the file owner-only and holding the bearer of a grant the owner issued that consumer with call:skarbiec#<route> for each route it forwards; stado config show --json shows what Stado resolves.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_forward.sh::a_host_stado_declares_no_consumer_for_forwards_nothing.
skarbiec.owner-write owner-write-on-replica#
check that this vault's owner may change an item directly, before anything is changed. Started by other functionalities only.
What failed: {operation} on this vault. Why: this vault replicates bond {bond} from {source}, so a direct {operation} here is replaced by the next pull. What the refusal shows: bond {bond}: mode replica, role replica, source {source}.
Fix: make the change on the source vault the bond names; skarbiec bond list shows the bond.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/owner_write.sh::a_change_on_a_replica_vault_is_refused_naming_its_source.
skarbiec.owner-write owner-write-item-missing#
check that this vault's owner may change an item directly, before anything is changed. Started by other functionalities only.
What failed: {operation} {id}. Why: this vault holds no live item {id}. What the refusal shows: vault file: {path}.
Fix: name a live item (skarbiec list); one in the trash is restored first with skarbiec restore {id}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/owner_write.sh::a_change_to_an_item_the_vault_does_not_hold_is_refused_naming_it.
skarbiec.owner-write owner-write-management-missing#
check that this vault's owner may change an item directly, before anything is changed. Started by other functionalities only.
What failed: {operation} {id}. Why: {id} records no management, so who may change it cannot be read. What the refusal shows: item {id}: no management block.
Fix: skarbiec upgrade --apply writes the management every current item carries.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/owner_write.sh::a_change_to_an_item_that_records_no_management_is_refused.
skarbiec.owner-write owner-write-not-owner-controlled#
check that this vault's owner may change an item directly, before anything is changed. Started by other functionalities only.
What failed: {operation} {id}. Why: {id} is controlled by {controller} (management mode {mode}), not by this vault's owner, and a direct change would bypass that controller. What the refusal shows: item {id}: management mode {mode}, controller {controller}.
Fix: change it through what controls it: a credential Weles manages through skarbiec credential <operation> role:<the role it plays>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/owner_write.sh::a_change_to_an_item_weles_controls_is_refused_naming_the_controller.
skarbiec.owner-write owner-write-external-writer#
check that this vault's owner may change an item directly, before anything is changed. Started by other functionalities only.
What failed: {operation} {id}. Why: {id} was written through the API by consumer {controller} (management mode external), so only that writer controls it, not this vault's owner. What the refusal shows: item {id}: management mode external, controller {controller}.
Fix: return it to owner control with skarbiec reclaim {id}, which moves control and changes nothing else, then run the change again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/owner_write.sh::a_change_to_an_item_an_api_writer_controls_is_refused_naming_reclaim.
skarbiec.item-payload payload-kind-unknown#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: unsupported canonical item kind: {kind}; the kinds are {kinds}. What the refusal shows: nothing was written.
Fix: write it as one of the kinds skarbiec kinds lists, each with the fields it takes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_kind_no_schema_declares_is_refused_naming_the_kinds.
skarbiec.item-payload payload-kind-missing#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: the payload names no kind as text, and every payload states the kind it is. What the refusal shows: nothing was written.
Fix: add kind to the payload, one of the kinds skarbiec kinds lists.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_naming_no_kind_is_refused.
skarbiec.item-payload payload-not-object#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: the payload is {held}, and a canonical payload is one JSON object. What the refusal shows: nothing was written.
Fix: write the payload as one JSON object holding schema skarbiec.item.v2, kind, fields and context, as skarbiec kinds {kind} describes.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_that_is_not_an_object_is_refused.
skarbiec.item-payload payload-property-unknown#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: unknown canonical item property: {property}; a payload holds only schema, kind, fields, context and extensions. What the refusal shows: nothing was written.
Fix: take {property} out of the payload, or move what it says into context.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_property_the_schema_does_not_declare_is_refused.
skarbiec.item-payload payload-schema-wrong#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: canonical item schema must be skarbiec.item.v2, and the payload states {held}. What the refusal shows: nothing was written.
Fix: set the payload's schema to skarbiec.item.v2.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_of_another_schema_is_refused.
skarbiec.item-payload payload-kind-mismatch#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: the payload states kind {stated}, and it is written as a {kind}. What the refusal shows: nothing was written.
Fix: make the payload's kind {kind}, or write the item as a {stated} (set --type names the item's kind).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_of_another_kind_than_the_item_is_refused.
skarbiec.item-payload payload-fields-not-object#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: the payload's fields are {held}, and a payload holds its fields as one JSON object. What the refusal shows: nothing was written.
Fix: write fields as one object from field name to value; skarbiec kinds {kind} names the fields.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::fields_that_are_not_an_object_are_refused.
skarbiec.item-payload payload-fields-empty#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: the payload holds no field, and every item holds at least one. What the refusal shows: nothing was written.
Fix: write at least the fields skarbiec kinds {kind} names as required.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_holding_no_field_is_refused.
skarbiec.item-payload payload-field-not-of-kind#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: field {name} is not allowed for {kind}; a {kind} takes {takes}. What the refusal shows: nothing was written.
Fix: write the value under one of {takes}, or as a kind that takes {name}; skarbiec kinds {kind} says which are required.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_field_the_kind_does_not_take_is_refused_listing_the_ones_it_does.
skarbiec.item-payload payload-field-shape#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: {kind} field {name} holds {held}, and a {kind} takes it as {shape}. What the refusal shows: nothing was written.
Fix: write fields.{name} as {shape}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_field_of_another_shape_is_refused.
skarbiec.item-payload payload-field-required#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: {kind} payload requires fields.{name}, and this one holds none. What the refusal shows: nothing was written.
Fix: add fields.{name}; skarbiec kinds {kind} names every field a {kind} requires.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_missing_a_required_field_is_refused_naming_it.
skarbiec.item-payload payload-field-set-missing#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: {kind} payload requires at least one {set}: {named}, and this one holds none. What the refusal shows: nothing was written.
Fix: add one of {named}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_payload_holding_none_of_a_set_is_refused_naming_the_set.
skarbiec.item-payload payload-field-name-invalid#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: invalid logical field name: {name}; a field name is letters, digits, '.', '_' and '-'. What the refusal shows: nothing was written.
Fix: rename the field to letters, digits, '.', '_' and '-'.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_field_name_with_other_characters_is_refused.
skarbiec.item-payload payload-context-not-object#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: the payload's context is {held}, and a payload holds its context as one JSON object. What the refusal shows: nothing was written.
Fix: write context as one JSON object, {} when it says nothing.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_context_that_is_not_an_object_is_refused.
skarbiec.item-payload payload-host-account-unnamed#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: host-account payload requires context.account_ref naming <user>@<host>, and this one holds {held}. What the refusal shows: nothing was written.
Fix: set context.account_ref to the account as <user>@<host>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_host_account_naming_no_user_and_host_is_refused.
skarbiec.item-payload payload-card-expiry#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: payment-card fields.expiry must be the year and month the card stops working, written YYYY-MM (for example 2031-04); the value given is not in that form. What the refusal shows: nothing was written.
Fix: write fields.expiry as YYYY-MM, for example 2031-04.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_card_expiry_not_written_as_a_month_is_refused.
skarbiec.item-payload payload-sso-identity-missing#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: an sso-login names the identity it signs in as in context.identity (an identity item's id), and this one names none. What the refusal shows: nothing was written.
Fix: set context.identity to the id of the identity item it signs in as; skarbiec list --kind identity names them.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::an_sso_login_naming_no_identity_is_refused.
skarbiec.item-payload payload-identity-reference-invalid#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: context.identity holds {held}, and it names an identity item by its id. What the refusal shows: nothing was written.
Fix: set context.identity to an identity item's id; skarbiec list --kind identity names them.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::an_identity_reference_that_is_not_an_item_id_is_refused.
skarbiec.item-payload payload-identity-names-identity#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: an identity cannot name another identity in context.identity. What the refusal shows: nothing was written.
Fix: take identity out of the identity's context; the logins that sign in as it name it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::an_identity_naming_an_identity_is_refused.
skarbiec.item-payload payload-extensions-not-object#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: the payload's extensions are {held}, and a payload holds its extensions as one JSON object. What the refusal shows: nothing was written.
Fix: write extensions as one JSON object, or leave them out.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::extensions_that_are_not_an_object_are_refused.
skarbiec.item-payload payload-second-factor-invalid#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: context.second_factor records what the login's sign-in demands after its password, and the one written is unreadable: {why}. What the refusal shows: nothing was written.
Fix: write context.second_factor as an object of factor (none, totp, push, sms, email or security-key), by (owner or weles) and at (seconds since the Unix epoch), or record it with skarbiec login factor set <id> --factor <factor>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_second_factor_record_of_another_shape_is_refused_naming_what_is_wrong.
skarbiec.item-payload payload-verification-invalid#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: checking a payload written as a {kind}. Why: context.verification or context.enrolled records whether the account accepts the seed and when it was enrolled, and the one written is unreadable: {why}. What the refusal shows: nothing was written.
Fix: write context.verification as an object of outcome (accepted, rejected or locked), by (owner or weles) and at (seconds since the Unix epoch), and context.enrolled as provider (google), at and an optional run, or record an outcome with skarbiec totp verified <item> --outcome <outcome>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/payload.sh::a_verification_record_of_another_shape_is_refused_naming_what_is_wrong.
skarbiec.item-payload payload-field-absent#
check a canonical item payload: one object of schema skarbiec.item.v2, its kind, the fields that kind takes and requires, its context and the identity it names. Started by skarbiec set, skarbiec field set, skarbiec import, skarbiec migrate, POST /v1/operator/credential.
What failed: reading the field {name} of a {kind}. Why: the item holds no {name}; it holds {held}. What the refusal shows: nothing was read.
Fix: name one of the fields it holds, or write {name} with skarbiec field set.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/helper/docker.sh::a_registry_login_holding_no_password_is_refused_naming_its_fields.
skarbiec.pin pin-verb#
pin a live item to the front, unpin one, or list the pins oldest first. Started by skarbiec pin add, skarbiec pin remove, skarbiec pin list, POST /v1/operator/items/pins, POST /v1/operator/items/pin/add, POST /v1/operator/items/pin/remove, Desktop: Items → a selected item → Pin to the top / Unpin.
What failed: reading which pin command was asked for. Why: pin takes add <id>, remove <id> or list, and was given {given}. What the refusal shows: arguments: {given}.
Fix: skarbiec pin add <id> | pin remove <id> | pin list.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/pins/pins.sh::a_pin_command_with_no_verb_is_refused_with_its_usage.
skarbiec.pin pin-item-not-live#
pin a live item to the front, unpin one, or list the pins oldest first. Started by skarbiec pin add, skarbiec pin remove, skarbiec pin list, POST /v1/operator/items/pins, POST /v1/operator/items/pin/add, POST /v1/operator/items/pin/remove, Desktop: Items → a selected item → Pin to the top / Unpin.
What failed: pinning {id}. Why: {id} is not a live item of this vault{trashed}. What the refusal shows: item {id}: {state}.
Fix: pin a live item (skarbiec list names them); a trashed one is restored first with skarbiec restore {id}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/pins/pins.sh::pinning_an_item_the_vault_does_not_hold_is_refused_naming_it.
skarbiec.pin pins-damaged#
pin a live item to the front, unpin one, or list the pins oldest first. Started by skarbiec pin add, skarbiec pin remove, skarbiec pin list, POST /v1/operator/items/pins, POST /v1/operator/items/pin/add, POST /v1/operator/items/pin/remove, Desktop: Items → a selected item → Pin to the top / Unpin.
What failed: reading the pins of the vault at {path}. Why: its pinned_items section is {found}, not a list of item ids, so which items are pinned cannot be read and writing a new list would replace it. What the refusal shows: pinned_items: {found}.
Fix: restore the vault from a backup taken before the section was damaged (skarbiec backup list), or remove the pinned_items section from the vault file to start the pins afresh.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/pins/pins.sh::a_damaged_pin_list_is_refused_instead_of_being_replaced.
skarbiec.policy policy-key-unknown#
read the rules the binary enforces, set or withdraw one, or decide a candidate against every one without storing it. Started by skarbiec policy get, skarbiec policy set, skarbiec policy unset, skarbiec policy check, POST /v1/operator/policy, POST /v1/operator/policy/set, POST /v1/operator/policy/unset, POST /v1/operator/policy/check.
What failed: setting the policy rule {key}. Why: {key} is not a rule this binary enforces, so setting it would report success and change nothing. What the refusal shows: rules this binary enforces: {supported}.
Fix: name one of the rules above.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/policy/check.sh::a_rule_the_binary_does_not_enforce_is_refused_naming_the_ones_it_does.
skarbiec.policy policy-value-unfit#
read the rules the binary enforces, set or withdraw one, or decide a candidate against every one without storing it. Started by skarbiec policy get, skarbiec policy set, skarbiec policy unset, skarbiec policy check, POST /v1/operator/policy, POST /v1/operator/policy/set, POST /v1/operator/policy/unset, POST /v1/operator/policy/check.
What failed: setting the policy rule {key} to {value}. Why: {key} requires {shape}, and {value} is not one, so the rule would be stored and never applied. What the refusal shows: rules this binary enforces: {supported}.
Fix: give {key} {shape}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/policy/check.sh::a_value_the_rule_cannot_apply_is_refused_naming_the_shape_it_needs.
skarbiec.policy policy-section-damaged#
read the rules the binary enforces, set or withdraw one, or decide a candidate against every one without storing it. Started by skarbiec policy get, skarbiec policy set, skarbiec policy unset, skarbiec policy check, POST /v1/operator/policy, POST /v1/operator/policy/set, POST /v1/operator/policy/unset, POST /v1/operator/policy/check.
What failed: reading the vault's policy. Why: the vault's policy section is {found}, not an object of rules. What the refusal shows: policy section: {found}.
Fix: restore the vault from a backup (skarbiec backup check names one that opens); skarbiec doctor names what else is damaged.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/policy/check.sh::a_policy_section_that_is_not_an_object_is_refused_naming_what_it_holds.
skarbiec.policy policy-candidate-unreadable#
read the rules the binary enforces, set or withdraw one, or decide a candidate against every one without storing it. Started by skarbiec policy get, skarbiec policy set, skarbiec policy unset, skarbiec policy check, POST /v1/operator/policy, POST /v1/operator/policy/set, POST /v1/operator/policy/unset, POST /v1/operator/policy/check.
What failed: reading the candidate policy check decides. Why: {why}. What the refusal shows: standard input: {observed}.
Fix: pipe the candidate in as UTF-8 text: printf '%s' "$CANDIDATE" | skarbiec policy check.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/policy/check.sh::a_candidate_that_is_empty_or_not_text_is_refused_naming_standard_input.
skarbiec.credential.preflight acquire-over-unmanaged#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: acquiring the credential of role {role}. Why: {item} already plays the role and was not written by Weles, so calling it acquired would claim a provenance it does not have. What the refusal shows: item {item}: live, not Weles-managed.
Fix: adopt it instead (skarbiec credential adopt role:{role} … --password-stdin --local), or give the role to no item before acquiring.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::acquiring_a_role_an_unmanaged_item_plays_is_refused_naming_adopt.
skarbiec.credential.preflight adopt-already-managed#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: adopting the credential of role {role}. Why: {item} is already a managed credential. What the refusal shows: lifecycle state of role {role}: managed.
Fix: rotate or verify it: skarbiec credential rotate role:{role} ….
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::adopting_a_managed_credential_is_refused_naming_rotate.
skarbiec.credential.preflight adopt-over-unmanaged#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: adopting the credential of role {role}. Why: {item} exists outside Weles management, and an item enters managed state only when it is created. What the refusal shows: item {item}: live, not Weles-managed.
Fix: move the role to no item (skarbiec retag --remove stado:role:{role} {item}) and adopt again, so the adoption creates the managed item.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::adopting_over_an_unmanaged_item_is_refused.
skarbiec.credential.preflight adopt-other-writer#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: adopting the credential of role {role} as {consumer}. Why: {item} is written by another Weles consumer, {writer}. What the refusal shows: writer of {item}: {writer}; --consumer {consumer}.
Fix: run it with --consumer {writer}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::adopting_as_another_writer_is_refused_naming_the_writer.
skarbiec.credential.preflight not-managed#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: running credential {command} on role {role}. Why: {item} is not an active Weles-managed credential, and {command} acts on a managed one. What the refusal shows: item {item}: {state}.
Fix: bring it under management first with credential adopt or credential acquire.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::rotating_an_unmanaged_credential_is_refused_naming_adopt.
skarbiec.credential.preflight adoption-unfinished#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: running credential {command} on role {role}. Why: {item} is {state}, not managed: its adoption has not finished. What the refusal shows: lifecycle state of role {role}: {state}.
Fix: finish the adoption (credential status role:{role} --local, then credential resume if it waits for approval) before {command}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::rotating_during_an_adoption_is_refused_naming_its_state.
skarbiec.credential.preflight pending-conflict#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: starting credential {command} on role {role}. Why: {conflict}. What the refusal shows: pending record: {record}.
Fix: finish or settle the pending operation first: skarbiec credential status role:{role} --local shows it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::a_pending_rotation_stops_an_acquisition_naming_it.
skarbiec.credential.preflight provider-effect-unknown#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: starting credential {command} on role {role}. Why: the last {previous} left the provider password in an unknown state. What the refusal shows: provider_effect: unknown.
Fix: settle it: skarbiec credential quarantine resolve role:{role} --confirm 'I know which password this provider account accepts' ….
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::an_unknown_provider_effect_stops_the_next_operation.
skarbiec.credential.preflight provider-effect-changed#
decide whether a credential operation may start on the role's credential. Started by other functionalities only.
What failed: starting credential {command} on role {role}. Why: PROVIDER_EFFECT_CHANGED_RETRY_BLOCKED: the last {previous} changed the provider password without a confirmed local commit or rollback. What the refusal shows: provider_effect: changed; rollback_status: {rollback}.
Fix: run skarbiec credential verify role:{role} … first, which finds out which password the provider accepts.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/preflight.sh::a_changed_provider_password_without_a_rollback_stops_a_rotation_naming_verify.
skarbiec.credential.provider-contract sealed-for-another-provider#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: planning credential {command} of role {role} with provider {provider}. Why: DIRECTORY_EXPECTATION_MISMATCH: the role's directory contract is sealed for provider {sealed}. What the refusal shows: sealed provider: {sealed}; --provider {provider}.
Fix: run it with --provider {sealed}, or reseal the role with skarbiec credential directory reseal role:{role} --provider {provider} ….
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::a_provider_other_than_the_sealed_one_is_refused.
skarbiec.credential.provider-contract entra-not-sealed#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: planning credential {command} of role {role} with provider microsoft_entra. Why: a microsoft_entra credential is bound to a sealed directory identity, and role {role} has none. What the refusal shows: sealed directory contract of role {role}: none.
Fix: seal it first: skarbiec credential directory seal role:{role} --provider microsoft_entra --tenant <uuid> --object-id <uuid> --account-upn <email> --local.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::an_entra_operation_without_a_seal_is_refused_naming_the_seal_command.
skarbiec.credential.provider-contract entra-account-given#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: planning credential {command} of role {role} with provider microsoft_entra. Why: the account of a microsoft_entra credential is its sealed account_upn, so --account cannot name another. What the refusal shows: --account {account}.
Fix: drop --account; credential status role:{role} --local shows the sealed account_upn.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::an_entra_operation_with_account_is_refused.
skarbiec.credential.provider-contract entra-operation-unsupported#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: planning credential {command} of role {role} with provider microsoft_entra. Why: microsoft_entra supports only adopt, rotate, verify and reset. What the refusal shows: operation: {command}.
Fix: run one of credential adopt, rotate, verify or reset for this role.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::an_entra_acquire_is_refused.
skarbiec.credential.provider-contract microsoft-account-missing#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: planning credential {command} of role {role} with provider microsoft. Why: a microsoft credential is bound to one account address, and --account names none. What the refusal shows: --account: absent.
Fix: pass --account <email>, the address of the Microsoft account.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::a_microsoft_operation_without_account_is_refused.
skarbiec.credential.provider-contract reset-unsupported#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: planning credential reset of role {role} with provider {provider}. Why: {provider} has no reset contract: a reset replaces a lost password through a directory, and only microsoft_entra has one. What the refusal shows: --provider {provider}.
Fix: rotate it with credential rotate role:{role} while the current password works, or recover the account at the provider.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::a_reset_of_a_generic_provider_is_refused.
skarbiec.credential.provider-contract directory-for-another-provider#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: planning credential {command} of role {role} with provider {provider}. Why: role {role} carries a sealed directory contract, which only a microsoft_entra credential has. What the refusal shows: sealed directory contract: present; --provider {provider}.
Fix: run it with --provider microsoft_entra, or play the role with an item that is not directory-bound.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::a_sealed_role_run_with_a_generic_provider_is_refused.
skarbiec.credential.provider-contract signup-origin-not-generic-acquire#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: reading --signup-origin of credential {command}. Why: a signup origin says where a new account is registered, which only credential acquire of a generic provider does; {provider} registers none here. What the refusal shows: --signup-origin {value}; --provider {provider}.
Fix: drop --signup-origin.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::a_signup_origin_outside_a_generic_acquisition_is_refused.
skarbiec.credential.provider-contract signup-origin-malformed#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: reading --signup-origin of credential acquire. Why: {value} is not https://<host>[:<port>]: an absolute https origin, lowercase host, no userinfo, path, query or fragment. What the refusal shows: --signup-origin {value}.
Fix: pass the origin the provider's signup page is served from, e.g. --signup-origin https://example.com.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::a_signup_origin_with_a_path_is_refused.
skarbiec.credential.provider-contract purpose-malformed#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: reading --purpose. Why: a purpose is non-empty printable text, and this one is empty or holds a control character. What the refusal shows: --purpose of {bytes} byte(s).
Fix: state why the credential is needed in one printable line, or leave --purpose out.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::an_empty_purpose_is_refused.
skarbiec.credential.provider-contract account-malformed#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: reading {flag}. Why: {value} is not one email address: a local part, one '@' and a domain with a dot that does not end the domain. What the refusal shows: {flag} {value}.
Fix: pass the account's email address, e.g. {flag} admin@example.com.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::an_account_that_is_not_an_address_is_refused.
skarbiec.credential.provider-contract slug-cannot-be-role#
decide whether a provider may run a lifecycle operation, with which identity and field. Started by other functionalities only.
What failed: naming the role credential acquire plays when none is given. Why: a generic provider's slug becomes the role, and {provider} is not lowercase ASCII letters, digits and '-' starting and ending with a letter or a digit. What the refusal shows: --provider {provider}; no role:<role> argument.
Fix: name the role: skarbiec credential acquire role:<role> --provider {provider} ….
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/provider_contract.sh::an_acquisition_naming_no_role_with_an_uppercase_provider_is_refused.
skarbiec.provider-cli provider-cli-absent#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: no {program} is in any directory of PATH, so {provider} cannot be asked through it. What the refusal shows: command: {command}; PATH: {path}; {state}.
Fix: install {package} and put its {program} on PATH (command -v {program} names the one that runs), then run skarbiec {again} again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_rotation_whose_provider_program_is_not_on_path_is_refused_naming_it.
skarbiec.provider-cli provider-cli-not-executable#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: a file named {program} was found on PATH, but this account may not run it (errno {errno}): the file is not executable, or a directory on its way may not be searched. What the refusal shows: command: {command}; PATH: {path}; the system said: {said}; {state}.
Fix: command -v {program} names the file that was found; make it executable (chmod +x) or put {package}'s {program} before it on PATH, then run skarbiec {again} again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_rotation_whose_provider_program_may_not_be_run_is_refused_naming_it.
skarbiec.provider-cli provider-cli-unstarted#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: {program} was found on PATH, and the system did not start it (errno {errno}): this account is out of processes or memory, or the file is not a program this system runs. What the refusal shows: command: {command}; PATH: {path}; the system said: {said}; {state}.
Fix: run {command} by hand to see the system's refusal, repair it, then run skarbiec {again} again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_provider_program_the_system_does_not_start_is_refused_naming_errno.
skarbiec.provider-cli provider-cli-input-unwritten#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: {program} started, and the statement for it could not be written to its standard input (errno {errno}), so it was ended without it. What the refusal shows: command: {command}; directory: {directory}; the system said: {said}; {state}.
Fix: run skarbiec {again} again; when it is refused the same way, run {command} by hand to see whether {program} reads its standard input.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_provider_program_whose_input_cannot_be_written_is_refused.
skarbiec.provider-cli provider-cli-unwaited#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: {program} started, and waiting for it to end failed (errno {errno}), so whether {provider} did it is not known. What the refusal shows: command: {command}; directory: {directory}; the system said: {said}; {state}.
Fix: look at {provider} to see whether it did it, then run skarbiec {again} again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_provider_program_that_cannot_be_waited_for_is_refused.
skarbiec.provider-cli provider-cli-refused#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: {program} refused it and ended with {ended}, so {provider} did not do it. What the refusal shows: command: {command}; directory: {directory}; {program} said: {said}; {state}.
Fix: run {command} as this account to see the refusal in full, repair what it names (the account {program} is signed in as, that account's permissions, a name {provider} does not know, or {provider} not answering), then run skarbiec {again} again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_provider_program_that_refuses_is_refused_in_its_words_with_the_command.
skarbiec.provider-cli provider-cli-signalled#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: {program} was ended by signal {signal} before it finished, so whether {provider} did it is not known. What the refusal shows: command: {command}; directory: {directory}; {program} said: {said}; {state}.
Fix: look at {provider} to see whether it did it (something on this host ended {program}: a timeout, the out-of-memory killer, or a person), then run skarbiec {again} again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_provider_program_ended_by_a_signal_is_refused_naming_it.
skarbiec.provider-cli provider-cli-not-json#
run a provider's own command-line program with the item's credential in its environment or input, and read its answer. Started by other functionalities only.
What failed: asking {program} to {purpose}. Why: {program} ended with status 0 and answered something that is not JSON, where it was asked to answer JSON: a {program} release that prints another format, or a wrapper in its place on PATH. What the refusal shows: command: {command}; {bytes} bytes; the JSON reader stopped at line {line}, column {column}: {why}; {state}.
Fix: run {command} by hand to see what it answers; command -v {program} names the one on PATH, which must be {package}'s own and answer JSON.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_provider_program_answering_no_json_is_refused_naming_it.
skarbiec.published-list published-list-not-json#
fetch a list a third party publishes (the 2FA Directory, Have I Been Pwned's breaches, Password Manager Resources' quirks) and read it as the JSON its publisher documents. Started by other functionalities only.
What failed: reading {list} at {url}. Why: {url} answered a body that is not JSON, so its publisher moved the list or serves a page in its place. What the refusal shows: the JSON reader stopped at line {line}, column {column}: {said}.
Fix: open {url} to see what it serves; when the publisher moved the list, a skarbiec release that reads its new address is needed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/published_list.sh::a_list_address_answering_no_json_is_refused_naming_it.
skarbiec.published-list published-list-shape#
fetch a list a third party publishes (the 2FA Directory, Have I Been Pwned's breaches, Password Manager Resources' quirks) and read it as the JSON its publisher documents. Started by other functionalities only.
What failed: reading {list} at {url}. Why: {url} answered {found}, where its publisher's format is {expected}, so the list changed its format. What the refusal shows: {found} at the top of the answer.
Fix: open {url} to see the format it serves now; a skarbiec release that reads it is needed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/published_list.sh::a_list_of_another_shape_is_refused_naming_both_shapes.
skarbiec.published-list published-list-entry-field#
fetch a list a third party publishes (the 2FA Directory, Have I Been Pwned's breaches, Password Manager Resources' quirks) and read it as the JSON its publisher documents. Started by other functionalities only.
What failed: reading {list} at {url}. Why: the entry for {entry} holds no text {field}, which every entry of the list carries in its publisher's format. What the refusal shows: entry {entry}: {held}.
Fix: open {url} to see the entry; a publisher's error there is reported to the list's project, and the site's own rules are recorded meanwhile.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/published_list.sh::a_list_entry_missing_its_field_is_refused_naming_it.
skarbiec.pull pull-refused#
fetch a source serve's whole ciphertext vault and install it in place of this one, keeping this vault's bonds and refusing a smaller vault unless forced. Started by skarbiec pull.
What failed: pulling the vault from {from} as {consumer}. Why: the source answered {status}: {said}. What the refusal shows: status: {status}.
Fix: the source's owner grants {consumer} sync:pull (skarbiec grant issue {consumer} --capabilities sync:pull on the source) and gives this host its bearer file.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/pull.sh::a_pull_the_source_refuses_is_refused_naming_its_answer.
skarbiec.pull pull-not-vault#
fetch a source serve's whole ciphertext vault and install it in place of this one, keeping this vault's bonds and refusing a smaller vault unless forced. Started by skarbiec pull.
What failed: pulling the vault from {from}. Why: the source answered {status} with {found}, where a serve of this release answers its whole vault document: an items object and a version. What the refusal shows: status: {status}; nothing was installed.
Fix: pull from a serve of this release (skarbiec about on the source names its version), or upgrade the source with stado.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/pull.sh::a_source_answering_no_vault_document_is_refused.
skarbiec.pull pull-local-damaged#
fetch a source serve's whole ciphertext vault and install it in place of this one, keeping this vault's bonds and refusing a smaller vault unless forced. Started by skarbiec pull.
What failed: comparing the pulled vault with {vault}. Why: {vault} {why}, where a vault is one JSON document with an items object, so how many items replacing it would lose cannot be counted. What the refusal shows: vault file: {vault}; {said}.
Fix: restore {vault} from a backup, or move it aside so the pull installs the source's vault.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/pull.sh::a_local_vault_that_does_not_read_as_one_is_refused_and_kept.
skarbiec.pull pull-would-shrink#
fetch a source serve's whole ciphertext vault and install it in place of this one, keeping this vault's bonds and refusing a smaller vault unless forced. Started by skarbiec pull.
What failed: replacing {vault} with the vault {from} holds. Why: the source holds {remote} items and this vault {local}, so the items only this vault holds would be lost. What the refusal shows: local items: {local}; source items: {remote}.
Fix: skarbiec backup <directory> keeps this vault first; then pull again with --force to accept the loss.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/bonds/pull.sh::a_pull_that_would_shrink_the_vault_is_refused_until_forced.
skarbiec.purge.item id-missing#
remove one trashed item and every saved version of it for good. Started by skarbiec purge, POST /v1/operator/items/purge, Desktop: Items → Purge Permanently.
What failed: reading which item skarbiec purge removes. Why: no item id, --trashed-before or --versions-before was given. What the refusal shows: arguments: none.
Fix: name the trashed item, skarbiec purge <id> --yes; skarbiec list --trashed lists the trash.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/purge/purge.sh::purge_without_an_id_is_refused_with_its_usage.
skarbiec.purge.item item-unknown#
remove one trashed item and every saved version of it for good. Started by skarbiec purge, POST /v1/operator/items/purge, Desktop: Items → Purge Permanently.
What failed: purging {id}. Why: the vault holds no item {id}, live or trashed. What the refusal shows: trashed items: {trashed}.
Fix: name one of the trashed items listed; skarbiec list --all lists every item.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/purge/purge.sh::purge_of_an_unknown_item_lists_the_trash.
skarbiec.purge.item item-live#
remove one trashed item and every saved version of it for good. Started by skarbiec purge, POST /v1/operator/items/purge, Desktop: Items → Purge Permanently.
What failed: purging {id}. Why: {id} is live, and purge removes only an item already in the trash. What the refusal shows: {id}: live.
Fix: move it to the trash with skarbiec delete {id} first, where restore still brings it back, then purge it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/purge/purge.sh::purge_of_a_live_item_is_refused.
skarbiec.purge.item records-left#
remove one trashed item and every saved version of it for good. Started by skarbiec purge, POST /v1/operator/items/purge, Desktop: Items → Purge Permanently.
What failed: forgetting the expiry, pin and rotation policy of purged {id}. Why: the records that name it outside the vault could not all be removed. What the refusal shows: removing them answered: {error}; {id} is removed from the vault; a record naming it is left.
Fix: skarbiec expiry list, skarbiec pin list and skarbiec rotation list name what is left; remove it there.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/purge/purge.sh::a_confirmed_purge_removes_the_item_and_its_records.
skarbiec.purge.trash both-forms#
remove every item put in the trash before a moment, with every saved version. Started by skarbiec purge --trashed-before, POST /v1/operator/items/purge-trash, Desktop: Trash → Empty old trash.
What failed: reading what skarbiec purge --trashed-before removes. Why: an item id and --trashed-before were both given, and purge takes one of them. What the refusal shows: item id: {given}; --trashed-before {before}.
Fix: drop the id to empty the trash before the moment, or drop --trashed-before to purge that one item.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/purge/purge.sh::purge_with_an_id_and_trashed_before_is_refused.
skarbiec.purge.trash moment-malformed#
remove every item put in the trash before a moment, with every saved version. Started by skarbiec purge --trashed-before, POST /v1/operator/items/purge-trash, Desktop: Trash → Empty old trash.
What failed: reading the moment {flag} names. Why: {before} is not a UTC time. What the refusal shows: {flag} {before}; a UTC time reads like {now}.
Fix: give the moment as a UTC time of that form.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/purge/purge.sh::purge_with_a_malformed_moment_is_refused.
skarbiec.purge.versions versions-item-unknown#
remove the saved versions stamped before a moment, keeping current values and later versions. Started by skarbiec purge --versions-before, POST /v1/operator/items/purge-versions, Desktop: Item → Saved versions → Forget versions before a day, Desktop: Settings → Policy → Forget every saved version before a day.
What failed: removing the saved versions of {id}. Why: the vault holds no live item {id}. What the refusal shows: live items: {live}.
Fix: name one of the live items listed, or --all for every live item.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/purge/purge.sh::forgetting_versions_of_an_unknown_item_lists_the_live_ones.
skarbiec.purge.versions moment-malformed#
remove the saved versions stamped before a moment, keeping current values and later versions. Started by skarbiec purge --versions-before, POST /v1/operator/items/purge-versions, Desktop: Item → Saved versions → Forget versions before a day, Desktop: Settings → Policy → Forget every saved version before a day.
What failed: reading the moment {flag} names. Why: {before} is not a UTC time. What the refusal shows: {flag} {before}; a UTC time reads like {now}.
Fix: give the moment as a UTC time of that form.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/purge/purge.sh::purge_with_a_malformed_moment_is_refused.
skarbiec.credential.quarantine confirmation-missing#
resolve a quarantined credential with the operator's explicit decision. Started by skarbiec credential quarantine resolve.
What failed: resolving the quarantine of role {role}. Why: --confirm does not carry the exact sentence that says you know which password the provider accepts. What the refusal shows: --confirm {given}.
Fix: pass --confirm 'I know which password this provider account accepts' once you have checked it at the provider.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/quarantine.sh::a_resolve_without_the_confirmation_sentence_is_refused_naming_it.
skarbiec.credential.quarantine staged-unknown#
resolve a quarantined credential with the operator's explicit decision. Started by skarbiec credential quarantine resolve.
What failed: reading --staged of credential quarantine resolve. Why: {value} is none of keep, activate or discard. What the refusal shows: --staged {value}.
Fix: pass --staged keep (the default), activate or discard.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/quarantine.sh::an_unknown_staged_decision_is_refused.
skarbiec.credential.quarantine nothing-quarantined#
resolve a quarantined credential with the operator's explicit decision. Started by skarbiec credential quarantine resolve.
What failed: resolving the quarantine of role {role}. Why: role {role} is not quarantined: {holder}, the item that plays it, carries no quarantine. What the refusal shows: quarantine of role {role}: none.
Fix: credential status role:{role} --local shows what the role holds; only a quarantined role is resolved.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/quarantine.sh::a_role_that_is_not_quarantined_is_refused.
skarbiec.credential.quarantine quarantine-role-unplayed#
resolve a quarantined credential with the operator's explicit decision. Started by skarbiec credential quarantine resolve.
What failed: resolving the quarantine of role {role}. Why: role {role} has no operation record ({record}) and no live item plays it, so nothing of it can be quarantined. What the refusal shows: quarantine of role {role}: none.
Fix: credential status role:{role} --local shows what the role holds; name the role as the item tagged stado:role:<role> plays it.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/quarantine.sh::a_role_nothing_plays_is_refused_naming_it.
skarbiec.credential.quarantine record-unreadable#
resolve a quarantined credential with the operator's explicit decision. Started by skarbiec credential quarantine resolve.
What failed: resolving the quarantine of role {role}. Why: the operation record {record} states no {name}, so the value it staged cannot be identified. What the refusal shows: record: {record}; nothing was resolved.
Fix: run skarbiec doctor to see why {record} cannot be read; resolve once it can.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/quarantine.sh::a_quarantine_whose_record_names_no_request_is_refused_naming_what_it_lacks.
skarbiec.credential.quarantine admin-not-granted#
resolve a quarantined credential with the operator's explicit decision. Started by skarbiec credential quarantine resolve.
What failed: resolving the quarantine of role {role} as {consumer}. Why: {consumer} holds no admin:role:{role} capability for the bearer it presented. What the refusal shows: consumer: {consumer}; capability asked: admin:role:{role}.
Fix: add admin:role:{role} to {consumer}'s grant: skarbiec grant list shows its capabilities; issue them again with admin:role:{role} added, then present that grant's bearer.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/quarantine.sh::a_resolve_without_the_admin_capability_is_refused.
skarbiec.credential.quarantine nothing-staged#
resolve a quarantined credential with the operator's explicit decision. Started by skarbiec credential quarantine resolve.
What failed: {decision} the staged value of role {role}. Why: {item} has no staged revision belonging to the quarantined operation, so there is nothing to {decision}. What the refusal shows: staged revision of {item}: none.
Fix: resolve with --staged keep, which clears the quarantine and keeps the current value.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/quarantine.sh::activating_when_nothing_is_staged_is_refused.
skarbiec.readiness readiness-canary-absent#
prove the audit journal takes an entry, the vault opens and, for /readyz, that every canary item opens with the keys this host holds. Started by GET /health, GET /readyz, skarbiec maintain.
What failed: choosing the canary items readiness opens. Why: SKARBIEC_READINESS_ITEMS names {item}, which this vault does not hold. What the refusal shows: SKARBIEC_READINESS_ITEMS: {configured}.
Fix: name only items the vault holds (skarbiec list names them) in SKARBIEC_READINESS_ITEMS, or unset it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/http_requests.sh::a_readiness_item_the_vault_does_not_hold_answers_503_naming_it.
skarbiec.reclaim reclaim-item-missing#
return an item a consumer wrote to this vault owner's control, touching nothing else. Started by skarbiec reclaim, POST /v1/operator/items/reclaim, Desktop: Items → a selected item → Reclaim ownership.
What failed: returning {id} to the owner. Why: this vault holds no item {id}. What the refusal shows: vault file: {path}.
Fix: name an item the vault holds (skarbiec list --trashed lists the trash too).
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/reclaim.sh::reclaiming_an_item_the_vault_does_not_hold_is_refused_naming_it.
skarbiec.reclaim reclaim-management-missing#
return an item a consumer wrote to this vault owner's control, touching nothing else. Started by skarbiec reclaim, POST /v1/operator/items/reclaim, Desktop: Items → a selected item → Reclaim ownership.
What failed: returning {id} to the owner. Why: {id} records no management, so who controls it cannot be read. What the refusal shows: item {id}: no management block.
Fix: skarbiec upgrade --apply writes the management every current item carries.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/reclaim.sh::an_item_that_records_no_management_is_refused.
skarbiec.reclaim reclaim-under-lifecycle#
return an item a consumer wrote to this vault owner's control, touching nothing else. Started by skarbiec reclaim, POST /v1/operator/items/reclaim, Desktop: Items → a selected item → Reclaim ownership.
What failed: returning {id} to the owner. Why: {id} is {why}, and taking it from that control would let its stored value diverge from the provider's. What the refusal shows: item {id}: {observed}.
Fix: change it through its credential operations: skarbiec credential <operation> role:<the role it plays>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/reclaim.sh::an_item_under_the_credential_lifecycle_is_refused.
skarbiec.recipient recipient-subcommand-missing#
choose a recipient command and register, list, export or reach the recipients of the vault. Started by skarbiec recipient, skarbiec recipient add, skarbiec recipient list, skarbiec recipient export, skarbiec recipient items, POST /v1/operator/recipients, POST /v1/operator/recipients/add, POST /v1/operator/recipients/export, POST /v1/operator/recipients/items, MCP skarbiec_recipient_items.
What failed: reading which recipient command to run. Why: recipient was given no subcommand. What the refusal shows: arguments: none; nothing was read or written.
Fix: name one: skarbiec recipient help lists add, remove, list, export, items and rekey.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/recipients/group.sh::recipient_alone_is_refused_naming_the_help.
skarbiec.recipient recipient-subcommand-unknown#
choose a recipient command and register, list, export or reach the recipients of the vault. Started by skarbiec recipient, skarbiec recipient add, skarbiec recipient list, skarbiec recipient export, skarbiec recipient items, POST /v1/operator/recipients, POST /v1/operator/recipients/add, POST /v1/operator/recipients/export, POST /v1/operator/recipients/items, MCP skarbiec_recipient_items.
What failed: reading which recipient command to run. Why: {verb} is not a recipient command; recipient takes add, remove, list, export, items and rekey. What the refusal shows: arguments: {given}; nothing was read or written.
Fix: run one skarbiec recipient help lists.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/recipients/group.sh::an_unknown_recipient_command_is_refused_naming_the_commands.
skarbiec.recipient recipient-uid-missing#
choose a recipient command and register, list, export or reach the recipients of the vault. Started by skarbiec recipient, skarbiec recipient add, skarbiec recipient list, skarbiec recipient export, skarbiec recipient items, POST /v1/operator/recipients, POST /v1/operator/recipients/add, POST /v1/operator/recipients/export, POST /v1/operator/recipients/items, MCP skarbiec_recipient_items.
What failed: reading which recipient recipient {verb} acts on. Why: recipient {verb} names no uid. What the refusal shows: arguments: none; nothing was read or written.
Fix: run skarbiec {usage}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/recipients/group.sh::a_recipient_command_naming_no_uid_is_refused_with_its_usage.
skarbiec.recipient recipient-add-owner#
choose a recipient command and register, list, export or reach the recipients of the vault. Started by skarbiec recipient, skarbiec recipient add, skarbiec recipient list, skarbiec recipient export, skarbiec recipient items, POST /v1/operator/recipients, POST /v1/operator/recipients/add, POST /v1/operator/recipients/export, POST /v1/operator/recipients/items, MCP skarbiec_recipient_items.
What failed: registering {uid} as the vault's owner with recipient add. Why: recipient add registers a key without re-encrypting the {count} item(s) already stored, so an owner added this way could read none of them. What the refusal shows: --role owner; items stored: {count}; nothing was registered.
Fix: run skarbiec owner rotate {uid}, which rewraps every version onto the new key and keeps the recovery recipient.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/group.sh::adding_an_owner_is_refused_naming_owner_rotate.
skarbiec.recipient recipient-add-import-uid-unmatched#
choose a recipient command and register, list, export or reach the recipients of the vault. Started by skarbiec recipient, skarbiec recipient add, skarbiec recipient list, skarbiec recipient export, skarbiec recipient items, POST /v1/operator/recipients, POST /v1/operator/recipients/add, POST /v1/operator/recipients/export, POST /v1/operator/recipients/items, MCP skarbiec_recipient_items.
What failed: registering the public key in {file} as {uid}'s. Why: the key in {file} names no user id matching {uid}, so it cannot be registered as {uid}'s key. What the refusal shows: {file} was imported into the key file {key_file}; no key there names {uid}; no recipient was registered.
Fix: import the public key whose user id is {uid} (skarbiec recipient add {uid} --import <its file>), or add {uid} without --import to mint one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/group.sh::importing_a_key_for_another_uid_is_refused_naming_the_uid.
skarbiec.recipient recipient-export-unknown#
choose a recipient command and register, list, export or reach the recipients of the vault. Started by skarbiec recipient, skarbiec recipient add, skarbiec recipient list, skarbiec recipient export, skarbiec recipient items, POST /v1/operator/recipients, POST /v1/operator/recipients/add, POST /v1/operator/recipients/export, POST /v1/operator/recipients/items, MCP skarbiec_recipient_items.
What failed: exporting the public key of {uid}. Why: {uid} is not a recipient of this vault ({path}). What the refusal shows: recipients: {recipients}.
Fix: name one skarbiec recipient list shows, or register them with skarbiec recipient add {uid}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/group.sh::exporting_an_unknown_recipient_is_refused_naming_the_recipients.
skarbiec.recipient recipient-items-unknown#
choose a recipient command and register, list, export or reach the recipients of the vault. Started by skarbiec recipient, skarbiec recipient add, skarbiec recipient list, skarbiec recipient export, skarbiec recipient items, POST /v1/operator/recipients, POST /v1/operator/recipients/add, POST /v1/operator/recipients/export, POST /v1/operator/recipients/items, MCP skarbiec_recipient_items.
What failed: listing the items {uid} can open. Why: {uid} is not a recipient of this vault ({path}), so no item lists them; an empty list would read as a person who can open nothing. What the refusal shows: recipients: {recipients}; nothing was read or written.
Fix: name one skarbiec recipient list shows (skarbiec recipient items <uid>).
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/group.sh::listing_the_items_of_an_unknown_recipient_is_refused_naming_the_recipients.
skarbiec.recovery recovery-drill-recipient-unknown#
report the vault's recovery recipient and whether its secret half is on this host, or open the lowest live item with a key file holding only the expected opener. Started by skarbiec recovery status, skarbiec recovery drill, POST /v1/operator/recovery, POST /v1/operator/recovery/drill.
What failed: drilling recovery as {expected}. Why: {expected} is not a recipient of this vault, so there is no key it is expected to open with. What the refusal shows: registered recipients: {recipients}.
Fix: name a registered recipient, or recovery for the vault's recovery key.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/drill.sh::a_drill_for_someone_who_is_not_a_recipient_is_refused_naming_the_recipients.
skarbiec.recovery recovery-drill-key-absent#
report the vault's recovery recipient and whether its secret half is on this host, or open the lowest live item with a key file holding only the expected opener. Started by skarbiec recovery status, skarbiec recovery drill, POST /v1/operator/recovery, POST /v1/operator/recovery/drill.
What failed: drilling recovery as {expected}. Why: the key file {key_file} does not hold the secret half of {expected} ({fingerprint}). What the refusal shows: key file: {key_file}.
Fix: bring it in with skarbiec keys import --gnupg-home <dir> --keys {fingerprint} into a key file of its own (SKARBIEC_KEYS_FILE) and drill again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/drill.sh::a_drill_whose_key_file_lacks_the_expected_key_is_refused_naming_the_import.
skarbiec.recovery recovery-drill-not-isolated#
report the vault's recovery recipient and whether its secret half is on this host, or open the lowest live item with a key file holding only the expected opener. Started by skarbiec recovery status, skarbiec recovery drill, POST /v1/operator/recovery, POST /v1/operator/recovery/drill.
What failed: drilling recovery as {expected}. Why: a drill proves one opener alone, and the key file {key_file} holds the secret half of {openers}. What the refusal shows: key file: {key_file}.
Fix: point SKARBIEC_KEYS_FILE at a key file holding only {fingerprint}, then drill again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/drill.sh::a_drill_with_more_than_the_expected_opener_in_the_key_file_is_refused.
skarbiec.recovery recovery-drill-no-item#
report the vault's recovery recipient and whether its secret half is on this host, or open the lowest live item with a key file holding only the expected opener. Started by skarbiec recovery status, skarbiec recovery drill, POST /v1/operator/recovery, POST /v1/operator/recovery/drill.
What failed: drilling recovery as {expected}. Why: the vault holds no live item, so there is nothing whose opening would prove recovery. What the refusal shows: vault file: {path}.
Fix: store one item (skarbiec set) and drill again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/drill.sh::a_drill_on_a_vault_with_no_live_item_is_refused.
skarbiec.recovery recovery-drill-failed#
report the vault's recovery recipient and whether its secret half is on this host, or open the lowest live item with a key file holding only the expected opener. Started by skarbiec recovery status, skarbiec recovery drill, POST /v1/operator/recovery, POST /v1/operator/recovery/drill.
What failed: drilling recovery as {expected}. Why: the canary item {canary} did not open with {fingerprint}. What the refusal shows: opening it said: {error}; canary {canary}; the failed drill is in the audit journal.
Fix: skarbiec readers {canary} names the keys it is sealed to; an item not sealed to {fingerprint} is rewrapped with skarbiec upgrade --apply or owner rotate.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recovery/drill.sh::a_drill_whose_canary_does_not_open_is_refused_and_journalled.
skarbiec.rename rename-ids-missing#
move one item to a new id, keeping its revisions, history, tags, recipients, policies and the grants that follow it. Started by skarbiec rename, POST /v1/operator/items/rename, Desktop: Items → a selected item → Rename.
What failed: reading which item rename moves, and to which id. Why: rename takes the item's id and its new id, and was given {given}. What the refusal shows: arguments: {arguments}.
Fix: skarbiec rename <id> <new-id> [--move-grants].
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_without_its_new_id_is_refused_with_its_usage.
skarbiec.rename rename-extra-argument#
move one item to a new id, keeping its revisions, history, tags, recipients, policies and the grants that follow it. Started by skarbiec rename, POST /v1/operator/items/rename, Desktop: Items → a selected item → Rename.
What failed: reading which item rename moves, and to which id. Why: rename moves one item to one new id, and {extra} was given after them. What the refusal shows: arguments: {arguments}.
Fix: skarbiec rename <id> <new-id> [--move-grants]; rename each item in its own call.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_third_id_is_refused_rather_than_ignored.
skarbiec.rename rename-same-id#
move one item to a new id, keeping its revisions, history, tags, recipients, policies and the grants that follow it. Started by skarbiec rename, POST /v1/operator/items/rename, Desktop: Items → a selected item → Rename.
What failed: renaming {from}. Why: {from} already has that id. What the refusal shows: id: {from}; new id: {to}.
Fix: name the new id the item should have.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_to_the_same_id_is_refused.
skarbiec.rename rename-id-invalid#
move one item to a new id, keeping its revisions, history, tags, recipients, policies and the grants that follow it. Started by skarbiec rename, POST /v1/operator/items/rename, Desktop: Items → a selected item → Rename.
What failed: renaming {from}. Why: a new item id is one non-empty name with no NUL, newline or carriage return. What the refusal shows: new id: {to}.
Fix: name the new id on one line.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_new_id_with_a_newline_is_refused.
skarbiec.rename rename-target-exists#
move one item to a new id, keeping its revisions, history, tags, recipients, policies and the grants that follow it. Started by skarbiec rename, POST /v1/operator/items/rename, Desktop: Items → a selected item → Rename.
What failed: renaming {from} to {to}. Why: {to} is already an item of this vault, and renaming onto it would replace it. What the refusal shows: item {to}: present.
Fix: choose another new id, or rename or delete {to} first.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_onto_an_existing_item_is_refused_and_both_are_kept.
skarbiec.rename rename-legacy-envelope#
move one item to a new id, keeping its revisions, history, tags, recipients, policies and the grants that follow it. Started by skarbiec rename, POST /v1/operator/items/rename, Desktop: Items → a selected item → Rename.
What failed: renaming {from}. Why: {from} is still kept in envelope format {format}, and only the current format {current} carries the item uid a rename keeps. What the refusal shows: item {from}: envelope format {format}.
Fix: skarbiec upgrade --apply moves it to the current envelope; then rename it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_legacy_item_is_refused_naming_the_upgrade.
skarbiec.request request-kind-unknown#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading the kind of access request to file. Why: {given} is no request kind. What the refusal shows: request kinds: {kinds}; nothing was recorded.
Fix: name --kind secret, device or membership.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_request_kind_that_does_not_exist_is_refused_naming_the_kinds.
skarbiec.request request-text-unfit#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading --{flag} of the access request. Why: --{flag} is not one line of text without surrounding space. What the refusal shows: --{flag}: {given}; nothing was recorded.
Fix: give --{flag} as one line of text, with no line break and no leading or trailing space.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_flag_that_is_not_one_line_of_text_is_refused_naming_it.
skarbiec.request request-number-unfit#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading --{flag} of the access request. Why: --{flag} {given} is not a whole number of at least {least}. What the refusal shows: --{flag}: {given}; nothing was recorded.
Fix: give --{flag} as a whole number of at least {least}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_count_that_is_not_a_whole_number_is_refused_naming_it.
skarbiec.request request-decider-unfit#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading who decides the access request. Why: --decider names a recipient uid, or the role owner or admin. What the refusal shows: --decider: {given}; nothing was recorded.
Fix: give --decider owner, --decider admin or --decider <recipient-uid>; skarbiec recipient list names the uids.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_decider_that_is_no_uid_or_role_is_refused.
skarbiec.request request-capability-action#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading the bounded capability the access request names. Why: a bounded capability redeems one value: --action must be read. What the refusal shows: --action: {action}; nothing was recorded.
Fix: file it with --action read, or ask for a standing consumer grant with --for-consumer <name>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_bounded_capability_for_an_action_other_than_read_is_refused.
skarbiec.request request-consumer-unfit#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading the consumer a standing grant is asked for. Why: --for-consumer must be one exact consumer name. What the refusal shows: --for-consumer: {given}; nothing was recorded.
Fix: give --for-consumer one name of letters, digits, '.', '_' and '-'.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_consumer_name_that_is_not_exact_is_refused.
skarbiec.request request-record-grant#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading the {kind} request. Why: a {kind} request is recorded for its owning product and names no vault grant. What the refusal shows: nothing was recorded.
Fix: drop --purpose, --target, --ttl-seconds, --max-uses and --for-consumer.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_device_or_membership_request_with_grant_flags_is_refused.
skarbiec.request request-lifetime-recorded#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading the lifetime an earlier decision on the access request recorded. Why: the decision records the lifetime {value}, which is neither whole seconds nor until-revoked. What the refusal shows: nothing was issued.
Fix: deny the request with skarbiec request deny <request-id> --by <uid> and file it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_recorded_lifetime_of_another_shape_is_refused_naming_it.
skarbiec.request request-uses-missing#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading how many times the approved capability is redeemed. Why: a capability is redeemed a stated number of times: --uses <N> is required. What the refusal shows: request {id} names a bounded capability; nothing was decided.
Fix: approve again with --uses <N>, N at most the {asked} the request asked.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_capability_approved_without_uses_is_refused.
skarbiec.request request-capability-forever#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading how long the approved capability lives. Why: a capability always expires: state --ttl-seconds <N> instead of --until-revoked. What the refusal shows: request {id} names a bounded capability; nothing was decided.
Fix: approve again with --ttl-seconds <N> and --uses <N>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_capability_approved_until_revoked_is_refused.
skarbiec.request request-uses-uncounted#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading how many times the approved grant is used. Why: a standing consumer grant is not counted in uses: drop --uses. What the refusal shows: request {id} names a standing grant for {consumer}; nothing was decided.
Fix: approve again without --uses.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_standing_grant_approved_with_uses_is_refused.
skarbiec.request request-uses-zero#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading how many times the approved capability is redeemed. Why: --uses must be at least one. What the refusal shows: --uses: 0; nothing was decided.
Fix: approve again with --uses 1 or more, or deny the request.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::an_approval_of_zero_uses_is_refused.
skarbiec.request request-unknown#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: reading access request {id}. Why: the register holds no access request {id}. What the refusal shows: nothing was changed.
Fix: name a request skarbiec request list shows.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_request_id_the_register_does_not_hold_is_refused.
skarbiec.request request-not-pending#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: deciding access request {id}. Why: access request {id} is {state}, not pending. What the refusal shows: nothing was changed.
Fix: file a new request for what is still needed; a decided request stays as it was decided.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::deciding_a_request_that_is_no_longer_pending_is_refused_naming_its_state.
skarbiec.request request-not-a-decider#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: letting {by} decide access request {id}. Why: {why}. What the refusal shows: nothing was changed.
Fix: decide it as a recipient with role owner or admin, or as the decider the request names (skarbiec request show {id}).
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_decider_the_request_does_not_name_is_refused_naming_why.
skarbiec.request request-decider-key-absent#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: letting {by} decide access request {id}. Why: {by}'s secret key is not in this host's key file. What the refusal shows: nothing was changed.
Fix: decide where {by} holds the key, or bring it here with skarbiec keys import.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_decider_whose_key_is_not_here_is_refused_naming_keys_import.
skarbiec.request request-already-decided#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: letting {by} decide access request {id}. Why: {by} already decided access request {id}. What the refusal shows: the first decision stands; nothing was changed.
Fix: a dual-control request needs a second decider: decide it as another owner or admin.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::a_second_decision_by_the_same_decider_is_refused.
skarbiec.request request-consumer-held#
record what an agent asks for, why and for whom, and let an owner or admin approve it into a bounded grant, deny it, or the agent withdraw it. Started by skarbiec request, POST /v1/access-requests, POST /v1/operator/requests, POST /v1/operator/requests/approve, POST /v1/operator/requests/deny.
What failed: approving access request {id}. Why: consumer {consumer} already holds a grant, and approving would replace its bearer and capabilities. What the refusal shows: nothing was issued.
Fix: deny this request and ask for a fresh consumer name, or revoke the existing grant first with skarbiec grant revoke {consumer}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_refusals.sh::approving_a_consumer_that_holds_a_grant_is_refused_naming_it.
skarbiec.request.register request-register-not-json#
keep every access request, who asked, why and each decision, owner-only beside the vault. Started by skarbiec request list, skarbiec request show, skarbiec request file, skarbiec request approve, skarbiec request deny, skarbiec request withdraw.
What failed: reading the access request register {path}. Why: it is not JSON (it stops being JSON at line {line}, column {column}), so no request it holds can be read. What the refusal shows: register: {path}, {bytes} bytes; the parser said: {said}; nothing was changed.
Fix: restore {path} from a backup taken before the damage, or move it aside and file the open requests again; it is a JSON object holding a requests list.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_register_that_is_not_json_is_refused_naming_where_it_stops.
skarbiec.request.register request-register-damaged#
keep every access request, who asked, why and each decision, owner-only beside the vault. Started by skarbiec request list, skarbiec request show, skarbiec request file, skarbiec request approve, skarbiec request deny, skarbiec request withdraw.
What failed: reading the access request register {path}. Why: it holds no requests list, which every register keeps, so which requests are open cannot be read. What the refusal shows: register: {path}, holding {holds}; nothing was changed.
Fix: restore {path} from a backup taken before the damage, or move it aside and file the open requests again; it is a JSON object holding a requests list.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_register_holding_no_requests_list_is_refused_naming_it.
skarbiec.request.register request-record-damaged#
keep every access request, who asked, why and each decision, owner-only beside the vault. Started by skarbiec request list, skarbiec request show, skarbiec request file, skarbiec request approve, skarbiec request deny, skarbiec request withdraw.
What failed: reading access request {id} from the register {path}. Why: the record holds no {field}, which {why}. What the refusal shows: record: {record}.
Fix: remove the record {id} from {path} and file the request again; skarbiec request list shows the others.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_record_missing_a_field_is_refused_naming_it.
skarbiec.request.register request-record-field-unreadable#
keep every access request, who asked, why and each decision, owner-only beside the vault. Started by skarbiec request list, skarbiec request show, skarbiec request file, skarbiec request approve, skarbiec request deny, skarbiec request withdraw.
What failed: reading access request {id} from the register {path}. Why: the record's {field} is {value}, and this skarbiec reads only {expected} there. What the refusal shows: the parser said: {said}; record: {record}.
Fix: remove the record {id} from {path} and file the request again; skarbiec request list shows the others.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_record_whose_grant_form_is_unreadable_is_refused_naming_it.
skarbiec.request.register request-recipient-damaged#
keep every access request, who asked, why and each decision, owner-only beside the vault. Started by skarbiec request list, skarbiec request show, skarbiec request file, skarbiec request approve, skarbiec request deny, skarbiec request withdraw.
What failed: reading {by}'s recipient record to decide access request {id}. Why: it holds no readable {field}: {expected} was looked for and {value} found. What the refusal shows: vault: {vault}; the request is still pending.
Fix: restore {by}'s recipient record from a backup taken before the damage; skarbiec recipient list shows the record and skarbiec doctor names what else is wrong.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_decider_whose_recipient_record_is_damaged_is_refused_naming_the_field.
skarbiec.request.register request-grant-unanswered#
keep every access request, who asked, why and each decision, owner-only beside the vault. Started by skarbiec request list, skarbiec request show, skarbiec request file, skarbiec request approve, skarbiec request deny, skarbiec request withdraw.
What failed: issuing the {form} grant access request {id} names. Why: skarbiec grant {leaf} answered nothing, so this build does not issue that grant. What the refusal shows: the request is still pending; nothing was issued.
Fix: deny the request with skarbiec request deny {id} --by <uid> and issue the grant with skarbiec grant {leaf}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_grant_leaf_that_answers_nothing_is_refused.
skarbiec.request.watch request-dialog-unstarted#
ask the decider about each pending request in a native dialog the moment it is filed, and apply the answer. Started by skarbiec request watch.
What failed: showing a request dialog through osascript. Why: osascript could not be started, so no dialog can ask the decider: it is not on PATH, or this account may not run it. What the refusal shows: PATH: {path}; the system said: {said}; the request it was asking about is still pending.
Fix: run skarbiec request watch --local in the decider's logged-in macOS session, where osascript shows dialogs, or decide from a terminal with skarbiec request approve|deny <request-id> --by <uid>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_watcher_that_cannot_show_a_dialog_stops_and_the_request_stays_pending.
skarbiec.request.watch request-dialog-answer#
ask the decider about each pending request in a native dialog the moment it is filed, and apply the answer. Started by skarbiec request watch.
What failed: reading what the {dialog} dialog answered. Why: it answered the button {choice}, which it did not offer. What the refusal shows: offered: {offered}; the request it was asking about is still pending.
Fix: start skarbiec request watch --local --by <uid> again, or decide from a terminal with skarbiec request approve|deny <request-id> --by <uid>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_dialog_answer_that_was_not_offered_stops_the_watcher.
skarbiec.request.watch request-dialog-answer-not-text#
ask the decider about each pending request in a native dialog the moment it is filed, and apply the answer. Started by skarbiec request watch.
What failed: reading what the request dialog answered. Why: osascript answered {bytes} bytes that stop being UTF-8 text at byte {offset}, so which button was pressed cannot be read. What the refusal shows: the request it was asking about is still pending.
Fix: start skarbiec request watch --local --by <uid> again, or decide from a terminal with skarbiec request approve|deny <request-id> --by <uid>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_dialog_answer_that_is_not_text_stops_the_watcher.
skarbiec.request.watch request-dialog-answer-unshaped#
ask the decider about each pending request in a native dialog the moment it is filed, and apply the answer. Started by skarbiec request watch.
What failed: reading what the request dialog answered. Why: the answer holds no line feed between the button and the typed text, which the dialog's script always returns, so the button cannot be told from what was typed. What the refusal shows: answered: {reply}; the request it was asking about is still pending.
Fix: start skarbiec request watch --local --by <uid> again, or decide from a terminal with skarbiec request approve|deny <request-id> --by <uid>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_dialog_answer_without_its_line_feed_stops_the_watcher.
skarbiec.request.watch request-words-unreadable#
ask the decider about each pending request in a native dialog the moment it is filed, and apply the answer. Started by skarbiec request watch.
What failed: reading the dialog's words from the texts bundle built into this skarbiec. Why: the bundle built in does not read as a wisent-texts bundle, so the dialog has no words to show. What the refusal shows: wisent-texts said: {said}; no dialog was shown.
Fix: install a skarbiec built from a release whose texts/bundle.json reads, or decide from a terminal with skarbiec request approve|deny <request-id> --by <uid>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/requests/request_register.sh::a_build_whose_texts_do_not_read_shows_no_dialog.
skarbiec.reseal reseal-unproven-run#
open every OpenPGP ciphertext an item holds and seal it again to the same recipients, keeping a copy of the vault until every ciphertext is proven to open from the file written. Started by skarbiec reseal, POST /v1/operator/reseal, POST /v1/operator/reseal/apply.
What failed: resealing the vault at {path}. Why: a reseal started at {started} has not proven that every ciphertext opens again ({last}). What the refusal shows: copy kept before it: {backup}.
Fix: import the keys it names (skarbiec keys import) and run skarbiec reseal --verify, or put the copy back with skarbiec backup restore {backup} --yes.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/gpg/gpg_free.sh::a_second_reseal_over_an_unproven_run_is_refused_naming_the_kept_copy.
skarbiec.reseal reseal-keys-missing#
open every OpenPGP ciphertext an item holds and seal it again to the same recipients, keeping a copy of the vault until every ciphertext is proven to open from the file written. Started by skarbiec reseal, POST /v1/operator/reseal, POST /v1/operator/reseal/apply.
What failed: resealing the vault at {path}. Why: the key file {key_file} holds no key {missing}, which items are sealed to, so resealing would drop them. What the refusal shows: key file: {key_file}.
Fix: bring them with skarbiec keys import (or skarbiec owner key import <file> for public keys), then run reseal again; nothing was written.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/gpg/gpg_free.sh::reseal_with_a_key_file_lacking_a_key_items_are_sealed_to_is_refused_naming_it.
skarbiec.reseal reseal-unopened#
open every OpenPGP ciphertext an item holds and seal it again to the same recipients, keeping a copy of the vault until every ciphertext is proven to open from the file written. Started by skarbiec reseal, POST /v1/operator/reseal, POST /v1/operator/reseal/apply.
What failed: opening vault item {item}'s {place} to reseal it. Why: it does not open with a secret key this host holds, so it cannot be sealed again. What the refusal shows: opening it said: {error}; key file: {key_file}; nothing was written.
Fix: run reseal where the key file holds a secret key the item is sealed to; skarbiec readers {item} names them.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/gpg/gpg_free.sh::reseal_with_a_key_file_that_opens_not_every_ciphertext_is_refused_and_writes_nothing.
skarbiec.reseal reseal-not-proven#
open every OpenPGP ciphertext an item holds and seal it again to the same recipients, keeping a copy of the vault until every ciphertext is proven to open from the file written. Started by skarbiec reseal, POST /v1/operator/reseal, POST /v1/operator/reseal/apply.
What failed: proving the resealed vault at {path}. Why: {failed} of {count} ciphertexts do not open with this host's keys (first: {first}). What the refusal shows: copy kept before resealing: {backup}.
Fix: import the missing keys and run skarbiec reseal --verify, or put the copy back with skarbiec backup restore {backup} --yes.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/gpg/gpg_free.sh::reseal_verify_with_keys_that_open_not_every_ciphertext_keeps_the_run_recorded.
skarbiec.reseal reseal-copy-unmade#
open every OpenPGP ciphertext an item holds and seal it again to the same recipients, keeping a copy of the vault until every ciphertext is proven to open from the file written. Started by skarbiec reseal, POST /v1/operator/reseal, POST /v1/operator/reseal/apply.
What failed: keeping the vault at {path} before resealing it. Why: the copy of the vault reseal keeps first cannot be written. What the refusal shows: the file system answered: {error}; nothing was written; the vault is as it was.
Fix: let this account create files in the vault's directory, then run skarbiec reseal --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/gpg/gpg_free.sh::reseal_that_cannot_keep_a_copy_of_the_vault_is_refused_and_writes_nothing.
skarbiec.credential.resume handle-missing#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: reading the approval credential resume continues. Why: {flag} is required: the approval id and its resume token are what Weles returned when it asked for approval. What the refusal shows: {flag}: absent.
Fix: pass --approval <id> and --resume-token-file <path> (or --resume-token <token>) from the approval Weles reported.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::a_resume_without_approval_is_refused_naming_it.
skarbiec.credential.resume handle-malformed#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: reading {flag} of credential resume. Why: it is not one handle: ASCII letters, digits, '.', '_' and '-', non-empty. What the refusal shows: {flag} of {bytes} byte(s).
Fix: pass {flag} exactly as Weles reported it.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::an_approval_id_with_a_space_is_refused.
skarbiec.credential.resume nothing-waiting#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: finding the credential operation of role {role} to resume. Why: {record} holds no operation that can be read. What the refusal shows: record: {record}; reading it said: {error}.
Fix: credential status role:{role} --local shows what the role holds; start the operation again if none is recorded.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::a_role_with_no_operation_record_is_refused.
skarbiec.credential.resume record-incomplete#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: reading the waiting operation of role {role}. Why: its record names no {what}, so the approval cannot be matched to it. What the refusal shows: record: {record}.
Fix: credential status role:{role} --local reports the record; start the operation again, which writes a whole record.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::a_record_naming_no_approval_is_refused_naming_what_it_lacks.
skarbiec.credential.resume wire-unsupported#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: resuming the operation of role {role}. Why: its record was written in the credential-operation wire {version}, and this release speaks {expected}. What the refusal shows: record version: {version}.
Fix: let the release that wrote it finish it, or start the operation again with this release.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::a_record_from_another_wire_version_is_refused_naming_both.
skarbiec.credential.resume not-waiting#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: resuming the operation of role {role}. Why: it is {status}, not waiting for human approval. What the refusal shows: operation status: {status}.
Fix: credential status role:{role} --local shows where it stands; only an operation that needs human approval is resumed.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::an_operation_that_is_not_waiting_is_refused_naming_its_status.
skarbiec.credential.resume operation-mismatch#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: resuming the operation of role {role}. Why: it is waiting on {waiting}, and --operation expects {expected}. What the refusal shows: waiting operation: {waiting}.
Fix: drop --operation, or name {waiting}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::a_resume_expecting_another_operation_is_refused_naming_both.
skarbiec.credential.resume consumer-mismatch#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: resuming the operation of role {role}. Why: it is waiting for another consumer than --consumer {expected}. What the refusal shows: --consumer {expected}.
Fix: drop --consumer, or name the consumer the operation was started for (credential status role:{role} --local).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::a_resume_for_another_consumer_is_refused.
skarbiec.credential.resume approval-mismatch#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: resuming the operation of role {role}. Why: the presented approval id or resume token is not the one the waiting operation holds. What the refusal shows: --approval {approval}.
Fix: pass the approval id and resume token Weles reported for this operation.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::a_wrong_resume_token_is_refused.
skarbiec.credential.resume approval-expired#
continue a credential operation after its human approval. Started by skarbiec credential resume, POST /v1/operator/credential, Desktop: Requests → Resume operation.
What failed: resuming the operation of role {role}. Why: APPROVAL_EXPIRED: its approval expired at {expires_at}; the operation was released and its staged candidate discarded. What the refusal shows: approval expires_at: {expires_at}.
Fix: start the operation again: skarbiec credential {operation} role:{role} ….
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/enrolment/resume.sh::an_expired_approval_releases_the_operation_and_is_refused.
skarbiec.retag retag-rename-same#
replace one item's tags, put one tag on or off several items, or rename one tag everywhere it is carried. Started by skarbiec retag, POST /v1/operator/items/retag, Desktop: Items → a selected item → Save tags, Desktop: Settings → Policy → Tags → Add the tag / Remove the tag, Desktop: Settings → Policy → Tags → Rename on every item.
What failed: renaming the tag {from}. Why: --rename and --to both name {from}, so there is nothing to rename. What the refusal shows: --rename {from} --to {from}.
Fix: name the new tag in --to, or --to "" to drop {from}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/tags/retag.sh::renaming_a_tag_to_itself_is_refused.
skarbiec.retag retag-no-carrier#
replace one item's tags, put one tag on or off several items, or rename one tag everywhere it is carried. Started by skarbiec retag, POST /v1/operator/items/retag, Desktop: Items → a selected item → Save tags, Desktop: Settings → Policy → Tags → Add the tag / Remove the tag, Desktop: Settings → Policy → Tags → Rename on every item.
What failed: renaming the tag {from}. Why: no live item carries {from}, so nothing was renamed. What the refusal shows: live items carrying {from}: none.
Fix: skarbiec tags lists every tag the live items carry.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/tags/retag.sh::renaming_a_tag_no_item_carries_is_refused.
skarbiec.retag retag-item-not-live#
replace one item's tags, put one tag on or off several items, or rename one tag everywhere it is carried. Started by skarbiec retag, POST /v1/operator/items/retag, Desktop: Items → a selected item → Save tags, Desktop: Settings → Policy → Tags → Add the tag / Remove the tag, Desktop: Settings → Policy → Tags → Rename on every item.
What failed: retagging {id}. Why: {id} is not a live item of this vault. What the refusal shows: item {id}: {state}.
Fix: name live items (skarbiec list); a trashed one is restored first with skarbiec restore {id}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/tags/retag.sh::an_item_that_is_not_live_is_named_and_the_others_are_retagged.
skarbiec.rotate.provider rotate-provider-unknown#
choose the provider a rotation runs through and refuse a flag it does not take. Started by other functionalities only.
What failed: choosing what rotates the secret. Why: --with {name} is not a provider this vault rotates through; it rotates through {providers}. What the refusal shows: nothing was rotated.
Fix: name one of the providers skarbiec rotation providers lists; a policy saved under an older spelling is moved by skarbiec upgrade --apply.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotate/refusals.sh::a_provider_this_vault_does_not_rotate_through_is_refused_naming_the_ones_it_does.
skarbiec.rotate.provider rotate-flag-untaken#
choose the provider a rotation runs through and refuse a flag it does not take. Started by other functionalities only.
What failed: rotating with {provider}. Why: --with {provider} takes no --{flag}. What the refusal shows: it takes: {usage}; nothing was rotated.
Fix: drop --{flag}, or name the provider whose flag it is.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotate/refusals.sh::a_flag_the_provider_does_not_take_is_refused_naming_its_usage.
skarbiec.rotate.api rotate-api-value-unfit#
read the token an item keeps, have its provider replace it through the provider's API, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with gitlab, skarbiec rotate <id> --with cloudflare, skarbiec rotate <id> --with sendgrid, skarbiec rotate <id> --with twilio, skarbiec rotate <id> --with vercel.
What failed: reading the {provider} credential {id} keeps. Why: {id}'s {field} does not read as {shape}, so {provider} cannot be asked about it. What the refusal shows: {observed}; nothing was asked of {provider} or changed.
Fix: store the {provider} credential in {field} as {shape} (skarbiec field set {id} {field} < file), then rotate.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_api.sh::a_credential_of_another_shape_is_refused_naming_the_shape.
skarbiec.rotate.api rotate-api-answer-not-json#
read the token an item keeps, have its provider replace it through the provider's API, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with gitlab, skarbiec rotate <id> --with cloudflare, skarbiec rotate <id> --with sendgrid, skarbiec rotate <id> --with twilio, skarbiec rotate <id> --with vercel.
What failed: reading {provider}'s answer to {method} {url}. Why: {provider} answered with a success status and a body that is not JSON, where its API answers JSON: a proxy or an outage page answered for it. What the refusal shows: {bytes} bytes; the JSON reader stopped at line {line}, column {column}: {said}; {state}.
Fix: run the same rotate again once {url} answers its API; skarbiec get {id} --revision names the revision the item holds now.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_api.sh::a_provider_answering_no_json_is_refused_naming_what_stands.
skarbiec.rotate.api rotate-api-answer-member-missing#
read the token an item keeps, have its provider replace it through the provider's API, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with gitlab, skarbiec rotate <id> --with cloudflare, skarbiec rotate <id> --with sendgrid, skarbiec rotate <id> --with twilio, skarbiec rotate <id> --with vercel.
What failed: reading {provider}'s answer to {method} {path}. Why: {provider} answered without {member}, which the rotation needs to {purpose}. What the refusal shows: the answer's members: {members}; {state}.
Fix: {repair}.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_api.sh::a_provider_answer_without_a_member_is_refused_naming_what_stands.
skarbiec.rotate.api rotate-api-cloudflare-unsuccessful#
read the token an item keeps, have its provider replace it through the provider's API, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with gitlab, skarbiec rotate <id> --with cloudflare, skarbiec rotate <id> --with sendgrid, skarbiec rotate <id> --with twilio, skarbiec rotate <id> --with vercel.
What failed: asking Cloudflare to {purpose} ({method} {path}). Why: Cloudflare answered with an HTTP success and success: {success} in its body, which is how its API refuses a request it read. What the refusal shows: Cloudflare's errors: {errors}; {state}.
Fix: repair what Cloudflare's errors name (the token's permissions on the dashboard's API Tokens page), then rotate again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_api.sh::cloudflare_reporting_no_success_is_refused_naming_its_errors.
skarbiec.rotate.api rotate-api-gitlab-expiry-unread#
read the token an item keeps, have its provider replace it through the provider's API, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with gitlab, skarbiec rotate <id> --with cloudflare, skarbiec rotate <id> --with sendgrid, skarbiec rotate <id> --with twilio, skarbiec rotate <id> --with vercel.
What failed: recording the expiry GitLab gave {id}'s new token. Why: GitLab answered expires_at {day}, which is not a calendar day in YYYY-MM-DD form, so no expiry is recorded and review cannot warn before the token ends. What the refusal shows: {part}: {said}; the token is rotated and stored, only its expiry is not recorded.
Fix: record the day GitLab shows for the token: skarbiec expiry set {id} --on <YYYY-MM-DDT00:00:00Z>.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_api.sh::a_gitlab_expiry_that_is_not_a_day_is_said_beside_the_rotation.
skarbiec.rotate.cli rotate-cli-aws-session-key#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: reading the AWS access key {id} keeps. Why: {id} keeps a session_token beside its access key: it is a temporary key AWS hands out, which ends by itself and which IAM cannot replace. What the refusal shows: {id}: access_key_id {key}, session_token of {length} characters; nothing was asked of AWS or changed.
Fix: rotate the long-lived key of the IAM user the session came from, kept in an access-key item without a session_token; skarbiec list --kind access-key lists them.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::an_aws_item_keeping_a_session_token_is_refused_before_aws_is_asked.
skarbiec.rotate.cli rotate-cli-aws-root-key#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: naming the IAM user {id}'s key {key} belongs to. Why: aws iam get-user answered no User.UserName: the key belongs to the AWS account's root user, whose keys IAM's access-key calls do not replace. What the refusal shows: the answer's members: {members}; nothing was changed.
Fix: replace the root user's key in the AWS console (Security credentials), or keep an IAM user's key in {id} and rotate that.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::an_aws_key_of_the_root_user_is_refused_naming_it.
skarbiec.rotate.cli rotate-cli-answer-member-missing#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: reading {program}'s answer to {request}. Why: {program} {request} answered without {member}, which the rotation needs to {purpose}. What the refusal shows: the answer's members: {members}; {state}.
Fix: run {program} {request} by hand to see its answer and update {package} when it names {member} otherwise; skarbiec get {id} --revision names the revision {id} holds now.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_provider_program_answer_without_a_member_is_refused_naming_what_stands.
skarbiec.rotate.cli rotate-cli-gcp-key-not-json#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: reading {whose} as a Google Cloud service account key. Why: {whose} is not JSON, and a service account key file Google issues is a JSON object. What the refusal shows: {bytes} bytes; the JSON reader stopped at line {line}, column {column}: {why}; {state}.
Fix: store the key file the Cloud console downloads for the service account (skarbiec field set {id} credential_json < key.json), then rotate again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_gcp_item_whose_key_is_not_json_is_refused_naming_where_it_stops.
skarbiec.rotate.cli rotate-cli-gcp-key-other-type#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: reading {whose} as a Google Cloud service account key. Why: {whose} is a credential of type {type}, not a service_account key file, and rotate --with gcp replaces a service account's key. What the refusal shows: type: {type}; {state}.
Fix: store a service account's key file in {id} (skarbiec field set {id} credential_json < key.json); a user's or an external account's credential is renewed by signing in again, not rotated.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_gcp_item_whose_key_is_another_credential_type_is_refused_naming_it.
skarbiec.rotate.cli rotate-cli-gcp-key-member-missing#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: reading {whose} as a Google Cloud service account key. Why: {whose} names no {member}, which the rotation needs to {purpose}, and every service account key file Google issues names it. What the refusal shows: the key file's members: {members}; {state}.
Fix: store the whole key file the Cloud console downloads for the service account (skarbiec field set {id} credential_json < key.json), then rotate again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_gcp_item_whose_key_names_no_account_is_refused_naming_the_member.
skarbiec.rotate.cli rotate-cli-azure-key-unlisted#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: finding the secret az ad app credential reset added to application {client}. Why: the application's credentials, listed after the secret was added, hold no new one whose hint begins the new secret: Entra had not listed it yet. What the refusal shows: {listed} credential(s) listed, key ids {keys}; Entra holds a new secret named skarbiec that the vault does not, and {id} keeps the old one.
Fix: delete the newest secret named skarbiec under the application's Certificates & secrets (az ad app credential list --id {client} lists them), then run skarbiec rotate {id} --with azure again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::an_azure_secret_entra_does_not_list_is_refused_naming_what_it_left.
skarbiec.rotate.cli rotate-cli-database-policy-unmet#
read the secret an item keeps, have the provider's own program replace it, store the new one as the item's next revision and prove it, undoing what it can when a step fails. Started by skarbiec rotate <id> --with database, skarbiec rotate <id> --with aws, skarbiec rotate <id> --with gcp, skarbiec rotate <id> --with azure.
What failed: making the new password for {id}. Why: a new password of {length} letters and digits does not clear the vault's password policy, whose rules {rules} refuse it. What the refusal shows: the policy's verdict: {verdict}; nothing was changed.
Fix: rotate with a longer --length (skarbiec policy get names the policy's rules), or change the policy with skarbiec policy set.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_cli.sh::a_database_rotation_whose_new_password_misses_the_policy_is_refused_naming_the_rules.
skarbiec.rotate.item rotate-api-kind-unfit#
read the kind and fields of the item a rotation replaces the secret of, before the provider is asked anything. Started by other functionalities only.
What failed: reading the {provider} credential {id} keeps. Why: {id} is an item of kind {kind}, and rotate --with {provider} replaces the {field} an item of kind {wanted} keeps. What the refusal shows: {id}: kind {kind}, where rotate --with {provider} replaces {article} {wanted} item; nothing was asked of {provider} or changed.
Fix: name the {wanted} item that keeps the {provider} credential (skarbiec list --kind {wanted} names them).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_api.sh::an_item_of_another_kind_is_refused_naming_the_kind_the_provider_takes.
skarbiec.rotate.item rotate-api-field-empty#
read the kind and fields of the item a rotation replaces the secret of, before the provider is asked anything. Started by other functionalities only.
What failed: reading the {provider} credential {id} keeps. Why: {id} keeps no {field}, so there is nothing to sign in to {provider} with and nothing to replace. What the refusal shows: {id}: {field} is empty or absent; nothing was asked of {provider} or changed.
Fix: store the current {provider} credential first (skarbiec field set {id} {field} < file), then rotate.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotate/provider_api.sh::an_item_keeping_no_credential_is_refused_naming_the_field.
skarbiec.rotation form-unknown#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: reading what skarbiec rotation is asked. Why: rotation {given} is not one of its forms. What the refusal shows: usage: {usage}.
Fix: run rotation set, list, remove, run or providers; skarbiec rotation help lists them.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::an_unknown_rotation_form_is_refused_with_its_usage.
skarbiec.rotation providers-argument#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: listing the rotation providers. Why: rotation providers takes no argument or flag. What the refusal shows: arguments: {given}.
Fix: run skarbiec rotation providers alone.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::rotation_providers_with_an_argument_is_refused.
skarbiec.rotation now-without-item#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: running one rotation policy before it falls due. Why: --now runs one policy, and --item names none. What the refusal shows: flags given: --now.
Fix: name it: skarbiec rotation run --item <item-id> --now.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::rotation_run_now_without_item_is_refused.
skarbiec.rotation set-flag-unknown#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: reading the flags of rotation set. Why: --{flag} is not a flag a managed rotation policy keeps. What the refusal shows: usage: {usage}.
Fix: drop --{flag}; a managed policy takes --every-days, --provider, --consumer and --purpose, and --with names a local provider.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_managed_policy_with_an_unknown_flag_is_refused_naming_it.
skarbiec.rotation item-argument#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: reading which item rotation {command} acts on. Why: rotation {command} names exactly one item, and {count} were given. What the refusal shows: arguments: {given}.
Fix: name one item: skarbiec rotation {command} <item-id> ….
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_policy_naming_no_item_is_refused.
skarbiec.rotation every-days#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: reading --every-days of rotation set. Why: --every-days must be a whole number of days above zero that fits in seconds. What the refusal shows: --every-days {value}.
Fix: pass the interval in whole days, e.g. --every-days 30.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/credential/files/owner_only_files.sh::a_non_numeric_interval_is_refused_with_the_value_given.
skarbiec.rotation managed-flag#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: reading the flags of a managed rotation policy. Why: --{flag} is required, or is not one name of ASCII letters, digits, '.', '_' and '-'. What the refusal shows: --{flag} {value}.
Fix: pass --{flag} as credential rotate --local is given it.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_managed_policy_without_provider_is_refused.
skarbiec.rotation no-live-item#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: declaring a rotation policy for {item}. Why: no live item {item} is in this vault. What the refusal shows: item {item}: absent or trashed.
Fix: name a live item; skarbiec list shows them, and skarbiec restore {item} brings a trashed one back.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_policy_for_an_absent_item_is_refused.
skarbiec.rotation not-managed#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: declaring a managed rotation policy for {item}. Why: {item} is {state}, not a Weles-managed credential, and only a managed credential is rotated through the lifecycle on a schedule. What the refusal shows: lifecycle state of role {role}: {state}.
Fix: bring it under management with credential adopt or credential acquire, or rotate it with a local provider: rotation set {item} --every-days <N> --with <provider>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_managed_policy_for_an_unmanaged_item_is_refused_naming_its_state.
skarbiec.rotation with-provider-flag#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: keeping the flags of a policy rotating with {provider}. Why: --with {provider} takes no --{flag}, so a policy rotating with it cannot keep one. What the refusal shows: flags {provider} takes: {taken}.
Fix: drop --{flag}; skarbiec rotation providers lists each provider's flags.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_local_policy_with_a_flag_its_provider_does_not_take_is_refused.
skarbiec.rotation section-malformed#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: reading the vault's rotation policies. Why: {why}. What the refusal shows: rotation section: {kind}.
Fix: run skarbiec upgrade to see the policies it can read; set each damaged policy again with rotation set, or remove it with rotation remove.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_rotation_section_that_is_not_an_object_is_refused_naming_its_kind.
skarbiec.rotation policy-damaged#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: reading the rotation policy of {item}. Why: it records no anchor_epoch or every_seconds, so when it falls due is unknown. What the refusal shows: policy {item}: no interval.
Fix: set it again with skarbiec rotation set {item} --every-days <N> ….
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_policy_without_its_interval_is_refused_naming_the_item.
skarbiec.rotation no-policy#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: withdrawing the rotation policy of {item}. Why: {item} has no rotation policy. What the refusal shows: policies: {policies}.
Fix: name an item rotation list shows.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::removing_a_policy_that_does_not_exist_is_refused_listing_the_policies.
skarbiec.rotation rotations-not-accepted#
declare, list, withdraw and run per-item rotation policies. Started by skarbiec rotation set, skarbiec rotation list, skarbiec rotation remove, skarbiec rotation run, skarbiec rotation providers, POST /v1/operator/rotation/set, POST /v1/operator/rotation/remove, POST /v1/operator/rotation/run, Desktop: Lifecycle → Rotation schedule.
What failed: running the due rotation policies. Why: {count} scheduled rotation(s) were not accepted ({alerted}): {items}. What the refusal shows: run report: {report}.
Fix: read each policy's last_error with skarbiec rotation list and act on it; the other due rotations ran.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/rotation/policies.sh::a_due_policy_that_cannot_rotate_fails_the_run_naming_it.
skarbiec.route.resolve route-unresolved#
answer which item and field each name reaches, and with --emit or --template write the values for one consumer. Started by skarbiec route resolve, POST /v1/operator/route/resolve.
What failed: resolving {names}. Why: {count} of the {asked} names asked reach no coordinate, each for the declared reason named beside it. What the refusal shows: each name with its cause and why: {problems}; the report above names what every name reached.
Fix: repair each name as its cause says (skarbiec route resolve <name> refuses one name with its own cause and fix): tag the item that answers it, or state the row with skarbiec route declare; skarbiec route resolve with no name lists every route this vault answers.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::several_names_reaching_nothing_are_refused_together_each_with_its_cause.
skarbiec.route.resolve route-unreadable-here#
answer which item and field each name reaches, and with --emit or --template write the values for one consumer. Started by skarbiec route resolve, POST /v1/operator/route/resolve.
What failed: writing the values {names} reach. Why: no coordinate they reach holds a value {caller} may read: each names a field its item does not hold, or one the caller is not granted. What the refusal shows: the report above names each coordinate, whether its field is there, and its reader.
Fix: point the route at a field the item holds (skarbiec route resolve <name> names it), grant the consumer the items it needs (skarbiec grant), or emit as the owner without --consumer.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_materialization_that_can_write_no_value_is_refused.
skarbiec.route.declare route-self-declared#
state, or withdraw, one route a vault item cannot declare for itself, keeping the previous table beside it. Started by skarbiec route declare, skarbiec route withdraw, POST /v1/operator/route/declare, POST /v1/operator/route/withdraw.
What failed: declaring the route {resource}. Why: {resource} is resolved from what an item declares, not from the table. What the refusal shows: {resource} is a provider, agent, login or exact coordinate name.
Fix: tag the item that answers it instead; skarbiec route help names each vocabulary.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_name_an_item_declares_is_refused_naming_the_tag_to_write.
skarbiec.route.declare route-repoint#
state, or withdraw, one route a vault item cannot declare for itself, keeping the previous table beside it. Started by skarbiec route declare, skarbiec route withdraw, POST /v1/operator/route/declare, POST /v1/operator/route/withdraw.
What failed: declaring the route {resource}. Why: {resource} already maps {target}, and repointing a live route is not a declaration. What the refusal shows: row for {resource}: {target}.
Fix: withdraw it first with skarbiec route withdraw --resource {resource} --reason <why>, then declare the new row.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_declaration_over_a_live_row_naming_another_target_is_refused_and_the_row_kept.
skarbiec.route.verify route-broken#
confront every resolvable route with the vault and refuse when one cannot serve a usable credential. Started by skarbiec route verify, POST /v1/operator/route/verify.
What failed: verifying every capability route. Why: {count} of {checked} capability routes do not resolve: {named}. What the refusal shows: the report above names each broken route and its problem.
Fix: skarbiec route resolve <name> names why each does not resolve; restore or retag the item, or withdraw the row.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_route_naming_a_deleted_item_fails_verify_naming_it.
skarbiec.route.table route-table-not-json#
read the hand-declared route rows, and publish a new table only after it reads back whole. Started by other functionalities only.
What failed: reading the capability route table {path}. Why: the file is not JSON, so no hand-declared row in it can be read. What the refusal shows: {bytes} bytes; the parser stopped at {at}: {said}.
Fix: restore it from the newest {path}.before-<stamp> beside it, which every write keeps; SKARBIEC_CAPABILITY_ROUTES_FILE names the table read.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_route_table_that_is_not_json_is_refused_naming_where_it_stops.
skarbiec.route.table route-table-not-object#
read the hand-declared route rows, and publish a new table only after it reads back whole. Started by other functionalities only.
What failed: reading the capability route table {path}. Why: the table holds {shape}, not an object of resources, so no row can be looked up by its name. What the refusal shows: it holds {held}, not an object of resources.
Fix: restore it from the newest {path}.before-<stamp> beside it, which every write keeps; SKARBIEC_CAPABILITY_ROUTES_FILE names the table read.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_route_table_that_is_not_an_object_of_rows_is_refused_naming_it.
skarbiec.route.table route-table-staged-torn#
read the hand-declared route rows, and publish a new table only after it reads back whole. Started by other functionalities only.
What failed: publishing the capability route table {path}. Why: the staged copy read back from disk is not the JSON just written, so the disk or filesystem did not keep the bytes. What the refusal shows: staged copy {staging}: {written} bytes read back; the parser said: {said}; the table in place is unchanged.
Fix: check the disk holding {path} (df -h on its directory; a full or failing volume tears writes), then run the same skarbiec route declare or withdraw again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_staged_table_that_reads_back_torn_is_refused.
skarbiec.route.coordinate route-coordinate-item-renamed#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: the row names {item}, and the item it was declared against is now called {found}. What the refusal shows: uid recorded with the row: {uid}; live item carrying it: {found}.
Fix: point the row at the new name: skarbiec route withdraw --resource <name> --reason <why>, then skarbiec route declare --resource <name> --tag <tag> --field {field} --reason <why> so a later rename changes nothing.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/coordinate_refusals.sh::a_row_naming_a_renamed_item_names_its_new_name.
skarbiec.route.coordinate route-coordinate-item-absent#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: no vault item is called {item}, and no live item carries the uid the row recorded. What the refusal shows: uid recorded with the row: {uid}.
Fix: declare the row again against the item's current id (skarbiec list --all lists every id): skarbiec route withdraw --resource <name> --reason <why>, then skarbiec route declare --resource <name> --item <id> --field {field} --reason <why>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/routes/coordinate_refusals.sh::a_route_naming_a_purged_item_names_no_item.
skarbiec.route.coordinate route-coordinate-item-trashed#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: {item} is in the trash, and a trashed item answers no route. What the refusal shows: {item}: trashed.
Fix: bring it back with skarbiec restore {item}, or withdraw the route that names it.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_route_naming_a_deleted_item_fails_verify_naming_it.
skarbiec.route.coordinate route-coordinate-item-unopened#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: the item layer refused to open {item} on this host, so whether it holds {field} cannot be told. What the refusal shows: the item layer's cause: {below}; it said: {said}.
Fix: {below_fix}; skarbiec readers {item} names the keys {item} is sealed to.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/routes/coordinate_refusals.sh::a_route_reaching_an_item_no_key_here_opens_names_the_item_layers_cause.
skarbiec.route.coordinate route-coordinate-field-absent#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: {item} opened and holds no field {field}. What the refusal shows: fields {item} holds: {held}.
Fix: write {field} into {item} with skarbiec set {item}, or point the route at one of {held}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/access/grants/grant_capability.sh::a_resource_whose_credential_holds_nothing_is_refused_naming_its_coordinate.
skarbiec.route.coordinate route-coordinate-fields-damaged#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: {item} opened, and its payload holds no fields object, so no field of it can be read. What the refusal shows: members of {item}'s payload: {members}.
Fix: rewrite the item in its canonical shape with skarbiec set {item} --type <kind>; skarbiec history {item} names the write that left it so.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/coordinate_refusals.sh::a_route_reaching_an_item_with_no_fields_object_is_named.
skarbiec.route.coordinate route-coordinate-field-not-text#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: {field} holds null, which redemption cannot hand out as text. What the refusal shows: {item}#{field}: null.
Fix: write the credential into {field} with skarbiec set {item}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/coordinate_refusals.sh::a_route_reaching_a_null_field_is_named.
skarbiec.route.coordinate route-coordinate-field-placeholder#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: {field} holds an uppercase placeholder written where the credential belongs, not a usable credential. What the refusal shows: {item}#{field} holds a placeholder of {length} characters.
Fix: write the real credential into {field} with skarbiec set {item}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/coordinate_refusals.sh::a_route_reaching_a_placeholder_is_named.
skarbiec.route.coordinate route-coordinate-field-empty#
tell whether one item and field a route reaches hold a credential redemption can hand out. Started by other functionalities only.
What failed: reading {item}#{field}. Why: {field} is present and holds only blank text, so it carries no credential. What the refusal shows: {item}#{field}: blank ({shape}).
Fix: write the credential into {field} with skarbiec set {item}; skarbiec history {item} names the write that emptied it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/coordinate_refusals.sh::a_route_reaching_an_emptied_field_is_named.
skarbiec.route.name route-name-undeclared#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name}. Why: no vault item declares {name} and the capability route table has no row for it. What the refusal shows: {name} is {form}; route table {table} holds {rows} rows, none for {name}.
Fix: tag the item that answers the name, or state the row with skarbiec route declare --resource {name} (--item <id> | --tag <tag>) --field <field> --reason <why>; skarbiec route resolve with no name lists every route this vault answers.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/routes/refusals.sh::a_name_that_reaches_nothing_is_refused_naming_why.
skarbiec.route.name route-name-provider-declared-twice#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name}. Why: {count} live vault items carry the tag {tag}, and which credential answers {name} is the operator's choice, never this program's. What the refusal shows: items declaring {name}: {items}.
Fix: keep {tag} on the one item that answers {name} and take it off the others with skarbiec retag --remove {tag} <id>, or give each its own subscription with skarbiec retag --add brama:id:<id> <item> and ask for provider:<provider>:<id>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_provider_two_items_declare_is_refused_naming_both.
skarbiec.route.name route-name-agent-declared-twice#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name}. Why: {count} live internal-authority items name the agent {agent} in their id field, and which signing identity answers it is the operator's choice, never this program's. What the refusal shows: items declaring {name}: {items}.
Fix: keep the agent's identity in one of {items} and trash the others with skarbiec delete <id>, or rewrite their id field with skarbiec set <id> --type internal-authority.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::an_agent_two_identity_items_declare_is_refused_naming_both.
skarbiec.route.name route-name-row-incomplete#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name} from its capability route row. Why: the row names no {missing}: a row names an item or a tag, and a field, and this one cannot say which coordinate {name} reaches. What the refusal shows: row for {name} in {table}: {row}.
Fix: withdraw it with skarbiec route withdraw --resource {name} --reason <why> and declare it whole with skarbiec route declare --resource {name} (--item <id> | --tag <tag>) --field <field> --reason <why>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_row_naming_no_field_is_refused_naming_the_row.
skarbiec.route.name route-name-tag-unclaimed#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name} from its capability route row. Why: the row names the tag {tag} and no live vault item carries it: the item was trashed, or the tag taken off or renamed. What the refusal shows: row for {name} in {table}: tag {tag}, field {field}; live items carrying {tag}: none.
Fix: put the tag on the item that answers {name} with skarbiec retag --add {tag} <id>, or withdraw the row with skarbiec route withdraw --resource {name} --reason <why>; skarbiec tags lists every tag the live items carry.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_row_naming_a_tag_no_item_carries_is_refused_naming_the_tag.
skarbiec.route.name route-name-credential-field-absent#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: reading which field of {item} carries the credential {name} reaches. Why: the item does not hold {known} as text, which is where its credential is read from. What the refusal shows: fields {item} holds: {held}; the credential is read from: {known}.
Fix: write the credential into {known} with skarbiec set {item}, or take the declaration off it with skarbiec retag --remove {tag} {item}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_provider_item_holding_no_credential_field_is_refused_naming_its_fields.
skarbiec.route.name route-name-credential-fields-several#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: reading which field of {item} carries the credential {name} reaches. Why: the item holds {count} credential fields as text, and which one answers is the operator's choice, never this program's. What the refusal shows: credential fields {item} holds: {fields}.
Fix: keep exactly one of {fields} in {item} with skarbiec set {item}, or move the others into an item of their own.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_provider_item_holding_two_credential_fields_is_refused_naming_them.
skarbiec.route.name route-name-kind-no-credential#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: reading which field of {item} carries the credential {name} reaches. Why: {item} is a {kind}, and a {kind} declares no provider credential (skarbiec kinds {kind} lists none with credential true): {why}. What the refusal shows: {item}: kind {kind}, tagged {tag}.
Fix: put the declaration on the item that holds the credential: skarbiec retag --remove {tag} {item}, then skarbiec retag --add {tag} <that item>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/provider_fields.sh::a_provider_tag_on_a_kind_without_a_credential_is_refused_naming_the_kind.
skarbiec.route.name route-name-fields-absent#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: reading the fields of {item}, which {name} reaches. Why: the item's payload carries no fields object, so it declares no field a name could reach. What the refusal shows: members of {item}'s payload: {members}.
Fix: rewrite the item in its canonical shape with skarbiec set {item} --type <kind>; skarbiec get {item} shows what it holds.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_name_reaching_an_item_with_no_fields_object_is_refused.
skarbiec.route.name route-name-login-absent#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name}. Why: no live vault item is called {item}, so no login answers the name. What the refusal shows: {item} is {state}.
Fix: name the login item exactly (skarbiec list --kind login lists them), or restore a trashed one with skarbiec restore {item}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_login_name_naming_no_item_is_refused.
skarbiec.route.name route-name-login-kind-other#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name}. Why: {item} is not a login: only an item of kind login declares the fields a sign-in exports. What the refusal shows: kind of {item}: {kind}.
Fix: name a login item (skarbiec list --kind login lists them), or resolve the field itself as {item}#<field>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_login_name_naming_an_item_of_another_kind_is_refused_naming_its_kind.
skarbiec.route.name route-name-login-fields-absent#
decide which item and field one capability name reaches, from what the items declare and the route table. Started by other functionalities only.
What failed: resolving the name {name}. Why: the login {item} holds none of the fields a sign-in exports. What the refusal shows: fields {item} holds: {held}; fields a sign-in exports: {known}.
Fix: write at least one of {known} into {item} with skarbiec set {item} --type login.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/routes/name_refusals.sh::a_login_holding_no_sign_in_field_is_refused_naming_what_it_holds.
skarbiec.sealing sealing-ciphertext-unknown#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading a stored ciphertext. Why: it is neither a Skarbiec sealed item nor an OpenPGP message; it starts {start}. What the refusal shows: the ciphertext was left as it is.
Fix: restore the item from a saved version (skarbiec history <id>, skarbiec restore <id> --at <stamp>) or from the backup that keeps it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_ciphertext_of_no_known_format_is_refused_naming_its_start.
skarbiec.sealing sealing-ciphertext-armor#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the {format} ciphertext. Why: its armor: the text around the data is missing a line, holds a character that is not base64, or fails its checksum. What the refusal shows: the reader said: {said}{locked}; the ciphertext was left as it is.
Fix: restore the item from a saved version (skarbiec history <id>, skarbiec restore <id> --at <stamp>) or from the backup that keeps it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_sealed_item_whose_armor_is_damaged_is_refused_naming_it.
skarbiec.sealing sealing-ciphertext-not-sealed#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the {format} ciphertext. Why: its armor says SKARBIEC SEALED, but the bytes inside do not start as a sealed item does. What the refusal shows: the reader said: {said}{locked}; the ciphertext was left as it is.
Fix: restore the item from a saved version (skarbiec history <id>, skarbiec restore <id> --at <stamp>) or from the backup that keeps it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_sealed_armor_around_other_bytes_is_refused_naming_it.
skarbiec.sealing sealing-ciphertext-malformed#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the {format} ciphertext. Why: its bytes are cut short or do not hold what the format puts where they stand. What the refusal shows: the reader said: {said}{locked}; the ciphertext was left as it is.
Fix: restore the item from a saved version (skarbiec history <id>, skarbiec restore <id> --at <stamp>) or from the backup that keeps it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_ciphertext_cut_short_is_refused_naming_where.
skarbiec.sealing sealing-ciphertext-unsupported#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the {format} ciphertext. Why: it uses an OpenPGP feature Skarbiec never wrote and does not read. What the refusal shows: the reader said: {said}{locked}; the ciphertext was left as it is.
Fix: restore the item from a saved version (skarbiec history <id>, skarbiec restore <id> --at <stamp>) or from the backup that keeps it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::an_openpgp_message_of_another_feature_is_refused_naming_it.
skarbiec.sealing sealing-ciphertext-forged#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the {format} ciphertext. Why: it fails its integrity check: it was changed after it was sealed, or the key held here is not the one it names. What the refusal shows: the reader said: {said}{locked}; the ciphertext was left as it is.
Fix: restore the item from a saved version (skarbiec history <id>, skarbiec restore <id> --at <stamp>) or from the backup that keeps it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_ciphertext_changed_after_sealing_is_refused.
skarbiec.sealing sealing-ciphertext-passphrase#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the {format} ciphertext. Why: it is sealed to no key: it is an OpenPGP message sealed with a passphrase, and a vault item opens only with a key. What the refusal shows: the reader said: {said}{locked}; the ciphertext was left as it is.
Fix: restore the item from a saved version (skarbiec history <id>, skarbiec restore <id> --at <stamp>) or from the backup that keeps it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_ciphertext_sealed_with_a_passphrase_is_refused.
skarbiec.sealing sealing-no-recipient-key#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: opening the {format} ciphertext. Why: the key file {path} holds the secret half of {held} key(s), none of them a recipient{locked}; it is sealed to key id(s) {recipients}. What the refusal shows: key file: {path}.
Fix: import the recipient's key here with skarbiec keys import, configure the unlock phrase a locked key was sealed under (SKARBIEC_UNLOCK_FILE or SKARBIEC_UNLOCK), or open it on the host that holds the key.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::an_item_no_key_here_opens_is_refused_naming_the_locked_keys.
skarbiec.sealing sealing-not-text#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the opened item as text. Why: the opened value stops being UTF-8 text at byte {offset} of its {length}. What the refusal shows: the item opened; its value is not shown.
Fix: read it as a file with skarbiec detach <id> <file>, or restore a version that holds text (skarbiec history <id>).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::an_opened_item_that_is_not_text_is_refused.
skarbiec.sealing sealing-no-recipients#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: sealing an item. Why: it names no recipient, so no key could open it. What the refusal shows: nothing was written.
Fix: give the vault an owner with skarbiec init <uid>, or name a reader with skarbiec share <id> <uid>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::sealing_to_no_recipient_is_refused.
skarbiec.sealing sealing-key-revoked#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: sealing to the key {fingerprint}. Why: its holder revoked it, so nothing new is sealed to it. What the refusal shows: nothing was written.
Fix: give its holder a new key with skarbiec recipient rekey <uid> --import <public-key-file> --yes, or skarbiec owner rotate for the owner.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::sealing_to_a_revoked_key_is_refused_naming_rekey.
skarbiec.sealing sealing-key-expired#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: sealing to the key {fingerprint}. Why: it expired at {expired}, so nothing new is sealed to it. What the refusal shows: nothing was written.
Fix: skarbiec keys names the repair: re-sign it with a later expiry and import it again, or give its holder a new key with skarbiec recipient rekey.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::sealing_to_an_expired_key_is_refused_naming_keys.
skarbiec.sealing sealing-checkpoint-no-signer#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: verifying a signed audit checkpoint. Why: it is signed by key {signer}, which the key file does not hold, so its signature cannot be checked. What the refusal shows: key file: {path}; it holds {held} key(s).
Fix: import the owner key that signed it with skarbiec keys import, or skarbiec audit verify names the line that changed.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_checkpoint_no_key_here_verifies_is_reported_naming_why.
skarbiec.sealing sealing-checkpoint-bad-signature#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: verifying a signed audit checkpoint. Why: its signature does not verify: the checkpoint's text was changed after it was signed, or it is no text signature. What the refusal shows: key file: {path}; the verifier said: {said}.
Fix: skarbiec audit verify names the line that changed; restore the journal from a backup taken before it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_checkpoint_changed_after_signing_is_reported_naming_why.
skarbiec.sealing sealing-checkpoint-malformed#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: verifying a signed audit checkpoint. Why: it is no whole cleartext-signed message: a PGP SIGNED MESSAGE or PGP SIGNATURE line is missing, its armor is damaged, or its signature uses what Skarbiec never writes. What the refusal shows: key file: {path}; the verifier said: {said}.
Fix: skarbiec audit verify names the line that holds it; restore the journal from a backup taken before it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_checkpoint_that_is_no_signed_message_is_reported_naming_why.
skarbiec.sealing sealing-key-block-secret#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading a public key block. Why: this is a secret key block, and Skarbiec takes only public keys here. What the refusal shows: nothing was imported.
Fix: export the public half with gpg --armor --export <uid>, or bring a secret key gpg kept with skarbiec keys import.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_secret_key_block_given_as_a_public_key_is_refused.
skarbiec.sealing sealing-key-block-several#
seal each item to every recipient's key, open it with the secret halves this host holds, and sign and verify the owner's audit checkpoints, in this process. Started by skarbiec get, skarbiec set, skarbiec share, skarbiec audit epoch.
What failed: reading the one key a key file names. Why: it holds {count} keys: {fingerprints}. What the refusal shows: nothing was imported.
Fix: give a file holding the one key: gpg --armor --export <fingerprint> exports one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_key_file_holding_several_keys_is_refused_naming_them.
skarbiec.workload-key sealing-workload-key-private#
read the PEM Ed25519 public key a workload registers and check the proofs it signs. Started by skarbiec grant issue.
What failed: reading the Ed25519 public key of {what}. Why: it is a private key, and a workload registers only its public half. What the refusal shows: {length} characters, none of them shown; the key was not used.
Fix: give its public half: openssl pkey -in <private-key-file> -pubout writes it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_private_key_given_as_a_workload_key_is_refused_without_showing_it.
skarbiec.workload-key sealing-workload-key-no-begin#
read the PEM Ed25519 public key a workload registers and check the proofs it signs. Started by skarbiec grant issue.
What failed: reading the Ed25519 public key of {what}. Why: it has no -----BEGIN PUBLIC KEY----- line, so it is no PEM public key. What the refusal shows: {length} characters; the key was not used.
Fix: make the workload key with openssl genpkey -algorithm ED25519 and give its PEM public key (openssl pkey -pubout).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_workload_key_with_no_pem_line_is_refused_naming_it.
skarbiec.workload-key sealing-workload-key-no-end#
read the PEM Ed25519 public key a workload registers and check the proofs it signs. Started by skarbiec grant issue.
What failed: reading the Ed25519 public key of {what}. Why: it has no -----END PUBLIC KEY----- line after its begin line; it was cut short. What the refusal shows: {length} characters; the key was not used.
Fix: make the workload key with openssl genpkey -algorithm ED25519 and give its PEM public key (openssl pkey -pubout).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_workload_key_cut_short_is_refused_naming_it.
skarbiec.workload-key sealing-workload-key-not-base64#
read the PEM Ed25519 public key a workload registers and check the proofs it signs. Started by skarbiec grant issue.
What failed: reading the Ed25519 public key of {what}. Why: the text between its PEM lines is not base64. What the refusal shows: {length} characters between the lines; the decoder said: {said}; the key was not used.
Fix: make the workload key with openssl genpkey -algorithm ED25519 and give its PEM public key (openssl pkey -pubout).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_workload_key_that_is_not_base64_is_refused_naming_it.
skarbiec.workload-key sealing-workload-key-unfit#
read the PEM Ed25519 public key a workload registers and check the proofs it signs. Started by skarbiec grant issue.
What failed: reading the Ed25519 public key of {what}. Why: it is not an Ed25519 public key (RFC 8410 id-Ed25519, 44 bytes of DER); this one is {bytes} bytes. What the refusal shows: the key was not used.
Fix: make the workload key with openssl genpkey -algorithm ED25519 and give its PEM public key (openssl pkey -pubout).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/sealing.sh::a_workload_key_that_is_not_ed25519_is_refused_naming_it.
skarbiec.datakey datakey-kind#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: using {id} to {doing}. Why: it is {kind}, and {doing} takes a data-key item whose purpose is {purpose}. What the refusal shows: {id} was not used.
Fix: name a data key made for it: skarbiec datakey new <id> --purpose {purpose}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::an_item_of_another_kind_or_purpose_is_refused_naming_both.
skarbiec.datakey datakey-key-unreadable#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: reading the key of {id} at revision {revision}. Why: {why}, so it is no 32-byte key. What the refusal shows: {id} was not used.
Fix: make it again: skarbiec datakey rotate {id} writes a fresh key as a new revision.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::a_key_that_is_not_32_bytes_is_refused.
skarbiec.datakey datakey-envelope-malformed#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: reading the envelope given to {doing} with {id}. Why: {why}, so it is no skarbiec.data-key.v1 envelope. What the refusal shows: standard input: {length} bytes; nothing was opened.
Fix: send the one line skarbiec datakey encrypt wrote, unchanged, on standard input.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::input_that_is_no_envelope_is_refused_naming_why.
skarbiec.datakey datakey-envelope-other-item#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: opening an envelope with {id}. Why: the envelope was sealed with {sealed_by}, not {id}. What the refusal shows: nothing was opened.
Fix: open it with the key that sealed it: skarbiec datakey decrypt {sealed_by}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::an_envelope_of_another_key_is_refused_naming_it.
skarbiec.datakey datakey-version-retired#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: opening an envelope sealed with {id} at revision {revision}. Why: {id} keeps that revision no longer: its saved versions were purged. What the refusal shows: kept revisions: {kept}; nothing was opened.
Fix: an envelope outlives its key only until purge --versions-before removes the version; rewrap envelopes before purging: skarbiec datakey rewrap {id}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::an_envelope_of_a_purged_revision_is_refused_naming_the_kept_ones.
skarbiec.datakey datakey-open-failed#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: opening an envelope sealed with {id} at revision {revision}. Why: its tag does not match: the context given differs from the one it was sealed under, or the envelope changed after sealing. What the refusal shows: context given: {context_bytes} bytes; nothing was opened.
Fix: give the --context it was sealed with; an envelope changed after sealing does not open with any.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::another_context_or_a_changed_envelope_does_not_open.
skarbiec.datakey datakey-signature-malformed#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: reading the signature given to verify with {id}. Why: {why}, so it is no Ed25519 signature. What the refusal shows: --signature: {length} characters; nothing was verified.
Fix: give the base64 text skarbiec datakey sign wrote: skarbiec datakey verify {id} --signature <base64> < message.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::a_signature_that_is_not_64_bytes_is_refused.
skarbiec.datakey datakey-signature-mismatch#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: verifying a signature with {id} at revision {revision}. Why: the signature is not the key's over this message: the message differs from the one signed, or another key signed it. What the refusal shows: message: {length} bytes; the signature was not accepted.
Fix: verify the exact bytes that were signed; a signature made before skarbiec datakey rotate {id} verifies only with the public key sign answered then.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/keys/data_key.sh::a_changed_message_does_not_verify.
skarbiec.datakey datakey-input-not-base64#
make a key Skarbiec keeps and never hands out, seal and open text with it, sign and verify with it, and give it a new revision that older envelopes still open with; every use is in the audit journal without the text, the key or a signature. Started by skarbiec datakey new, skarbiec datakey encrypt, skarbiec datakey decrypt, skarbiec datakey sign, skarbiec datakey verify, skarbiec datakey rotate, skarbiec datakey rewrap, POST /v1/keys/encrypt, POST /v1/keys/decrypt, POST /v1/keys/rewrap, POST /v1/keys/sign, POST /v1/keys/verify.
What failed: reading the input {route} was sent for {id}. Why: its `base64` member is not base64. What the refusal shows: `base64`: {length} characters; the decoder said: {error}; nothing was sealed, opened, signed or verified.
Fix: send the bytes as standard base64 in `base64`, or UTF-8 text as `text`.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/operators/consumer_keys.sh::input_that_is_not_base64_is_answered_400.
skarbiec.serve serve-port-held#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: listening on {address}. Why: another process already listens on {address}. What the refusal shows: the system said: {said}; nothing was started and the journal records no serve.
Fix: stop what holds {address} (lsof -nP -iTCP:{port} names it), or start serve on the port its unit declares.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/refusals.sh::serve_on_a_port_another_process_holds_is_refused_naming_it.
skarbiec.serve serve-port-denied#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: listening on {address}. Why: this account may not listen on port {port}: the system keeps ports below 1024 for root. What the refusal shows: the system said: {said}; nothing was started and the journal records no serve.
Fix: start serve on the port its unit declares, one from 1024 to 65535 (skarbiec serve --port <port>).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/refusals.sh::serve_on_a_privileged_port_is_refused_naming_it.
skarbiec.serve serve-port-unbound#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: listening on {address}. Why: the system refused to {step} the loopback socket with errno {errno}, which is neither a held port nor a port kept for root. What the refusal shows: the system said: {said}; nothing was started and the journal records no serve.
Fix: ifconfig lo0 says whether the loopback interface is up; start serve again once it is (launchd does so on its own).
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/refusals.sh::serve_on_a_loopback_the_system_will_not_bind_is_refused.
skarbiec.serve serve-accept-descriptors#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: accepting a connection on {address}. Why: the {scope} open-file limit is used up (errno {errno}), so the next connection cannot get a descriptor. What the refusal shows: the system said: {said}; serve ends, so launchd starts it again with a fresh listener.
Fix: raise the open-file limit serve runs under (ulimit -n, or the unit's SoftResourceLimits); lsof -nP -p <pid> lists what the process holds.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_listener_out_of_descriptors_ends_serve_naming_the_accept.
skarbiec.serve serve-accept-failed#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: accepting a connection on {address}. Why: the system failed accept with errno {errno}, which is no error of one connection and no exhausted descriptor limit, so the listener itself is broken. What the refusal shows: the system said: {said}; serve ends, so launchd starts it again with a fresh listener.
Fix: start serve again (launchd does so on its own); lsof -nP -p <pid> lists what the process holds.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_listener_the_system_breaks_ends_serve_naming_the_accept.
skarbiec.serve serve-broker-path-not-socket#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: opening the capability socket {socket}. Why: {socket} is there and is not a socket, and serve never removes a file it did not make. What the refusal shows: it is {kind}; the capability broker was not started.
Fix: move what is at {socket} aside, or name another path with --socket.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/refusals.sh::a_broker_path_that_is_not_a_socket_is_refused_naming_it.
skarbiec.serve serve-broker-socket-served#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: opening the capability socket {socket}. Why: another process already answers on {socket}. What the refusal shows: the capability broker was not started; the one answering keeps serving.
Fix: stop the serve that answers on {socket} (lsof {socket} names it), or name another path with --socket.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/refusals.sh::a_broker_socket_another_serve_answers_is_refused.
skarbiec.serve serve-broker-path-long#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: opening the capability socket {socket}. Why: the path is {length} bytes, and a Unix socket's address holds a path of at most {most} bytes. What the refusal shows: nothing was checked, bound or started.
Fix: name a shorter path with --socket (or SKARBIEC_CAP_SOCKET), e.g. one under ~/.stado.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/serve/refusals.sh::a_broker_socket_path_longer_than_a_socket_holds_is_refused.
skarbiec.serve serve-image-unnamed#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: finding the executable this declared Skarbiec unit runs. Why: the system did not say which file this process was started from. What the refusal shows: the system said: {said}; nothing was started: serving without watching the image would keep an old release running after an install.
Fix: start the unit from an installed skarbiec this account can read (stado service ensure skarbiec reloads it).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_declared_unit_whose_image_cannot_be_read_is_refused.
skarbiec.serve serve-image-replaced#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: serving from {path}. Why: an install replaced {path} with another file, and this process still runs the old one. What the refusal shows: serve ends, and the journal records serve-replaced.
Fix: nothing to do: launchd starts the installed release; stado service status skarbiec says it runs.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::an_install_over_the_running_image_ends_serve.
skarbiec.serve serve-component-unstarted#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: starting the Skarbiec {component} component. Why: the system refused this process another thread (errno {errno}). What the refusal shows: the system said: {said}; serve ends before it answers anything.
Fix: start serve again once the host has threads to spare; launchd does so on its own.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_component_the_system_gives_no_thread_ends_serve.
skarbiec.serve serve-component-returned#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: running the Skarbiec {component} component. Why: it returned as if finished, which a component never does while serve runs. What the refusal shows: it answered: {report}; serve ends with it, so no listener is left answering for a process that lost a part.
Fix: read the serve log for what the component did last; launchd starts serve again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_component_that_returns_ends_serve_naming_it.
skarbiec.serve serve-component-panicked#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: running the Skarbiec {component} component. Why: it panicked, a defect of this build. What the refusal shows: the panic said: {said}; serve ends with it, so no listener is left answering for a process that lost a part.
Fix: read the serve log for what the component did last and report it with skarbiec version; launchd starts serve again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_component_that_panics_ends_serve_naming_it.
skarbiec.serve serve-listener-ended#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: running the Skarbiec http component on {address}. Why: its listener stopped handing over connections, which an open listening socket never does. What the refusal shows: serve ends with it, so no listener is left answering for a process that lost a part.
Fix: read the serve log for what the component did last; launchd starts serve again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_listener_that_stops_handing_over_connections_ends_serve.
skarbiec.serve serve-components-lost#
run the host's one Skarbiec process: the loopback HTTP API on its declared port, the capability socket, or both. Started by skarbiec serve.
What failed: waiting for a Skarbiec component to end. Why: every component's channel closed without one saying how it ended. What the refusal shows: serve ends.
Fix: read the serve log for the component that ended; launchd starts serve again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::components_that_all_vanish_end_serve.
skarbiec.serve-client serve-client-address-invalid#
send one request to another Skarbiec's loopback serve and read its status line and JSON body. Started by other functionalities only.
What failed: sending {method} {path} to the serve {base}. Why: {base} is not the http://host:port with no path a serve listens on. What the refusal shows: address: {base}; nothing was sent.
Fix: name the serve as http://<host>:<port>, the address skarbiec serve prints when it starts.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/client.sh::a_serve_address_with_a_path_is_refused_naming_it.
skarbiec.serve-client serve-client-unanswered#
send one request to another Skarbiec's loopback serve and read its status line and JSON body. Started by other functionalities only.
What failed: sending {method} {path} to the serve {authority}. Why: nothing at {authority} took the request and answered it: no serve listens there, or it closed the connection. What the refusal shows: the system said: {error}.
Fix: run the same command again once skarbiec serve answers at {authority}: start it there, or name the address it listens on.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/bonds/pull.sh::a_pull_from_a_serve_that_does_not_answer_is_refused_naming_it.
skarbiec.serve-client serve-client-reply-malformed#
send one request to another Skarbiec's loopback serve and read its status line and JSON body. Started by other functionalities only.
What failed: reading the answer to {method} {path} from {authority}. Why: what answered at {authority} is not a Skarbiec serve: its reply is {found}, where a serve answers an HTTP status line, headers and a JSON body. What the refusal shows: reply begins: {start}.
Fix: name the address a skarbiec serve listens on; another program answers at {authority}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/client.sh::a_listener_that_is_not_a_serve_is_refused_naming_its_reply.
skarbiec.signing signing-not-a-key#
point git's commit and tag signing at an SSH key the vault keeps, say what git signs with, and take those settings away. Started by skarbiec signing, POST /v1/operator/git-sign/setup, POST /v1/operator/git-sign/status, POST /v1/operator/git-sign/unset.
What failed: signing with {id}. Why: {why}. What the refusal shows: git's settings were not touched.
Fix: name a key-pair item that keeps an SSH public key; skarbiec ssh new <id> makes one, and skarbiec rotate {id} --with ssh gives a key pair a new one.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/signing/refusals.sh::signing_with_an_item_that_keeps_no_ssh_key_is_refused_naming_it.
skarbiec.signing signing-git-refused#
point git's commit and tag signing at an SSH key the vault keeps, say what git signs with, and take those settings away. Started by skarbiec signing, POST /v1/operator/git-sign/setup, POST /v1/operator/git-sign/status, POST /v1/operator/git-sign/unset.
What failed: {doing} in {scope}. Why: git config refused: {said}. What the refusal shows: settings written before this one stay as git wrote them.
Fix: name with --repo a folder inside a git repository, or let this account write the global git configuration, then run the same command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/signing/refusals.sh::a_git_configuration_that_refuses_the_setting_is_refused_naming_it.
skarbiec.signing signing-setting-not-ssh#
point git's commit and tag signing at an SSH key the vault keeps, say what git signs with, and take those settings away. Started by skarbiec signing, POST /v1/operator/git-sign/setup, POST /v1/operator/git-sign/status, POST /v1/operator/git-sign/unset.
What failed: reading the key {scope} signs with. Why: user.signingkey is {value}, which is not an SSH public key. What the refusal shows: git's settings were not touched.
Fix: set it with skarbiec signing setup <id>, or remove it with git config --unset user.signingkey.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/signing/refusals.sh::a_signing_key_that_is_not_an_ssh_key_is_refused_naming_it.
skarbiec.signing signing-nothing-set#
point git's commit and tag signing at an SSH key the vault keeps, say what git signs with, and take those settings away. Started by skarbiec signing, POST /v1/operator/git-sign/setup, POST /v1/operator/git-sign/status, POST /v1/operator/git-sign/unset.
What failed: unsetting the signing settings of {scope}. Why: {scope} signs with no key signing setup set. What the refusal shows: nothing was changed.
Fix: nothing to undo here; skarbiec signing status names what git signs with.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/signing/refusals.sh::unset_with_nothing_set_is_refused.
skarbiec.signing signing-key-not-kept#
point git's commit and tag signing at an SSH key the vault keeps, say what git signs with, and take those settings away. Started by skarbiec signing, POST /v1/operator/git-sign/setup, POST /v1/operator/git-sign/status, POST /v1/operator/git-sign/unset.
What failed: unsetting the signing settings of {scope}. Why: {scope} signs with {key}, a key no item in this vault keeps, so it was set by someone else. What the refusal shows: it is left alone.
Fix: remove it with git config --unset user.signingkey if it is not wanted.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/signing/refusals.sh::unset_of_a_key_no_item_keeps_leaves_it_alone.
skarbiec.sources sources-adapter-unknown#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: finding the import adapter {adapter}. Why: {adapter} is not an adapter of this Skarbiec. What the refusal shows: adapters: {known}.
Fix: name one of them; skarbiec sources --all lists every adapter with its source.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/sources/sources.sh::an_unknown_adapter_is_refused_naming_the_adapters.
skarbiec.sources sources-not-found#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: reading {source} for {adapter}. Why: {source} is not on this machine where {adapter} looks for it. What the refusal shows: looked in: {places}.
Fix: name where it is with --path <file or directory>, or export it from {source} first.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::a_source_not_on_the_machine_is_refused_naming_where_it_looked.
skarbiec.sources sources-path-needed#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: reading {source} for {adapter}. Why: {adapter} reads an export file a person makes in {source}, and no --path names it. What the refusal shows: no --path.
Fix: export from {source} and run it again with --path <the exported file>.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/sources/sources.sh::an_export_adapter_without_a_path_is_refused_naming_the_source.
skarbiec.sources sources-format-version-unknown#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: reading {path} for {adapter}. Why: {path} is {format} version {version}, and this adapter reads {known}. What the refusal shows: {format} version {version}; nothing was stored.
Fix: export again from a version of {source} that writes {known}, or report the new version so the adapter learns it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::an_unknown_format_version_is_refused_naming_it.
skarbiec.sources sources-format-unreadable#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: reading {path} for {adapter}. Why: {path} is not readable as {format}: {why}. What the refusal shows: {why}; nothing was stored.
Fix: name the file {source} exported, unchanged.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::a_file_that_is_not_the_format_is_refused_naming_the_problem.
skarbiec.sources sources-release-before-import#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: releasing {source} for {adapter}. Why: the journal records no import of {adapter}, so the values {source} keeps are the only copy. What the refusal shows: no sources-imported entry for {adapter}.
Fix: run skarbiec sources import {adapter} --yes first.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::a_release_before_any_import_is_refused.
skarbiec.sources sources-release-unsupported#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: releasing {source} for {adapter}. Why: {source} is {why}, so Skarbiec does not change it. What the refusal shows: {adapter} has no release.
Fix: {remedy}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::a_release_of_an_adapter_without_one_is_refused_naming_why.
skarbiec.sources sources-import-unknown#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: forgetting import {import} of {adapter}. Why: the journal records no import {import} of {adapter}. What the refusal shows: imports of {adapter}: {known}.
Fix: name one of them, or leave out --import to forget every import of {adapter}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::forgetting_an_unknown_import_is_refused_naming_the_imports.
skarbiec.sources sources-discovery-only#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: importing {adapter}. Why: {source} {why}, so this adapter names what is there and imports nothing. What the refusal shows: {adapter} discovers only.
Fix: {remedy}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::a_discovery_only_adapter_refuses_import_naming_what_to_do.
skarbiec.sources sources-service-unreadable#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: reading {source} for {adapter}. Why: {program}, the command line {adapter} reads {source} through, answered no values. What the refusal shows: {program} said: {said}.
Fix: install {program} and sign it in to {source} (or name the scope with --from), then run discover again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/sources/sources.sh::a_service_whose_command_line_fails_is_refused_naming_it.
skarbiec.sources sources-pulled-unremoved#
find every source on this machine that keeps a secret outside the vault, preview and import it as items, release the source once the vault keeps the value, and forget an import. Started by skarbiec sources, skarbiec sources discover, skarbiec sources preview, skarbiec sources import, skarbiec sources release, skarbiec sources forget, skarbiec sources log, skarbiec sources share, POST /v1/operator/sources.
What failed: reading {source} for {adapter}. Why: {program} writes every value to {file} for Skarbiec to read, and the file could not be removed after. What the refusal shows: {why}; {file} still holds the values in plain text, and none was imported.
Fix: remove {file} (rm {file}), make its directory writable by this user, then run the import again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/sources/sources.sh::a_pulled_file_that_cannot_be_removed_is_refused_naming_it.
skarbiec.ssh ssh-item-exists#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: making the key-pair item {id}. Why: {id} already exists, and ssh {verb} creates an item and never replaces one. What the refusal shows: nothing was written.
Fix: name a new id, or replace {id}'s key with skarbiec rotate {id} --with ssh.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/refusals.sh::a_key_pair_id_that_exists_is_refused_naming_rotate.
skarbiec.ssh ssh-keygen-refused#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: {doing}. Why: ssh-keygen refused it and ended with {status}. What the refusal shows: command: {command}, in {directory}; ssh-keygen said: {said}; nothing was written.
Fix: {fix}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/refusals.sh::a_key_ssh_keygen_cannot_read_is_refused_in_its_words.
skarbiec.ssh ssh-no-private-key#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: {doing}. Why: {id} holds no private_key text, so there is no key to use. What the refusal shows: nothing was changed.
Fix: name a key-pair item; skarbiec list --kind key-pair lists them.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/refusals.sh::an_item_that_holds_no_private_key_is_refused_naming_it.
skarbiec.ssh ssh-no-agent#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: loading {id} into an ssh-agent. Why: neither --agent nor SSH_AUTH_SOCK names an ssh-agent socket, so there is no agent to hand the key to. What the refusal shows: the key was not read.
Fix: start one with eval $(ssh-agent), or name the session's socket with --agent <socket>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/refusals.sh::ssh_add_with_no_agent_is_refused_naming_both_ways_to_name_one.
skarbiec.ssh ssh-agent-refused#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: loading {id} into the ssh-agent at {socket}. Why: ssh-add refused the key and ended with {status}, so the agent did not take it. What the refusal shows: command: {command}, the key on its standard input; ssh-add said: {said}; the agent does not hold the key.
Fix: name the socket of a running agent with --agent, or start one with eval $(ssh-agent); ssh-add -l with SSH_AUTH_SOCK={socket} says whether it answers.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/refusals.sh::an_agent_that_refuses_the_key_is_refused_in_ssh_adds_words.
skarbiec.ssh ssh-add-unstarted#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: loading {id} into the ssh-agent at {socket}. Why: ssh-add could not be started (errno {errno}): none is on PATH, or the file found there is not a program this account may run. What the refusal shows: command: {command}; PATH: {path}; the system said: {said}; the key was not read out.
Fix: install OpenSSH's ssh-add and put it on PATH; command -v ssh-add names the one that runs.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/refusals.sh::ssh_add_without_ssh_add_on_path_is_refused_naming_it.
skarbiec.ssh ssh-add-unfed#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: loading {id} into the ssh-agent at {socket}. Why: the key could not be {step} ssh-add (errno {errno}): it ended before reading its standard input. What the refusal shows: command: {command}; the system said: {said}; the agent does not hold the key.
Fix: run the same command again; ssh-add -l with SSH_AUTH_SOCK={socket} says whether the agent answers.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/ssh/refusals.sh::an_ssh_add_that_ends_before_reading_the_key_is_refused.
skarbiec.ssh ssh-add-unwaited#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: loading {id} into the ssh-agent at {socket}. Why: waiting for ssh-add to end failed (errno {errno}), so whether the agent took the key is not known. What the refusal shows: command: {command}; the system said: {said}.
Fix: ssh-add -l with SSH_AUTH_SOCK={socket} lists what the agent holds; run the same command again if the key is not there.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/ssh/refusals.sh::an_ssh_add_that_cannot_be_waited_for_is_refused.
skarbiec.ssh ssh-tag-unmatched#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: loading the keys tagged {tag} into an ssh-agent. Why: no live item carries the tag {tag}. What the refusal shows: no key was added.
Fix: name a tag skarbiec tags lists, or tag the keys with skarbiec retag --add {tag} <id>.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/refusals.sh::ssh_add_tag_with_no_tagged_item_is_refused_naming_the_tag.
skarbiec.ssh ssh-workdir-unreadable#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: finding {file} in the working directory. Why: {file} is a relative path, and this process's working directory cannot be read: it was removed, or a directory on its way may not be searched. What the refusal shows: the system said: {said}; nothing was written.
Fix: run it from a directory that exists, or name the key file by its absolute path.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/files.sh::an_import_from_a_removed_working_directory_is_refused.
skarbiec.ssh ssh-keygen-absent#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: {doing}. Why: no ssh-keygen is in any directory of PATH, so the key cannot be made or read. What the refusal shows: command: {command}; PATH: {path}; the system said: {said}; nothing was written.
Fix: install OpenSSH's ssh-keygen and put it on PATH; ssh -V names the OpenSSH installed.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/files.sh::ssh_new_without_ssh_keygen_on_path_is_refused_naming_it.
skarbiec.ssh ssh-keygen-unstarted#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: {doing}. Why: an ssh-keygen was found on PATH but could not be started (errno {errno}): it is not a program this account may run. What the refusal shows: command: {command}; PATH: {path}; the system said: {said}; nothing was written.
Fix: command -v ssh-keygen names the file that was found; make it executable (chmod +x) or put OpenSSH's ssh-keygen before it on PATH.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/files.sh::ssh_new_with_an_ssh_keygen_that_cannot_run_is_refused_naming_it.
skarbiec.ssh ssh-keygen-output-missing#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: reading the {what} ssh-keygen wrote for {doing}. Why: ssh-keygen ended with status 0 but wrote no {what} at {file}, where every OpenSSH ssh-keygen writes it. What the refusal shows: command: {command}; nothing was written, and the workspace was removed.
Fix: run ssh-keygen -t ed25519 by hand to see what it writes; command -v ssh-keygen names the one on PATH, which writes something other than a key file and its .pub.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/files.sh::an_ssh_keygen_that_writes_no_key_is_refused_naming_it.
skarbiec.ssh ssh-import-readback-differs#
make an SSH key whose private half lives only in the vault, bring one in from a file, load one into an ssh-agent through a pipe, and sign a public key with an authority the vault keeps. Started by skarbiec ssh new, skarbiec ssh import, skarbiec ssh add, skarbiec ssh sign, POST /v1/operator/items/new-ssh-key, POST /v1/operator/items/ssh-import, POST /v1/operator/items/ssh-add, POST /v1/operator/ssh-sign.
What failed: checking {id} holds the key from {file}. Why: {id} was written but reads back another private key. What the refusal shows: vault: {vault}; the file is left in place.
Fix: read {id} with skarbiec history {id} to see which write took its place, and import {file} again under another id.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/files.sh::an_import_overtaken_before_it_reads_back_is_refused.
skarbiec.rotate.ssh ssh-rotate-not-key-pair#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: rotating the SSH key of {id}. Why: {id} is a {kind} item, and rotate --with ssh replaces the SSH key a key-pair item holds. What the refusal shows: nothing was changed.
Fix: name a key-pair item; skarbiec list --kind key-pair lists them.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::rotating_an_item_that_is_not_a_key_pair_is_refused_naming_its_kind.
skarbiec.rotate.ssh ssh-rotate-no-public-key#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: finding the key {id} holds at {places}. Why: {id} holds no public_key, so its key cannot be found where it is trusted. What the refusal shows: nothing was changed.
Fix: write {id}'s public key with skarbiec field set {id} public_key, or rotate it without --github, --gitlab and the account flags.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::rotating_onto_a_forge_an_item_without_a_public_key_is_refused.
skarbiec.rotate.ssh ssh-rotate-public-key-not-ssh#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: finding the key {id} holds at {places}. Why: {id}'s public_key is not an SSH public key line (<type> <base64> [comment]). What the refusal shows: nothing was changed.
Fix: write {id}'s public key as the line ssh-keygen -y -f <private-key-file> prints, with skarbiec field set {id} public_key.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::rotating_onto_a_forge_a_public_key_that_is_no_ssh_line_is_refused.
skarbiec.rotate.ssh ssh-rotate-host-refused#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: reaching {host} with ssh to {step}. Why: {error}. What the refusal shows: the vault keeps the old key; the new key is taken back off every place it reached, and any place it is left on is named above.
Fix: log in to {host} with ssh -o BatchMode=yes and the key being rotated (skarbiec ssh add <id> loads it) to see what it refuses: an unknown host key, an account that does not take the key, or a host that is down.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::a_host_that_refuses_the_key_is_refused_naming_it.
skarbiec.rotate.ssh ssh-rotate-forge-refused#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: carrying the new key to {place} with {program} api {request}. Why: {program} refused ({status}): {said}. What the refusal shows: the vault keeps the old key; the new key is taken back off every place it reached, and any place it is left on is named above.
Fix: sign {program} in to an account that may change those keys ({program} auth status shows which one it is), then rotate again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::a_forge_that_refuses_the_request_is_refused_in_its_words.
skarbiec.rotate.ssh ssh-rotate-forge-not-json#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: carrying the new key to {place} with {program} api {request}. Why: {program} answered something that is not JSON: {error}. What the refusal shows: the vault keeps the old key; the new key is taken back off every place it reached, and any place it is left on is named above.
Fix: run {program} api {request} by hand to see what it answers, and update {program} to a release that answers the forge's JSON.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::a_forge_cli_answering_no_json_is_refused_naming_it.
skarbiec.rotate.ssh ssh-rotate-forge-key-unmatched#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: finding the key {id} holds at {place}. Why: {place} hold no key matching {id}'s public key, so there is nothing there to rotate. What the refusal shows: the vault keeps the old key; the new key is taken back off every place it reached, and any place it is left on is named above.
Fix: add {id}'s public key there first, or leave that place out of the rotation.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::a_forge_place_without_the_items_key_is_refused_naming_it.
skarbiec.rotate.ssh ssh-rotate-forge-key-incomplete#
replace a key-pair item's SSH key with a fresh Ed25519 pair, carrying the new public key first to every host's authorized_keys and every forge place named, and taking it back off them when one refuses. Started by skarbiec rotate --with ssh.
What failed: copying the key {id} holds at {place}. Why: the forge lists it without {member}, which the new key has to carry as the old one did. What the refusal shows: the vault keeps the old key; the new key is taken back off every place it reached, and any place it is left on is named above.
Fix: look at the key there ({program} api {request}), and rotate it by hand on the forge when it lists keys of another shape.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/ssh/rotate.sh::a_forge_key_missing_what_the_new_key_carries_is_refused_naming_it.
skarbiec.stado-config stado-config-stado-named-absent#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: asking Stado which vault this machine uses ({asked}). Why: STADO_BIN names {program}, and no program is there, so Stado's declaration cannot be asked and no vault is chosen without it. What the refusal shows: STADO_BIN: {program}; nothing was read or written.
Fix: point STADO_BIN at the installed stado (command -v stado names it), or unset it to ask the stado on PATH.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/stado_routing.sh::a_stado_bin_naming_no_program_is_refused_naming_it.
skarbiec.stado-config stado-config-stado-unrunnable#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: asking Stado which vault this machine uses ({asked}). Why: {program} is there but the system would not start it ({kind}), so Stado's declaration cannot be asked and no vault is chosen without it. What the refusal shows: starting {program}: {error}; nothing was read or written.
Fix: make {program} an executable Stado ({program} --version answers when it is), point STADO_BIN at one, or name a vault with SKARBIEC_VAULT_FILE for one command.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/stado_routing.sh::a_stado_that_cannot_be_started_is_refused_naming_it.
skarbiec.stado-config stado-config-stado-refused#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: asking Stado which vault this machine uses ({asked}). Why: Stado refused to resolve its own configuration on this machine, so whether this machine holds the vault or reads the owner's cannot be told. What the refusal shows: {program} exited {status}, naming its cause {stado_cause}: {said}; nothing was read or written.
Fix: repair what Stado names ({program} config validate names every setting it refuses, and the stado errors show its cause line names says how), or name a vault with SKARBIEC_VAULT_FILE for one command.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/status.sh::a_stado_config_that_does_not_read_is_refused_naming_it.
skarbiec.stado-config stado-config-answer-not-json#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading Stado's answer to {asked}. Why: {program} answered text that is not JSON, so it is a Stado older than the one --json was added to, or another program under that name. What the refusal shows: the JSON reader stopped at line {line}, column {column} ({said}); the answer begins: {start}.
Fix: upgrade Stado on this machine (stado product update stado), or point STADO_BIN at the installed stado.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/stado_routing.sh::a_stado_answering_no_json_is_refused_naming_its_answer.
skarbiec.stado-config stado-config-answer-shape#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading Stado's answer to {asked}. Why: {program}'s answer holds {key} as {held}, where a Stado that declares Skarbiec's routing answers text, so it is a Stado older than skarbiec_vault_file and skarbiec_url. What the refusal shows: {key}: {held}.
Fix: upgrade Stado on this machine (stado product update stado); {program} config show --json shows what it answers.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/stado_routing.sh::a_stado_answering_no_routing_keys_is_refused_naming_the_key.
skarbiec.stado-config stado-config-owner-route-unresolved#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the vault owner route Stado declares for this machine ({file}). Why: Stado declares a vault owner route ({declared}) it cannot resolve to an address, and declares no vault file here, so this machine reads no vault: a local one would be a copy the owner never sees. What the refusal shows: Stado names the absence {kind} and says: {why}; nothing was read or written.
Fix: correct the route as Stado's reason names ({program} config show lists skarbiec_url and where it was declared; {program} resolver status names the adapters this host serves), or declare this machine's vault with {program} config set secrets.skarbiec.vault_file <path>.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_route.sh::a_service_route_naming_no_consumer_is_refused_naming_it.
skarbiec.stado-config stado-config-owner-route-malformed#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the vault owner route Stado declares for this machine ({file}). Why: Stado's configuration holds secrets.skarbiec.url, or a section above it, in another shape than text, so whether this machine holds the vault or reads the owner's cannot be told, and no vault is opened on a guess. What the refusal shows: Stado names the absence {kind}, declared {declared}, and says: {why}; nothing was read or written.
Fix: write the owner's address as text ({program} config set secrets.skarbiec.url <address>), or remove it ({program} config unset secrets.skarbiec.url); {program} config validate names every setting it refuses.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_route.sh::a_route_of_another_shape_is_refused_naming_it.
skarbiec.stado-config stado-config-owner-route-marker-unreadable#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the vault owner route Stado declares for this machine ({file}). Why: the forward marker Stado reads the owner route from is there but cannot be read or names no address, so whether this machine reads the owner's vault cannot be told, and no vault is opened on a guess. What the refusal shows: Stado names the absence {kind}, declared {declared}, and says: {why}; nothing was read or written.
Fix: write the marker again from the directory ({program} service directory publish), or remove the marker Stado names if this machine holds its own vault.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_route.sh::an_unreadable_forward_marker_is_refused_naming_it.
skarbiec.stado-config stado-config-owner-route-variable-unreadable#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the vault owner route Stado declares for this machine ({file}). Why: WC_SKARBIEC_URL is set to a value that is not text, so the owner route it declares cannot be read, and no vault is opened on a guess. What the refusal shows: Stado names the absence {kind}, declared {declared}, and says: {why}; nothing was read or written.
Fix: set WC_SKARBIEC_URL to the owner's address as UTF-8 text, or unset it to use the route Stado's configuration declares ({program} config show lists skarbiec_url).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_route.sh::a_route_variable_that_is_not_text_is_refused_naming_it.
skarbiec.stado-config stado-config-owner-route-configuration-unreadable#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the vault owner route Stado declares for this machine ({file}). Why: Stado cannot read its configuration file, so whether it declares an owner route for this machine cannot be told, and no vault is opened on a guess. What the refusal shows: Stado names the absence {kind}, declared {declared}, and says: {why}; nothing was read or written.
Fix: make {file} readable by this account as Stado's reason names ({program} config validate reads it the same way), or point STADO_CONFIG at a readable one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_route.sh::an_unreadable_stado_configuration_is_refused_naming_it.
skarbiec.stado-config stado-config-owner-route-absence-unknown#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the vault owner route Stado declares for this machine ({file}). Why: Stado says no owner route resolves for a reason ({kind}) this Skarbiec does not know, where it knows undeclared, malformed, unresolved, marker-unreadable, variable-unreadable and configuration-unreadable, so whether nothing declares a route cannot be told, and no vault is opened on a guess. What the refusal shows: Stado names the absence {kind}, declared {declared}, and says: {why}; nothing was read or written.
Fix: update Skarbiec to one that knows Stado's reason (stado product update skarbiec), or name this machine's vault with SKARBIEC_VAULT_FILE for one command.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/owner_route.sh::an_absence_kind_this_skarbiec_does_not_know_is_refused_naming_it.
skarbiec.stado-config stado-config-absence-untold#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the vault owner route Stado declares for this machine ({file}). Why: Stado resolves neither a vault file nor an owner route here and answers no skarbiec_url_absent_kind, only a sentence, so whether nothing declares a route or a declared route does not resolve cannot be told, and a vault opened here could be a copy of the fleet vault. What the refusal shows: {program} ({version}) says in skarbiec_url_absent: {why}; nothing was read or written.
Fix: update Stado to one that answers skarbiec_url_absent_kind (stado product update stado), declare this machine's vault ({program} config set secrets.skarbiec.vault_file <path>), or name it with SKARBIEC_VAULT_FILE for one command.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/absence_untold.sh::a_stado_answering_no_absence_kind_is_refused_quoting_it.
skarbiec.stado-config stado-config-path-not-absolute#
ask Stado (stado config show --json) whether it declares this machine's vault file or routes it to the vault owner. Started by other functionalities only.
What failed: reading the path Stado resolves as {key} ({file}). Why: {program} answers {key} as {held}, which is no absolute path: Stado expands a leading home form and passes any other text through as written (an older Stado expands ~/ and $HOME/ but not HOME written in braces after the dollar sign), so opening it would name a file relative to wherever this command runs, not the one other readers of the same declaration open. What the refusal shows: {key}: {held}; nothing was read or written.
Fix: declare it in Stado as an absolute path, or one starting with ~/ or $HOME/, which every Stado expands; {program} config show --json shows what it resolves.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/selection/stado_routing.sh::a_declared_path_stado_leaves_relative_is_refused_naming_the_key.
skarbiec.stado-resolver stado-resolver-state-absent#
read where this host's Stado resolver publishes its API, and ask it the loopback adapter a service answers at for one consumer. Started by other functionalities only.
What failed: asking this host's Stado resolver where {service} answers for {consumer}. Why: no Stado resolver has published its state at {path}, so no service route can be asked for on this host: the resolver is not running here. What the refusal shows: state file: {path} (STADO_RESOLVER_STATE_FILE names another).
Fix: start Stado's resolver here (it runs in stado serve); stado resolver status says whether it runs and why not.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/net/stado_resolver.sh::a_host_whose_resolver_published_no_state_is_refused_naming_it.
skarbiec.stado-resolver stado-resolver-state-not-json#
read where this host's Stado resolver publishes its API, and ask it the loopback adapter a service answers at for one consumer. Started by other functionalities only.
What failed: asking this host's Stado resolver where {service} answers for {consumer}. Why: the resolver's state {path} is not a JSON document, so where its API answers cannot be read. What the refusal shows: the JSON reader said: {said}.
Fix: stado resolver status says whether the resolver runs; a running resolver writes its state again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/stado_resolver.sh::a_resolver_state_that_is_not_json_is_refused_naming_it.
skarbiec.stado-resolver stado-resolver-state-unbound#
read where this host's Stado resolver publishes its API, and ask it the loopback adapter a service answers at for one consumer. Started by other functionalities only.
What failed: asking this host's Stado resolver where {service} answers for {consumer}. Why: the resolver's state {path} names no api_bind: that resolver (pid {pid}) predates answering routes over its API, or has not bound it yet. What the refusal shows: state file: {path}.
Fix: upgrade Stado on this host and let its serve start the resolver again; stado resolver status says what it binds.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/stado_resolver.sh::a_resolver_state_naming_no_api_bind_is_refused_naming_it.
skarbiec.stado-resolver stado-resolver-reply-not-json#
read where this host's Stado resolver publishes its API, and ask it the loopback adapter a service answers at for one consumer. Started by other functionalities only.
What failed: asking this host's Stado resolver where {service} answers for {consumer}. Why: the resolver at {address} answered {status} with a body that is not JSON, so it is not the resolution API this release reads. What the refusal shows: reply status: {status}.
Fix: stado resolver status names what serves at {address}; upgrade Stado on this host when it is an older resolver.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/stado_resolver.sh::a_resolver_answering_no_json_is_refused_naming_its_status.
skarbiec.stado-resolver stado-resolver-refused#
read where this host's Stado resolver publishes its API, and ask it the loopback adapter a service answers at for one consumer. Started by other functionalities only.
What failed: asking this host's Stado resolver where {service} answers for {consumer}. Why: the resolver refused {service} for the consumer {consumer}: Stado's service directory does not admit that consumer to the service, or the resolver is not serving. What the refusal shows: {status}: {said}.
Fix: stado service directory consumer add {service} {consumer} declares the consumer; stado resolver status names a resolver that is not serving.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/net/stado_resolver.sh::a_consumer_the_directory_does_not_admit_is_refused_naming_it.
skarbiec.stado-resolver stado-resolver-no-adapter#
read where this host's Stado resolver publishes its API, and ask it the loopback adapter a service answers at for one consumer. Started by other functionalities only.
What failed: asking this host's Stado resolver where {service} answers for {consumer}. Why: the resolver admits {consumer} to {service} but listens on no adapter for that pair on this host. What the refusal shows: resolver answer: {answer}.
Fix: stado service directory consumer add {service} {consumer} --target <this host> declares one, and the resolver publishes it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/net/stado_resolver.sh::a_consumer_with_no_adapter_here_is_refused_naming_the_pair.
skarbiec.staged-write stage-item-inactive#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: staging a new {field} for {id}. Why: {id} is {state}, and only an active item takes a staged revision. What the refusal shows: nothing was staged.
Fix: the item is no longer its controller's to change while it is {state}: its owner takes it back (skarbiec reclaim {id}) and restores it (skarbiec restore {id}), the controller adopts it again through its adopt operation, and then the operation starts again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_stage_of_an_item_that_is_not_active_is_refused.
skarbiec.staged-write stage-revision-moved#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: staging a new {field} for {id}. Why: the item is at revision {revision}, and the write was made against revision {expected}. What the refusal shows: nothing was staged.
Fix: read the item again and stage against the revision it holds now.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_stage_against_a_revision_that_moved_since_admission_is_refused.
skarbiec.staged-write stage-other-writer#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: {doing} {id} as {writer}. Why: {id} is managed by {controller} through its writer {holder}, and only that exact writer {does} it. What the refusal shows: management: {management}.
Fix: write through the writer the item records (skarbiec credential status {id} names it), or take the item back with skarbiec reclaim {id}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_stage_by_a_writer_other_than_the_items_is_refused_naming_it.
skarbiec.staged-write stage-other-pending#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: staging a new {field} for {id} under operation {operation}. Why: {id} already holds a revision staged under operation {pending}. What the refusal shows: pending: {pending}.
Fix: activate or discard the staged revision of operation {pending} first (skarbiec credential status {id} names it).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::a_second_operation_staging_over_a_pending_revision_is_refused_naming_it.
skarbiec.staged-write stage-none-pending#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: {doing} the staged revision of {id}. Why: {id} holds no staged revision. What the refusal shows: nothing was changed.
Fix: stage the new value first; skarbiec credential status {id} says what the operation did.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::an_activation_with_nothing_staged_is_refused.
skarbiec.staged-write stage-not-yours#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: {doing} the staged revision of {id}. Why: the staged revision belongs to operation {pending_operation}, field {pending_field} and writer {pending_writer}, not to operation {operation}, field {field} and writer {writer}. What the refusal shows: nothing was changed.
Fix: finish it from the operation that staged it; skarbiec credential status {id} names it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::an_activation_by_another_operation_is_refused_naming_the_staged_one.
skarbiec.staged-write stage-trash-pending#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: trashing the managed item {id}. Why: {id} holds a staged revision, which would be lost with it. What the refusal shows: nothing was changed.
Fix: activate or discard the staged revision first, then trash it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::trashing_an_item_with_a_staged_revision_is_refused.
skarbiec.staged-write stage-trash-inactive#
stage one field's new value of a managed item, then make it current or drop it, only through the exact writer that controls the item. Started by other functionalities only.
What failed: trashing the managed item {id}. Why: {id} is {state}, not active, and a controller trashes only an active item it writes (one it already trashed is that remove settled). What the refusal shows: nothing was changed.
Fix: the item is no longer its controller's to remove while it is {state}: its owner takes it back (skarbiec reclaim {id}) and trashes it (skarbiec delete {id}) when it should go, or restores it (skarbiec restore {id}) for the controller to adopt again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/files/managed_write.sh::trashing_an_item_that_is_not_active_is_refused_naming_its_state.
skarbiec.star star-unplaced#
read, dismiss or reset the GitHub star request Skarbiec makes once after a person's fifth successful set or get on a terminal. Started by skarbiec star.
What failed: finding where the star request is kept. Why: neither XDG_STATE_HOME nor HOME names a directory to keep the star request in, or USER names no person to keep it for. What the refusal shows: XDG_STATE_HOME: {state_home}; HOME: {home}; USER: {user}; the onboarding runtime said: {error}.
Fix: run skarbiec as an account with HOME (or XDG_STATE_HOME) and USER set.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cli/star.sh::a_process_with_no_home_is_refused_naming_the_variables.
skarbiec.star star-state-damaged#
read, dismiss or reset the GitHub star request Skarbiec makes once after a person's fifth successful set or get on a terminal. Started by skarbiec star.
What failed: {doing} the star request kept in {file}. Why: {file} holds what does not read as the star request this release keeps. What the refusal shows: state file: {file}; the onboarding runtime said: {error}.
Fix: skarbiec star reset sets the file aside and counts from zero.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/cli/star.sh::a_state_file_that_does_not_read_as_the_request_names_star_reset.
skarbiec.stdin stdin-unread#
read a value a command takes on standard input, whole and as UTF-8 text. Started by other functionalities only.
What failed: reading {what} from standard input. Why: standard input could not be read to its end, so the value is not known whole: it is a directory, a closed descriptor or a device that fails. What the refusal shows: read before the failure: {read} bytes; the system said: {said}.
Fix: send the value from a file or a pipe that reads to its end, e.g. < value.txt.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/field.sh::a_value_whose_input_cannot_be_read_is_refused_and_nothing_is_written.
skarbiec.stdin stdin-not-text#
read a value a command takes on standard input, whole and as UTF-8 text. Started by other functionalities only.
What failed: reading {what} from standard input. Why: the value stops being UTF-8 text at byte {offset}, and this value is text. What the refusal shows: standard input: {length} bytes.
Fix: give it as UTF-8 text on standard input.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/fields/field.sh::a_value_that_is_not_text_is_refused_and_nothing_is_written.
skarbiec.credential.status record-unreadable#
read where a credential's operation stands, once. Started by skarbiec credential status, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status.
What failed: reading the operation status of role {role}. Why: its operation record {record} exists but cannot be read. What the refusal shows: record: {record}; reading it said: {error}.
Fix: run skarbiec doctor to see why the vault cannot open {record}; a running operation is never reported as settled from a record nobody can read.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/status.sh::an_unreadable_operation_record_is_refused_naming_it.
skarbiec.credential.status role-empty#
read where a credential's operation stands, once. Started by skarbiec credential status, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status.
What failed: reading the operation status of role {role}. Why: no item plays role {role}, no operation is recorded for it and no directory contract is sealed for it. What the refusal shows: items carrying stado:role:{role}: none; record: none; seal: none.
Fix: tag the item holding this credential with `skarbiec retag --add stado:role:{role} <item>`, or start it with `skarbiec credential acquire role:{role}`.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/credential/status.sh::a_role_with_nothing_behind_it_is_refused_naming_both_ways_in.
skarbiec.credential.status wire-unsupported#
read where a credential's operation stands, once. Started by skarbiec credential status, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status.
What failed: reading the operation status of role {role}. Why: its record was written in the credential-operation wire {version}, and this release speaks {expected}. What the refusal shows: record version: {version}.
Fix: let the release that wrote it finish it, or start the operation again with this release.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/status.sh::a_record_from_another_wire_version_is_refused_naming_both.
skarbiec.credential.status record-incomplete#
read where a credential's operation stands, once. Started by skarbiec credential status, GET /v1/credential/operations/<role>, POST /v1/operator/credential, Desktop: Lifecycle → a selected item's status.
What failed: reading the operation status of role {role}. Why: its record names no {what}, so the operation cannot be followed. What the refusal shows: record: {record}.
Fix: start the operation again, which writes a whole record.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/status.sh::a_record_naming_no_provider_is_refused_naming_what_it_lacks.
skarbiec.subscription form-unknown#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading what skarbiec subscription is asked. Why: subscription {given} is not one of its forms. What the refusal shows: usage: {usage}.
Fix: run subscription list, refuse, withdraw or run; skarbiec subscription help lists them.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::an_unknown_subscription_form_is_refused_with_its_usage.
skarbiec.subscription flag-unknown#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading the flags of subscription {verb}. Why: subscription {verb} takes no --{flag}. What the refusal shows: usage: {usage}.
Fix: drop --{flag}; subscription {verb} takes {takes}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_flag_a_form_does_not_take_is_refused_naming_it.
skarbiec.subscription item-argument#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading which subscription subscription {verb} acts on. Why: subscription {verb} names exactly one subscription item, and {count} were given. What the refusal shows: arguments: {given}.
Fix: name one item `skarbiec subscription list` shows: skarbiec subscription {verb} <item-id> ….
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_refusal_naming_no_item_is_refused.
skarbiec.subscription reason-missing#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: recording that the provider refused the grant of {item}. Why: a refusal is recorded with the provider's own words, and --reason gives none. What the refusal shows: --reason: {given}.
Fix: pass the provider's answer: skarbiec subscription refuse {item} --reason '<what the provider said>'.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_refusal_without_its_reason_is_refused.
skarbiec.subscription now-without-item#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: signing one subscription in before it is due. Why: --now signs one subscription in, and --item names none. What the refusal shows: flags given: --now.
Fix: name it: skarbiec subscription run --item <item-id> --now.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::subscription_run_now_without_item_is_refused.
skarbiec.subscription not-subscription#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading the subscription {item}. Why: {item} is not a live subscription in this vault: {why}. What the refusal shows: subscriptions: {subscriptions}.
Fix: name an item `skarbiec subscription list` shows; a subscription is a live item tagged brama:subscription.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::an_item_that_is_no_subscription_is_refused_listing_the_subscriptions.
skarbiec.subscription section-malformed#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading the vault's subscription sign-in records. Why: {why}. What the refusal shows: subscriptions section: {kind}.
Fix: run skarbiec upgrade to see what it can read; withdraw each damaged record with subscription withdraw, which writes it again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_subscriptions_section_that_is_not_an_object_is_refused_naming_its_kind.
skarbiec.subscription no-refusal#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: withdrawing the recorded refusal of {item}. Why: no refusal of {item}'s grant is recorded. What the refusal shows: refused grants: {refused}.
Fix: name an item whose grant `skarbiec subscription list` shows as refused.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::withdrawing_a_refusal_that_is_not_recorded_is_refused.
skarbiec.subscription unsignable#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: signing the subscription {item} in. Why: its grant is {grant} and Weles cannot be asked to sign it in: {blockers}. What the refusal shows: tags of {item}: {tags}.
Fix: tag {item} with exactly one brama:provider:<provider>, brama:id:<subscription id> and brama:login:<login item> (skarbiec retag --add <tag> {item}), naming a login item that exists and opens here, whose recorded second factor the vault can answer (skarbiec login factor list <login item> names what it lacks; skarbiec totp set adds a seed), then run skarbiec subscription run --item {item} --now.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_due_subscription_without_its_login_is_refused_naming_what_it_lacks.
skarbiec.subscription grant-unreadable#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading the stored grant of the subscription {item}. Why: the item does not open with the keys this host holds, so whether its grant needs a sign-in is not known. What the refusal shows: item {item}: {error}.
Fix: open it by hand (skarbiec get {item}) and repair what that names; skarbiec doctor names a missing key.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_subscription_whose_item_does_not_open_is_named.
skarbiec.subscription stado-absent#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: asking Stado's browser-automation family to sign {item} in. Why: a subscription is signed in by Weles, which Skarbiec reaches only through Stado, and no Stado program is here. What the refusal shows: program: {program}; PATH: {path}.
Fix: install Stado (it puts stado on PATH), or point STADO_BIN at the installed stado.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_sign_in_with_no_stado_is_refused_naming_where_it_was_looked_for.
skarbiec.subscription stado-unstarted#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: asking Stado's browser-automation family to sign {item} in. Why: {program} did not start. What the refusal shows: command: {command}; the system said: {error}.
Fix: make {program} an executable Stado ({program} --version answers when it is), or point STADO_BIN at one.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_sign_in_whose_stado_does_not_start_is_refused.
skarbiec.subscription stado-answer-unreadable#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading what Stado answered for the sign-in of {item}. Why: Stado ended with {ended} and printed no JSON answer and no failure envelope. What the refusal shows: command: {command}; standard output: {stdout}; standard error: {said}.
Fix: run the command above by hand and repair what it says; a Stado older than the browser-automation operation subscription-sign-in is updated with stado product update stado.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_stado_answer_that_is_not_json_is_named.
skarbiec.subscription sign-in-refused#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: signing the subscription {item} ({provider} {subscription}) in. Why: the sign-in was refused for a cause that asking again unchanged will not change ({code}), so it is held until the grant is refused anew or the sign-in is asked for by hand. What the refusal shows: Stado: {said}.
Fix: {remedy}; then skarbiec subscription run --item {item} --now.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_sign_in_the_browser_family_refuses_is_held_naming_why.
skarbiec.subscription sign-in-unconfirmed#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: confirming the sign-in of the subscription {item}. Why: Weles answered the sign-in finished, and the vault does not hold a new grant on {item}: {found}. What the refusal shows: revision before the sign-in: {before}; now: {after}; Weles answered: {answer}.
Fix: read the run Weles names (weles runs show <run>), repair why its grant did not reach {item}, then skarbiec subscription run --item {item} --now.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_sign_in_that_leaves_the_grant_unchanged_is_refused.
skarbiec.subscription run-refused#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: signing the due subscriptions in. Why: {count} subscription sign-in(s) were refused or left no new grant ({alerted}): {items}. What the refusal shows: run report: {report}.
Fix: read each subscription's last_error with skarbiec subscription list and act on it; the other due sign-ins ran.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/lifecycle.sh::a_run_with_a_failed_sign_in_fails_naming_it.
skarbiec.subscription report-unknown#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: finding the subscription {subscription} of {provider} a consumer named. Why: no live item carries brama:subscription, brama:provider:{provider} and brama:id:{subscription}. What the refusal shows: subscriptions of {provider}: {held}.
Fix: send the provider and subscription id the subscription item's own tags carry (skarbiec subscription list names both).
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/refusal_route.sh::a_refusal_of_an_unknown_subscription_is_refused.
skarbiec.subscription report-ambiguous#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: finding the subscription {subscription} of {provider} a consumer named. Why: {count} live items carry brama:provider:{provider} and brama:id:{subscription}, so which subscription is meant is not known. What the refusal shows: items: {items}.
Fix: keep the id on one item: skarbiec retag --remove brama:id:{subscription} <item> on each other one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/refusal_route.sh::a_refusal_two_items_answer_for_is_refused_naming_both.
skarbiec.subscription report-not-granted#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: answering {route} for {consumer}. Why: {consumer} holds no report:subscriptions capability for the bearer it presented. What the refusal shows: consumer: {consumer}; capability asked: report:subscriptions.
Fix: add report:subscriptions to {consumer}'s grant on the vault owner (skarbiec grant list shows its capabilities; Brama's launcher issues it to brama-subscription-reporter at each start), then present that grant's bearer.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/refusal_route.sh::a_consumer_without_the_report_capability_is_refused_naming_it.
skarbiec.subscription report-stale#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: recording that the provider refused the grant of subscription {item}, as {by} reported it. Why: {item} holds another grant than the one {by} presented and was refused: a sign-in has replaced it since, so the refusal is not recorded and nothing is signed in again. What the refusal shows: revision of {item} now: {revision}.
Fix: read the grant {item} holds now and present it; report a refusal of that grant if the provider refuses it too.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/subscription/refusal_route.sh::a_refusal_of_a_grant_since_replaced_is_refused_as_stale.
skarbiec.subscription report-grant-malformed#
list the subscription grants, record and withdraw a provider's refusal of one, and sign every due one in through Stado's browser-automation family. Started by skarbiec subscription list, skarbiec subscription refuse, skarbiec subscription withdraw, skarbiec subscription run, skarbiec maintain, POST /v1/subscriptions/refused, POST /v1/subscriptions/standing, POST /v1/operator/subscriptions, POST /v1/operator/subscriptions/refuse, POST /v1/operator/subscriptions/withdraw, POST /v1/operator/subscriptions/run.
What failed: reading which grant {consumer} reports refused. Why: grant_sha256 is not 64 hexadecimal digits, so it names no grant. What the refusal shows: grant_sha256: {given}.
Fix: send the SHA-256 of the grant's JSON with its object members in name order and no whitespace, as 64 hexadecimal digits, or leave grant_sha256 out.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/subscription/refusal_route.sh::a_refusal_naming_a_grant_that_is_no_digest_is_refused.
skarbiec.tag-write tag-reserved#
judge every tag a write puts on an item against the registry, after reading the tags it already carries. Started by other functionalities only.
What failed: writing the tag {tag}. Why: {tag} is reserved: only an authenticated Weles write marks an item as Weles-managed. What the refusal shows: tag: {tag}.
Fix: leave {tag} off; an item becomes Weles-managed through skarbiec credential adopt role:<role>.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/tags/write.sh::the_reserved_weles_tag_is_refused.
skarbiec.tag-write tag-namespace-unregistered#
judge every tag a write puts on an item against the registry, after reading the tags it already carries. Started by other functionalities only.
What failed: writing the tag {tag}. Why: {tag} claims a namespace (the part before its colon) that is not registered, and no consumer filters on an unregistered one. What the refusal shows: tag: {tag}; registered namespaces: {registered}.
Fix: use a registered namespace (skarbiec tags lists them), or a tag with no colon, which is the operator's own label.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/tags/write.sh::a_tag_in_an_unregistered_namespace_is_refused_naming_the_registered_ones.
skarbiec.tag-write tag-namespace-value-unusable#
judge every tag a write puts on an item against the registry, after reading the tags it already carries. Started by other functionalities only.
What failed: writing the tag {tag}. Why: {tag} claims the {namespace} namespace without a usable {value}: the value must be non-empty and carry no NUL, newline or carriage return. What the refusal shows: tag: {tag}.
Fix: write the tag as {namespace} with its {value} filled in on one line.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/tags/write.sh::a_role_tag_with_no_role_is_refused.
skarbiec.tag-write tag-write-legacy-envelope#
judge every tag a write puts on an item against the registry, after reading the tags it already carries. Started by other functionalities only.
What failed: writing the tags of {id}. Why: {id} is still kept in envelope format {format}, and its tags are written only in the current format {current}. What the refusal shows: item {id}: envelope format {format}.
Fix: skarbiec upgrade --apply moves it to the current envelope; then write its tags.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/tags/write.sh::a_legacy_items_tags_are_refused_naming_the_upgrade.
skarbiec.serve.takeover takeover-home-unset#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: finding this account's launch agents. Why: HOME is not set (or is empty) in serve's environment, so ~/Library/LaunchAgents, where every predecessor's launch agent was loaded from, cannot be found. What the refusal shows: no predecessor unit is taken over, each keeps running on its own ports; serve answers on its own.
Fix: start serve with HOME set to this account's home, as launchd sets it for a launch agent (launchctl print gui/$(id -u)/com.wisent.skarbiec shows the unit's environment).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_declared_unit_started_without_home_takes_over_nothing_naming_it.
skarbiec.serve.takeover takeover-launchd-name-nul#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: asking launchd to {verb} {label}. Why: the verb or the label holds a NUL byte, which a launchd request cannot carry; both are constants of this build, so the build itself is damaged. What the refusal shows: verb {verb}, label {label}; {label} is kept as it is.
Fix: install a release whose binary is whole (skarbiec version names the one running), then start the unit again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_launchd_label_holding_a_nul_byte_keeps_the_unit.
skarbiec.serve.takeover takeover-launchd-unallocated#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: asking launchd to {verb} {label}. Why: launch_data could not make the {part} of the request, which happens when this process has run out of memory. What the refusal shows: nothing was sent to launchd; {label} is kept as it is, on whatever ports it holds.
Fix: free memory on this host (vm_stat says how much is free); serve takes the unit over at its next start.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_launchd_request_that_cannot_be_allocated_keeps_the_unit.
skarbiec.serve.takeover takeover-launchd-silent#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: asking launchd to {verb} {label}. Why: launch_msg returned no reply, so launchd could not be reached from this process (errno {errno}). What the refusal shows: the system said: {said}; {label} is kept as it is, on whatever ports it holds.
Fix: launchctl print gui/$(id -u)/{label} shows whether this account's launchd answers; serve takes the unit over at its next start.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_launchd_that_does_not_answer_keeps_the_unit.
skarbiec.serve.takeover takeover-launchd-refused#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: asking launchd to {verb} {label}. Why: launchd answered the request with errno {errno} instead of the job, and only an absent job (ESRCH) means there is nothing to take over. What the refusal shows: launchd said: {said}; {label} is kept as it is, on whatever ports it holds.
Fix: launchctl print gui/$(id -u)/{label} shows what launchd holds; serve takes the unit over at its next start.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_launchd_that_refuses_the_job_keeps_the_unit.
skarbiec.serve.takeover takeover-pid-malformed#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading which process runs {label}. Why: launchd answered its PID as {pid}, which is not a process id. What the refusal shows: {label} is kept as it is.
Fix: launchctl print gui/$(id -u)/{label} shows what launchd holds; serve takes the unit over at its next start.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_launchd_pid_that_is_not_a_process_id_keeps_the_unit.
skarbiec.serve.takeover takeover-ports-pid-range#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: listing the loopback ports pid {pid} listens on. Why: pid {pid} is above {most}, the largest process id proc_pidinfo takes. What the refusal shows: the unit is kept, so no port it serves is left unanswered.
Fix: lsof -nP -a -p {pid} -iTCP -sTCP:LISTEN names its ports; serve takes the unit over at its next start.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_pid_beyond_what_the_kernel_takes_keeps_the_unit.
skarbiec.serve.takeover takeover-ports-list-refused#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: listing the loopback ports pid {pid} listens on. Why: the kernel refused to list the descriptors of pid {pid} ({step}, errno {errno}), so which ports it holds cannot be known. What the refusal shows: the system said: {said}; the unit is kept, so no port it serves is left unanswered.
Fix: lsof -nP -a -p {pid} -iTCP -sTCP:LISTEN names its ports; serve takes the unit over at its next start.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_process_whose_sockets_the_kernel_will_not_list_keeps_the_unit.
skarbiec.serve.takeover takeover-ports-too-many#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: listing the loopback ports pid {pid} listens on. Why: pid {pid} holds {count} descriptors, whose list of {bytes} bytes is more than one proc_pidinfo request carries. What the refusal shows: the unit is kept, so no port it serves is left unanswered.
Fix: lsof -nP -a -p {pid} -iTCP -sTCP:LISTEN names its ports; stop the unit by hand (launchctl bootout gui/$(id -u)/<label>) once nothing dials them.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_process_with_more_descriptors_than_one_request_carries_keeps_the_unit.
skarbiec.serve.takeover takeover-ports-socket-size#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: listing the loopback ports pid {pid} listens on. Why: the kernel described socket {fd} in {read} bytes, not the {expected} of the socket_fdinfo this build reads, so this macOS lays the record out differently. What the refusal shows: descriptor {fd} of pid {pid}; the unit is kept, so no port it serves is left unanswered.
Fix: run the skarbiec release built for this macOS (skarbiec version names the running one); lsof -nP -a -p {pid} -iTCP -sTCP:LISTEN names the ports meanwhile.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_socket_record_of_another_layout_keeps_the_unit.
skarbiec.serve.takeover takeover-plist-not-text#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the ProgramArguments the launch agent {path} declares. Why: {path} is neither a binary plist nor UTF-8 text, so it is no property list. What the refusal shows: {detail} ({bytes} bytes); the unit is kept, so the bond bearer its arguments may name is not lost.
Fix: plutil -lint {path} names what is wrong; write it again as a launch agent plist (a top-level dict holding ProgramArguments, an array of strings), or remove it if the unit is gone.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_predecessor_agent_that_is_not_text_is_kept_naming_the_byte.
skarbiec.serve.takeover takeover-plist-truncated#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the ProgramArguments the launch agent {path} declares. Why: {path} ends before the property list it begins is complete. What the refusal shows: {detail} ({bytes} bytes); the unit is kept, so the bond bearer its arguments may name is not lost.
Fix: plutil -lint {path} names what is wrong; write it again as a launch agent plist (a top-level dict holding ProgramArguments, an array of strings), or remove it if the unit is gone.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_predecessor_agent_that_is_not_a_plist_is_kept_naming_why.
skarbiec.serve.takeover takeover-plist-unclosed#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the ProgramArguments the launch agent {path} declares. Why: {path} opens an XML comment, declaration, tag, element or entity it never closes. What the refusal shows: {detail} ({bytes} bytes); the unit is kept, so the bond bearer its arguments may name is not lost.
Fix: plutil -lint {path} names what is wrong; write it again as a launch agent plist (a top-level dict holding ProgramArguments, an array of strings), or remove it if the unit is gone.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_predecessor_agent_with_an_unclosed_element_is_kept_naming_it.
skarbiec.serve.takeover takeover-plist-shape#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the ProgramArguments the launch agent {path} declares. Why: {path} holds a value of another kind where a launch agent needs a <plist>, a top-level dict, a key, an array or a string. What the refusal shows: {detail} ({bytes} bytes); the unit is kept, so the bond bearer its arguments may name is not lost.
Fix: plutil -lint {path} names what is wrong; write it again as a launch agent plist (a top-level dict holding ProgramArguments, an array of strings), or remove it if the unit is gone.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_predecessor_agent_whose_top_level_value_is_no_dict_is_kept_naming_it.
skarbiec.serve.takeover takeover-plist-no-arguments#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the ProgramArguments the launch agent {path} declares. Why: {path}'s top-level dict declares no ProgramArguments, so the command the unit runs cannot be known. What the refusal shows: {detail} ({bytes} bytes); the unit is kept, so the bond bearer its arguments may name is not lost.
Fix: plutil -lint {path} names what is wrong; write it again as a launch agent plist (a top-level dict holding ProgramArguments, an array of strings), or remove it if the unit is gone.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_predecessor_agent_declaring_no_program_arguments_is_kept_naming_it.
skarbiec.serve.takeover takeover-plist-text#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the ProgramArguments the launch agent {path} declares. Why: a string in {path} is not text, or names an entity a property list may not hold. What the refusal shows: {detail} ({bytes} bytes); the unit is kept, so the bond bearer its arguments may name is not lost.
Fix: plutil -lint {path} names what is wrong; write it again as a launch agent plist (a top-level dict holding ProgramArguments, an array of strings), or remove it if the unit is gone.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_predecessor_agent_naming_an_unknown_entity_is_kept_naming_it.
skarbiec.serve.takeover takeover-plist-layout#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the ProgramArguments the launch agent {path} declares. Why: {path} is a binary plist whose trailer, offsets or references point at nothing it holds. What the refusal shows: {detail} ({bytes} bytes); the unit is kept, so the bond bearer its arguments may name is not lost.
Fix: plutil -lint {path} names what is wrong; write it again as a launch agent plist (a top-level dict holding ProgramArguments, an array of strings), or remove it if the unit is gone.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_binary_predecessor_agent_with_an_impossible_trailer_is_kept_naming_it.
skarbiec.serve.takeover takeover-bond-flag-missing#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: recording the bond the replica unit {label} pulls. Why: its arguments name no {flag}, and the bond is recorded only as the unit ran it. What the refusal shows: arguments: {arguments}; the unit is kept.
Fix: record the bond yourself with skarbiec bond add <name> --token-file <file> --consumer <consumer>, then remove the launch agent.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_replica_unit_naming_no_token_file_is_kept_naming_the_flag.
skarbiec.serve.takeover takeover-bond-unknown#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: recording the bond the replica unit {label} pulls. Why: the vault holds no bond {bond} with a channel, which the unit names. What the refusal shows: vault: {vault}; the unit is kept.
Fix: skarbiec bond list names the bonds; add it with skarbiec bond add {bond}, or remove the unit's launch agent.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_replica_unit_naming_a_bond_the_vault_lacks_is_kept.
skarbiec.serve.takeover takeover-bond-not-serve#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: recording the bond the replica unit {label} pulls. Why: bond {bond} does not pull over a serve channel (its type is {kind}), and a replica unit pulled only over a serve channel. What the refusal shows: channel: {channel}; the unit is kept.
Fix: skarbiec bond list shows bond {bond}; record it again with skarbiec bond add {bond}, or remove the unit's launch agent.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_replica_unit_whose_bond_is_not_a_serve_channel_is_kept.
skarbiec.serve.takeover takeover-bond-no-interval#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: recording the bond the replica unit {label} pulls. Why: bond {bond} pulls over a serve channel that has no interval_seconds (a whole number of seconds), and a replica unit pulled on an interval. What the refusal shows: channel: {channel}; the unit is kept.
Fix: skarbiec bond list shows bond {bond}; record it again with skarbiec bond add {bond} and its interval, or remove the unit's launch agent.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_replica_unit_whose_bond_has_no_interval_is_kept.
skarbiec.serve.takeover takeover-inherited-no-place#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: finding where the inherited ports record is kept. Why: the vault path {vault} names no file, so nothing has a place beside it. What the refusal shows: serve answers only on its own port.
Fix: name the vault file itself with SKARBIEC_VAULT_FILE, as the unit declares it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::a_vault_path_naming_no_file_keeps_no_inherited_ports.
skarbiec.serve.takeover takeover-inherited-not-json#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the inherited ports record {path}. Why: it is not a JSON list of ports: its {bytes} bytes are not JSON (line {line}, column {column}). What the refusal shows: the parser said: {said}; the record is left as it is, and serve answers on the ports the journal and the retired units name.
Fix: write {path} as a JSON list of the ports the retired units answered on, e.g. [8788, 8790], or remove it to rebuild it from the journal.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::an_inherited_ports_record_that_is_not_a_list_is_kept.
skarbiec.serve.takeover takeover-inherited-not-ports#
record a replica unit's bond, note the loopback ports each predecessor unit listens on, remove it through launchd and its launch agent, and answer on its ports. Started by skarbiec serve, started by launchd as com.wisent.skarbiec.
What failed: reading the inherited ports record {path}. Why: it is not a JSON list of ports: it is JSON, but {kind} where a list of port numbers from 1 to 65535 belongs. What the refusal shows: record: {record}; the parser said: {said}; the record is left as it is, and serve answers on the ports the journal and the retired units name.
Fix: write {path} as a JSON list of the ports the retired units answered on, e.g. [8788, 8790], or remove it to rebuild it from the journal.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/serve/lifecycle.sh::an_inherited_ports_record_holding_no_ports_is_kept.
skarbiec.tool tool-entry-none#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: importing {tool}'s {entry}. Why: {file} keeps no {entry}. What the refusal shows: it keeps {known}{why}; nothing was changed.
Fix: name an entry it keeps (skarbiec tool status {tool} lists them), or keep the token with skarbiec set.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/packages/gem_credential.sh::a_key_the_file_does_not_hold_is_refused_naming_those_it_does.
skarbiec.tool tool-section-none#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: importing {tool}'s {entry}. Why: {file} has no {section} section. What the refusal shows: sections there: {sections}; nothing was changed.
Fix: name a section the file holds with --select (skarbiec tool status {tool} lists them).
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/packages/pypi_credential.sh::a_section_the_file_lacks_is_refused_naming_those_it_holds.
skarbiec.tool tool-bound-elsewhere#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: binding {name} in {file}. Why: {file} already binds {name} as {kept}, and one variable reads one value. What the refusal shows: nothing was changed.
Fix: give another --bindings file, or remove that line from {file}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/packages/gem_credential.sh::a_variable_bound_elsewhere_is_refused_naming_the_line.
skarbiec.tool tool-readback#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: reading back {id} after importing {tool}'s {entry}. Why: {id} was written, and reading it back does not give the token that was moved: another write replaced it between the two. What the refusal shows: {file} was left as it was.
Fix: look at {id} (skarbiec history {id} names its writes), then run the same import again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/tool/refusals.sh::an_import_overtaken_before_it_reads_back_is_refused.
skarbiec.tool tool-select-unfit#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: choosing the {tool} entry to import. Why: --select {given} is not {shape}. What the refusal shows: nothing was read or changed.
Fix: name the entry as skarbiec tool status {tool} lists it, e.g. {example}.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/packages/npm_credential.sh::a_registry_that_is_not_a_registry_key_is_refused_naming_the_shape.
skarbiec.tool tool-already-variable#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: importing {tool}'s {entry}. Why: {file} already reads {entry}'s token from the variable {name}, so it keeps no token to move. What the refusal shows: nothing was changed.
Fix: bind {name} to the item holding the token in your --bindings file, and run the tool through skarbiec exec --env-from.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/packages/npm_credential.sh::a_registry_read_from_a_variable_is_refused_naming_it.
skarbiec.tool tool-tokens-several#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: importing {tool}'s {entry}. Why: {file} keeps {count} different tokens for {entry}, one per account, and one item takes one. What the refusal shows: nothing was changed.
Fix: sign out of all but one account (gh auth logout --hostname {entry} --user <name>), then import.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/packages/gh_credential.sh::a_host_keeping_several_tokens_is_refused_naming_logout.
skarbiec.tool tool-file-not-object#
list the developer tools whose plain-text tokens this vault moves, say how each keeps its entries, and move one entry's token into the vault behind an exec binding. Started by skarbiec tool, POST /v1/operator/tool/list, POST /v1/operator/tool/status, POST /v1/operator/tool/import.
What failed: reading {tool}'s {file}. Why: {file} is not the JSON object the {program} writes. What the refusal shows: {observed}; nothing was changed.
Fix: repair {file}, or sign in again with the {program} so it writes the file afresh.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/huggingface/vercel_credential.sh::an_auth_json_that_is_not_json_is_refused_naming_it.
skarbiec.totp-code totp-identity-unopened#
compute one item's current one-time code, say which state each stored seed is in, or which state a seed text read on stdin would be in, never printing a seed. Started by skarbiec totp code, skarbiec totp seed, skarbiec totp judge, POST /v1/operator/totp/seed-state, POST /v1/operator/totp/judge, Desktop: Items → a selected item → Code.
What failed: reading the second factor of {id}, which names the identity {identity}. Why: until it opens here, no code can be said for {id}. What the refusal shows: opening {identity}: {error}.
Fix: skarbiec readers {identity} and skarbiec doctor name why it does not open here.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/totp.sh::a_code_through_an_identity_that_does_not_open_is_refused_naming_it.
skarbiec.totp-set totp-field-undeclared#
store one login's or identity's authenticator seed from the Base32 secret or otpauth:// address on standard input. Started by skarbiec totp set, POST /v1/operator/items/totp-set, Desktop: Items → a selected item → Add seed, Update seed.
What failed: storing {what} in {id}. Why: a {kind} item has no {field} field, so nothing was stored. What the refusal shows: {id} is a {kind}.
Fix: store it in the login or identity the second factor guards.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/totp.sh::second_factor_material_for_an_item_that_cannot_hold_it_is_refused.
skarbiec.totp-uri totp-no-seed#
write the otpauth:// address of one item's seed, to enroll a phone without asking the site for a new seed. Started by skarbiec totp uri, POST /v1/operator/items/totp-uri, Desktop: Items → a selected item → Show the authenticator QR code.
What failed: writing the otpauth:// address of {id}. Why: {id} keeps no authenticator seed, so there is no address to move. What the refusal shows: {id}'s totp_secret: none.
Fix: store one from the site's QR code: skarbiec totp set {id}.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/totp.sh::an_address_for_an_item_keeping_no_seed_is_refused_naming_totp_set.
skarbiec.totp-recovery totp-field-undeclared#
count one item's second-factor recovery codes, take the next one so it is never offered twice, or replace the set; an account's identity is named by the role it plays (role:<role>). Started by skarbiec totp recovery, POST /v1/operator/items/recovery-codes, POST /v1/operator/items/recovery-codes/take, POST /v1/operator/items/recovery-codes/replace, Desktop: Items → a selected item → Replace recovery codes.
What failed: storing {what} in {id}. Why: a {kind} item has no {field} field, so nothing was stored. What the refusal shows: {id} is a {kind}.
Fix: store it in the login or identity the second factor guards.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/totp.sh::second_factor_material_for_an_item_that_cannot_hold_it_is_refused.
skarbiec.totp-recovery totp-recovery-none#
count one item's second-factor recovery codes, take the next one so it is never offered twice, or replace the set; an account's identity is named by the role it plays (role:<role>). Started by skarbiec totp recovery, POST /v1/operator/items/recovery-codes, POST /v1/operator/items/recovery-codes/take, POST /v1/operator/items/recovery-codes/replace, Desktop: Items → a selected item → Replace recovery codes.
What failed: reading the recovery codes of {id}. Why: {id} {state}. What the refusal shows: {id}'s recovery_codes: {stored}.
Fix: generate new ones at the provider and store them: skarbiec totp recovery {id} --replace, one per line on standard input.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/totp.sh::recovery_codes_an_item_does_not_hold_are_refused_naming_replace.
skarbiec.totp-recovery totp-recovery-damaged#
count one item's second-factor recovery codes, take the next one so it is never offered twice, or replace the set; an account's identity is named by the role it plays (role:<role>). Started by skarbiec totp recovery, POST /v1/operator/items/recovery-codes, POST /v1/operator/items/recovery-codes/take, POST /v1/operator/items/recovery-codes/replace, Desktop: Items → a selected item → Replace recovery codes.
What failed: reading the recovery codes of {id}. Why: {id}'s recovery_codes holds {stored}, neither a list of codes nor text. What the refusal shows: {id}'s recovery_codes: {stored}.
Fix: store the provider's codes again: skarbiec totp recovery {id} --replace, one per line on standard input.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/totp.sh::recovery_codes_of_another_shape_are_refused_naming_it.
skarbiec.totp-recovery totp-recovery-role-unheld#
count one item's second-factor recovery codes, take the next one so it is never offered twice, or replace the set; an account's identity is named by the role it plays (role:<role>). Started by skarbiec totp recovery, POST /v1/operator/items/recovery-codes, POST /v1/operator/items/recovery-codes/take, POST /v1/operator/items/recovery-codes/replace, Desktop: Items → a selected item → Replace recovery codes.
What failed: reading the recovery codes of role {role}. Why: no live item plays role {role}, so it names no item keeping recovery codes. What the refusal shows: items tagged stado:role:{role}: none.
Fix: skarbiec login identity list --accounts names every account's identity and its roles; skarbiec retag --add stado:role:{role} <identity-id> gives one the role.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/recovery.sh::a_role_no_item_plays_is_refused_naming_the_role.
skarbiec.totp-recovery totp-recovery-empty-input#
count one item's second-factor recovery codes, take the next one so it is never offered twice, or replace the set; an account's identity is named by the role it plays (role:<role>). Started by skarbiec totp recovery, POST /v1/operator/items/recovery-codes, POST /v1/operator/items/recovery-codes/take, POST /v1/operator/items/recovery-codes/replace, Desktop: Items → a selected item → Replace recovery codes.
What failed: replacing the recovery codes of {id}. Why: standard input held no recovery code, so nothing was stored. What the refusal shows: lines read: none with a code.
Fix: send the provider's new codes on standard input, one per line.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/totp.sh::an_empty_set_of_recovery_codes_is_refused_and_the_old_set_kept.
skarbiec.totp-missing totp-missing-not-login#
judge whether every login, or one, needs a second factor it does not keep: seeded, needs, not_offered or no_site, from where it signs in and the 2FA Directory. Started by skarbiec totp missing, skarbiec totp missing <item-id>, POST /v1/operator/items/codes-missing, MCP skarbiec_codes_missing, Desktop: Settings → Policy → Logins without a code, Desktop: Settings → Policy → Logins without a code → Judge one login.
What failed: judging whether {id} needs a second factor. Why: {id} is a {kind}, and totp missing judges logins only. What the refusal shows: {id} is a {kind}.
Fix: skarbiec totp seed {id} says whether it keeps a seed; skarbiec totp missing with no item judges every login.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/missing.sh::an_item_that_is_not_a_login_is_refused_naming_its_kind.
skarbiec.totp-verified totp-verified-role-unheld#
record whether the account accepted, refused or locked a code a sign-in submitted, on the item keeping the seed (the identity a login signs in as, else the login), so totp seed says verified, rejected or locked instead of only present. Started by skarbiec totp verified, POST /v1/operator/items/totp-verified.
What failed: recording what the account did with the code of role {role}. Why: no live item plays role {role}, so it names no item keeping a seed. What the refusal shows: items tagged stado:role:{role}: none.
Fix: skarbiec login identity list --accounts names every account's identity and its roles.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/verification.sh::a_role_no_item_plays_is_refused_naming_the_role.
skarbiec.totp-verified totp-verified-no-seed#
record whether the account accepted, refused or locked a code a sign-in submitted, on the item keeping the seed (the identity a login signs in as, else the login), so totp seed says verified, rejected or locked instead of only present. Started by skarbiec totp verified, POST /v1/operator/items/totp-verified.
What failed: recording what the account did with the code of {id}. Why: {holder} keeps no working seed, so no code of it was submitted and there is no outcome to record. What the refusal shows: {holder}'s seed state is not present.
Fix: skarbiec totp seed {id} says what {holder} keeps; store a seed with skarbiec totp set {holder} first.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/verification.sh::an_outcome_for_an_item_keeping_no_seed_is_refused.
skarbiec.totp-seed-read totp-seed-empty#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: standard input held no seed. What the refusal shows: standard input: nothing but blanks; nothing was stored in {id}.
Fix: send the Base32 secret, or the whole otpauth://totp/ address the provider's QR code holds, on standard input: skarbiec totp set {id} < seed.txt.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::empty_input_is_refused_naming_what_to_send.
skarbiec.totp-seed-read totp-seed-not-totp#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the address is not otpauth://totp/; only time-based codes are computed here. What the refusal shows: the address is of type {type}; nothing was stored in {id}.
Fix: send the time-based address (otpauth://totp/...) or the Base32 secret of an authenticator whose code changes every {period_here} seconds: skarbiec totp set {id}; a counter-based (hotp) seed makes no code here.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::an_address_that_is_not_totp_is_refused_naming_its_type.
skarbiec.totp-seed-read totp-seed-no-parameters#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the otpauth:// address has no parameters, so it carries no secret. What the refusal shows: the address ends before a ?; nothing was stored in {id}.
Fix: send the whole address the QR code encodes, its secret= parameter included, or the Base32 secret the provider shows beside the QR code: skarbiec totp set {id}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::an_address_without_parameters_is_refused.
skarbiec.totp-seed-read totp-seed-parameter-twice#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the otpauth:// address states {key} twice. What the refusal shows: parameter {key}: stated twice, so which one counts is unknown; nothing was stored in {id}.
Fix: send the address exactly as the provider's QR code encodes it, each parameter once: skarbiec totp set {id}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::a_parameter_stated_twice_is_refused_naming_it.
skarbiec.totp-seed-read totp-seed-algorithm#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the address asks for {algorithm}; codes here are computed with SHA1. What the refusal shows: algorithm={algorithm}; nothing was stored in {id}.
Fix: send an address the provider issues for SHA1, {digits_here} digits and a {period_here}-second period, or its Base32 secret if its codes are computed that way: skarbiec totp set {id}; a seed stored under other parameters yields codes the provider never accepts.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::another_algorithm_is_refused_naming_sha1.
skarbiec.totp-seed-read totp-seed-digits-unreadable#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the address states digits={digits}, which is not a number. What the refusal shows: digits={digits}: {error}; nothing was stored in {id}.
Fix: send the address as the provider's QR code encodes it, with digits={digits_here} or no digits parameter, which means {digits_here}: skarbiec totp set {id}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::a_digit_count_that_is_not_a_number_is_refused.
skarbiec.totp-seed-read totp-seed-digits#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the address asks for {stated} digits; codes here have {digits_here}. What the refusal shows: digits={stated}; nothing was stored in {id}.
Fix: send an address the provider issues for SHA1, {digits_here} digits and a {period_here}-second period, or its Base32 secret if its codes are computed that way: skarbiec totp set {id}; a seed stored under other parameters yields codes the provider never accepts.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::another_digit_count_is_refused_naming_the_one_computed.
skarbiec.totp-seed-read totp-seed-period-unreadable#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the address states period={period}, which is not a number of seconds. What the refusal shows: period={period}: {error}; nothing was stored in {id}.
Fix: send the address as the provider's QR code encodes it, with period={period_here} or no period parameter, which means {period_here} seconds: skarbiec totp set {id}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::a_period_that_is_not_a_number_is_refused.
skarbiec.totp-seed-read totp-seed-period#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the address asks for a {stated}-second period; codes here change every {period_here} seconds. What the refusal shows: period={stated}; nothing was stored in {id}.
Fix: send an address the provider issues for SHA1, {digits_here} digits and a {period_here}-second period, or its Base32 secret if its codes are computed that way: skarbiec totp set {id}; a seed stored under other parameters yields codes the provider never accepts.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::another_period_is_refused_naming_the_one_computed.
skarbiec.totp-seed-read totp-seed-no-secret#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the otpauth:// address carries no secret parameter. What the refusal shows: parameters stated: {keys}; nothing was stored in {id}.
Fix: send the whole address the QR code encodes, its secret= parameter included, or the Base32 secret the provider shows beside the QR code: skarbiec totp set {id}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::an_address_without_a_secret_is_refused_naming_its_parameters.
skarbiec.totp-seed-read totp-seed-not-base32#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the seed is not Base32 (letters A to Z and digits 2 to 7). What the refusal shows: {length} characters once blanks are dropped, {outside} of them outside A to Z and 2 to 7, and {padding} = at the end; nothing was stored in {id}.
Fix: send the secret as the provider shows it: letters A to Z and digits 2 to 7, spaces allowed, with = only at the end, at most {padding_most} of them, padding it to a multiple of {block} characters: skarbiec totp set {id}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::a_value_that_is_not_base32_is_refused_counting_what_is_not.
skarbiec.totp-seed-read totp-seed-no-code#
read an authenticator seed given as a Base32 secret or an otpauth://totp/ address, held to the SHA1, six-digit, thirty-second codes every reader computes, and prove it computes a code. Started by other functionalities only.
What failed: reading the authenticator seed given for {id}. Why: the seed computes no code: the seed decodes to no bytes. What the refusal shows: {length} Base32 characters; nothing was stored in {id}.
Fix: send the whole Base32 secret the provider shows with skarbiec totp set {id}; a seed that decodes to no bytes holds no key a code is computed from.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/authenticator/seed.sh::a_seed_that_computes_no_code_is_refused_naming_why.
skarbiec.trash trash-nothing-tagged#
put one item, every live item one tag carries, or every live item nothing used since a moment in the trash. Started by skarbiec delete, POST /v1/operator/items/trash, DELETE /v1/items, Desktop: Items → a selected item → Move to trash, Desktop: Settings → Policy → Tags → Move them to the trash.
What failed: {doing} every {state} item tagged {tag}. Why: no {state} item carries the tag {tag}, so nothing was moved. What the refusal shows: {state} items carrying {tag}: none.
Fix: skarbiec tags lists the tags live items carry; skarbiec list --trashed lists the trash.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/trash/trash.sh::a_tag_no_item_carries_is_refused_and_nothing_moves.
skarbiec.trash trash-nothing-untouched#
put one item, every live item one tag carries, or every live item nothing used since a moment in the trash. Started by skarbiec delete, POST /v1/operator/items/trash, DELETE /v1/items, Desktop: Items → a selected item → Move to trash, Desktop: Settings → Policy → Tags → Move them to the trash.
What failed: trashing the live items untouched since {moment}. Why: every live item has been named in the audit journal since {moment}, so nothing was trashed. What the refusal shows: live items untouched since {moment}: none.
Fix: name an earlier moment; skarbiec list --untouched-since <iso8601> lists what a moment selects.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/trash/trash.sh::a_moment_every_item_was_used_since_trashes_nothing.
skarbiec.restore trash-nothing-tagged#
bring one item or every trashed item one tag carries back from the trash, or make a saved version the current one. Started by skarbiec restore, POST /v1/operator/items/restore, Desktop: Items → a trashed item → Restore from trash, Desktop: Settings → Policy → Tags → Bring them back, Desktop: Items → a selected item → History → Restore this version.
What failed: {doing} every {state} item tagged {tag}. Why: no {state} item carries the tag {tag}, so nothing was moved. What the refusal shows: {state} items carrying {tag}: none.
Fix: skarbiec tags lists the tags live items carry; skarbiec list --trashed lists the trash.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/trash/trash.sh::a_tag_no_item_carries_is_refused_and_nothing_moves.
skarbiec.restore restore-version-of-trashed#
bring one item or every trashed item one tag carries back from the trash, or make a saved version the current one. Started by skarbiec restore, POST /v1/operator/items/restore, Desktop: Items → a trashed item → Restore from trash, Desktop: Settings → Policy → Tags → Bring them back, Desktop: Items → a selected item → History → Restore this version.
What failed: restoring the version of {id} saved at {at}. Why: {id} is in the trash, and a version is restored only on a live item, so it never comes back live with an old value in one step. What the refusal shows: item {id}: trashed.
Fix: skarbiec restore {id} brings it back first, then skarbiec restore {id} --at {at} picks the version.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/trash/trash.sh::a_version_of_a_trashed_item_is_refused_naming_the_restore_first.
skarbiec.restore restore-no-such-version#
bring one item or every trashed item one tag carries back from the trash, or make a saved version the current one. Started by skarbiec restore, POST /v1/operator/items/restore, Desktop: Items → a trashed item → Restore from trash, Desktop: Settings → Policy → Tags → Bring them back, Desktop: Items → a selected item → History → Restore this version.
What failed: restoring the version of {id} saved at {at}. Why: {id} keeps no version saved at {at}. What the refusal shows: saved versions of {id}: {stamps}.
Fix: pick one of the stamps above; skarbiec history {id} lists every version with its stamp.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/trash/trash.sh::a_stamp_no_version_has_is_refused_naming_the_stamps_there_are.
skarbiec.restore restore-version-unreadable#
bring one item or every trashed item one tag carries back from the trash, or make a saved version the current one. Started by skarbiec restore, POST /v1/operator/items/restore, Desktop: Items → a trashed item → Restore from trash, Desktop: Settings → Policy → Tags → Bring them back, Desktop: Items → a selected item → History → Restore this version.
What failed: restoring the version of {id} saved at {at}. Why: the version cannot be brought back. What the refusal shows: item {id}: version {at}; opening it said: {error}.
Fix: skarbiec doctor names why a version does not open (a key this host lacks, a damaged revision); skarbiec history {id} names the other versions there are.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/trash/trash.sh::a_damaged_saved_version_is_refused_naming_why.
skarbiec.upgrade upgrade-version-unrecorded#
plan, or with --apply perform, every step that brings the vault to the current schema, keeping a snapshot before the envelope is rewritten. Started by skarbiec upgrade, POST /v1/operator/upgrade, POST /v1/operator/upgrade/apply.
What failed: planning the upgrade of {path}. Why: {path} records its schema version as {recorded}, where every vault records it as text (v2, or the version it was written in), so which steps it needs cannot be told. What the refusal shows: vault file: {path}; nothing was written.
Fix: restore the vault from a backup taken before the damage (skarbiec backup restore <backup-file>); skarbiec doctor names what else is wrong.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/refusals.sh::a_vault_that_records_no_schema_version_is_refused_naming_it.
skarbiec.upgrade upgrade-rotation-section-damaged#
plan, or with --apply perform, every step that brings the vault to the current schema, keeping a snapshot before the envelope is rewritten. Started by skarbiec upgrade, POST /v1/operator/upgrade, POST /v1/operator/upgrade/apply.
What failed: planning the upgrade of the rotation policies in {path}. Why: {path} records its rotation section as {recorded}, where it keeps one object of rotation policies by item. What the refusal shows: vault file: {path}; nothing was written.
Fix: restore the vault from a backup taken before the damage (skarbiec backup restore <backup-file>), or correct the rotation section in the vault file into an object.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/refusals.sh::a_vault_whose_rotation_section_is_not_an_object_is_refused_naming_it.
skarbiec.upgrade upgrade-rotation-policy-damaged#
plan, or with --apply perform, every step that brings the vault to the current schema, keeping a snapshot before the envelope is rewritten. Started by skarbiec upgrade, POST /v1/operator/upgrade, POST /v1/operator/upgrade/apply.
What failed: planning the upgrade of the rotation policy {item} in {path}. Why: rotation policy {item} records {found}, where a policy records a submission object whose with names a provider as text. What the refusal shows: vault file: {path}; nothing was written.
Fix: set the policy again with skarbiec rotation set {item} --every-days <N> --with <provider> (skarbiec rotation providers lists them), or remove it with skarbiec rotation remove {item}.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/refusals.sh::a_rotation_policy_without_a_submission_is_refused_naming_it.
skarbiec.upgrade upgrade-rotation-plan-stale#
plan, or with --apply perform, every step that brings the vault to the current schema, keeping a snapshot before the envelope is rewritten. Started by skarbiec upgrade, POST /v1/operator/upgrade, POST /v1/operator/upgrade/apply.
What failed: renaming the provider of the rotation policy {item} in {path}. Why: rotation policy {item} no longer records the provider {from} the plan read from it before the other steps ran. What the refusal shows: vault file: {path}; the steps before the rotation policies are written, the policies are not.
Fix: run skarbiec upgrade --apply again: it plans the policies from what the vault records now.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/refusals.sh::a_rotation_policy_changed_after_planning_is_refused_naming_it.
skarbiec.upgrade upgrade-snapshot-exists#
plan, or with --apply perform, every step that brings the vault to the current schema, keeping a snapshot before the envelope is rewritten. Started by skarbiec upgrade, POST /v1/operator/upgrade, POST /v1/operator/upgrade/apply.
What failed: keeping the vault at {path} before upgrading it. Why: the snapshot {snapshot} already exists, and writing over it would lose the copy it keeps. What the refusal shows: snapshot: {snapshot}; nothing was written.
Fix: name another path with --snapshot, or move the old snapshot away.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/refusals.sh::an_upgrade_whose_snapshot_path_exists_is_refused_and_writes_nothing.
skarbiec.upgrade upgrade-snapshot-unwritten#
plan, or with --apply perform, every step that brings the vault to the current schema, keeping a snapshot before the envelope is rewritten. Started by skarbiec upgrade, POST /v1/operator/upgrade, POST /v1/operator/upgrade/apply.
What failed: keeping the vault at {path} before upgrading it. Why: the snapshot {snapshot} could not be created: its directory does not exist or does not let this account add a file. What the refusal shows: snapshot: {snapshot}; the file system said: {error}; nothing was written.
Fix: name with --snapshot a file in a directory that exists and this account can write.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/refusals.sh::an_upgrade_whose_snapshot_cannot_be_written_is_refused_and_writes_nothing.
skarbiec.upgrade upgrade-snapshot-uncopied#
plan, or with --apply perform, every step that brings the vault to the current schema, keeping a snapshot before the envelope is rewritten. Started by skarbiec upgrade, POST /v1/operator/upgrade, POST /v1/operator/upgrade/apply.
What failed: copying the vault at {path} into the snapshot {snapshot}. Why: the snapshot was created, and reading the vault or writing its bytes to the disk failed (a full disk, a failing device). What the refusal shows: the file system said: {error}; the partial snapshot was {removed}; nothing was written to the vault.
Fix: free space on the disk holding {snapshot}, or name with --snapshot a file on another disk, then run skarbiec upgrade --apply again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/upgrade/refusals.sh::an_upgrade_whose_snapshot_bytes_cannot_be_written_is_refused_and_removes_it.
skarbiec.vault-file vault-not-here#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: opening the vault file {path}. Why: this machine holds no Skarbiec vault: Stado reads the fleet vault through {declared_by} ({route}), so {path} is a copy and is neither read nor written. What the refusal shows: route: {route}, as stado config get skarbiec_url shows it; nothing was read or written.
Fix: work on the vault owner (stado credentials vault show names it), or name a vault of your own with SKARBIEC_VAULT_FILE.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/vault/init.sh::init_where_stado_routes_to_a_vault_owner_is_refused_naming_the_route.
skarbiec.vault-file vault-absent#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: opening the vault file {path}. Why: vault not initialized at {path} (no file is there, and no copy that reads as a vault is kept beside it). What the refusal shows: vault file: {path}.
Fix: skarbiec init <owner-uid> creates a vault there; SKARBIEC_VAULT_FILE names another file, and skarbiec doctor names why this vault does not open.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_with_no_vault_names_the_file_it_looked_for.
skarbiec.vault-file vault-gone-copy-kept#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: opening the vault file {path}. Why: vault not initialized at {path}: the file is gone, and {copy} is the newest copy kept beside it that reads as a vault. What the refusal shows: vault file: {path}; kept copy: {copy}.
Fix: skarbiec backup restore {copy} says what it holds and with --yes puts it back (init would start an empty vault).
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_gone_with_a_copy_beside_it_names_the_copy.
skarbiec.vault-file vault-copies-unlisted#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: looking beside the absent vault file {path} for a copy kept there. Why: listing {directory} failed, so whether a copy is kept beside the vault is unknown. What the refusal shows: vault file: {path}; the file system answered: {error}.
Fix: let this account read and search {directory}; SKARBIEC_VAULT_FILE names the vault file.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_directory_this_account_cannot_list_is_refused_naming_it.
skarbiec.vault-file vault-not-json#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: reading the vault file {path}. Why: it is not the JSON document skarbiec writes: a write was cut short, or another program wrote the file. What the refusal shows: vault file: {path}, {bytes} bytes; the JSON reader stopped at line {line}, column {column}: {error}.
Fix: skarbiec backup restore <copy> puts back a copy that reads; skarbiec vaults names the copies kept beside it.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_file_that_is_not_json_is_refused_naming_it.
skarbiec.vault-file vault-generation-damaged#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: reading the vault file {path}. Why: it records generation {recorded}, not a count of saves above zero, so whether another write landed cannot be told. What the refusal shows: vault file: {path}.
Fix: skarbiec backup restore <copy> puts back a copy whose generation reads.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_generation_that_is_not_a_count_is_refused_naming_it.
skarbiec.vault-file vault-owner-unrecorded#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: reading the vault file {path}. Why: it records its owner as {recorded}, not a user id, so who writes as the owner is unknown. What the refusal shows: vault file: {path}.
Fix: skarbiec backup restore <copy> puts back a copy that names its owner.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_naming_no_owner_is_refused_naming_it.
skarbiec.vault-file vault-recovery-unrecorded#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: reading the vault file {path}. Why: it records its recovery key as {recorded}, not a fingerprint, so whether it can be recovered is unknown. What the refusal shows: vault file: {path}.
Fix: skarbiec backup restore <copy> puts back a copy that names its recovery key.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_naming_no_recovery_key_is_refused_naming_it.
skarbiec.vault-file vault-damaged#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: reading the vault file {path}. Why: it holds no {section} object of {shape}: its {section} section is {recorded}, so the vault is damaged. What the refusal shows: vault file: {path}.
Fix: restore the damaged vault from a backup: skarbiec backup restore <copy> says what a kept copy holds and puts it back.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/migrations/migrate.sh::a_vault_holding_no_items_object_is_refused_naming_it.
skarbiec.vault-file vault-lock-uncreated#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: writing the vault at {path}. Why: {doing} {target} failed; the file on disk is as it was before this command. What the refusal shows: vault file: {path}; the file system answered: {error}.
Fix: free the disk or let this account write the file and its directory, as the error names, then run the same command again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_into_a_vault_directory_this_account_cannot_write_keeps_the_old_id.
skarbiec.vault-file vault-write-locked#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: writing the vault at {path}. Why: another write holds the vault write lock {lock}, which records pid {holder}; the file on disk is as it was before this command. What the refusal shows: write lock: {lock}; holder pid: {holder}.
Fix: run the same command again once that write is done; if no process {holder} runs (ps -p {holder}), the lock was left behind and removing {lock} releases it.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_while_the_write_lock_is_held_keeps_the_old_id_and_names_the_holder.
skarbiec.vault-file vault-fenced#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: writing the vault at {path}. Why: {held}; the file on disk is as it was before this command. What the refusal shows: writes to this vault are held by fence transaction {transaction}: {fence}.
Fix: skarbiec fence lift --transaction {transaction} ends the fence once the move is over; until then make the change where the vault moved to, or run a step of that move with --fence {transaction}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_while_the_vault_is_fenced_keeps_the_old_id_and_names_the_transaction.
skarbiec.vault-file fence-not-json#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: {doing} the vault's write fence {path}. Why: the fence file is not JSON (it stops being JSON at line {line}, column {column}), so whether writes are held cannot be read, and every write to the vault is held until it goes. What the refusal shows: fence file: {path}, {bytes} bytes; the parser said: {said}.
Fix: skarbiec fence lift --transaction <T> removes it and journals the text it held (a damaged fence is lifted by any transaction), then the move arms its fence again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/fence.sh::a_fence_file_that_is_not_json_is_refused_and_lift_removes_it.
skarbiec.vault-file fence-incomplete#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: {doing} the vault's write fence {path}. Why: the fence file is JSON, and names no {lacks}, so which move holds the vault cannot be read, and every write to the vault is held until it goes. What the refusal shows: fence file: {path}, holding {holds}.
Fix: skarbiec fence lift --transaction <T> removes it and journals the text it held (a damaged fence is lifted by any transaction), then the move arms its fence again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/fence.sh::a_fence_file_naming_no_transaction_or_time_is_refused_and_lift_removes_it.
skarbiec.vault-file vault-changed-underneath#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: writing the vault at {path}. Why: another write landed on the vault after this command read it (loaded generation {loaded}, persisted generation {persisted}), and writing over it would undo that write; the file on disk keeps the other write. What the refusal shows: vault file: {path}.
Fix: run the same command again: it reads the vault as it now is.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/items/writes/rename.sh::a_rename_racing_another_write_keeps_the_other_write_and_is_refused.
skarbiec.vault-file vault-disappeared#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: writing the vault at {path}. Why: the vault file was removed after this command read it, and it is not made again from what was read. What the refusal shows: vault file: {path} is absent.
Fix: skarbiec vaults names the copies kept beside it, and skarbiec backup restore <copy> puts one back.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_removed_before_its_write_is_not_made_again.
skarbiec.vault-file vault-persisted-unreadable#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: writing the vault at {path}. Why: the vault on disk did not read under the write lock; nothing was written. What the refusal shows: vault file: {path}; reading it said: {error}.
Fix: skarbiec doctor names why the vault does not read; skarbiec backup restore <copy> puts back a copy that does.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_damaged_between_read_and_write_is_not_written_over.
skarbiec.vault-file vault-generation-full#
open the vault file, refusing a copy this machine must not read and a document of another shape, and write it back atomically under its write lock. Started by other functionalities only.
What failed: writing the vault at {path}. Why: it records generation {generation}, and no count of saves follows it. What the refusal shows: vault file: {path}.
Fix: skarbiec migrate --from {path} --to <new-file> copies the items into a vault that counts from one.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/open.sh::a_vault_at_the_last_generation_is_not_written.
skarbiec.status status-section-damaged#
report the configured vault, or the vault owner Stado routes this machine to, and the vault's counts without decrypting anything. Started by skarbiec status, POST /v1/operator/status.
What failed: counting the vault's {section} at {path}. Why: the vault's {section} section is not an object, so its entries cannot be counted. What the refusal shows: {section} section: {held}.
Fix: skarbiec doctor names what else is damaged; restore the vault from a backup taken before the damage.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/vault/status.sh::a_vault_section_held_in_another_shape_is_refused_naming_it.
skarbiec.warnings form-unknown#
list, show and check what every Skarbiec functionality warns of before its caller confirms. Started by skarbiec warnings list, skarbiec warnings show, skarbiec warnings check, POST /v1/operator/warnings.
What failed: reading what skarbiec warnings is asked. Why: warnings {given} is not one of its forms. What the refusal shows: arguments: {given}.
Fix: run skarbiec warnings list, skarbiec warnings show <functionality> or skarbiec warnings check.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/warnings/catalogue.sh::an_unknown_warnings_form_is_refused_with_its_usage.
skarbiec.warnings functionality-unknown#
list, show and check what every Skarbiec functionality warns of before its caller confirms. Started by skarbiec warnings list, skarbiec warnings show, skarbiec warnings check, POST /v1/operator/warnings.
What failed: showing the warnings of {id}. Why: no functionality of this skarbiec is declared under {id}. What the refusal shows: declared functionalities: {declared}.
Fix: name one of the declared functionalities; skarbiec warnings list prints those that warn.
Code not_found, exit status 2, not worth retrying unchanged. Provoked by tests/warnings/catalogue.sh::an_undeclared_functionality_is_refused_listing_the_declared_ones.
skarbiec.warnings baseline-unreadable#
list, show and check what every Skarbiec functionality warns of before its caller confirms. Started by skarbiec warnings list, skarbiec warnings show, skarbiec warnings check, POST /v1/operator/warnings.
What failed: reading the unexplained-confirmation baseline {path}. Why: the file could not be read. What the refusal shows: --baseline {path}; the file system answered: {error}.
Fix: name the baseline file the repository holds, ci/warnings-baseline.json.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/warnings/catalogue.sh::a_baseline_that_cannot_be_read_is_refused_naming_it.
skarbiec.warnings baseline-malformed#
list, show and check what every Skarbiec functionality warns of before its caller confirms. Started by skarbiec warnings list, skarbiec warnings show, skarbiec warnings check, POST /v1/operator/warnings.
What failed: reading the unexplained-confirmation baseline {path}. Why: it is not a JSON list of command names. What the refusal shows: --baseline {path}; the JSON reader said: {error}.
Fix: write it as a JSON list of the commands whose confirmation no warning explains yet, e.g. ["lockdown"]; skarbiec warnings check prints them as unexplained_confirmations.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/warnings/catalogue.sh::a_baseline_that_is_not_a_list_is_refused.
skarbiec.warnings findings#
list, show and check what every Skarbiec functionality warns of before its caller confirms. Started by skarbiec warnings list, skarbiec warnings show, skarbiec warnings check, POST /v1/operator/warnings.
What failed: checking the declared warnings. Why: {count} finding(s): a malformed warning, a declared test the repository does not hold, a confirmation no warning explains, a warning no confirmation puts before its caller, or a baseline entry no longer needed. What the refusal shows: the findings, each listed in the answer printed above.
Fix: fix each finding as it says: correct the warning in src/failures, write the declared test, declare the warning a confirmation is for, or remove the command from the baseline.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/warnings/catalogue.sh::a_baseline_allowing_an_explained_confirmation_is_a_finding.
skarbiec.warnings warnings-declaration-unreadable#
list, show and check what every Skarbiec functionality warns of before its caller confirms. Started by skarbiec warnings list, skarbiec warnings show, skarbiec warnings check, POST /v1/operator/warnings.
What failed: listing what {id} warns of. Why: wisent-errors rendered the warnings of {id} as text that does not read as JSON, which it always writes. What the refusal shows: the JSON reader said: {error}.
Fix: install a skarbiec build whose wisent-errors renders warnings as JSON (the skarbiec release installer at stado://releases/skarbiec/<version>/<platform>/install.sh).
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/warnings/catalogue.sh::a_warning_listing_rendered_as_no_json_is_refused_naming_it.
skarbiec.credential.weles-call entra-identity-contract-mismatch#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: handing role {role}'s {operation} to Weles. Why: provider {provider} and the request's field and sealed directory disagree: an Entra password carries its directory, every other provider none, so nothing was sent to Weles. What the refusal shows: provider: {provider}; field: {field}; directory: {directory}.
Fix: seal the directory for an Entra role with skarbiec credential directory seal role:{role}; a role of any other provider must carry no sealed directory.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::a_directory_on_a_provider_that_takes_none_is_recorded_as_needs_configuration.
skarbiec.credential.weles-call weles-bearer-variable-malformed#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading the bearer Skarbiec presents to Weles from WELES_TOKEN. Why: WELES_TOKEN is set but holds {found}, where exactly one bearer, one word with no whitespace, is expected, so nothing was sent to Weles. What the refusal shows: WELES_TOKEN: {words} words in {length} characters.
Fix: set WELES_TOKEN to the one bearer of the skarbiec-weles-credential-client grant, or unset it so the file is read: WELES_TOKEN_FILE, else ~/.stado/skarbiec-weles-credential-client-token.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/admission_in_process.mjs::a_bearer_variable_holding_two_words_is_recorded_naming_it.
skarbiec.credential.weles-call weles-bearer-variable-unreadable#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading the bearer Skarbiec presents to Weles from WELES_TOKEN. Why: WELES_TOKEN is set to a value that is not UTF-8 text, so no bearer can be read from it and nothing was sent to Weles. What the refusal shows: reading WELES_TOKEN: {error}.
Fix: set WELES_TOKEN to the bearer as text, or unset it so the file is read: WELES_TOKEN_FILE, else ~/.stado/skarbiec-weles-credential-client-token.
Code auth, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::a_bearer_variable_that_is_not_text_is_recorded_naming_it.
skarbiec.credential.weles-call weles-endpoint-unresolved#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: handing role {role}'s {operation} to Weles. Why: this host's Stado resolver answered no alternative of the credential-operations family (Weles credential admission, weles-admission) for consumer skarbiec-weles-credential-client, so the operation was not handed over and nothing at the provider changed. What the refusal shows: asking the resolver: {error}.
Fix: run Stado's resolver (stado resolver status says why it does not serve), see what the family answers with stado capabilities resolve credential-operations --consumer skarbiec-weles-credential-client, and admit this host to Weles: stado service directory consumer add weles-admission skarbiec-weles-credential-client; then start the operation again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/credential/admission_in_process.mjs::no_resolver_state_is_recorded_as_weles_endpoint_unresolved.
skarbiec.credential.weles-call weles-endpoint-not-loopback#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: handing role {role}'s {operation} to Weles. Why: the route this host's Stado resolver answered for weles-admission, {url}, is not a loopback address this host reaches, and Skarbiec hands a bearer only to its loopback adapter, so nothing was sent. What the refusal shows: route: {url}; reading it: {error}.
Fix: publish weles-admission to this host's resolver as a loopback adapter (stado resolver status names the adapters this host serves), then start the operation again.
Code config, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::a_route_that_is_not_loopback_is_recorded_naming_it.
skarbiec.credential.weles-call weles-credential-transport-failed#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: handing role {role}'s {operation} to Weles at {address}. Why: Weles credential admission at {address} gave no answer to a request that may have been sent, so whether Weles began the operation is unknown. What the refusal shows: the connection: {error}; provider effect: unknown.
Fix: start Weles where Stado routes weles-admission ({address}), then ask skarbiec credential status role:{role}: it asks Weles what became of the operation before anything is started again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_admission_nothing_listens_on_is_recorded_as_weles_credential_transport_failed.
skarbiec.credential.weles-call weles-credential-answer-not-json#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: handing role {role}'s {operation} to Weles at {address}. Why: Weles credential admission at {address} answered {status} with a body that is not JSON, so what it decided cannot be read and whether it began the operation is unknown. What the refusal shows: {bytes} bytes; the JSON reader stopped at line {line}, column {column} ({said}); provider effect: unknown.
Fix: check that {address} is Weles's credential admission (stado resolver status names the adapter), then ask skarbiec credential status role:{role} before starting anything again.
Code infra_down, exit status 69, worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_admission_answering_text_is_recorded_naming_it.
skarbiec.credential.weles-call weles-credential-admission-refused#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: handing role {role}'s {operation} to Weles. Why: Weles credential admission answered {status} with no operation state, so it refused the operation before deciding it. What the refusal shows: Weles said: {detail}; its code: {code}; provider effect: {effect}.
Fix: act on Weles's words above (skarbiec credential status role:{role} shows the recorded outcome); a code Weles names itself is recorded in this one's place.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_admission_that_refuses_without_an_operation_state_is_recorded_with_its_words.
skarbiec.credential.weles-call weles-response-other-version#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles answered in wire version {found}, not {expected}, the one this Skarbiec speaks, so no member of the answer is read. What the refusal shows: answer status: {status}; nothing of the answer is kept.
Fix: run a Weles that speaks {expected}, or a Skarbiec that speaks {found} (stado product update skarbiec), then ask skarbiec credential status role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_answer_in_another_wire_version_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-member-missing#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles's answer has no {member}, which the contract skarbiec.credential-operation.v4 requires there ({expected}), so the answer cannot be held to the operation. What the refusal shows: answer status: {status}; members present: {members}; nothing of the answer is kept.
Fix: run a Weles that speaks skarbiec.credential-operation.v4, then ask skarbiec credential status role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_answer_missing_a_required_member_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-member-out-of-contract#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles's answer holds {member} as {found}, where the contract skarbiec.credential-operation.v4 takes {expected}, so the answer cannot be held to the operation. What the refusal shows: answer status: {status}; nothing of the answer is kept.
Fix: run a Weles that speaks skarbiec.credential-operation.v4, then ask skarbiec credential status role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_answer_with_a_status_no_weles_sends_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-queued-untracked#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles queued the operation and named no action log id, so what became of it cannot be asked and the queued state is not recorded. What the refusal shows: answer status: operation_queued; actionLogId: absent; nothing of the answer is kept.
Fix: ask Weles's operators which action it queued for role {role} (weles runs list names its runs), then ask skarbiec credential status role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::a_queued_answer_naming_no_action_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-dry-run-executed#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles answered {answered} to an operation submitted as a dry run, so it ran what was only to be planned, and the provider may have changed. What the refusal shows: sent: a dry run; answered: {answered}; nothing of the answer is kept.
Fix: ask Weles what it ran for role {role} (weles runs list), check the provider by hand, then ask skarbiec credential status role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::a_dry_run_weles_executed_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-plan-for-run#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles answered a plan (operation_plan) to an operation submitted to run, so nothing it answered says whether the operation ran. What the refusal shows: sent: an operation to run; answered: operation_plan; nothing of the answer is kept.
Fix: check that the route this host's Stado resolver answers for weles-admission leads to the Weles that holds this operation, then ask skarbiec credential status role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::a_plan_answered_to_a_run_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-other-item#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles's answer names operation/provider/item {answered}, not {sent} that was sent, so it is not about this operation. What the refusal shows: sent: {sent}; answered: {answered}; nothing of the answer is kept.
Fix: check that the route this host's Stado resolver answers for weles-admission leads to the Weles that holds this operation, then ask skarbiec credential status role:{role}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_answer_for_another_item_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-other-directory#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles's answer names {member} {answered}, not the sealed directory's {sent}, so it is about another principal. What the refusal shows: sent: {sent}; answered: {answered}; nothing of the answer is kept.
Fix: check the directory sealed for role {role} (skarbiec credential status role:{role} names it) and the Weles that answered, then ask again.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_answer_for_another_directory_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-other-receipt#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles's receipt names another principal, request or operation than request {sent}, so it proves nothing about this one. What the refusal shows: sent: request {sent}; receipt: {answered}; nothing of the answer is kept.
Fix: ask Weles for the receipt of request {sent} (skarbiec credential status role:{role}); a receipt for another request is never recorded.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::a_receipt_for_another_request_is_refused_and_kept_nowhere.
skarbiec.credential.weles-call weles-response-other-action#
hand a credential operation to Weles and hold its answer to that operation. Started by other functionalities only.
What failed: reading Weles's answer to role {role}'s {operation}. Why: Weles answered about action {answered}, not {sent} that was asked about, nor one chained from it. What the refusal shows: asked: {sent}; answered: {answered}; nothing of the answer is kept.
Fix: ask again with the action log id the operation recorded (skarbiec credential status role:{role} shows it).
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/credential/routing/weles_call.sh::an_answer_about_another_action_is_refused_and_kept_nowhere.
skarbiec.recipient.remove uid-missing#
take one person out of every item, every saved version and the recipient registry. Started by skarbiec recipient remove, POST /v1/operator/recipients/remove, Desktop: Recipients → Remove from vault.
What failed: reading whom skarbiec recipient remove takes out of the vault. Why: no recipient uid was given. What the refusal shows: arguments: none.
Fix: name one, skarbiec recipient remove <uid>; skarbiec recipient list names them.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/recipients/withdrawal.sh::recipient_remove_without_a_uid_is_refused.
skarbiec.recipient.remove remove-unknown-recipient#
take one person out of every item, every saved version and the recipient registry. Started by skarbiec recipient remove, POST /v1/operator/recipients/remove, Desktop: Recipients → Remove from vault.
What failed: taking {uid} out of the vault. Why: the vault registers no recipient {uid}. What the refusal shows: registered recipients: {registered}.
Fix: name one of the registered recipients; skarbiec recipient list prints them.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/withdrawal.sh::recipient_remove_of_an_unknown_recipient_lists_the_registered_ones.
skarbiec.recipient.remove remove-owner#
take one person out of every item, every saved version and the recipient registry. Started by skarbiec recipient remove, POST /v1/operator/recipients/remove, Desktop: Recipients → Remove from vault.
What failed: taking {uid} out of the vault. Why: {uid} owns this vault, and every item stays sealed to its owner. What the refusal shows: owner: {uid}.
Fix: install another owner first with skarbiec owner rotate <new-owner-uid>, then remove {uid}.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/withdrawal.sh::recipient_remove_of_the_owner_names_owner_rotate.
skarbiec.recipient.remove remove-recovery-holder#
take one person out of every item, every saved version and the recipient registry. Started by skarbiec recipient remove, POST /v1/operator/recipients/remove, Desktop: Recipients → Remove from vault.
What failed: taking {uid} out of the vault. Why: {uid} holds the recovery key, which every item stays sealed to so the vault can be recovered. What the refusal shows: recovery key: {fingerprint}.
Fix: leave {uid} registered: removing it would take nothing away; skarbiec recipient items {uid} lists what the recovery key opens.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/withdrawal.sh::recipient_remove_of_the_recovery_key_holder_is_refused.
skarbiec.recipient.rekey rekey-unknown-recipient#
give one recipient a new key and write every live item they read again to it. Started by skarbiec recipient rekey, POST /v1/operator/recipients/rekey, Desktop: Kit → Give them a new key.
What failed: giving {uid} a new key. Why: the vault registers no recipient {uid}. What the refusal shows: registered recipients: {registered}.
Fix: name one of the registered recipients; skarbiec recipient add registers a new person.
Code not_found, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/withdrawal.sh::recipient_rekey_of_an_unknown_recipient_lists_the_registered_ones.
skarbiec.recipient.rekey rekey-owner#
give one recipient a new key and write every live item they read again to it. Started by skarbiec recipient rekey, POST /v1/operator/recipients/rekey, Desktop: Kit → Give them a new key.
What failed: giving {uid} a new key. Why: {uid} owns this vault, and an owner's new key must also rewrap every saved version. What the refusal shows: owner: {uid}.
Fix: run skarbiec owner rotate <new-owner-uid>, which rewraps every current and saved version.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/withdrawal.sh::recipient_rekey_of_the_owner_names_owner_rotate.
skarbiec.recipient.rekey rekey-same-key#
give one recipient a new key and write every live item they read again to it. Started by skarbiec recipient rekey, POST /v1/operator/recipients/rekey, Desktop: Kit → Give them a new key.
What failed: giving {uid} the key in {file}. Why: {file} holds the key {uid} already has. What the refusal shows: fingerprint: {fingerprint}.
Fix: name the file of the new key they made.
Code refused, exit status 1, not worth retrying unchanged. Provoked by tests/recipients/withdrawal.sh::recipient_rekey_to_the_same_key_changes_nothing.
skarbiec.grant.revoke-idle idle-with-consumer#
withdraw every consumer grant the audit journal shows unused since a moment. Started by skarbiec grant revoke --idle-since, POST /v1/operator/grants/revoke, Desktop: Grants → Idle grants → Withdraw every grant unused since then.
What failed: reading which grants skarbiec grant revoke withdraws. Why: a consumer and --idle-since {moment} were both given, and revoke takes one of them. What the refusal shows: consumer: {given}; --idle-since {moment}.
Fix: drop the consumer to withdraw every idle grant, or drop --idle-since to withdraw that one.
Code config, exit status 2, not worth retrying unchanged. Provoked by tests/grant/idle.sh::grant_revoke_with_a_consumer_and_idle_since_is_refused.