@Seirdy @neurovagrant so you admit defeat amidst the fact that you refuse to acknowledge the fact that a #centralized #SingleVendor / #SingleProvider solution is impossible to secure against the will of the government it's incorporated under (as per law)...

Not Opensourcing the backend and it's APIs is literally violating #KerckhoffsPrinciple so hard it disqualifies any security claims as fanboyism!

@md @bmi @bsi #TETRA's #Crypto is so #weak that it's trivial to crack with any modern #GPGPU, because it's #SecurityThroughObscurity makes all the #TEA versions as weak as #CSA on #DVB.

But then again noone pays me to fix it, so it's not my problem.

Spoiler: The proper fix is to abolish all #proprietary shit and demand a fully #OpenSource'd communications system, since everything else violates #KerckhoffsPrinciple and is thus inherently and unfixably insecure by design!

@artikel10ev basically worse than everthing else...

[Or maybe not. cuz #QQ and #WeChat don't bother to lie into users' faces like @protonmail and #WhatsApp do]

Remember #KerckhoffsPrinciple:
#NotYourPrivateKeys = #NotSecureEncryption!

Also all #Singlevendor and/or #SingleProvider and/or non-#FLOSS solutions are inherently & unfixably bad as well as insecure per design!

@neil @Em0nM4stodon #Signal as well isn't secure.

NO #SingleVendor / #SingleProvider solution can be secure as they all violate #KerckhoffsPrinciple.
https://en.wikipedia.org/wiki/Kerckhoffs's_principle

If you can't do #SelfCustody of the #PrivateKeys and don't have 100% control over these, then consider said #encryption to be easily #MITM'd and / or #backdoored.

@Jamilla @thehackernews

IOW: DON'T TRUST ANYONE!

Only actual E2EE like #OMEMO [#XMPP] or #GnuPG [#eMail] you can verify and that doesn't violate #KerckhoffsPrinciple can be secure.

Anything else is a "#blackbox" and thus insecure.
https://pastebin.com/GrV3uYh5