Yes, JuDaC, there's absolutely nothing you can do about that. If the user wants to see something, they can, and it's their responsibility to make sure their browser isn't compromised. You can take steps toward making sure what they sent actually came from them to try and prevent what they send from being tampered with (steps which can all be broken anyway, as far as I know), but there's simply no way to keep them from seeing what you're sending over the wire.
On Oct 13, 10:17 am, JuDaC <[email protected]> wrote: > Jeff, this problem is after the submit and before the SSL. > > Just like firebug. any attacker can easily put and plugging up to your > browser (i.e FF), that you think this only make possible to download > youtube movies, but it does more than that. It intercept you > submission before it reaches the SSL. (Just like FireBug). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
