social.bund.de

0 posts0 participants0 posts today

GeorgAuch diesen Monat gibt es am 4ten Donnerstag eine <a href="https://digitalcourage.social/tags/CryptoParty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CryptoParty</a> in <a href="https://digitalcourage.social/tags/Augsburg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Augsburg</a>. Thema ist diesmal: E-Mail-Verschlüsselung auf PC und Handy. Wie immer 19 Uhr (Donnerstag, 24.04.2025), im <a href="https://digitalcourage.social/tags/OpenLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenLab</a>, Bäckergasse 32.Bringt bitte eure Freundinnen/Freunde mit. Eintritt frei. Keine Vorkenntnisse erforderlich.<a href="https://cryptoparty.in/augsburg" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://cryptoparty.in/augsburg</a><a href="https://digitalcourage.social/tags/Medienkompetenz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Medienkompetenz</a> <a href="https://digitalcourage.social/tags/Digitalisierung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Digitalisierung</a> <a href="https://digitalcourage.social/tags/verschlusselung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#verschlusselung</a> <a href="https://digitalcourage.social/tags/Openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Openpgp</a>

l<a href="https://mastodon.social/@eff" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@eff</a> <a href="https://hachyderm.io/@evacide" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@evacide</a> GnuPG is not the only way to encrypt email, I use <a href="https://fosstodon.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> with Thunderbird and <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@delta</a>, both don't use GPG.Also pages <a href="https://ssd.eff.org/module/how-use-pgp-linux" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ssd.eff.org/module/how-use-pgp-linux</a> and <a href="https://ssd.eff.org/module/how-use-pgp-windows" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ssd.eff.org/module/how-use-pgp-windows</a> are outdated, Thunderbird now has built-in OpenPGP implementation and Enigmail does not work with the latest versions.

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? :)

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" translate="no" 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>

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" translate="no" 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" translate="no" 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" translate="no" 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" translate="no" 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" translate="no" 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>

StefanOpenPGP. Vielleicht, weil 1) Eine <a href="https://devlug.de/social?t=openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> Software (z.b. <a href="https://devlug.de/social?t=gnupg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a>) nicht standardmäßig vorinstalliert ist 2) nicht alle Anbieter Web Key Directory (WKD) anbieten 3) Viele nicht wissen, dass es existiert und für was sie es gebrauchen könnten CC: <a href="https://social.bund.de/users/bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bsi@social.bund.de</a>

David Sardari<a href="https://fedifreu.de/tags/ePA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ePA</a> und <a href="https://fedifreu.de/tags/ePerso" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ePerso</a> lasse/ließ ich gut abhängen. Wenn es nach einiger Zeit bekömmlich ist, lasse ich mich drauf ein.Demnächst wird mein <a href="https://fedifreu.de/tags/Personalausweis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Personalausweis</a> erstmalig mit aktiver <a href="https://fedifreu.de/tags/ePerso" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ePerso</a> Funktionalität ausgestellt, sodass mein <a href="https://fedifreu.de/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> Schlüssel endlich beglaubigt werden kann: <a href="https://pgp.governikus.de/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://pgp.governikus.de/</a>

Gharbeia, ⒶIst es jemandem gelungen, seinen <a href="https://mastodon.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a>-Schlüssel über <a href="https://pgp.governikus.de" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://pgp.governikus.de</a> mit <a href="https://mastodon.social/tags/AusweisApp2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AusweisApp2</a> zu zertifizieren? Ich erhalte immer wieder die Fehlermeldung „Ausweisvorgang fehlgeschlagen“, die bei näherer Betrachtung intern als „Workflow_TrustedChannel_Server_Format_Error“ beschrieben zu werden scheint, da „PathSecurity-Protocol is no valid URI“<a href="https://mastodon.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://mastodon.social/tags/BSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSI</a> <a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bsi</a>

samuel<a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bsi</a> digital signieren mit <a href="https://sueden.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a>

Pixelcode 🇺🇦You may have noticed I updated my <a href="https://social.tchncs.de/tags/Keyoxide" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keyoxide</a> profile link in various places. That was legit – my old RSA <a href="https://social.tchncs.de/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> had expired back in early November without me noticing, and yesterday, I created a new <a href="https://social.tchncs.de/tags/ed25519" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ed25519</a> key. If you still see my old Keyoxide link somewhere, please tell me. <a href="https://social.tchncs.de/tags/pgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pgp</a> <a href="https://social.tchncs.de/tags/rsa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rsa</a>🔗 <a href="https://keyoxide.org/FEF07E34F003F58EF486E744A49FCA80F5B7DE61" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://keyoxide.org/FEF07E34F003F58EF486E744A49FCA80F5B7DE61</a>First, however, I had to manually update <a href="https://social.tchncs.de/tags/GPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> 2.4 by compiling it from source. 🤡🔗 <a href="https://www.procustodibus.com/blog/2023/02/gpg-2-4-on-ubuntu-22-04/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.procustodibus.com/blog/2023/02/gpg-2-4-on-ubuntu-22-04/</a>QT <a href="https://fed.brid.gy/r/https://bsky.app/profile/did:plc:dxkyhpbv4bsktz3x2yp6m2rz/post/3lcvpgpgnu22j" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fed.brid.gy/r/https://bsky.app/profile/did:plc:dxkyhpbv4bsktz3x2yp6m2rz/post/3lcvpgpgnu22j</a>

