Encrypted Connection vs. Unnencrypted
Posted 10 December 2007 - 07:53 PM
Posted 10 December 2007 - 09:41 PM
So say I'm logging into a website such as geekstogo.com. If you notice, when you pull up GTG, it starts out with http:// this is telling the browser that everything that is passed to the server is clear all along the wire from my computer to the server on port 80.
A person who wants to see my username and password would have to place themselves in between me and the GTG server and use a program to view my traffic as it would show as "Username: Gravity Gripp Password: somerandompassword".
On the other hand, you have encrypted connections which uses SSL or secure socket layer. If you visit something like your bank's website, you will notice (hopefully) that their site uses https://. This tells the browser that everything that is going from your browser to your banks server is encrypted using certificates (SSL Certificates) that are located within your browser. All of this traffic is on port 443 typically.
So using the same scenario as above, say I was to login to GTG using https://geekstogo.com the traffic with my username and password would look like this to the person who's looking at my traffic. "DLXCOIJcasdcoijClkjadfoiajcsdkl;fja1oi" you get the idea.
The only thing that you can do to protect yourself on clear text connections is to be careful what you submit to websites that aren't using SSL.
I hope this explains it a bit.
Posted 10 December 2007 - 10:34 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users