tom_secrets_client 0.2.11
tom_secrets_client: ^0.2.11 copied to clipboard
The Dart client of the Tom Secrets Manager: finds the local secrets service, speaks its client protocol (frames, hello, get, getMany, getFile) and parses and formats secret references.
Changelog #
0.2.11 #
- 0.2.10 exported
tomSecretsBrowserHostName, whichtom_secrets_servicedefines too and exports beside this library, so every importer of the service failed to compile: the client no longer exports it (tomSecretsBrowserHostBesidekeeps the name).
0.2.10 #
- The browsers' native-messaging manifests of
tsm-browser-host(part-browser):TomSecretsBrowserHosts(Chrome, Chromium, Edge, Brave and Firefox on macOS, Linux and Windows: the manifest's folder, on Windows the registry value throughreg.exe; install, remove, the start check; a Flatpak or Snap browser named),TomSecretsBrowserHostState,TomSecretsRegistry; the extension ids the host serves (tomSecretsChromiumExtensionIds, the development build's key and id,tomSecretsFirefoxExtensionId);tomSecretsBrowserHostBeside.
0.2.9 #
- The OS unlock's key bundle (protocol.md 6.4, part-os-unlock):
TomSecretsUnlockBundle(the composite key and the repository key),tomSecretsBundleKey(HKDF-SHA256 per admin connection),tomSecretsSealBundle/tomSecretsOpenBundle(AES-256-GCM, checked againstprotocol/vectors/bundles.json), andTomSecretsAdminClient.unlockWithBundle. New dependency:cryptography. TomSecretsAdminClient.serviceStartnow answers the service's start (it answered 0).
0.2.8 #
TomSecretsIntegrationsreads and writes its (small) files synchronously behind itsFutureAPI, so the manager app's widget tests, which run on fake time, see them written.
0.2.7 #
matchtakesuserName(only that user's logins),pick(the helpers: one login of the host, the one the grants decide or the one the user picks in the app) andonProgress;proposeanswers whether the vaults hold the credential already (a helper'sstore, DP-52).- The developer-tool integrations (
TomSecretsIntegrations, admin library): the ssh block (IdentityAgentof the service's agent, at the top of~/.ssh/config, itsHostpatterns editable; on Windows the pipe's backslashes doubled, as ssh's config reader takes them) and the git block (credential.helper tsmin~/.gitconfig,git-credential-tsmbesidetsm), installed, checked (status: still this machine's agent and helper), repaired and removed;tomSecretsWithBlock/tomSecretsBlockOfkeep everything outside the marked block.
0.2.6 #
- The ssh-agent's endpoint in the runtime directory [B]:
TomSecretsRuntime.agentSocket(agent.sockon Linux and macOS),TomSecretsRuntime.agentPipe(\\.\pipe\tsm-ssh-agenton Windows) andagentEndpoint, the one of the runtime's OS;agent.sockis an endpoint file (removed with the others);writeInfotakes the agent's endpoint forservice.json.
0.2.5 #
matchandpropose[B] (protocol.md 5.5) for the browser host and the developer-tool helpers: the login entries of a page the client's grants cover (TomSecretsLoginCandidate, never a value), and a login proposed for the manager app; each fails asunsupportedwhen the service does not offer its feature.hello.featuresnamesbinary,getFile,matchandpropose;getFilechecks only its own two features.
0.2.4 #
- The pairing mode's handover carries
approvalLink(TomSecretsPairingHandover.approvalLink): the address the new machine's approval link listens on, which goes into its device settings and is told to the giving machine. tomSecretsApprovalLinkProblem: the check of an approval link address (host:port, never every interface), shared bytsm, the service and the app.
0.2.3 #
TomSecretsRuntimejoins its files with the separator of the OS it is made for (separator;TomSecretsRuntime.currenttakes the givenoperatingSystem's), so Windows paths computed elsewhere use a backslash.getMany's argument error for an empty or over-long list is documented as the caller's mistake, raised before anything is sent.
0.2.2 #
- The README rewritten as the package's manual; API summaries of the client and the admin library in
doc/api/. tomSecretsStartService: a status line that is not JSON or not an object is a failed start (no_answer), not an exception.
0.2.1 #
pairing_mode.dartin the admin library: the service's pairing mode astsm pairdrives it — the handover (TomSecretsPairingHandover), what the pairing gave (TomSecretsPairingReport) and the conversation (TomSecretsServicePairing:received,setUp,close).
0.2.0 #
distribution.dartin the admin library: the layout of the manager app's distribution, which carriestsmand the service in itstsm/binfolder (tomSecretsServiceCandidates,tomSecretsDistributionApp).TomSecretsAdminKeyringin the admin library: the admin keys in the keychain with the index of their starts (tsm.admin.index);keep,forget,pruneOthers.
0.1.0 #
- The admin side, in its own library
package:tom_secrets_client/admin.dartfor the manager app,tsmand the service:TomSecretsAdminClient(the mutual challenge andclaim),TomSecretsRuntime(the runtime directory),tomSecretsStartServicewith the admin-key handover,tomSecretsDataDirectory/tomSecretsBootstrapPath(TSM_DATA_DIR, else the OS's application-data folder), and the keychain names (tomSecretsKeychainService,tomSecretsAdminKeyHandle). - The client endpoint of the Tom Secrets Manager protocol, version 1: finding
the service (runtime directory, Unix socket, or on Windows the localhost
port and the client token re-read at every connect), frames with their
limits and strict JSON payloads,
hello/welcome,get,getManyand (phase B)getFileover binary chunks with its SHA-256 check. - Waiting for an unlock or an approval:
wait,timeoutastimeoutMs, progress notices with the approval code. TomSecretReference.parse/format: the reference grammar, its canonical form and the malformed reasons, refused locally.TomSecretValue: text or bytes, entry (sourcegithub,fileorcache), bindings, version, expiry, client token; maskedtoString,disposeoverwrites the buffer.TomSecretsClientExceptionwithTomSecretsErrorKind: the protocol's kinds plusnotRunning;rateLimitedwaited out on request.