Answers:
Gmail encrypts or encodes the password on the flex, so the password is not contained by clear manuscript for anyone to sniff. However, you don't obligation the password if you're on equal subnet as the Gmail authentication attempt, as you would be if you be connected through a WAP. A WAP is indistinguishable entry as a shroud 2 bridge. You can see adjectives of the traffic on the wireless segment if you simply sniff it.
Anyway, the drive you don't necessitate the Gmail password is because when you can sniff the traffic, you can do an attack call a "Sidejack" and, to date, nearby is nil that can be done to prevent this type of attack. See the relationship for much more information give or take a few Sidejacking.
For the second piece of your interrogate, if your information is flowing through a proxy, the sidejack attack is also as possible because adjectives of the packet you are sending are routed through that proxy server. This make it as simple to sidejack you because they hold adjectives of the information going through the server, so it become trivial to reassemble it and sidejack your nouns.
WG
might want to form it more clear what it is your wanting to know. one you can not access your email through a online proxy due to the certainty you will have need of to input your login info and whos to influence that its not some kid only just waiting for someone to do that. secondly sniff what individual channel to hold it sniffed is if someone have hack that site or someone you know have a keylogger on your computer.