c't Magazinheise+ | OpenPGP im Umbruch: Implementierungen, bessere Standards und ein großer StreitDie OpenPGP-Community modernisiert E-Mail-Sicherheit, doch nach Streitigkeiten der Arbeitsgruppe entstehen nun zwei zueinander inkompatiblen Standards.<a href="https://www.heise.de/hintergrund/OpenPGP-im-Umbruch-Implementierungen-bessere-Standards-und-ein-grosser-Streit-9790850.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.heise.de/hintergrund/OpenPGP-im-Umbruch-Implementierungen-bessere-Standards-und-ein-grosser-Streit-9790850.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon</a><a href="https://social.heise.de/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://social.heise.de/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://social.heise.de/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://social.heise.de/tags/Standards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Standards</a> <a href="https://social.heise.de/tags/Verschl%C3%BCsselung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Verschlüsselung</a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a>

heise Security"Passwort" Folge 2: Geheime NachrichtenIm neuen Podcast von heise Security reden Christopher Kunz und Sylvester Tremmel über moderne und weniger moderne Lösungen zur sicheren Kommunikation.<a href="https://www.heise.de/news/Passwort-Folge-2-Geheime-Nachrichten-9745961.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.heise.de/news/Passwort-Folge-2-Geheime-Nachrichten-9745961.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon</a><a href="https://social.heise.de/tags/Verschl%C3%BCsselung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Verschlüsselung</a> <a href="https://social.heise.de/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://social.heise.de/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a> <a href="https://social.heise.de/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a>

BDM (BeautifulDowntownMannheim)Hi <a href="https://xn--baw-joa.social/users/lfdi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lfdi</a> 👋. <a href="https://freude.social/users/alvar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alvar</a>spricht etwas dagegen, euren öffentlichen <a href="https://squeet.me/search?tag=OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> Schlüssel auf <a href="https://keys.openpgp.org" rel="nofollow noopener noreferrer" target="_blank">keys.openpgp.org</a> zu laden und die E-Mail-Adresse zu verifizieren?Eine Suche nach poststelle@lfd.bwl.de bringt aktuell leider keinen Treffer.Klar, Schlüssel liegt unter <a href="https://www.baden-wuerttemberg.datenschutz.de/kontakt-aufnehmen" rel="nofollow noopener noreferrer" target="_blank">baden-wuerttemberg.datenschutz…</a> ab, aber einfacher wäre es, wenn er auch leicht vom Schlüsselserver zu beziehen wäre.PS: Danke für euer Fediverse und PeerTube Angebot für Behörden und Verwaltungen im Land. Ohne das würde Stadt Mannheim vermutlich sonst immer noch nur auf Twitter rumgeistern 🤦

Kevin Karhan :verified:Hey, <a href="https://social.bund.de/@BaFin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BaFin</a> / <a href="https://social.bund.de/@Bundesregierung" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Bundesregierung</a>, ist es gewollt dass eure <a href="https://www.bafin.de/SharedDocs/Kontaktdaten/DE/BaFin/Kontakt/Kontakt_BaFin_IF.html" rel="nofollow noopener noreferrer" target="_blank">"Abteilung Integrität des Finanzsystems" (IF) </a> keine <a href="https://infosec.space/tags/sichere" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sichere</a> = <a href="https://infosec.space/tags/EndeZuEndeVerschl%C3%BCsselte" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EndeZuEndeVerschlüsselte</a> <a href="https://infosec.space/tags/Kommunikation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kommunikation</a> ermöglicht? Weil weder eure <a href="https://www.bafin.de/DE/DieBaFin/Kontakt/GesicherteKommunikation/gesicherte_kommunikation_node.html" rel="nofollow noopener noreferrer" target="_blank">Zertifikat-Selbstbedienung</a> noch eurer <a href="https://secmail.bafin.de/web.app" rel="nofollow noopener noreferrer" target="_blank">Keyserver</a> spucken mir den <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a>-Key für diese aus...<a href="https://infosec.space/tags/getcertificate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#getcertificate</a> <a href="https://infosec.space/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://infosec.space/tags/GPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> <a href="https://infosec.space/tags/GnuPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a> <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> <a href="https://infosec.space/tags/SicherKommiunikation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SicherKommiunikation</a> <a href="https://infosec.space/tags/Datenschutz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Datenschutz</a> <a href="https://infosec.space/tags/Informationssicherheit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Informationssicherheit</a> <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITsec</a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InfoSec</a> <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ComSec</a>

