MastodonTech.de

adb<a href="https://infosec.exchange/@pancake" class="u-url mention" rel="nofollow noopener" target="_blank">@pancake</a> every post, comment and like in the social network is <a href="https://mastodon.social/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#e2ee</a> thanks to <a href="https://mastodon.social/tags/DeltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeltaChat</a>, the container super-app, but if you want forward-secrecy-secure ephemeral <a href="https://mastodon.social/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> communications inside a Delta Chat chat, there is the "Live Chat" mini-app in the store (IRC style plus /me and "foo is typing..." support!!) <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a>

xoron :verified:<a href="https://glitr.io" rel="nofollow noopener" translate="no" target="_blank">https://glitr.io</a>im looking for feedback on my project.IMPORTANT NOTES (PLEASE READ!): * this is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#demonstration</a> purposes only. * It has NOT been reviewed or audited. Do NOT use for sensitive data. * All functionality demonstrated is experimental. * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/magicwormhole" class="mention hashtag" rel="nofollow noopener" target="_blank">#magicwormhole</a> <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> <a href="https://infosec.exchange/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#e2ee</a> <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypted</a> <a href="https://infosec.exchange/tags/pwa" class="mention hashtag" rel="nofollow noopener" target="_blank">#pwa</a> <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://infosec.exchange/tags/filetransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#filetransfer</a> <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#webrtc</a> <a href="https://infosec.exchange/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#secure</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a>

Open Rights GroupMake our voice heard at the Apple encryption hearing!On the sly, the UK government tried to force a backdoor into the firewall that protects your privacy. We made the hearing public.Now we need to win in court ✊Donate now to fund legal representation ⬇️<a href="https://action.openrightsgroup.org/make-our-voice-heard-apple%E2%80%99s-encryption-hearing" rel="nofollow noopener" translate="no" target="_blank">https://action.openrightsgroup.org/make-our-voice-heard-apple%E2%80%99s-encryption-hearing</a><a href="https://social.openrightsgroup.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#e2ee</a> <a href="https://social.openrightsgroup.org/tags/apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#apple</a> <a href="https://social.openrightsgroup.org/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a> <a href="https://social.openrightsgroup.org/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://social.openrightsgroup.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://social.openrightsgroup.org/tags/ukpolitics" class="mention hashtag" rel="nofollow noopener" target="_blank">#ukpolitics</a> <a href="https://social.openrightsgroup.org/tags/ukpol" class="mention hashtag" rel="nofollow noopener" target="_blank">#ukpol</a> <a href="https://social.openrightsgroup.org/tags/crowdfunder" class="mention hashtag" rel="nofollow noopener" target="_blank">#crowdfunder</a> <a href="https://social.openrightsgroup.org/tags/surveillance" class="mention hashtag" rel="nofollow noopener" target="_blank">#surveillance</a> <a href="https://social.openrightsgroup.org/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>

Jon YoderIt's been quite some time since I posted about <a href="https://mstdn.social/tags/Mensago" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mensago</a>, and there's good reason: <a href="https://mstdn.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> device sync is HARD. *sigh*It's frustrating because once device sync is out of the way, I can get user-facing stuff like replying to messages going and try to get this thing out the door.

Ian Brown 👨🏻‍💻WOW! <a href="https://eupolicy.social/tags/Beeper" class="mention hashtag" rel="nofollow noopener" target="_blank">#Beeper</a> goes <a href="https://eupolicy.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> (and MUCH more) 👏🔥😍 <a href="https://eupolicy.social/tags/UniversalInbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#UniversalInbox</a> <a href="https://blog.beeper.com/2025/07/16/the-new-beeper/" rel="nofollow noopener" translate="no" target="_blank">https://blog.beeper.com/2025/07/16/the-new-beeper/</a>

StrypeyNew <a href="https://mastodon.nzoss.nz/tags/Disintermedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Disintermedia</a> blog post, on the challenges of keeping communications private in networked software; <a href="https://disintermedia.substack.com/p/get-a-room" rel="nofollow noopener" translate="no" target="_blank">https://disintermedia.substack.com/p/get-a-room</a>As I say at the outset, I am not a security professional, and this is not security advice. I’m just an old school Direct Action activist and indymediatista, with some information to add to the mix. Add a grain of salt and stir well.<a href="https://mastodon.nzoss.nz/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://mastodon.nzoss.nz/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a>

