Show HN: Send encrypted secrets from the command line
1–10 of 43 posts
Re: Show HN: Send encrypted secrets from the command line
#2Don't have much time now but just wanted to give this a quick +1, worth checking out.
Re: Show HN: Send encrypted secrets from the command line
#3Re: Show HN: Send encrypted secrets from the command line
#4For this reason I use something like read then burn[1,2] for passwords.
[1] https://readthenburn.fnkr.net/ [2] https://github.com/Tethik/burn-after-reading
Re: Show HN: Send encrypted secrets from the command line
#5How does this compare to keybase?
Re: Show HN: Send encrypted secrets from the command line
#6 ./sshencdec.sh -p
It's just a simple bash script really, but it works, and almost everyone has a github account and an ssh key set up, so it works out of the box with most developers.Re: Show HN: Send encrypted secrets from the command line
#7How does this compare to keybase?
Re: Show HN: Send encrypted secrets from the command line
#8Is a self-hosted version of the same possible?
Additionally, there should probably be
a) Some sort of "paranoid" mode whereby it would show me peer's key (in some form) so that I could, if really wanted, manually verify it.
b) An option to cache peer keys locally. I assume this is done already and that the local cache lookup is given a priority over the registry search. Correct?
Re: Show HN: Send encrypted secrets from the command line
#9Fetches from where? Public key servers?
Anybody can upload a key for you@your-company.com to a public key server.
Re: Show HN: Send encrypted secrets from the command line
#10> Fluidkeys automatically fetches keys based on the verified email address and encrypts the secret to the key. Fetches from where? Public key servers? Anybody can upload a key for you@your-company.com to a public key server.
> We chose not to use the public keyserver network until it supports deleting keys and cryptographic validation.
... as well as the fact that there's no email validation, yep!