#OpenPGP - muenchen.social - Die erste Mastodon Instanz für München

vanitasvitaeJust figured out, that the massive performance hit my <a href="https://fosstodon.org/tags/PGPainless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGPainless</a> test suite was suffering since I started to port to a newer BC version was caused by the default S2K iteration count being bumped to 0xff instead of 0x60. This had caused the runtime of the test suite to rise to 7 minutes compared to ~1 minute.I decided to dial down the default value again, but make it customizable :D<a href="https://fosstodon.org/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a>

Delta ChatWe are not aware of other FOSS development teams that have as extensive knowledge, both theoretical and practical, about <a href="https://chaos.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> and <a href="https://chaos.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> and regularly release across all platforms for users world wide ... except for <a href="https://chaos.social/tags/protonmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protonmail</a> with whose technical and security experts we discuss regularly. They are the other major game in town doing pervasive email encryption after all. Did you know that Proton's and delta's VCards are compatible across ecosystems and establish immediate encryption?

Delta Chat<a href="https://jura.social/@mathilde" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mathilde</a> <a href="https://chaos.social/tags/chatmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatmail</a> server users don't have these problems because they don't even need to know their password or email address. Messages in delta chat are stored locally and the server only stores them for a limited time, up to 20 days by default, so all devices have a chance to download the message. Blocklists are also not used, the only requirements are <a href="https://chaos.social/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DKIM</a> signature and <a href="https://chaos.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> encryption.

Keith NasmanRemember the old days with key signing parties? I never really got into that but I think with all the "AI" bots we are going to get to a place where we need to have trust networks built on cryptographic keys to filter out the crap.Note to self: Set up public key and share it.<a href="https://fosstodon.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://fosstodon.org/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSSL</a>

Neustradamus :xmpp: :linux:<a href="https://mastodon.social/tags/GnuPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a> 2.5.5 (dev) has been released (<a href="https://mastodon.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> / <a href="https://mastodon.social/tags/GPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> / <a href="https://mastodon.social/tags/GNUPrivacyGuard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUPrivacyGuard</a> / <a href="https://mastodon.social/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a> / <a href="https://mastodon.social/tags/PrettyGoodPrivacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrettyGoodPrivacy</a> / <a href="https://mastodon.social/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> / <a href="https://mastodon.social/tags/Gpg4win" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gpg4win</a>) <a href="https://gnupg.org/" rel="nofollow noopener noreferrer" target="_blank">https://gnupg.org/</a>

Delta ChatThe downside of our project approach was that we often got experts being very dismissive on re-using email and <a href="https://chaos.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> ... and there still is some opposition which often subsides when actually trying <a href="https://chaos.social/tags/deltachat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#deltachat</a> and <a href="https://chaos.social/tags/chatmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatmail</a>, looking at security audits and our strong usable security focus. There may also be surprising upsides. The UK "Online Safety Bill" which attacks end-to-end encryption integrity seems to not apply for ... e-mail. Because everyone knows, e-mail is unencrypted, right? :)

Pirate PraveenHas anyone here on <a href="https://social.masto.host/tags/fedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedi</a> figured out the correct recipe for dealing with <a href="https://social.masto.host/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a>, <a href="https://social.masto.host/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DMARC</a> and <a href="https://social.masto.host/tags/mailman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailman</a> ?The problem, by default mailman will modify messages and this will break the dkim signature. <a href="https://gitlab.com/mailman/mailman/-/issues/1079" rel="nofollow noopener noreferrer" target="_blank">https://gitlab.com/mailman/mailman/-/issues/1079</a>Mailman provides two DMARC mitigation options (other option is reject or discard which is not useful in this case).1. Replace the from address with list address 2. Wrap original message in an envelopethunderbird flags 1 and fails 2. <a href="https://social.masto.host/tags/askfedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#askfedi</a> <a href="https://social.masto.host/tags/gnupg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnupg</a> <a href="https://social.masto.host/tags/gpg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpg</a> <a href="https://social.masto.host/tags/thunderbird" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#thunderbird</a>

Em :official_verified:New Privacy Guides article 🔑✨ by me: If you are using a YubiKey, you might get in some situations where you need to reset your key to factory default, and/or set up a backup of it on a spare key.This tutorial will guide you through each step to reset and back up your YubiKey successfully, with clear instructions and plenty of visual support.I hope you find it helpful!<a href="https://www.privacyguides.org/articles/2025/03/06/yubikey-reset-and-backup/" rel="nofollow noopener noreferrer" target="_blank">https://www.privacyguides.org/articles/2025/03/06/yubikey-reset-and-backup/</a><a href="https://infosec.exchange/tags/PrivacyGuides" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrivacyGuides</a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Yubico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Yubico</a> <a href="https://infosec.exchange/tags/YubiKey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#YubiKey</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/OTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OTP</a> <a href="https://infosec.exchange/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/MFA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MFA</a>