Kevin Karhan :verified:I mean, these ain't like in the old days where a few Megabytes got you <a href="https://infosec.space/tags/Pidgin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pidgin</a> and other <a href="https://en.wikipedia.org/wiki/Comparison_of_cross-platform_instant_messaging_clients" rel="nofollow noopener" target="_blank">Multi-Protocol Clients</a> of the old days where everyone had to implement bespoke, custom and incompatible and *often completely undocumented, proprietary * protocols like <a href="https://infosec.space/tags/ICQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#ICQ</a>, <a href="https://infosec.space/tags/AIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#AIM</a>, <a href="https://infosec.space/tags/SIPE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIPE</a>, etc.<ul><li>Nowadays all these do have some kind of <a href="https://infosec.space/tags/WebApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebApp</a> or Web Interface one can just login (because *none of them do proper <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> of all the keys!) so this should be way easier these days: All they do is do HTTP(S) GET/POST so the most critical part is to attain credentials like a <a href="https://infosec.space/tags/Login" class="mention hashtag" rel="nofollow noopener" target="_blank">#Login</a> <a href="https://infosec.space/tags/cookie" class="mention hashtag" rel="nofollow noopener" target="_blank">#cookie</a> and to basically run a console on i.e. <a href="https://infosec.space/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firefox</a> to reverse-engineer the <a href="https://infosec.space/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#API</a>...</li></ul>

9x0rg<a href="https://tux.social/@Rhababerbarbar" class="u-url mention" rel="nofollow noopener" target="_blank">@Rhababerbarbar</a>[Correction]: LeastAuthority [1] implements a web application of <a href="https://mamot.fr/tags/MagicWormhole" class="mention hashtag" rel="nofollow noopener" target="_blank">#MagicWormhole</a> called <a href="https://mamot.fr/tags/Winden" class="mention hashtag" rel="nofollow noopener" target="_blank">#Winden</a>, available at <a href="https://winden.app/s" rel="nofollow noopener" translate="no" target="_blank">https://winden.app/s</a>. Haven't used it though.<a href="https://io.mwl.io/@mwl" class="u-url mention" rel="nofollow noopener" target="_blank">@mwl</a> <a href="https://mas.to/@alternativeto" class="u-url mention" rel="nofollow noopener" target="_blank">@alternativeto</a> [1]: <a href="https://github.com/LeastAuthority/winden" rel="nofollow noopener" translate="no" target="_blank">https://github.com/LeastAuthority/winden</a><a href="https://mamot.fr/tags/WeTransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#WeTransfer</a> <a href="https://mamot.fr/tags/DataPrivacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataPrivacy</a> <a href="https://mamot.fr/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#Encryption</a> <a href="https://mamot.fr/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a>

9x0rgHi <a href="https://tux.social/@Rhababerbarbar" class="u-url mention" rel="nofollow noopener" target="_blank">@Rhababerbarbar</a>Agreed.Magic Wormhole [1] uses a PAKE construction to ensure high-security, end-to-end encryption with human-sized codes. It is a peer-to-peer protocol that requires both the sender and recipient to have it running, which can be less convenient than `Send`, for instance. It works great. A list of available clients can be found here [2].<a href="https://io.mwl.io/@mwl" class="u-url mention" rel="nofollow noopener" target="_blank">@mwl</a> <a href="https://mas.to/@alternativeto" class="u-url mention" rel="nofollow noopener" target="_blank">@alternativeto</a> [1]: <a href="https://github.com/warner/magic-wormhole" rel="nofollow noopener" translate="no" target="_blank">https://github.com/warner/magic-wormhole</a> [2]: <a href="https://magic-wormhole.readthedocs.io/en/latest/ecosystem.html#end-user-client-applications" rel="nofollow noopener" translate="no" target="_blank">https://magic-wormhole.readthedocs.io/en/latest/ecosystem.html#end-user-client-applications</a><a href="https://mamot.fr/tags/WeTransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#WeTransfer</a> <a href="https://mamot.fr/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> <a href="https://mamot.fr/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#Encryption</a> <a href="https://mamot.fr/tags/DataPrivacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataPrivacy</a>

