End-to-end-encryption (aka E2EE).....but citizens do not have to rely on service providers!!!
Ha.....End-to-end-encryption....
The people who want to break E2EE, or who want to implement client-side scanning....none of these people ask two simple questions:
(1) Who controls the E2EE process?
(2) Who controls the client-side scanning process?
(A1) The answer in both cases is likely to be some corporate entity (e.g. Signal, FB, Apple.....).
So my questions about this situation are these:
(3) Do you trust the implementers mentioned in answer #A1?
(4) Do you trust the folk (Levy, Robinson, NSA, GCHQ...) who want to break E2EE?
My position is simple: I don't trust ANY of the E2EE implememters, and I don't trust Levy, Robinson and all the other government sock puppets.
So...what to do? Why not implement private encryption to be used by you and your correspondents? Note that your private encryption only needs to deliver secret communications for, say, a year. Message encryption does not need to be secret forever....
So....what to do:
(5) Do some design work around Diffie/Hellman. Some research on prime numbers bigger than 8192 bits would also help.
(6) Do some design work around available public encryption schemes (AES, IDEA, samba, chacha and so on).
(7) Do some design work around implementing multi-pass encryption (so that snoops cannot deternine even that the first pass has been broken).
(8) Coded in C, items #5 through #7 can be implemented in less than 3000 lines of code.
Now if multiple private groups were to go this route, then the snoops (NSA, GCHQ, Five Eyes, and so on) would NOT ONLY have to attack commercial products (Signal, FB, Apple and so on), but they would have to attack all the private schemes as well!! They can start with this privately encrypted message:
dx+VY7JSKmX3chDDoJJ2m/HLkX45Xq3db9r4U732/JwB3Qu0cS5L+PZ/RJw/UJX3obDEqQZ53D91
wJ7Sqo+TqHqv25jfQ0IYA9Owu29Klu0se6vD8hhdBEh2KjmzC13hRmndfE6qN27glMtgQ5AfCsZN
W6ZHOmxNLtlb4qQ3ykHeEN2tJppFK+P9NV9rX8x5rpBcIuI5ttN02FRKpBfPoMMoVyy80JTUCNUa
E/Fo9eohar6OaQwpsAT8s0PIY33TKtFYdF3UtWTsV2SIu4c1hUrUb68UEJOtXUWMDdc5eU2i3a/J
mXjB8pORkQ35SpGMFjTjSLY9j9YacfdMkBj/R3g5NV2qlhEoyMeySjc3PP4Un1z906TIO4emym43
WZTVZxxKQH3R//I888TB4xWkrvfwv/IkE7GbrgtlJMQKisi3JMVxqNqHLMEvXTrjKi0OBRwenADp
RlW+/nWUpI5v1V+GH6+7dRdwqOVuM70sUnE9ED9QFP60k7OoWHrCGHchusxy6ruiL3vOGBcOMa0j
ZMrsgttOkr1Itv0VHXIxXZdi43I5aFvk01AoSxHf8enJ4x9jWRK/lAopxg98h4z8tjTJWcDYQtS0
OSNLZkAA1Ei//5vvaYyiWjlDklej4eLaO/wemTXCNFjxdikaLTJwn1xu8RAu+0wUpw4x+q3b/wd8
dqwV0kxWv4Q0QH1r8qE0U8XKwBlTI1QI8rXDikwipJHfmyym6hGLx916KdrqoSWlyg+tRVDedRHz
piR1e+3vy2b0bOVCo0EnwLrKIZqk8u6Setdn8obhe2j5UJgUHgaBwt3jTtyJHLDZWY9DmJ59hLRn
KL4CvOg+cSBew4kpg/goc1zfqmjzu4WHrH82BC7WPjI1FTu5x15WI9KagQQac4LJYc/IRbMAk/oE
+Dhznxxm98C3QoXmPOG8+5WS6hO/JS5wmGNhPvKRWBhc/pIdVYRiV6pQpRCtmdy31bfWL3CHkSUx
M9FVMMD9RV2IQYmbrY4GgyDBppvuw3dVVdqUV8nKP4j2KsDKhx5k/9DP4w81DmtJiG2x3JMicQOH
cjEMwV3Bg23babtHW3Lj8eRWvMITu+37SNSisW5+JpLGIKdJBsSXPVi31aMe/SF1Wal85T4E3v9Z
tbNLGEwW8U+hYzU2C3iRjgXwvCa2wcsR9sGYC5K7mYxRgjj/UCEsnpOVekhC775NQoZvU7qH4Cen
B6D0fNI68DAuDS4BcxhDXtKDS1d1uy9N+iPtvQRzWNcmMhUUIaO7QKPgg86/Gi7ww213hL9ekiWt
Fb/cqZmniTkjvHJle1MfkYUhD1XlNu9Ida6X/zkxswfS6z1TcHSBfsww7VMWgujixVeuTsMgRnQI
0nyh6P7BXs4MENH52FiwpDnAQvbKMa1o0kMwMqlRnbdpgOkr4RwHxyvFAOp6GZ3OIfB4gFtaN2X6
F/QW55vk8acMey47hEIBOgBwpmPI9SobYdOBPB5Ql2XSZ8DydSGA9iaWz64kIuyKm8/eGHe6iTDC
RT50kHp+zAQdmgwa/fj/HXWfNVnRrxf/BUWHuCRV5906Tmb+bCm4CFdt18GoZZaGshK4lhORY0KD
WIyS67M1nMMZJd1k27RFim1jJkhBxXg/UxHnw2Xe8ZOip5Os/Q5lgfmZnbRkrgJVHLfsvYX40KQs
MMILTxB3Ll00CrkMEshyb9n5g3mUm0kHYPgW0IzWU0K2L7GEpYvxWNHl/F12yuwtMr0htWg5Hv4f
we4vRreoPk2C13NySRmeR5vOe4uLShcpiExbi8jSm8HbNzE8jASWgK9eq6USdXV6cLoa3gmAiv9n
T9thMNXJYQ==
Private groups who use private encryption BEFORE their messages enter any public channel ensure that this example is exactly the type of thing that the snoops will see when the snoops break E2EE!!! Yup.....E2EE might be broken, but all the snoops get to see....is more encryption!
====