USAGE
cmk-coffer-set [OPTIONS] COFFER_FILE [PKEY_FILE...]
Open COFFER_FILE, unlock it by whatever means are required, merge new dictionary items into it (or completely overwrite it with new content), then save it.
A list of PKey files may follow it on the argument list, each of which will be loaded and considered for whether it can help unlock the Coffer. For Coffers with the PKey objects serialized in the same file, use option --bundled-keys (-b).
This is mainly intended for the case of altering Coffers containing dictionary content, because for a single-content-blob Coffer you could just as easily use cmk-coffer-new to create a fresh one rather than decrypting the old one first and overwritng it. Overwriting the content might save you the effort of re-specifying the metadata and access locks, though.
OPTIONS
- --bundled-keys (-b)
-
Scan the remainder of the coffer file for embedded PKey objects
- --parse=FORMAT
-
Parse names and values from stdin and store them as dictionary content.
Formats:
- ini
-
Parse input as lines of
NAME=VALUEin the tradition of INI files, where ';' and '#' begin comments and whitespace is trimmed from the names and values. Bare names (lacking an '=') are not supported, nor are multiline values. INI headers are currently ignored. - 0
-
Parse the input as NUL-delimited strings alternating between Name and Value.
- --dict-item (-d) NAME=VALUE_FILE
-
Read a value from VALUE_FILE and store it as dictionary item NAME. This option can be used multiple times, and applies after items generated by
--parse. If option--parseis not used,--dict-itemimplies that no value will be read from stdin. - --content-type MIMETYPE
-
Optionally specify a MIME-type for the content of the Coffer, stored in the public headers (not encrypted). Dictionary storage implies its own content type, so no need to set this if you specify dictionary storage options.
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 51:
Expected text after =item, not a number