tom_secrets_core 0.2.3
tom_secrets_core: ^0.2.3 copied to clipboard
The core of the Tom Secrets Manager: secret stores over KDBX files, overlays, dimensions and the resolution of secret references, the GitHub vault cycle and the outer encryption.
Changelog #
0.2.3 #
tomSecretsReceivePairingForSetuptakeslinkAddress: where the new machine's approval link will listen, sent to the giving machine with its keys so the giver records it and opens the link; checked withtom_secrets_client'stomSecretsApprovalLinkProblem. Needstom_secrets_client0.2.4.
0.2.2 #
- The README rewritten as the package's manual; API summaries of every area in
doc/api/.
0.2.1 #
- Setting a machine up by pairing (part-sharing):
tomSecretsReceivePairingForSetupreceives with fresh trust material and refuses a bundle a new machine cannot be set up from (tomSecretsPairingSetupProblem: the primary missing, agithub:primary without its token);TomSecretsFirstRun.runPairedsets the machine up from the receipt;tomSecretsParsePairingAddressreads thehost:portthe giving side shows. - The pairing: a receiving side may refuse the bundle
(
TomSecretsPairingRefusal,{"op":"refused","reason"}), which ends it withTomSecretsPairingFailure.refusedon both sides. TomSecretsTrust.recordPeer: what a pairing gave, recorded in the trust material.
0.2.0 #
- Pairing (part-sharing, DP-60âDP-64, DP-177):
TomSecretsSpake2: SPAKE2 as RFC 9382 specifies it (P256-SHA256-HKDF-HMAC, the RFC's M and N, key confirmation), checked with the RFC's test vectors, refusing a point off the curve.tomSecretsGivePairing/tomSecretsReceivePairing: the pairing over a channel. The code (TomSecretsPairingCode,<number>-<word>-<word>) proved by SPAKE2, an ML-KEM-768 exchange inside, the session key mixing both secrets with the transcript; then the giving side's bundle (TomSecretsPairingBundle: vaults with their key files and repository keys, the shared configuration, tokens pasted for the device, its public keys), the receiving side's public keys, and the approval-token key both derive.TomSecretsPairingWindow: the giving side's window on the LAN and VPN addresses only, the first connection only, five minutes.tomSecretsReceivePairingAt: the receiving side over TCP.
TomSecretsDeviceRecords: the device records of the primary (.tom-secrets/devices, DP-62).TomSecretsLinkFrameReader: the approval link's framing, for pairing.
0.1.6 #
TomSecretsLinkSession.underPreviousKey: on the host, whether the approver connected under the host's previous link key, so the host passes it the new one.
0.1.5 #
- A device rotates its own key pairs (part-key-rotation):
TomSecretsTrust.rotateApproverKeymakes a new hybrid approver pair and answers the key-change statement signed by the old and the new pair;rotateLinkKeymakes a new approval-link pair and keeps the previous one for the hosts the new key has not reached (linkKeyFor,markLinkKeyDelivered,linkKeyPending) during the migration period (tomSecretsLinkKeyMigration, 14 days;expirePreviousLinkKey;previousLinkKey, kept to the end of the period while approvers are recorded). TomSecretsLinkSession.respond(previousMe:)also answers an approver that still holds the host's previous link key.
0.1.4 #
TomSecretsVaultUnit.rekey: commits a re-keyed file as it is in one commit on top of the base's head (never merged; a moved branch is refused withTomCasConflictException), after which the unit reads and writes with the new credentials and outer layer.
0.1.3 #
TomSecretsVaultUnit.mergeOverRemotemerges a working copy handed in withreplaceWorking(stored:)over the rewritten remote instead of pushing the bytes it was given, andtakeRemotedrops those bytes.
0.1.2 #
- The device settings carry the rotation ages and the reminder start of
DP-85:
otherKeyWarningDays(30),keyPairAgeMonths(24),primaryKeyAgeMonths(24),vaultKeyAgeMonths(12).
0.1.1 #
TomSecretsResolver.explain: a request explained step by step (the request's values, every candidate kept with its rank vector or dropped by the binding that drops it, the outcome with its winner or tied candidates), ranked through the same code asresolve.
0.1.0 #
- Stores over KDBX files with their index (logical paths, bindings, keys),
overlays in both placements, the metadata entry and
tsm.config, dimensions with priority, configured defaults andfallback_to_default, resolution with its rank vectors, ambiguity and fields (string fields, attachments,totp, refused passkey fields), the KDBX mapping and TOTP (RFC 6238, the three conventions). - Vault locators, the GitHub cycle as a
tom_core_syncsync unit overtom_core_storage(TomGitHubStorage, no clone), the three-way vault merge with conflict records, and the primary vault's.tom-secrets/vaults. tomSecretsDeviceCommitter: the device as author and committer of the cycle's commits (<device>@tsm.invalid), forTomGitHubStorage.committer(tom_core_storage 0.1.1).- Signed objects, approval codes and tokens, the approval link (both roles),
the grants group
tsm.grants/<host>and the device's trust material (protocol.md 9;tom_pqcfor ML-DSA-65 and ML-KEM-768). TomSecretsFieldValueheld as aTomProtectedValue(tom_crypto 1.5.0):withByteshands out bytes zeroed after use,disposezeroes it without touching the vault's attachment.- Key files (
TomSecretsKeyFile, KeePass 2.0 XML) in the composite key, the key derived once from the file's bytes as KeePass derives it, and the.tsmxouter format with key slots under XChaCha20-Poly1305 (default) or AES-256-GCM (tomSecretsOuterEncrypt/Decrypt,TomSecretsOuterCodec,TomSecretsRepositoryKey). - New vaults (
tomSecretsNewVault): KDBX 4.1 keyed through Argon2id,tomSecretsDefaultArgon2(64 MiB, 3 iterations);TomSecretsVaultUnit.createrefuses a file keyed otherwise. - The offline cache (
TomSecretsOfflineCache) in the vault cycle: kept on every read and write, opened from when the remote is unreachable or refuses the token; telling a compaction from a force push (tomSecretsClassifyMove,TomSecretsCommitReader,TomSecretsHistoryRewritten,mergeOverRemote); the app's compaction withtom_git(tomSecretsCompact) and the compaction workflow, script and configuration for the vault repositories (tomSecretsCompactionFiles). - Imports (
tomSecretsImport,TomSecretsImportSource, the report) and the 1Password importer for 1PUX and CSV (tomSecretsRead1Pux,tomSecretsRead1PasswordCsv). - The Enpass importer for JSON and CSV (
tomSecretsReadEnpassJson,tomSecretsReadEnpassCsv) with passkeys intoKPEX_PASSKEY_*(TomSecretsPasskey,tomSecretsPasskeyPem), and the Enpass JSON export (tomSecretsExportEnpassJson). Imports know folders, trashed items and kept passkeys. - The device settings and their container with the key modes
(
TomSecretsDeviceSettings,TomSecretsDeviceContainer,TomSecretsDeviceKeys,TomSecretsLockPolicy); the KDBX types the other packages handle are re-exported (DP-29). A.tom-secretsgroup is never indexed, at any depth. - The first run (
TomSecretsFirstRun): a primary created or opened, local or on GitHub, its key file and repository key kept in the device keychain (tsm.key-file.<id>,tsm.repository-key.<id>),tsm.keys-due24 months on, the device settings andbootstrap.yaml; a.tsmxrewrite keeps its cipher; a.kdbx.tsmxfile's store name drops both suffixes.