Lars WirzeniusI've made release 0.3.0 of sopass, my command line password manager that uses a Stateless OpenPGP implementation for cryptography.* configuration file * add value from named file or stdin * default to rsop * manual page, built-in help<a href="https://sopass.liw.fi/" rel="nofollow noopener noreferrer" target="_blank">https://sopass.liw.fi/</a><a href="https://toot.liw.fi/tags/sopass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sopass</a> <a href="https://toot.liw.fi/tags/pass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pass</a> <a href="https://toot.liw.fi/tags/passwordManager" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#passwordManager</a> <a href="https://toot.liw.fi/tags/commandLine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commandLine</a> <a href="https://toot.liw.fi/tags/cli" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cli</a> <a href="https://toot.liw.fi/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> <a href="https://toot.liw.fi/tags/statelessOpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#statelessOpenPGP</a> <a href="https://toot.liw.fi/tags/sop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sop</a>

Lars WirzeniusI made a couple of changes to sopass, my command line password manager that uses a Stateless OpenPGP implementation for cryptography.* It no longer creates the configuration file. * It has built-in help for all sub-commands, options, and other command line arguments.There is also a rudimentary manual page.<a href="https://sopass.liw.fi/" rel="nofollow noopener noreferrer" target="_blank">https://sopass.liw.fi/</a><a href="https://toot.liw.fi/tags/paswordManager" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#paswordManager</a> <a href="https://toot.liw.fi/tags/sopass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sopass</a> <a href="https://toot.liw.fi/tags/pass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pass</a> <a href="https://toot.liw.fi/tags/commandLine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commandLine</a> <a href="https://toot.liw.fi/tags/cli" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cli</a> <a href="https://toot.liw.fi/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> <a href="https://toot.liw.fi/tags/cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cryptography</a>

