beige.party

24 posts17 participants0 posts today

René Mayrhofer :verified: 🇺🇦 🇹🇼Sigh. We are, as a security community, making good progress on some old as well as some new topics. <a href="https://infosec.exchange/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a>, <a href="https://infosec.exchange/tags/Go" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Go</a>, and other memory safe systems languages are going well and having a real impact in reducing memory safety issues - which has been the most important security bug class for decades, and we are finally improving! Compartmentalization and isolation of processes and services have now become common knowledge and the minimum bar for new designs. Security and privacy by design are being honored in many new projects, and not just as lip service, but because the involved developers deeply believe in these principles nowadays. <a href="https://infosec.exchange/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> is finally available to most end-users, both for messaging and backups.And again and again, we are forced into having discussions (<a href="https://www.theregister.com/2025/04/03/eu_backdoor_encryption/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.theregister.com/2025/04/03/eu_backdoor_encryption/</a>) about breaking all the progress.Let me be clear for Nth time: * We *cannot* build encryption systems that can only be broken by the "good guys". If they are not completely secure, foreign enemy states, organized crime, and intimate partners will break and abuse them as well. There is no halfway in this technology. Either it is secure or it isn't - for and against everybody. * We *cannot* build safe, government-controlled censorship filters into our global messaging apps that are not totally broken under the assumption of (current or future) bad government policies and/or insider attacks at the technology providers (<a href="https://www.mayrhofer.eu.org/talk/insider-attack-resistance-in-the-android-ecosystem/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.mayrhofer.eu.org/talk/insider-attack-resistance-in-the-android-ecosystem/</a>). Either one-to-one communication remains secure and private, or it doesn't (<a href="https://www.ins.jku.at/chatcontrol/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.ins.jku.at/chatcontrol/</a>). * We *cannot* allow exploitation of open security vulnerabilities in smartphones or other devices for law enforcement. If they are not closed, they are exploitable by everybody. "Nobody but us" is an illusion, and makes everybody less secure.My latest recorded public talk on the topic was <a href="https://www.mayrhofer.eu.org/talk/secure-messaging-and-attacks-against-it/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.mayrhofer.eu.org/talk/secure-messaging-and-attacks-against-it/</a>, and nothing factual has changed since then. Policymakers keep asking for a different technological reality than the one we live in, and that sort of thing doesn't tend to produce good, sustainable outcomes.(Edited to only fix a typo. No content changes.)CC <a href="https://chaos.social/@epicenter_works" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@epicenter_works</a> <a href="https://eupolicy.social/@edri" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@edri</a> <a href="https://chaos.social/@suka_hiroaki" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@suka_hiroaki</a> <a href="https://social.heise.de/@heisec" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@heisec</a> <a href="https://ioc.exchange/@matthew_d_green" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@matthew_d_green</a> <a href="https://eupolicy.social/@ilumium" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ilumium</a>

Scimmia di Mare<a href="https://livellosegreto.it/@kenobit" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kenobit</a> ho letto e condivido tutto. Solo una accortezza: <a href="https://mastodon.uno/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a> non è cifrato <a href="https://mastodon.uno/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a>. Se posso fidarmi di te, non ho idea di chi sia il tuo host o, se lo tieni a casa, il tuo ISP. Ed in ogni caso, a queste condizioni, compromettere un nodo significa esporre molta gente a rischio.

PrivacyDigest<a href="https://mas.to/tags/UK" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UK</a> Effort To Keep <a href="https://mas.to/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apple</a> <a href="https://mas.to/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> Fight <a href="https://mas.to/tags/Secret" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Secret</a> Is Blocked - Slashdot <a href="https://mas.to/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://mas.to/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mas.to/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://apple.slashdot.org/story/25/04/07/1444256/uk-effort-to-keep-apple-encryption-fight-secret-is-blocked?utm_source=rss1.0mainlinkanon&utm_medium=feed" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://apple.slashdot.org/story/25/04/07/1444256/uk-effort-to-keep-apple-encryption-fight-secret-is-blocked?utm_source=rss1.0mainlinkanon&utm_medium=feed</a>