zeitkapsl.eu👤 Face recognition is almost here — and it’s built the zeitkapsl way:🔍 Find and group photos by people 🔐 Fully end-to-end encrypted 📱 Runs locally on your phone 🛑 No cloud processing, no leaks🙏 Sorry it takes a bit longer we expected, but it's worth the wait.Here’s a first look at what’s coming. 👇<a href="https://mastodon.social/tags/zeitkapsl" class="mention hashtag" rel="nofollow noopener" target="_blank">#zeitkapsl</a> <a href="https://mastodon.social/tags/facerecognition" class="mention hashtag" rel="nofollow noopener" target="_blank">#facerecognition</a> <a href="https://mastodon.social/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#e2ee</a> <a href="https://mastodon.social/tags/privacyfirst" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacyfirst</a> <a href="https://mastodon.social/tags/photobackup" class="mention hashtag" rel="nofollow noopener" target="_blank">#photobackup</a> <a href="https://mastodon.social/tags/madeineu" class="mention hashtag" rel="nofollow noopener" target="_blank">#madeineu</a> <a href="https://mastodon.social/tags/europeanalternatives" class="mention hashtag" rel="nofollow noopener" target="_blank">#europeanalternatives</a>

Marcel Waldvogel7️⃣ Gleich mehrere Artikel der letzten Tage beschäftigen sich mit der Sicherheit von Ende-zu-Ende-verschlüsselten Messengern wie <a href="https://waldvogel.family/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> oder <a href="https://waldvogel.family/tags/Threema" class="mention hashtag" rel="nofollow noopener" target="_blank">#Threema</a>.Alle laufen darauf hinaus, dass der Firmen- oder Serverstandort eigentlich keine Rolle spielt, wenn die Verschlüsselung und der Client sicher sind.Wir von <a href="https://waldvogel.family/tags/DNIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNIP</a> sehen das grundsätzlich auch so. Aber natürlich gibt es noch ein paar Rahmenbedingungen, die man durch <a href="https://waldvogel.family/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> nicht wegbekommt. Lest selbst.<a href="https://dnip.ch/2025/07/15/dnip-briefing-33-mcpasswort-mit-sicherheitsluecke/#Bei-einem-sicheren-Messenger-ist-der-Server-irrelevant" rel="nofollow noopener" translate="no" target="_blank">https://dnip.ch/2025/07/15/dnip-briefing-33-mcpasswort-mit-sicherheitsluecke/#Bei-einem-sicheren-Messenger-ist-der-Server-irrelevant</a>

ThePfromtheO<a href="https://infosec.exchange/@Em0nM4stodon" class="u-url mention" rel="nofollow noopener" target="_blank">@Em0nM4stodon</a> <a href="https://social.vivaldi.net/tags/VivaldiBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#VivaldiBrowser</a> does have both! <a href="https://social.vivaldi.net/tags/endToEndEncryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#endToEndEncryption</a> and <a href="https://social.vivaldi.net/tags/NoAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#NoAI</a>! <a href="https://social.vivaldi.net/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> <a href="https://social.vivaldi.net/tags/no_ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#no_ai</a> <a href="https://social.vivaldi.net/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://social.vivaldi.net/tags/dataPrivacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataPrivacy</a> <a href="https://social.vivaldi.net/tags/DataProtection" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataProtection</a> <a href="https://social.vivaldi.net/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://social.vivaldi.net/tags/AIcrap" class="mention hashtag" rel="nofollow noopener" target="_blank">#AIcrap</a> <a href="https://social.vivaldi.net/tags/European" class="mention hashtag" rel="nofollow noopener" target="_blank">#European</a> <a href="https://social.vivaldi.net/tags/VivaldiTechnologies" class="mention hashtag" rel="nofollow noopener" target="_blank">#VivaldiTechnologies</a> <a href="https://social.vivaldi.net/tags/Vivaldi" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vivaldi</a>

maexchen1<a href="https://toot.teckids.org/@nik" class="u-url mention" rel="nofollow noopener" target="_blank">@nik</a> Für <a href="https://nrw.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> Emails die nicht bei <a href="https://nrw.social/tags/gmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#gmail</a> landen wird dem Empfänger ein Code übermittelt, lese ich aus den Anleitungen. <a href="https://nerdculture.de/@ulfi" class="u-url mention" rel="nofollow noopener" target="_blank">@ulfi</a>

