Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am designing a website and have been learning about POST and GET requests and how POST requests can be read through 'packet sniffing'. Further reading seems to suggest that the data flowing to and from my computer can be 'sniffed' by anyone if it's not encoded through SSL or similar? Is this true? My network has WEP encryption I think it is called.

Can people read my hotmail and gmail emails? And see my msn conversations, what sites I am visting and when I am online?

I am posting this here since I ahve read conflicting information over the last half and hour and I know there are some real experts here who could potentiall shed some light on this. Thanks guys.

share|improve this question

migrated from Mar 18 '11 at 18:30

This question came from our site for professional and enthusiast programmers.

Further reading seems to suggest that the data flowing to and from my computer can be 'sniffed' by anyone if it's not encoded through SSL or similar? Is this true?

Yes, this is true. Both wireless (WiFi) and wired (Ethernet) networks can be sniffed easily, although it may be a little more complicated on switched Ethernet.

Even if you are connected to Internet directly over wired DSL or dial-up, for example, there is still a possibility for someone to tap the line, although this is a lot less probable than outsiders monitoring a public WiFi network. (On the other hand, some ISPs have been caught inspecting traffic too carefully.)

My network has WEP encryption I think it is called.

Aside from being hilariously insecure, WEP only protects traffic between your computer and the wireless AP – and even then only from passive monitoring, not from people connected to the same network. Most of it applies to WPA too.

WPA2 is a bit more secure, but like WEP it only secures one segment (you ↔ AP).

In comparison, TLS (aka SSL) offers end-to-end encryption: the data is secure at any point between you and the server. It also ensures that you are connecting to the real server, to prevent man-in-the-middle attacks.

Besides TLS, there are other methods of securing traffic: SSH is similar in function but is used mostly for shell access.

You can use an encrypted VPN or proxy server to encrypt everything you do, including MSN and generic web browsing. However:

  • TLS/SSL and SSH do end-to-end encryption but only protect specific services on specific hosts (for example, HTTP at; IMAP at,
  • whereas connecting through a VPN or using WEP/WPA will secure all traffic but only between you and the VPN server or the WPA2-enabled access point.

Can people

  • People connected to the same WiFi hotspot? Coworkers? Your school's IT guy? Yes, see above.
  • People using the same ISP? For most ISPs, no; customers only receive their own traffic.
  • People in the same city/country/planet? No. IP routing doesn't allow this. (IP routing can be subverted – there is a history of countries allowing a website block to propagate over BGP – but be assured that this gets noticed really fast.)

read my hotmail and gmail emails?

Yes, unless you access Gmail over SSL (

And see my msn conversations,

Yes. The MSNP protocol is plain-text.

what sites I am visting


and when I am online?

Depends on your definition of "online" (connected to Internet? connected to MSN Messenger?), but for most of them the answer is "yes".

Also, terminology: to encode something is to convert it into a different representation (such as Base64); whoever knows the algorithm can easily decode it. To encrypt something is to scramble it in a cryptographically secure way, so that only the key holder(s) can decrypt it, even though the algorithm is (should be) widely known. TLS/SSL does encryption. WEP does "encryption" (see note on security).

share|improve this answer

Anything that's not encrypted via SSL/TLS can be read. If there's no lock symbol in the browser, it's like a postcard being passed between letter carriers.

Your wireless encryption has little to do with this issue. That only means the connection from your computer to your access point is encrypted. Switch to WPA2 if you can, though.

share|improve this answer

In order to intercept your data the person doing the intercepting either has to break into your wireless network (which is quite easy with WEP - upgrade to WPA2 ASAP), or they have to have access to a computer or router that lies on the path between you and the web server (the packets either pass through that machine or it is able to read the network data passing through another machine on its local network). You can't just abitrarilly sniff the data passing between points A and B from point C unless the data passes through point C.

share|improve this answer

Yes, it can be read, especially when you're using old WEP encryption (breakable by my netbook in reasonable time). You should switch to WPA2. SSL can be sniffed as well (ettercap can do it).

share|improve this answer
SSL can be sniffed (just like everything else), but not decrypted – unless you start a MitM attack, in which case the victim will surely notice the ton of certificate errors that they are receiving. – grawity Mar 18 '11 at 18:32
As noted by the previous commenter: SSL cannot be trivially decrypted. For most intents and purposes, it's safe to consider SSL-encrypted information secure between your computer and the server you're connecting to. – Hyppy Mar 18 '11 at 18:58

You must log in to answer this question.