3 ms·
> Most in browser crypto seems to view the web server as both the adversary and the trusted party at the same time. I think that only considering a single web
by Karellen 4y ago
> Most in browser crypto seems to view the web server as both the adversary and the trusted party at the same time.
I think that only considering a single web server ("the web server") is an oversimplification that's crucial here.
I believe that the threat model in this case is that some web servers are fully trusted by the people you want to interact with (e.g. servers belonging to the website owner), whereas other servers are less trusted (e.g. servers belonging to CDNs, 3rd party repo owners e.g. npm/github, ad networks, etc...) - and many web pages/apps will load executable code and data from multiple sites in a single session.
- bawolff 4y agoThat's fair, but even then the problem is better solved by technogies other than js-based crypto like SRI, CSP, iframe sandboxes, etc. However that said, if you trust your bootstrap server (whatever serves initial html) then all the problems with javascript based crypto dissappear basically instantly. Most people experimenting in this space seem to be trying to protect against a malicious bootstrap server, and that is where everything goes off the rails.