The problem with these is that even if the code is set to be cached forever, there's no easy way for the user to verify that this is the case. How do you defend against an attacker (say, the FBI) taking control of the servers and causing them to serve javascript which sends the messages to themselves unencrypted?
0bin is not made to prevent the user from being buster. 0bin is made so that it's difficult to sue the host for hosting hot content since he can claim he can't moderate it.
[+] [-] rabidsnail|14 years ago|reply
[+] [-] arkem|14 years ago|reply
Edit: though of course if the javascript is never requested again it limits the window of opportunity to man-in-the-middle.
[+] [-] sametmax|14 years ago|reply
0bin is not made to prevent the user from being buster. 0bin is made so that it's difficult to sue the host for hosting hot content since he can claim he can't moderate it.
[+] [-] tomlanyon|14 years ago|reply
Damn.
[+] [-] sametmax|14 years ago|reply
[+] [-] cnu|14 years ago|reply
[+] [-] Aeons|14 years ago|reply
[+] [-] mxxx|14 years ago|reply