maexchen1Ich lese gerade vermehrt das <a href="https://nrw.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> <a href="https://nrw.social/tags/Gmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gmail</a> die Inhalte von empfangenen <a href="https://nrw.social/tags/Emails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Emails</a> verändert.Wie geht das wenn <a href="https://nrw.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> selber schreibt das sie wegen der <a href="https://nrw.social/tags/EndeZuEndeVerschl%C3%BCsselung" class="mention hashtag" rel="nofollow noopener" target="_blank">#EndeZuEndeVerschlüsselung</a> keinen Zugriff auf die <a href="https://nrw.social/tags/Emails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Emails</a> hat? Nachtrag Bild.Es scheint nicht bekannt zu sein das Gmail <a href="https://nrw.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> kann.<a href="https://nrw.social/tags/Datenschutz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Datenschutz</a> <a href="https://nrw.social/tags/digitalcourage" class="mention hashtag" rel="nofollow noopener" target="_blank">#digitalcourage</a>

Hans-Christoph SteinerDoes anyone know of any <a href="https://social.librem.one/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> implementations of the <a href="https://social.librem.one/tags/RCS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RCS</a> encrypted messaging protocol? There is the nine year old <a href="https://github.com/android-rcs/rcsjta" rel="nofollow noopener" target="_blank">https://github.com/android-rcs/rcsjta</a> I wonder if that is usable?<a href="https://social.librem.one/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> <a href="https://social.librem.one/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> <a href="https://social.librem.one/tags/messaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#messaging</a>

khaleesi (Elina Eickstädt)<a href="https://eupolicy.social/tags/Chatkontrolle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chatkontrolle</a> Mit <a href="https://chaos.social/@Chatgeheimnis" class="u-url mention" rel="nofollow noopener" target="_blank">@Chatgeheimnis</a> sind wir weiter zusammen dran. Einen guten Überblick findet ihr hier: <a href="https://chat-kontrolle.eu/index.php/2025/07/08/neuer-anlauf-zur-chatkontrolle/" rel="nofollow noopener" translate="no" target="_blank">https://chat-kontrolle.eu/index.php/2025/07/08/neuer-anlauf-zur-chatkontrolle/</a>Wenn ihr Organisationen kennt die sich dem Büdnis anschließen sollten immer her damit. Wir setzen uns für den Schutz von <a href="https://eupolicy.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> ein egal ob <a href="https://eupolicy.social/tags/Chatkontrolle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chatkontrolle</a> oder <a href="https://eupolicy.social/tags/ProtectEU" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProtectEU</a>

StrypeyHey <a href="https://mastodon.matrix.org/@matrix" class="u-url mention" rel="nofollow noopener" target="_blank">@matrix</a>, given recent events around the world, I think it would be really helpful to have a regularly reviewed security status page on your website, summarising all known information affecting the security of the Matrix protocol. Threat models, security audits, disclosed vulnerabilities and mitigations, etc.If such a thing already exists, please link me!Oh and <a href="https://mastodon.matrix.org/@element" class="u-url mention" rel="nofollow noopener" target="_blank">@element</a>, same for you and the software you steward.<a href="https://mastodon.nzoss.nz/tags/chat" class="mention hashtag" rel="nofollow noopener" target="_blank">#chat</a> <a href="https://mastodon.nzoss.nz/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> <a href="https://mastodon.nzoss.nz/tags/Matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Matrix</a> <a href="https://mastodon.nzoss.nz/tags/SecurityStatus" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityStatus</a>

Strypey"This article charts the privacy–public safety debate with a focus on its relevance to a sound philosophical, legal and ethical position on E2EE for Aotearoa New Zealand’s legal system ... Ultimately, Aotearoa New Zealand should adopt a technologically and legally defensible position rather than enacting emotionally clouded emergency legislation in the wake of a crisis exacerbated by E2EE."<a href="https://mastodon.nzoss.nz/tags/BejaminChristy" class="mention hashtag" rel="nofollow noopener" target="_blank">#BejaminChristy</a>, Public Interest Law Journal of New Zealand, 2022<a href="https://www.auckland.ac.nz/en/law/our-research/research-publications/piljnz/past-issues.html" rel="nofollow noopener" translate="no" target="_blank">https://www.auckland.ac.nz/en/law/our-research/research-publications/piljnz/past-issues.html</a><a href="https://mastodon.nzoss.nz/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> <a href="https://mastodon.nzoss.nz/tags/PILJNZ" class="mention hashtag" rel="nofollow noopener" target="_blank">#PILJNZ</a>

