2 ms·

I made something similar, but the payload gets encrypted with the users ssh rsa key instead of pgp (that not many use): ./sshencdec.sh -p <(curl -sf "https:/

I made something similar, but the payload gets encrypted with the users ssh rsa key instead of pgp (that not many use): ./sshencdec.sh -p <(curl -sf "https://github.com/S2-.keys" | \ grep ssh-rsa | tail -n1) < plain-text-file.txt 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. https://github.com/S2-/sshencdec https://github.com/S2-/sshencdec

paulfurley 8y ago
That's cool! We were doing similar things ourselves with GPG. But ultimately we'd forget the exact command, or the copy-pasting in then out of Slack was enough of a barrier that we'd basically never bother. Curious how such a small barrier was a blocker. Our hypothesis is that, if we can make `fk secret send` easier than literally everything else, people will default to it, and it'll be a win for security. We shall see!