- Fix init directory
- Storage: sqlite3
- Add key pair for native user
- Add pkey for foreign user
- Add app:env(key:value) pair
- Export app:env(key:value) pair to foreign user
- import export file
-
pluggable storage backends
-
pluggable export/import formats
-
backup
-
multi-signature secrets (Shamir)
-
pluggable backup backends
-
rename admin to owner?
-
rename users to keyring?
-
server installation
-
re-key database
-
ssh [email protected] "/srv/venv/dev310/bin/python -V"
looks promising requires%userprofile%\.ssh\id_rsa
to be present, valid, and have the correct permissions.
- update documentation
-
seeqret list --filter ...
-
seeqret export to --filter ...
- Filters:
::key == *:*:key
(all keys matching key regardless of app:env), -
myapp:dev:*
(all keys for myapp in dev) -
myapp-*::
(all keys for myapp-sales, myapp-marketing, etc)
- Filters:
-
seeqret import ...
selectively -
seeqret update --filter <filter> --set env=prod
- more convenient export/import
- is there a way to do ACLs
- web of trust (discrete webs can be safely merged whenever two persons) in different webs achieve a direct trust relationship, correct? - emergent web of confidence?)
- differentiated features based on user
- asdf
seeqret init --user bp --email [email protected]
in another directory
seeqret init --user tkbe --email [email protected]
Note: the url here is suspect (no proof of ownership).
seeqret add user --url https://raw.githubusercontent.com/tkbeorg/tkbe/refs/heads/main/public.key --username tkbe --email [email protected]
seeqret add user --username bp --email [email protected] --url https://gitlab.com/thebjorn/public/-/raw/main/public.key?ref_type=heads
seeqret add key SEECRET 42
@echo off
echo foo ^
this is ^
a multiline ^
echo > out.txt
@echo on