Open Rights GroupORG has joined 237 civil society groups, companies and cybersecurity experts in an open letter to members of the Swedish Riksdag.We call on them to reject legislation that would force companies to undermine the encryption of their services.Read more ⬇️<a href="https://www.globalencryption.org/2025/04/joint-letter-on-swedish-data-storage-and-access-to-electronic-information-legislation/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.globalencryption.org/2025/04/joint-letter-on-swedish-data-storage-and-access-to-electronic-information-legislation/</a><a href="https://social.openrightsgroup.org/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://social.openrightsgroup.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://social.openrightsgroup.org/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://social.openrightsgroup.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Ian Brown 👨🏻‍💻Love this, as I hate bloody voice notes! <a href="https://eupolicy.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> and on-device. Question: are they are used anyway to train WA model? 🧐 <a href="https://eupolicy.social/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatsApp</a> <a href="https://eupolicy.social/tags/VoiceNote" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VoiceNote</a> <a href="https://eupolicy.social/tags/transcripts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transcripts</a>

ilias :thepiratebay:well the whole thing just gets more interesting :blobcatpopcornnom: <a href="https://www.bbc.co.uk/news/articles/cvgn1lz3v4no" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bbc.co.uk/news/articles/cvgn1lz3v4no</a><a href="https://mstdn.social/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://mstdn.social/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apple</a> <a href="https://mstdn.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> <a href="https://mstdn.social/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> <a href="https://mstdn.social/tags/UnitedKingdom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitedKingdom</a> <a href="https://mstdn.social/tags/UK" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UK</a>

Open Rights GroupThere is now the opportunity for some public scrutiny of the UK government’s decisions to attack technologies that keep us safe online.We must stand against the attack on encryption.Sign and share our petition to keep Apple data encrypted ⬇️<a href="https://you.38degrees.org.uk/petitions/keep-our-apple-data-encrypted" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://you.38degrees.org.uk/petitions/keep-our-apple-data-encrypted</a><a href="https://social.openrightsgroup.org/tags/apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apple</a> <a href="https://social.openrightsgroup.org/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://social.openrightsgroup.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://social.openrightsgroup.org/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://social.openrightsgroup.org/tags/ukpolitics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpolitics</a> <a href="https://social.openrightsgroup.org/tags/ukpol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpol</a> <a href="https://social.openrightsgroup.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Open Rights Group"This is bigger than the UK and Apple.The Court’s judgment will have implications for the privacy and security of millions of people around the world.Such an important decision cannot be made behind closed doors and we welcome the IPT’s decision to bring parts of the hearing into the open."🗣️ <a href="https://social.openrightsgroup.org/@jim" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jim</a> – ORG Executive Director.<a href="https://social.openrightsgroup.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://social.openrightsgroup.org/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://social.openrightsgroup.org/tags/apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apple</a> <a href="https://social.openrightsgroup.org/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://social.openrightsgroup.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://social.openrightsgroup.org/tags/ukpol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpol</a> <a href="https://social.openrightsgroup.org/tags/ukpol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpol</a>

Open Rights GroupEarlier this year, the UK government ordered Apple to grant it access to encrypted data stored by Apple users worldwide in its cloud service.The secret order was made under the Investigatory Powers Act and the government has tried to keep the public in the dark ever since. Even when Apple appealed the order.Now there will be some level of transparency with today's decision.<a href="https://www.reuters.com/technology/apple-appealing-against-uk-governments-back-door-order-tribunal-confirms-2025-04-07/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.reuters.com/technology/apple-appealing-against-uk-governments-back-door-order-tribunal-confirms-2025-04-07/</a><a href="https://social.openrightsgroup.org/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://social.openrightsgroup.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://social.openrightsgroup.org/tags/apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apple</a> <a href="https://social.openrightsgroup.org/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://social.openrightsgroup.org/tags/ukpolitics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpolitics</a> <a href="https://social.openrightsgroup.org/tags/ukpol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpol</a>

