2 ms·
I dont know what case you are trying to make? Should we not create cryptographic storage on the web? Is that not ok? Do you think there's anything that would ke
by rektide 5y ago
I dont know what case you are trying to make? Should we not create cryptographic storage on the web? Is that not ok? Do you think there's anything that would keep us from using secure keys for encrypting storage? Is there some barrier you perceieve to why the web couldnt make use of such a capability?
I have no clue why you are building a case out for the web being something special & different & weird & hard to expect basic common sense secure cryptography from. Nitrokey had a pretty basic simple sensible early draft spec. Having some storage & a key that alone cam decrypt it seems trivially obvious. Not sure what kind of smoke you are attempting to blow on this idea.
TLS has absolutely nothing to do with this. The idea of e2e messaging usually is that you could send the message over untrusted links just fine. The other party could validate & decrypt it. Discussion on TLS seems wildly off topic/tangenti to the kind of e2e storage that messaging apps do, and that secure end to end storage entails.
Edit: to your credit, the MLS link you have above is indeed relevant.
- raggi 5y agohttps://github.com/w3c/webauthn/issues/1462 https://github.com/w3c/webauthn/issues/1462