3 ms·
How is what you're designing any more secure than a typical website that communicates over HTTPS? The user can't prevent you from sending a broken Java applet
by shrughes 17y ago
How is what you're designing any more secure than a typical website that communicates over HTTPS? The user can't prevent you from sending a broken Java applet or a webpage with broken encryption code, so the user still has to trust you. Look at what happened with Hushmail.
- klodolph 17y agoIf you did use a dedicated client-side app, it could be made more secure than HTTPS for those who don't trust the CA system. The explicit trust of all CAs (and there are many, scattered throughout the world) makes HTTPS a lot weaker than the algorithms alone would suggest.