Think of your information like a letter in the mail. Well, for this example, think of it even more as a post-card. Your message is written on the outside where the anyone that touches it can read it.
This post-card is going through the post office. It is going through mail centers, hubs, etc. Whatever path it needs to take to get from point A to Point B. At anyone of these post offices, if someone wants to read it, they just look at it, read it, then pass it along like normal. How would you ever know someone read it? Regular internet traffic is not encrypted, when you send a request, you send a written request like a post-card. Anyone in the middle could decide to read it. If you encrypt it, then they may have a harder time reading it, they would have to decrypt it. Of course, with the encrypted message, they could say, photocopy your post card, pass the post-card along, then work on figuring out how to read it in their spare time. The better your encryption, the longer it would take them to figure out what it says. But, say your mail system is all internal. You are sending mail from inside your building to inside your building. In this case, if the system is set up right, your mail will go from your office, to another office with-out ever leaving your building, which makes it much more secure. Someone in your own building would have to be devious enough to read your post-cards.(hopefully, your internal mail system would know not to send this message out to the normal post-office, just so the post-office will send it back to you) Anyway, that's my take on it. -- MySQL ODBC Mailing List For list archives: http://lists.mysql.com/myodbc To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
