No log keeps a password or a secret: the log file, the run log, or the remote history
Passwords, channel secrets, pairing PINs, and private keys reached the DEBUG log and the runs table in plain text: every chat run stored its channel secret inside the Conversation repr, and --password, --secret, channel links, and config set device_pin were stored as typed. meshterm.core.secrets now hides each one as <secret> by its shape (a secret-named key, record, set operation, or dataclass field; bytes; a Secret; a remote `password`/`set guest.password` command; name=value in text), and by value for each secret MeshTerm has read or sent. Both log handlers and the runs table go through it, always. The remote CLI history keeps `password ` without its value. Schema v20 hides the secrets that older versions stored. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
9e579424b4
commit
1d983013d7
13 files changed
+896
-60
No files matched your search
@@ -115,6 +115,14 @@ radios from two directories in the same shell.
|
||||
| `meshterm.log` | The log file. |
|
||||
| `.lock` | The lock for a single instance. |
|
||||
|
||||
**No log keeps a password or a secret.** The log file, the run log in the database (the
|
||||
arguments and the result of each command), and the remote command history of
|
||||
`remote.json` write `<secret>` in the place of a password, a channel secret, a pairing
|
||||
PIN, or a private key. This is always true, at each log level and with or without the
|
||||
**Anonymize** preference. The history keeps `password ` without its value, so ↑ still
|
||||
recalls the start of the command. `admin.json` keeps the admin passwords that you asked
|
||||
MeshTerm to remember, because that is its purpose.
|
||||
|
||||
**`--db` alone does not isolate a run.** It moves the database. The database is most of
|
||||
the data, but it does not hold the identity. The contact caches, the channel caches, the
|
||||
outbox, the stored admin passwords, and the remembered device are all in the config
|
||||
|
||||
Reference in new issue
Block a user