-
-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it possible to get a public key from the name chosen in Secretive via shell/CLI #499
Comments
Hey @ari-becker there's a few reasons for this right now:
Overall, basically Secretive is not designed to be managed from a CLI currently. A few people have requested that over the years so it's kind of on my radar, although not with any particular timetable now. If you have specific thoughts on what an ideal CLI interface for your specific use case would be, I'd be interested in hearing it. |
Ah, I see.
Basically I'm trying to write a bootstrap / new-hire / new-laptop kind of script, something like: brew install secretive
secretive create-new-key --username "$(whoami)" --label "super-special-bootstrap"
gcloud compute os-login ssh-keys add --key-file=$(secretive get-key-file --username "$(whoami)" --label "super-special-bootstrap") But at the moment this appears to be a non-automatable segment, where I need to ask the user to go do some stuff manually, which is kind of a bummer and more likely to fail compared to running |
I was looking at this today, trying to use
Having to give Terminal.app/iTerm2.app full access to other applications is not ideal, as it means any other process that you run in the terminal (or any of its children) also have that access to these apps. A solution that might solve this is to add an option in Secretive to write the public key (and empty private key) into Has this been considered? |
For the original issue of mapping key labels to keys, adding the key name as comment to the .pub file the same way it is in the copy-enabled screen section of Secretive could help, and be easy to accomplish ? |
At the moment,
ssh-add -l
only shows the hash of the keys added via Secretive, but no metadata (like the name of the key). The data under~/Library/Containers/com.maxgoedjen.Secretive.SecretAgent/Data/PublicKeys
is junk.If I want to write a script that adds a particular key to the remote, then I need to already know the fingerprint of the key I created, which is less convenient than having a convention for key names and fetching the correct key via its name.
The text was updated successfully, but these errors were encountered: