On Monday, September 15, 2008, 22:23:31, Jack S. LaRosa wrote: > I need to send credit card info to a vendor in payment for a part yet > to be shipped. Is there an easy way to encrypt the info so it can't be > read if it's intercepted in transit and yet *can* be read by the > recipient? Or am I worrying about nothing?
The safest way is to use a secure web form, if the vendor offers it (and if they do, it's likely that the info you send them in any other way will end up being entered to that webform by an employee anyway, so you just increase the risk of the data being intercepted in-flight by using other means of communication). Before entering the data, ensure that the address starts with https, and that there's a lock symbol near the titlebar (or in status bar, depending on your browser). https and the lock icon signify that the connection is encrypted, and that nobody will be able to read the data, even if it's intercepted. Note that listening in on phone conversations (and fax communications) is much easier than intercepting even unencrypted communication over the internet. -- < Jernej Simončič ><><><><>< http://eternallybored.org/ > The solution to a problem changes the problem. -- Peer's Law ________________________________________________ Current version is 4.0.24.0 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