Deutschland<a href="https://www.europesays.com/de/248172/" rel="nofollow noopener" translate="no" target="_blank">https://www.europesays.com/de/248172/</a> „Beispielloser Angriff“: Bürgerrechtler reagieren auf iCloud-Anordnung in UK <a href="https://pubeurope.com/tags/AktuelleNachrichten" class="mention hashtag" rel="nofollow noopener" target="_blank">#AktuelleNachrichten</a> <a href="https://pubeurope.com/tags/AktuelleNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#AktuelleNews</a> <a href="https://pubeurope.com/tags/CryptoWars" class="mention hashtag" rel="nofollow noopener" target="_blank">#CryptoWars</a> <a href="https://pubeurope.com/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> <a href="https://pubeurope.com/tags/Headlines" class="mention hashtag" rel="nofollow noopener" target="_blank">#Headlines</a> <a href="https://pubeurope.com/tags/iCloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#iCloud</a> <a href="https://pubeurope.com/tags/Nachrichten" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nachrichten</a> <a href="https://pubeurope.com/tags/Netzpolitik" class="mention hashtag" rel="nofollow noopener" target="_blank">#Netzpolitik</a> <a href="https://pubeurope.com/tags/News" class="mention hashtag" rel="nofollow noopener" target="_blank">#News</a> <a href="https://pubeurope.com/tags/Schlagzeilen" class="mention hashtag" rel="nofollow noopener" target="_blank">#Schlagzeilen</a> <a href="https://pubeurope.com/tags/UK" class="mention hashtag" rel="nofollow noopener" target="_blank">#UK</a> <a href="https://pubeurope.com/tags/UnitedKingdom" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitedKingdom</a> <a href="https://pubeurope.com/tags/UnitedKingdomOfGreatBritainAndNorthernIreland" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitedKingdomOfGreatBritainAndNorthernIreland</a> <a href="https://pubeurope.com/tags/VereinigtesK%C3%B6nigreich" class="mention hashtag" rel="nofollow noopener" target="_blank">#VereinigtesKönigreich</a> <a href="https://pubeurope.com/tags/VereinigtesK%C3%B6nigreichGro%C3%9FbritannienUndNordirland" class="mention hashtag" rel="nofollow noopener" target="_blank">#VereinigtesKönigreichGroßbritannienUndNordirland</a> <a href="https://pubeurope.com/tags/VereinigtesK%C3%B6nigreichVonGrossbritannienUndNordirland" class="mention hashtag" rel="nofollow noopener" target="_blank">#VereinigtesKönigreichVonGrossbritannienUndNordirland</a> <a href="https://pubeurope.com/tags/Verschl%C3%BCsselung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Verschlüsselung</a>

Em :official_verified:Magical backdoor only for "the good guys" is a complete fantasy 🔑✨Let's say the strategy is akin to creating a MagicalKey that unlocks every door (a magical key because thinking encryption backdoors would only be used by "the good guys" is a great example of magical thinking).Imagine only 1000 police officers have MagicalKeys. Overtime, let's say only 1% of the police officers accidentally lose their MagicalKey. Now 10 MagicalKeys are lost in the wild and could be used by anyone else, for any purposes, including crime.Then, let's say only 0.1% of police officers get corrupted by a crime gang. That's just one right? This corrupted "good guy" lets the gang create a double of the MagicalKey. Which crime gang wouldn't want a key that can magically open any door? Now, the gang creates doubles of the MagicalKey they have. They use it subtly at first to avoid detection. They make sure they never leave traces behind, so victims have no idea their door got unlocked.During this time, they steal your data, they sell it, they use it to impersonate you, they use it to harm you and your loved ones.Then, another criminal figures out on their own how to emulate a MagicalKey without even having access to one. The criminal creates a reproducible mold for this Emulated-MagicalKey and sells it to other criminals on the criminal market. Now, the MagicalKey™️ is available to any criminals looking for it. Restrictions on the backdoor are off. Your personal data is up for grabs.This is what is going to happen if backdoors are implemented in end-to-end encryption. But don't worry they say, "it's only for the good guys!".At least, the criminals' data will also be up for grabs, right?Nope! The criminals knew about this, so they just started using different channels that weren't impacted. Criminals will have their privacy intact, they don't care about using illegal tools, but your legal privacy protections will be gone.Backdoored end-to-end encryption isn't end-to-end anymore, it's just open-ended encryption. This offers pretty much no protection at all.Extract from: <a href="https://www.privacyguides.org/articles/2025/04/11/encryption-is-not-a-crime/" rel="nofollow noopener" translate="no" target="_blank">https://www.privacyguides.org/articles/2025/04/11/encryption-is-not-a-crime/</a><a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> <a href="https://infosec.exchange/tags/RootForE2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#RootForE2EE</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#e2ee