Open Rights GroupBREAKING: The UK government's attempt to hold the Apple encryption case entirely in secret has been REJECTED.ORG, Big Brother Watch and Index on Censorship made a submission to the court arguing for open justice.In a win for privacy rights, the court agrees.It said it didn't accept “that the revelation of the bare details of the case would be damaging to the public interest or prejudicial to national security”.<a href="https://www.openrightsgroup.org/press-releases/ipt-supports-orgs-call-for-open-hearing-in-apple-encryption-case-uk/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.openrightsgroup.org/press-releases/ipt-supports-orgs-call-for-open-hearing-in-apple-encryption-case-uk/</a><a href="https://social.openrightsgroup.org/tags/apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apple</a> <a href="https://social.openrightsgroup.org/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://social.openrightsgroup.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://social.openrightsgroup.org/tags/ukpolitics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpolitics</a> <a href="https://social.openrightsgroup.org/tags/ukpol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ukpol</a> <a href="https://social.openrightsgroup.org/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a>

Jim KillockBREAKING: VICTORY for <a href="https://social.openrightsgroup.org/@openrightsgroup" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@openrightsgroup</a> BBW and <a href="https://mastodon.xyz/@privacyint" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@privacyint</a> and othersThe <a href="https://social.openrightsgroup.org/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apple</a> IPT case will be held in open, including the bare details of the case, so that the principles of the issue can be discussed! <a href="https://social.openrightsgroup.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a href="https://social.openrightsgroup.org/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a>

Ian Brown 👨🏻‍💻BOOOOM! UK Investigatory Powers Tribunal dismisses with extreme prejudice (§43) the UK <a class="hashtag" href="https://bsky.app/search?q=%23HomeOffice" rel="nofollow noopener noreferrer" target="_blank">#HomeOffice</a> attempt to cover up the case brought by <a class="hashtag" href="https://bsky.app/search?q=%23Apple" rel="nofollow noopener noreferrer" target="_blank">#Apple</a> against the global snooping order from the Home Office against Advanced Data Protection 🚀 h/t <a class="mention" href="https://bsky.app/profile/kind.ac" rel="nofollow noopener noreferrer" target="_blank">@kind.ac</a> <a class="hashtag" href="https://bsky.app/search?q=%23IPT" rel="nofollow noopener noreferrer" target="_blank">#IPT</a> <a class="hashtag" href="https://bsky.app/search?q=%23ADP" rel="nofollow noopener noreferrer" target="_blank">#ADP</a> <a class="hashtag" href="https://bsky.app/search?q=%23E2EE" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> <a href="https://www.judiciary.uk/wp-content/uploads/2025/04/Apple-v-Secretary-of-State-for-the-Home-Department.pdf" rel="nofollow noopener noreferrer" target="_blank">www.judiciary.uk/wp-content/u...</a> <a href="https://www.judiciary.uk/wp-content/uploads/2025/04/Apple-v-Secretary-of-State-for-the-Home-Department.pdf" rel="nofollow noopener noreferrer" target="_blank">judiciary.uk/wp-content/upl...</a>

Hache☕Si usas <a href="https://masto.es/tags/GMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GMail</a> y te has enterado de su última afirmación de introducir un verdadero <a href="https://masto.es/tags/cifrado" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cifrado</a> de extremo a extremo: es mentira.Google tiene el control y/o no puedes hacer nada en contra de que Google tome el control en cualquier momento. El <a href="https://masto.es/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> real funciona de otra manera: sólo el emisor y el receptor pueden acceder al contenido protegido. <a href="https://arstechnica.com/security/2025/04/are-new-google-e2ee-emails-really-end-to-end-encrypted-kinda-but-not-really/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://arstechnica.com/security/2025/04/are-new-google-e2ee-emails-really-end-to-end-encrypted-kinda-but-not-really/</a><a href="https://michal.sapka.pl/2025/gmail-e2e-is-as-terrible-as-expected/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://michal.sapka.pl/2025/gmail-e2e-is-as-terrible-as-expected/</a><a href="https://masto.es/tags/Meta" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Meta</a> también definió el E2EE de tal manera que el mensaje se cifra desde el emisor hasta ellos, se procesa en texto claro y se vuelve a cifrar para la transmisión al receptor.No dejes que te engañen con afirmaciones falsas y definiciones erróneas.<a href="https://graz.social/@publicvoit" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@publicvoit</a> <a href="https://graz.social/@publicvoit/114295836158573196" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://graz.social/@publicvoit/114295836158573196</a>

