skeyd 0.2.0__tar.gz

skeyd-0.2.0/.gitignore

@@ -0,0 +1,44 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+*.egg
+
+# Virtual environments
+.venv/
+venv/
+env/
+
+# Testing / coverage
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+
+# Type checking / linting
+.mypy_cache/
+.ruff_cache/
+.dmypy.json
+
+# Editors
+.vscode/
+.idea/
+*.swp
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# skeyd's own runtime state — never commit a real store, key, or audit log
+.skeyd/
+*.skeyd-store
+store.json
+store.key
+policy.toml
+audit.jsonl
+!examples/**/policy.toml

skeyd-0.2.0/CHANGELOG.md

@@ -0,0 +1,97 @@
+# Changelog
+
+All notable changes to skeyd are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows [Semantic Versioning](https://semver.org/).
+
+## [0.2.0] — 2026-09-20
+
+### Changed
+- **Renamed the package** from `skeyd-cli` to `skeyd`, so the install command and the
+  run command are the same name (`pip install skeyd`, then `skeyd ...`). The package
+  directory (`src/skeyd/`), the console-script entry point (`skeyd`), and the importable
+  module (`import skeyd`) were already named `skeyd`; only the PyPI project name and the
+  documented install commands were `skeyd-cli`. The old `skeyd-cli` PyPI project is left
+  published for anyone who already installed it.
+
+### Added
+- **Text User Interface (TUI).** `skeyd tui` — an interactive terminal dashboard built on
+  Textual, available as an optional extra (`pip install 'skeyd[tui]'`). It is a view and a
+  transmitter only: every action is driven by the existing CLI command functions through a
+  bridge that keeps Textual's raw-mode terminal isolated from any `getpass()`/prompt, so the
+  CLI, its `--json` agent envelope, its exit codes, and its error types are all unchanged.
+  Screens: a launcher/home menu; a store browser (list, detail, add, remove); a TOML policy
+  editor with save/revert/`$EDITOR`; an audit-log browser (tail, summary, verify); and a
+  guided `skeyd init` wizard (store directory, passphrase source, policy drive). Launched
+  with `skeyd tui` (or `skeyd tui --screen=...`). The Textual dependency is optional and
+  imported lazily — the base `skeyd` CLI works without it, and running `skeyd tui` without
+  Textual installed fails with a clear, actionable error (exit 65, hint: install the `[tui]`
+  extra).
+
+## [0.1.1] — 2026-09-19
+
+### Fixed
+- README tables now render as tables on GitHub (`||` → `|` GFM syntax); the
+  command reference, exit-code, configuration, and problem/quickstart tables
+  were all affected.
+- `shlex.split` in the passphrase-command runner now takes an explicit `posix`
+  flag (`posix=(os.name == "posix")`). On Windows, `shlex` treats backslash as
+  an escape character, which mangled paths like `C:\Users\gebzerly\...` in
+  `SKEYD_PASSPHRASE_COMMAND` — causing 6 CI test failures on Windows + py3.13.
+- `resolve_executable` on Windows now checks for executable extensions
+  (`.exe`, `.bat`, `.cmd`, `.com`, `.ps1`, `.vbs`, `.wsf`) instead of relying
+  on `os.X_OK`, which is always `True` on Windows and made the non-executable
+  path rejection test fail.
+- `build_child_env` now sets `PYTHONIOENCODING=utf-8` so child Python processes
+  use UTF-8 on Windows where the default console/pipe encoding is not, fixing
+  the multi-byte UTF-8 subprocess output test.
+- `fsutil._write_payload` now applies `os.fchmod(fd, SECRET_FILE_MODE)` on
+  POSIX as a belt-and-suspenders safeguard alongside the existing `os.open`
+  mode parameter.
+- Test compatibility with Windows CI:
+  - `test_creates_the_file_privately` and `test_file_has_owner_only_permissions`
+    skipped on Windows (POSIX `st_mode` permission bits have no meaning there).
+  - `test_no_shell_is_involved` skipped on Windows (requires `/bin/sh`).
+  - `test_reports_no_change` skipped on Windows (requires `vi`/`nano` editor).
+  - Three policy TOML tests use `Path.as_posix()` when embedding paths in TOML
+    strings so Windows backslashes don't break TOML parsing.
+
+## [0.1.0] — 2026-09-19
+
+Initial public release. Ground-up rewrite of the single-file prototype into a packaged, tested, documented project. See [`docs/migration.md`](docs/migration.md) for moving an existing prototype store across, and [`docs/architecture.md`](docs/architecture.md) for what changed structurally and why.
+
+### Added
+
+- **Encryption at rest.** AES-256-GCM envelope; scrypt (passphrase) or HKDF-SHA256 (key file) key derivation, with KDF parameters and format version bound into the ciphertext as associated data.
+- **Zero-Trust policy engine.** Deny-by-default TOML rules matching principal, label, command and arguments, with rate limiting, working-directory scoping, tag requirements, expiry, and a `sandbox` command-prefix hook. Unknown policy keys are hard errors with "did you mean" suggestions.
+- **Leak-resistant output.** `SecretValue` renders as `«secret:redacted»` through every ordinary Python path (`str`, `repr`, f-strings, `%`, `json`, pickling refused entirely). Child process output is scrubbed of the credential across its common encodings (base64 at all phase alignments, hex, percent-encoding, JSON/shell escaping), safe across arbitrary chunk boundaries, plus structural detection of well-known credential shapes as defence in depth.
+- **Environment scrubbing.** A child receives an allowlist-built environment, never the parent's full `os.environ`; skeyd's own `SKEYD_*` configuration is always stripped.
+- **Tamper-evident audit log.** Hash-chained JSONL; `skeyd audit verify` detects edits and reports the first break.
+- **Machine-readable agent interface.** `skeyd agent manifest` (native, Anthropic, OpenAI, and MCP tool-schema dialects) and `skeyd agent call`. No tool returns plaintext — an agent can use a credential, never hold one.
+- **CLI surface:** `init`, `status`, `doctor` (security self-check), `set`, `list`, `show`, `rm`, `rename`, `suggest`, `run`, `check` (policy dry-run, decrypts nothing), `policy {init,check,show,test,edit}`, `audit {tail,verify,summary}`, `rekey`, `migrate`.
+- **Stable exit codes** in the 64–79 range so they never collide with a propagated child exit code (`run` returns the child's own code on success).
+- **Multiple key-material sources**, resolved in a documented, precedence order: explicit key file → `SKEYD_PASSPHRASE_COMMAND` → `SKEYD_PASSPHRASE` → OS keyring (optional extra) → default key file → interactive prompt — supporting both unattended agent hosts and human-operated machines.
+- **Metadata-bearing store entries**: stable ids (not list positions), creation/expiry/last-used timestamps, use counts, tags, notes. Rotation is "add a new value, let the old one expire" rather than editing every reference to it.
+- Full test suite (`pytest`) covering adversarial cases: redaction across encodings and chunk boundaries, ciphertext and header tamper detection, KDF downgrade/exhaustion guardrails, audit chain edit/reorder/truncation detection, subprocess timeout with process-group reaping, and end-to-end assertions that no command surfaces plaintext under any output mode.
+
+### Changed from the v0 prototype
+
+All of the following were identified as weaknesses in the original single-file prototype and addressed in this rewrite — see [`docs/threat-model.md`](docs/threat-model.md) for the full before/after reasoning:
+
+- Store moved from plaintext JSON to an encrypted envelope.
+- Child stdout/stderr redaction, previously defined (`check_no_leak()`) but never actually called, is now wired into every output path and covers encoded forms, not just the literal string.
+- The full parent environment is no longer passed to child processes.
+- An authorization layer (previously absent entirely) now gates every injection.
+- Store file permissions are enforced at creation time (`os.open` with an explicit mode) rather than reported after an insecure write; the prototype's write-then-chmod left a race window where the file existed world-readable.
+- Atomic writes use `mkstemp` in the destination directory plus `os.replace`, fixing a `.with_suffix(".tmp")` collision bug and adding `fsync` before rename.
+- Label and environment-variable name validation are now separate concerns (the prototype's shared regex accepted invalid POSIX names like `MY-KEY` and `9LIVES`).
+- Secret values are wrapped in a non-`str` container rather than held as plain `str`, closing the accidental-repr/traceback/f-string disclosure path.
+- `--value` on the command line is still supported (some workflows need it) but now emits an explicit warning about shell-history and `/proc` exposure.
+- The prototype's `suggest_label` dead code, assertions, and substring-blacklist (which could mangle a legitimate name like `mytokenservice`) are replaced with whole-token matching and ranked suggestions.
+- No audit trail existed previously; every grant, denial, and store mutation is now recorded.
+- No machine-readable agent contract or stable exit codes existed previously.
+- A duplicate `--store` flag definition on both the main parser and a subparser is resolved.
+- Process timeout previously did not kill a spawned process's own children; execution now runs in its own process group with SIGTERM→SIGKILL escalation across the whole group.
+
+[0.1.0]: https://github.com/gebzerly/skeyd/releases/tag/v0.1.0
+[0.1.1]: https://github.com/gebzerly/skeyd/releases/tag/v0.1.1
+[0.1.2]: https://github.com/gebzerly/skeyd/releases/tag/v0.1.2
+[0.2.0]: https://github.com/gebzerly/skeyd/releases/tag/v0.2.0

skeyd-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the
+      purposes of this License, Derivative Works shall not include works
+      that remain separable from, or merely link (or bind by name) to the
+      interfaces of, the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 skeyd contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.