l<a href="https://chaos.social/@sten" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sten</a> > Sign-then-encrypt is also a bit dodgy when combined with certain cipher modes.You probably refer to "MAC-then-encrypt" vulnerabilities (<a href="https://moxie.org/2011/12/13/the-cryptographic-doom-principle.html" rel="nofollow noopener noreferrer" target="_blank">https://moxie.org/2011/12/13/the-cryptographic-doom-principle.html</a>). <a href="https://fosstodon.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> encryption and signatures are not on the level where you need to think about such low-level details. OpenPGP encrypted packets (Symmetrically Encrypted and Integrity Protected Data Packet) add integrity protection after encryption, so encrypted packets are not malleable.

l<a href="https://chaos.social/@sten" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sten</a> <a href="https://fosstodon.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> messages are normally signed then encrypted. E.g. RFC 4880 says "OpenPGP implementations SHOULD compress the message after applying the signature but before encryption.".This is what <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@delta</a> does.This is also written down explicitly in <a href="https://www.ietf.org/archive/id/draft-ietf-lamps-e2e-mail-guidance-17.html#name-encryption-outside-signatur" rel="nofollow noopener noreferrer" target="_blank">https://www.ietf.org/archive/id/draft-ietf-lamps-e2e-mail-guidance-17.html#name-encryption-outside-signatur</a>But you can do whatever suits your application, OpenPGP is used not only for message encryption.

Rivane RasetiansyahInitializing a new project - Interplanetary Markdown. Might explore a <a href="https://fosstodon.org/tags/Web3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Web3</a> (off-chain) approach later for a better experience, but for now, keeping it simple with good old <a href="https://fosstodon.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a>.A censorship-resistant <a href="https://fosstodon.org/tags/Markdown" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Markdown</a> publishing platform, enabling seamless content distribution. Powered by the Interplanetary File System (<a href="https://fosstodon.org/tags/IPFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPFS</a>), ensuring <a href="https://fosstodon.org/tags/blogs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blogs</a>, <a href="https://fosstodon.org/tags/articles" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#articles</a>, and other written content remain accessible and verifiable across the distributed web.<a href="https://github.com/rvnrstnsyh/cupoftea" rel="nofollow noopener noreferrer" target="_blank">https://github.com/rvnrstnsyh/cupoftea</a>

boredsquirrel<a href="https://fosstodon.org/@libreoffice" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@libreoffice</a> The <a href="https://tux.social/tags/Libreoffice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Libreoffice</a> Youtube channel is posting a lot of interesting talks from the "Libreoffice and <a href="https://tux.social/tags/Opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Opensource</a> Conference 2024"Some of them:<a href="https://tux.social/tags/LuxChat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LuxChat</a> for Governments: <a href="https://www.youtube.com/watch?v=JXdMKaEXq0Q" rel="nofollow noopener noreferrer" target="_blank">https://www.youtube.com/watch?v=JXdMKaEXq0Q</a><a href="https://tux.social/tags/OpenDesk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenDesk</a> on <a href="https://tux.social/tags/OpenCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenCode</a>: <a href="https://www.youtube.com/watch?v=rVhAltODe-M" rel="nofollow noopener noreferrer" target="_blank">https://www.youtube.com/watch?v=rVhAltODe-M</a><a href="https://tux.social/tags/Education" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Education</a>: <a href="https://www.youtube.com/watch?v=V4fkWfuFXfo" rel="nofollow noopener noreferrer" target="_blank">https://www.youtube.com/watch?v=V4fkWfuFXfo</a><a href="https://tux.social/tags/Encrypted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encrypted</a> and <a href="https://tux.social/tags/Signed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signed</a> Documents (UI, with <a href="https://tux.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> or <a href="https://tux.social/tags/x509" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#x509</a>): <a href="https://www.youtube.com/watch?v=W-qFr8tL-LE" rel="nofollow noopener noreferrer" target="_blank">https://www.youtube.com/watch?v=W-qFr8tL-LE</a><a href="https://tux.social/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matrix</a> <a href="https://tux.social/tags/Luxembourg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Luxembourg</a>

Anthony Accioly-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256Good afternoon, folks! Just a quick reminder: PGP isn't dead. Sign with pride!Signed with my GPG key: 1BBD C23D 1853 255D 6415 D2EC 814E DF85 1AAB 370E<a href="https://accioly.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://accioly.social/tags/GPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> <a href="https://accioly.social/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cybersecurity</a> <a href="https://accioly.social/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a> <a href="https://accioly.social/tags/DigitalIdentity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DigitalIdentity</a> <a href="https://accioly.social/tags/SignYourCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SignYourCode</a> -----BEGIN PGP SIGNATURE-----iHUEARYIAB0WIQTHaQ+iFRwfaXx+TxhjUbpCCVDiNAUCZ7cd5gAKCRBjUbpCCVDi NOZSAPoDPFoZXKuxya98iY6nAV6hzgOghpqF/OtOVSW4qtEdMQEA3x/jqaD4R9vo qi89wA4Hsd4KeqwTSQxKDECesI+W8QU= =3gty -----END PGP SIGNATURE-----

/dev/LUGGuten Morgen Pinguine! Eine kleine Info / Status update \o/ Ein erster Meilenstein ist erreicht! Ich habe heute einen ersten tag (0.0.1) für libcxmpp erstellt. Es ist nicht viel, aber ein Anfang. <a href="https://devlug.de/social?t=libcxmpp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libcxmpp</a> besteht aus einer kleinen Menge von <a href="https://devlug.de/social?t=gobject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GObject</a> types. Diese sollen eine einfach zu verwendete Schnittstelle für Funktionen rundum <a href="https://devlug.de/social?t=xmpp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a> bereitstellen. Aktuell ist es möglich, dass sich ein Client mit einem XMPP Server verbindet, eine presence schickt. Den roster abfragt und einfach Nachrichten (type chat) senden und empfangen kann. Hierfür habe ich eine Demo Implementierung im Projekt angelegt. Dies sieht dann wie folgt aus. Loading Client Manager... XMPP> connect XMPP Connect - JID> demo@domain.tld XMPP Connect - PWD> 123456 XMPP> Client has been connected with XMPP Server XMPP> presence XMPP> message XMPP Message - JID> stefan@domain.tld XMPP Message - Text> Hallo! Das ist ein Test :) XMPP> Message from stefan@domain.tld/Coffein: Hallo. Die Nachricht ist angekommen. Anwendungsdesign muss ich mir noch mal genauer überlegen. Der ersten Entwurf beinhaltet einen CM (Connection Manager). Der Connection Manager soll alle Accounts und Connections verwalten. Die Connection ist eine funktionale Sicht auf die XMPP Verbindung, währen der XMPP Wrapper die technische Implementierung via <a href="https://devlug.de/social?t=libstrophe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libstrophe</a> bereitstellt. Der Client kann sich mit Signalen verbinden - <a href="https://devlug.de/social?t=signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#signal</a> :-x g_signal_connect_object(connection, "connected", G_CALLBACK(cxmpp_connected), connection, G_CONNECT_SWAPPED); g_signal_connect_object(connection, "new-contact", G_CALLBACK(new_contact), connection, G_CONNECT_SWAPPED); g_signal_connect_object(connection, "new-chat-message", G_CALLBACK(new_chat_message), connection, G_CONNECT_SWAPPED); Ausblick für den nächsten Meilenstein Als Backend solle eine <a href="https://devlug.de/social?t=sqlite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sqlite</a> Datenbank verwendet werden. Verschlüsselung im ersten Schritt mit <a href="https://devlug.de/social?t=openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://devlug.de/social?t=ox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OX</a> via <a href="https://devlug.de/social?t=gnupg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a>. Ziel ist es, dass ich im ersten Schritt die Implementierung von <a href="https://devlug.de/social?t=xmppc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xmppc</a> (ein XMPP command line client) auf <a href="https://devlug.de/social?t=libcxmpp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libcxmpp</a> umstellen kann. Code ist auf <a href="https://devlug.de/social?t=codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codeberg</a> <a href="https://codeberg.org/devLUG/libcxmpp" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/devLUG/libcxmpp</a> Happy chatting! <a href="https://devlug.de/social?t=messenger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Messenger</a> <a href="https://devlug.de/social?t=debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://devlug.de/social?t=gnu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> <a href="https://devlug.de/social?t=linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://devlug.de/social?t=jabber" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Jabber</a>

chimbosonicIntroducing WKD Tester – a free, open-source tool for testing OpenPGP Web Key Directory implementations! I built it to help out with the Keyoxide project, making it easier to generate lookup URIs and discover keys on the fly. Check it out at <a href="https://wkd.chimbosonic.com" rel="nofollow noopener noreferrer" target="_blank">https://wkd.chimbosonic.com</a>.<a href="https://fosstodon.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://fosstodon.org/tags/WKD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WKD</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://fosstodon.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://fosstodon.org/tags/Keyoxide" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keyoxide</a>

Delta ChatIsn't it poetic and ironic that out of all possible time lines we are in one where <a href="https://chaos.social/tags/securejoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#securejoin</a> <a href="https://chaos.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> protocols on top of the existing <a href="https://chaos.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> protocols offer the arguably most solidly scaling, useable, world-wide federated end-to-end encrypted messaging reality, safe against compromised <a href="https://chaos.social/tags/mitm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mitm</a> servers? Hundreds of billions spend to create "the email successor" and here we are in 2025 .... <a href="https://chaos.social/tags/interoperable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#interoperable</a> <a href="https://chaos.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> and <a href="https://chaos.social/tags/cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cryptography</a> as the tortoise looking at Achilles through the back mirror :)

Todd A. Jacobs | RubyistI’m *trying* to like <a href="https://ruby.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> again, but PEP-761 requires <a href="https://ruby.social/tags/sigstore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sigstore</a>. <a href="https://ruby.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> key management has issues, but this requires trusting <a href="https://ruby.social/tags/openidconnect" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openidconnect</a> from <a href="https://ruby.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> & <a href="https://ruby.social/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a>. Plus there’s a stated design goal of supporting automated signatures from private keys held by <a href="https://ruby.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a>.Easier? Probably. Safer? Probably not. Security is about trust and the required certificate authorities haven’t earned mine over the past 20 years. As always, YMMV.<a href="https://peps.python.org/pep-0761/" rel="nofollow noopener noreferrer" target="_blank">https://peps.python.org/pep-0761/</a>

Kevin Karhan :verified:<a href="https://jorts.horse/@kobilacroix" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kobilacroix</a> also <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> is used as a means to identify espionage and manipulation attempts and enable quicjer fixing if security issues.And that works not only for <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a>, but <a href="https://infosec.space/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a>, <a href="https://infosec.space/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSSL</a>, <a href="https://infosec.space/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSSH</a>, <a href="https://infosec.space/tags/OpenVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenVPN</a>, <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>, ...In fact, <a href="https://infosec.space/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a>'s security is based upon <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openness</a>, <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> and <a href="https://infosec.space/tags/KISSprinciple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KISSprinciple</a>'d design.Not to mention <a href="https://infosec.space/tags/Monero" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Monero</a> is really frustrating the U.S. Govt. (espechally IRS) because it is <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> and with basically billions in value locked in, every cryptographer of every major state and non-state actor is trying to exploit it.That's the strenght of <a href="https://infosec.space/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a>:With every commit and every line if cide beibg public, noone can get away with <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Govware</a>-<a href="https://infosec.space/tags/Backdoors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backdoors</a> ob most stuff as they do constantly with <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a>!Cuz you can be shure everytime someone from NSA, CIA, GAFAMs, Huawei, etc. even commits a single line to linux or requests a merge there are countless people literally waiting to find a reason to say no and evidence it's a <a href="https://infosec.space/tags/backdoor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backdoor</a> of some kind.

Verwaltet von:

Serverstatistiken:

Aktuelle Trends

Verwaltet von:

Serverstatistiken:

OpenPGPZurück

Aktuelle Trends