pull down to refresh
295 sats \ 22 replies \ @Natalia 23 Feb 2024 \ on: Stacker Saloon
deleted by author
A long time ago, way before bitcoin, I think in the late 1980s or early 1990s, I was in a PGP message group. There were probably some famous people in there too. I started using PGP for encrypted emails. It worked well and was easy to use, but no one I knew cared about privacy so I didn't use it much. This was either before or around the time the US government tried to ban it.
reply
how do you use PGP now, self-hosting is the way? 👀 I don't use email that much, but curious to see what's the proper way to use it.
I feel these encrypted mail providers take away all the burdens and blend everything with a single password, and then users become "stupid" by default; It feels the same when using custodial wallets without having the burden of safeguarding the seeds yourself, but then how come it's pretty much all "custodial way" in the email case? fascinating.
reply
I don't use it any more. I use protonmail, but you're right. It's easy and I'm ignorant about what goes on beneath the hood.
reply
would it be really cool if email blends with sats one day? 👀
- paid to send, no spams.
- need private key to decrypt the msg.
- all the msg follows the key instead of being stuck in the email provider.
it feels almost the same with DM over LN, only the encrypted message part is missing.
reply
it feels almost the same with DM over LN, only the encrypted message part is missing
It's encrypted, only the receiving node can read it. But on SN, we all share the same node and thus k00b and me could just lookup the decrypted messages in the database.
Software verification with PGP has a terrible UX, and that is what I'm trying to fix with zap.store using nostr
reply
indeed, and the information of each software is in different place, even simple things like the public key of the Devs ( OMG ) which means certain manual work needs to be done, or maybe that's the charm of decentralization instead of depending on Apple or Google to do that for us?
what I'm trying to fix with zap.store using nostr
and how?
reply
You're right!
I wrote about it here: #404908
reply
interesting read - the path of regaining freedom is like saying goodbye to the illusion of security/safety and taking things back into your own hands, from as simple as verifying software to making life decisions.
reply
deleted by author
reply
Do you have a link to read about this new DMing? Is it still a LN transaction?
reply
no link to read, I just did a test early today with @ek, all I did is I use his key to encrypted the message and then I send that to him over LN:) ⚡️ really fun!
reply
I'm trying to decrypt your message but I am confused and a bit embarrassed lol. It says I don't have the decryption key:
$ gpg --decrypt natalia.asc
gpg: encrypted with rsa3072 key, ID 72BBE6ACFD911E48, created 2023-11-23
"ekzyis <ekzyis@ekzyis.com>"
gpg: public key decryption failed: No secret key
gpg: decryption failed: No secret key
It says it was encrypted with rsa3072 key, ID 72BBE6ACFD911E48 but I indeed don't seem to have the decryption key for that:
$ gpg --list-secret-keys --keyid-format long ekzyis@ekzyis.com
sec rsa4096/ECEC37F68FB73398 2023-11-23 [SC] [expires: 2024-03-24]
47705D79F55713643556F499ECEC37F68FB73398
uid [ultimate] ekzyis <ekzyis@ekzyis.com>
ssb rsa4096/57C6E94C763DA6C9 2023-11-23 [E] [expires: 2024-03-24]
Seems like I used to have a rsa3072 key:
$ gpg --list-keys --keyid-format long ekzyis@ekzyis.com
pub rsa3072/DEECE3CF8D4D258F 2023-11-23 [SC] [expires: 2025-11-22]
E13F6708015D2D55082A14F1DEECE3CF8D4D258F
uid [ultimate] ekzyis <ekzyis@ekzyis.com>
sub rsa3072/72BBE6ACFD911E48 2023-11-23 [E] [expires: 2025-11-22]
pub rsa4096/ECEC37F68FB73398 2023-11-23 [SC] [expires: 2024-03-24]
47705D79F55713643556F499ECEC37F68FB73398
uid [ultimate] ekzyis <ekzyis@ekzyis.com>
sub rsa4096/57C6E94C763DA6C9 2023-11-23 [E] [expires: 2024-03-24]
And the key that was used for encryption was that one since the ID matches for the encryption key:
sub rsa3072/72BBE6ACFD911E48 2023-11-23 [E] [expires: 2025-11-22]
I guess the rsa4096 key was not used because it is marked as expired in the PGP keyfile that I host here:
$ gpg --show-keys pgp.txt
pub rsa3072 2023-11-23 [SC] [expires: 2025-11-22]
E13F6708015D2D55082A14F1DEECE3CF8D4D258F
uid ekzyis <ekzyis@ekzyis.com>
sub rsa3072 2023-11-23 [E] [expires: 2025-11-22]
pub rsa4096 2023-11-23 [SC] [expired: 2023-12-23]
47705D79F55713643556F499ECEC37F68FB73398
uid ekzyis <ekzyis@ekzyis.com>
sub rsa4096 2023-11-23 [E] [expired: 2023-12-23]
gpg: WARNING: No valid encryption subkey left over.
I think the warning mentions that the message won't be encrypted with that key but only with the rsa3072 key.
The above commands don't show the same expiration date since I manually updated it in the hope I could decrypt and don't have to write this message; mentioning that I wasn't able to decrypt the first PGP message that I received haha.
I uploaded a new PGP keyfile where the rsa4096 key is not expired:
$ gpg --show-keys pgp2.txt
pub rsa3072 2023-11-23 [SC] [expires: 2025-11-22]
E13F6708015D2D55082A14F1DEECE3CF8D4D258F
uid ekzyis <ekzyis@ekzyis.com>
sub rsa3072 2023-11-23 [E] [expires: 2025-11-22]
pub rsa4096 2023-11-23 [SC] [expires: 2024-03-24]
47705D79F55713643556F499ECEC37F68FB73398
uid ekzyis <ekzyis@ekzyis.com>
sub rsa4096 2023-11-23 [E] [expires: 2024-03-24]
Can you try again @Natalia? I would have loved to read your message! But I will never be able to read the original message now.
Thanks for testing! Didn't know my key expired haha
reply
deleted by author
reply
deleted by author