Kevin Karhan :verified:<a href="https://social.tchncs.de/@phreaknerd" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@phreaknerd</a> <a href="https://nrw.social/@melsdung" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@melsdung</a> <a href="https://punk.cyber77.de/@nocci" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nocci</a> exakt deshalb rate ich zu <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OMEMO</a> ( <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@monocles</a> & <a href="https://fosstodon.org/@gajim" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gajim</a> ) sowie <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a>/MIME ( <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@delta</a> & <a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thunderbird</a> ), denn nur <a href="https://infosec.space/tags/dezentral" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dezentral</a> mit <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfCustody</a> aller <a href="https://infosec.space/tags/Keys" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keys</a> besteht echte <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a>!<ul><li>Außerdem funktionieren die einwandfrei via <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a> und damit auch noch <a href="https://infosec.space/tags/anonym" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#anonym</a>!</li></ul>Ich helfe gern "<a href="https://infosec.space/tags/Normies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Normies</a>" und "<a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechIlliterates</a>" darauf umzustellen...

mkj<a href="https://infosec.exchange/@0xF21D" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@0xF21D</a> The way I see it is that even if end-user device security is poor, proper E2EE such as that used by Signal still provides a significant benefit: It shifts the burden of an attacker from wholesale dragnet surveillance (which is easy to do in bulk) to focused attack targetting (very difficult to do in bulk, especially inconspiciously).*Even if* device security sucks, which would equally impact other services as well, that *still* provides a privacy benefit.<a href="https://social.mkj.earth/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a> <a href="https://social.mkj.earth/tags/opsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opsec</a> <a href="https://social.mkj.earth/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://social.mkj.earth/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a>

Debacle<a href="https://social.screamingatmyscreen.com/@fallenhitokiri" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fallenhitokiri</a> Most people seem to believe <a href="https://framapiaf.org/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> were just a misspelling of gmail anyway 🤷<a href="https://framapiaf.org/tags/mu4e" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mu4e</a> <a href="https://framapiaf.org/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://framapiaf.org/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://framapiaf.org/tags/e2ee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a>

Muminpappa 🇪🇺The government in <a href="https://mastodonsweden.se/tags/Sweden" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sweden</a> is working on legislation that would force platforms to store and provide law enforcement with access to their users’ communications, including those that are end-to-end encrypted <a href="https://mastodonsweden.se/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> The Internet Society is asking security experts, civil society organizations, private industry and trade organizations to sign a "Joint Letter on the Swedish Data Storage and Access to Electronic Information Legislation". Please sign before April 7 1 pm UTC.<a href="https://app.smartsheet.com/b/form/e3cf0c35c3a84837b0accdf21966a554" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://app.smartsheet.com/b/form/e3cf0c35c3a84837b0accdf21966a554</a>

Ian Brown 👨🏻‍💻UPDATE: it’s the former. Google says: “When the recipient has S/MIME configured, Gmail sends an <a href="https://eupolicy.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> email via <a href="https://eupolicy.social/tags/SMIME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SMIME</a> (just like it does today).” ✅ <a href="https://workspace.google.com/blog/identity-and-security/gmail-easy-end-to-end-encryption-all-businesses" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://workspace.google.com/blog/identity-and-security/gmail-easy-end-to-end-encryption-all-businesses</a>

Ian Brown 👨🏻‍💻Obviously, <a href="https://eupolicy.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> (under order from the US government) could serve compromised “updates” at any time to individual users. It would be technically possible to enable users to compare a “fingerprint” (hash) of security-critical plugins they are running, such as the one supporting Gmail’s <a href="https://eupolicy.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> capability. If I can see I’m getting a different plugin for my OS/CPU to 99% of other users on the same platform, that’s a big warning sign. But I haven’t seen such software widely deployed (yet) 🧐

Ian Brown 👨🏻‍💻Secondly, it’s not clear if <a href="https://eupolicy.social/tags/gmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gmail</a> is using this workaround just for message recipients who don’t have their own “digital <a href="https://eupolicy.social/tags/X509" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#X509</a> certificates” to enable message encryption yet (which would be justifiable) or not (which would be an improvement over the status quo, but not genuine <a href="https://eupolicy.social/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a>.)

Recent searches

Search options

Administered by:

Server stats:

#e2ee