@Badener1848 @feda @ulrichkelber unabhängig davon sind beide #SingleVendor & #SingoeProvider, proprietär ubd nichz unabhängig verifizierbar.

https://infosec.space/@kkarhan/114698420750672345

Kevin Karhan :verified: (@[email protected])

@[email protected] dass #NSAbook keine wirkliche #E2EE hat erkennen wir daran dass jene Dienste nicht in #SaudiArabien und #Russland verboten sind! - Auch den #Werbelügen von @[email protected] darf angesichts #CloudAct nicht geglaubt werden. Stattdessen bieten sich #XMPP+#OMEMO ( @[email protected] & @[email protected] ) bsw. #PGP/MIME ( @[email protected] & @[email protected] ) an...

Infosec.Space

@tejan the only correct way to deal with this is using proper #E2EE like #PGP/MIME & anonymous eMail accounts.

  • Providers can only #decrypt and #read for what they have the keys!

Same goes with #Messengers, which is why I only recommend #XMPP+#OMEMO (i.e. @monocles / #monoclesChat & @gajim / #gajim ) & PGP/MIME (i.e. @delta / #deltaChat & @thunderbird / #Thunderbird), because unlike #proprietary #SingleVendor & #SingoeProvider solutions, they offer #SelfCustody so even if a provider is cooperative or served a #subopena or got theor equipment seized, they can't decrypt the contents!

@dnsprincess @WiGLEnet @eff

#XMPP + #OMEMO >>> @signalapp simply because #Signal falls under #CloudAct and demands #PII like #Phone numbers ehich they shouldn't and have no business to even request for.

Also all #centralozed, #SingleVendor & #SingoeProvider solutions are inherently insecure per design.

@Mer__edith et. al. will snitch when threatened with lifetime for not doing so.

#OpenSource #OpenStandards #Decentralization