bolha.us: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.6
Has anbody a clue why #pass tells me "gpg: decryption failed: No secret key" but when I use plain gpg --decrypt bla.gpg it shows me its contents without problems? I had an expired gpg key and created a new one, but meanwhile already imported my old one. My feeling is that pass is using the wrong GPG key, but I have no clue where to configure it which one to use. Any help appreciated #encryption #gpg #linux #terminal
#gpg key expirations have been updated for another two-year bump. I also removed #twitter / X signature notation (I've deleted my account there), and added a bunch of other signature notations for other places I am online. It's making my #keyoxide page look dirty, but I intend to try and add support for as many of these as possible in the next few months.
Also, I updated my #tails #TailsOS installation while I was at it. I do most of my GPG key work from that environment.
Another quick & dirty poll, this time on generating a GPG key: Which type of GPG key would you recommend to someone starting out with GPG for the first time? Voting & additional feedback are optional, but I would like to know as I'm wanting to set up a GPG key for my email + to encrypt files before they get uploaded to the cloud. #GPG #KeyGeneration #Privacy #MailEncryption #FileEncryption #SeekingAdvice #SetupQuestions #Poll
Every time I get a new e-mail address I'll use for committing into a #Git repo, which is not very often, I just type "florimond.dev" in Firefox to get quick access to this awesome straight-to-the-point post about #gpg commit signing: https://florimond.dev/en/posts/2022/07/github-signed-commits.
Thanks @florimond for that, it will remain a reference for years!
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLogin