fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

#pgp

2 posts2 participants0 posts today

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hey! I'm lor.sh/@skobkin and I'm moving to my own GoToSocial instance here:
gts.skobk.in/@skobkin
Feel free to verify this message using my public PGP key which is present in my profile, on my site or several key servers.
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQReSjXrVHxrrK5L33ZDieZwWVv4qAUCZ/19rgAKCRBDieZwWVv4
qBACAQCEgBG7Y05wxU37/3vqGO56y8khraqhLM3EKtd7EBLeoAD8CnK9KaWAYqqB
OQZNN+NjZT+41XZ5zzLl6h7vXqnQ4AA=
=Xy5J
-----END PGP SIGNATURE-----

lor.shAlexey Skobkin (@skobkin@lor.sh)35.6K Posts, 694 Following, 2.23K Followers · Back-end developer from Northern Russia. I like OpenSource, using Linux (work, hobby and home infrastructure), Windows (games and creativity) and Android. Sometimes I play FPS games (R6: Siege, Apex Legends, PUBG), sometimes I play guitar. 98% of my posts are in Russian. I can be very annoying and sometimes even rude in some discussions so be prepared. Contacts: https://skobk.in/contacts/ PGP key: https://f.skobk.in/2024-03-18-public_addresses.asc License: CC-BY if I'm the author.

So I've given @mailfence a very quick test on their Free tier.

That seems to be quite reasonable alternative for e-mail services. In som parts it's what I would expect @mailbox_org being. Except of one thing: Unencrypted incoming e-mails will not be stored encrypted.

Since I'm on the free tier currently, I've not tested the IMAP integration.

The weakness of #Mailfence and #Mailbox are that the PGP setup requires some efforts to happen. The "settings" panel on Mailfence is cleaner and better organized than mailbox.org, but the latter one is capable of ensuring all received e-mails are stored encrypted - regardless if it was encrypted at arrival or not.

PGP key management is still not as easy as it should be for non-tech users. "It should just happen automatically", is my stance here. It's close to being good, but you need to explicitly enable encryption on each mail you send - unless you reply to an already encrypted mail. This will confuse users and it will result in more unencrypted mails sent than intended.

Neither Mailfence nor mailbox.org will decrypt encrypted Subject fields.

I've briefly tested the WebDAV integration, which seems to work. But WebDAV is not end-to-end-encrypted, so uploaded data will not be stored in so-called "zero access" mode. This means the Mailfence people managing their servers can access and read your data. This will be the same for CalDAV/CardDAV too (calendar and contacts synching)

Mailbox.org recently announced they will upgrade their login system - which is long overdue. Their OTP setup is currently just confusing and very far from user friendly. Here Mailfence is very straight forward.

Both Mailfence and #mailbox_org still got quite a long way to provide a properly privacy enabled service. They're on a good path, but currently far from the capabilities of @protonprivacy, even on the most basic features in e-mail.

#privacy#email#pgp
Replied to xeniax ⏚

@Xeniax Totally nerdsniped :D I'd love to be a part of the study.

I don't think that #KeyServers are dead. I think they evolved into Verifying Key Servers (VKS), like the one run by a few folks from the OpenPGP ecosystem at keys.openpgp.org/about . More generally, I believe that #PGP / #GPG / #OpenPGP retains important use-cases where accountability is prioritized, as contrasted with ecosystems (like #Matrix, #SignalMessenger) where deniability (and Perfect Forward Secrecy generally) is prioritized. Further, PGP can still serve to bootstrap those other ecosystems by way of signature notations (see the #KeyOxide project).

Ultimately, the needs of asynchronous and synchronous cryptographic systems are, at certain design points, mutually exclusive (in my amateur estimation, anyway). I don't think that implies that email encryption is somehow a dead-end or pointless. Email merely, by virtue of being an asynchronous protocol, cannot meaningfully offer PFS (or can it? Some smart people over at crypto.stackexchange.com seem to think there might be papers floating around that can get at it: crypto.stackexchange.com/quest).

To me, the killer feature of PGP is actually not encryption per se. It's certification, signatures, and authentication/authorization. I'm more concerned with "so-and-so definitely said/attested to this" than "i need to keep what so-and-so said strictly private/confidential forever and ever." What smaller countries like Croatia have done with #PKI leaves me green with envy.

keys.openpgp.orgkeys.openpgp.org
Continued thread

#survey #keyservers #pgp #encryption

PART 3 OF THE KEYSERVER STUDY

(see Part 1 here: mastodon.ml/@Xeniax/1142733550)

❓QUESTION 3: WHY HAVE YOU STOPPED USING KEYSERVERS

Mastodon.mlxeniax ⏚ (@Xeniax@mastodon.ml)Dear Fedi friends. I want to make a short #survey to understand who actively uses #keyservers today. I am interested in understanding the meaning and the value that people attribute to keyservers nowadays, and the shift in perceptions of email #encryption 🔑🔒 📊 I will be making several polls (follow the thread!) 💌 I also would be happy if some of you agree to talk with me more in depth over an e2ee encrypted channel of your choice, no need to make a call, just messages are enough 👾 Feel free to share the polls and reach out in comments if you can and want to be part of this study. 👩🏽‍🎓 If this ever leads to any kind of publication, I will be following the standard ethical protocol adopted in the academic research community, which is to 1. ask informed consent for quoting; 2. quoting anonymously by default, unless the person wants to be named and 3. right to withdraw from the study even after responding to the questions QUESTION 1: DO YOU USE KEYSERVERS? [ ] Yes, actively (at least twice a month) [ ] Yes, sometimes (at least once every 2-3 months) [ ] I have used keyservers in the past but not anymore [ ] I have never used keyservers

Looking back...

In 1991, Bill 266 was proposed in the U.S. Senate. It would have forced electronic communications service providers to turn over people's personal information.

The key clause, S.266, was pushed by the then chairman of the U.S. Senate Judiciary Committee [guess who...] :

...
...
...

Senator Joe Biden.

**Cypherpunks Write Code**

americanscientist.org/article/

American Scientist · Cypherpunks Write CodeWhat happens in this virtual world—the Dark Net—and why?

0d - #Zeroday: 0d122 - #PGP per #DNS

Für die heutige Episode hat sich Sven die verschiedenen Möglichkeiten angesehen, um PGP-Keys per DNS auszuliefern und eine eigene Bewertung durchgeführt.

Es kristallisiert sich ein klarer Favorit heraus, bei dem Stefan jedoch ein durchaus reales Risiko sieht, dessen Eintrittswahrscheinlichkeit jedoch nicht abschätzbar ist.

Webseite der Episode:
0x0d.de/2025/03/0d122-pgp-per-

Mediendatei:
zeroday-podcast.de/podlove/fil

@zeroday@chaos.social
@zeroday@podcasts.social

0d - Zeroday0d122 - PGP per DNSDer Podcast für Informationssicherheit und Datenschutz Für die heutige Episode hat sich Sven die verschiedenen Möglichkeiten angesehen, um PGP-Keys per DNS auszuliefern und eine eigene Bewertung durchgeführt. Es kristallisiert sich ein klarer Favorit heraus, bei dem Stefan jedoch ein durchaus reales Risiko sieht, dessen Eintrittswahrscheinlichkeit jedoch nicht abschätzbar ist. Disclaimer In diesem Podcast werden Techniken oder Hardware vorgestellt, die geeignet sind, andere Systeme anzugreifen. Dies geschieht ausschließlich zu Bildungszwecken, denn nur, wenn man die Angriffstechniken kennt, kann man sich effektiv davor schützen. Denkt immer daran, diese Techniken oder Hardware nur bei Geräten anzuwenden, deren Eigner oder Nutzer das erlaubt haben.Der unerlaubte Zugriff auf fremde Infrastruktur ist strafbar (In Deutschland §202a, §202b, §202c StGB).Unsere Aussagen spiegeln ausschließlich unsere eigene Meinung wider.

#Gwit est un protocole de publication de contenus textuels (sites, documentation, etc) simplissime, pensé pour fonctionner essentiellement hors-ligne. Il est basé sur #Git et #PGP. Il permet de repartager des sites (même hors ligne) sans risque que le contenu ait été modifié

Pour le moment, seuls deux sites existent à ma connaissance ^^. Mais n'importe quel site statique léger peut facilement être "hébergé" sur Gwit.

gwit : sr.ht/~ivilata/gwit/

#gpg #offline

1/2

sr.htgwit: gwit - Web sites over Git

Den krönenden Abschluss hat heute für mich @qbi gemacht. Danke! In seinem Vortrag „25 Jahre später verschlüsselt Johnny immer noch nicht” geht er auf die vielfältigen Probleme der Emailverschlüsselung ein. Er kommt zur einfachen, aber sicher auch traurigen Schlussfolgerung: „Email ist irreparabel kaputt für Verschlüsselung, nutzt @signalapp#clt2025 #encryption #pgp

Note to self: Heul doch!

Ich kann, will und werde es nicht verstehen, warum die Menschen um mich herum immer noch nach Motto „Dann haben die halt meine Daten. Na und?“ verfahren, und es erst einen Trump braucht, um sie zumindest von US-amerikanischen Datensammlern gaaanz langsam wegzubekommen.

Aber Mail verliert ohnehin an Bedeutung, seit es mehr oder weniger verschlüsselte Messenger gibt, die einem die ganze Arbeit mit der Verschlüsselung abnehmen.

konstantinklein.com/note-to-se

konstantinklein.comNote to self: Heul doch! – K reloaded
More from K reloaded

Getting started with XMPP/Jabber and PGP for federated, encrypted messaging

This is a short thread where I explain how I started using the XMPP protocol and PGP encryption for secure messaging. I am not a security expert, but I am a mathematician and I am confortable with the Linux command line. This guide is for people who want to use PGP for secure messaging easily. You will need to be okay with typing commands into the Linux command line in order to do this, but I will tell you exactly what to enter.

Part 1: XMPP

Mastodon is like email, but for social media. You sign up for an account with a server, and then you can talk with any other accounts that are signed up on other servers, as long as your servers are getting along. (No one wants emails from the sketchy spam server, and we want to be able to choose between Yahoo, Gmail, etc.) XMPP (a.k.a. Jabber) is the same thing for text messaging.

Just like signing up for an email/Mastodon account, you need to sign up for an account. You can find a list of servers at list.jabber.at/ and will probably at least need to provide an email addess when making an account.

Once you have made an account, you need a client. On Linux, I've been having a good time using Dino (dino.im/). You can then enter your account name and password to log into your XMPP account and start chatting! There are both public rooms and you can also message directly with your friends.

#security #PGP #XMPP #FOSS #Jabber #Dino #MonoclesChat

(1/4)

list.jabber.atXMPP servers

I'd already begun my journey into transforming my online experience: data security, supporting ethical software/services, right to repair, degoogling, federation, etc. (May make ACCESSIBLE guides?)
But today was a big milestone for me because I've done something that, in it's current form (possibly on purpose), is pretty frustrating and inaccessible. I'd been eyeing PGP encryption for a variety functional and philosophical reasons (eg the creator was #punk ).
So I finally figured out how to make encryption keys, exchanged public keys with contacts, joined an XMPP server (XMPP is a similar federated protocol to email but with an SMS/text feel), downloaded DINO, a GUI (graphical user interface for Linux that does XMPP communication AND supports PGP encryption), signed in, subscribed to my contacts so we could enable PGP-encrypted communication, and started chatting.
Now, I can breathe and freely communicate knowing my messages are the most secure they've ever been.

#PGP#DINO#XMPP