M. K. BrollImmer mal wieder habe ich das Bedürfnis, privat verschlüsselte <a href="https://gruene.social/tags/eMails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eMails</a> per <a href="https://gruene.social/tags/openPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openPGP</a> zu verschicken. Nach 10 Jahren Pause habe ich mir mal wieder die Voraussetzungen dazu durchgelesen. Und nach einer halben Stunde den Deckel wieder zugeklappt. Ich verstehe nicht, warum die EU nach 25 Jahren email-Verschlüsselung mit einem offenen Standard immer noch nicht zum Pflichtangebot für die Staaten mit seinen Behörden gemacht hat. Stattdessen gibt es in Deutschland das tote Pferd de-mail. Unfassbar.

JanGestern habe ich meinen <a href="https://social.tchncs.de/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> Schlüssel über den Anbieter <a href="https://social.tchncs.de/tags/Governikus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Governikus</a> beglaubigen lassen. Zuvor habe ich die <a href="https://social.tchncs.de/tags/AusweisApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AusweisApp</a> auf meinem Smartphone (App gibts in <a href="https://social.tchncs.de/tags/Fdroid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fdroid</a>!) und in <a href="https://social.tchncs.de/tags/Arch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Arch</a> Linux installiert. Das war auch das erste Mal für mich, dass ich die Online-Ausweisfunktion von meinem <a href="https://social.tchncs.de/tags/Personalausweis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Personalausweis</a> benutzt habe. Hat gut und schnell funktioniert. Und die Beglaubigung war überdies kostenlos.<a href="https://pgp.governikus.de/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://pgp.governikus.de/</a><a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bsi</a>

Kevin Karhan :verified:<a href="https://social.bund.de/@hib_Nachrichten" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hib_Nachrichten</a> ja, dafür gibt's Standards wie <a href="https://mstdn.social/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a>/MIME & <a href="https://mstdn.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> seit Ewigkeiren.

PGPkeys EUThe project leader of <a href="https://infosec.exchange/tags/gnupg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnupg</a> has announced a fork of the <a href="https://infosec.exchange/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> standard, justifying it with a list of accusations against the <a href="https://infosec.exchange/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> working group that fall apart under scrutiny. <a href="https://infosec.exchange/tags/pgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pgp</a> is being threatened with destruction over a personal grievance. We strongly urge de-escalation.<a href="https://blog.pgpkeys.eu/critique-critique" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.pgpkeys.eu/critique-critique</a>

PGPkeys EUThe pgpkeys.eu test swarm (a set of four containerised hockeypuck keyservers) is now running the hockeypuck 2.2 development branch, to test eventual consistency. Waiting to see if they will stabilise overnight. 🤞Hockeypuck 2.2 will include several updates:* drop support for deprecated algorithms (and therefore sync compatibility with sks-keyserver) * drop support for images * delete UIDs from hard-revoked keys * implement timestamp-aware merge strategy * experimental support for v5 and v6 <a href="https://infosec.exchange/tags/pgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pgp</a> keysDropping sks-keyserver backwards compatibility should get rid of several long-running sync issues. Hockeypuck validates self-sigs but sks-keyserver does not, and maintaining sync consistency with sks-keyserver means storing and propagating unverifiable self-sigs made with unsupported algorithms (in particular elGamal encrypt-and-sign and RSA1024, which are long deprecated). This has never worked reliably, and sks-keyserver compatibility is no longer a priority for the keyserver operators. Removing this support also significantly simplifies the code.Dropping support for images will reduce the storage footprint of a keyserver, and will eliminate an obvious abuse vector. Hard (i.e. retrospective) revocation of a key (e.g. by publishing the revocation certificate saved at key generation time) will cause all User IDs attached to that key to be deleted. This allows key owners to remove their personal information from the entire keyserver network without having to contact individual operators (which can still be done, your rights are not affected). The timestamp-aware merge strategy will allow key owners to remove spammy third-party signatures from their published key by creating a fresh self-signature (e.g. by updating the expiry date) and republishing. This works similarly to attestation signatures, but is compatible with clients that don’t yet support attestations. v5 (GnuPG) and v6 (RFC9760?) signatures will soon start appearing in the wild. Several changes will need to be made in the codebase to enable support to be added in the future.These vital developments will help keep the <a href="https://infosec.exchange/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> keyserver network stable, relevant, and compliant, into the foreseeable future.

Recent searches

Search options

Administered by:

Server stats:

#openpgp