While I understand the challenges with SMTP-based email, dismissing privacy concerns as ignorance is unhelpful. It's not at all a technical difficulty—Modern threats demand updated solutions, and opportunistic-TLS isn't enough. Financial incentives and data monetization do play a role in the reluctance of major providers. If new protocols can secure chat apps, similar efforts should be made for email.
> multiple symmetric ciphers in sequence is still a permutation.
No its not. The data feeding to the next algorithm is an already encrypted data from the previous algorithm. Theres 0 connection b/w them.
For example .
step 1 . encrypt message (M) with key (K1) using AES to produce cipher text (C1)
step 2 . encrypt message C1 with key K2 using TripleDES to produce C2.
step n . and so on using all algorithms with different Keys.
I don't see any connections b/w them. 0 entropy. Please correct me if i'm wrong.
"roll your own crypto" means writing a new encryption scheme. But here i'm just using multiple schemes without connection to one another by using different encryption keys.
What if AES-256 gets compromised?
Basically i'm storing my encrypted data online. Anyone can see it but only i can decrypt it.
Users deserve better privacy protections despite historical constraints.