7 replies
by rcc
http://www.thawte.com/support/malachi/contents.html
Yes, 128bits encryption is enough for fast SSL web transactions (where you send your credit card number to a WEB site).
The problem is that you:
1. need to trust that the WEB site is trustworthy.
2. your browser does not keep the information cached somewhere (usualy encrypted pages are not kept in cache)
So if you're worried about somebody snooping in while you are transacting with the WEB server (several seconds), 128 bits encryption is enough. You should worry more about the browser, caching, and the posibility that you may be hacked and if the information is stored in a plain-readable format in your computer you can think of consequences...
I hope this helps. There are many other views to encryption, not just the lenght of the encryption key...there are algorithms and type (symetric/asymetric)
Regards,
Radu
by trenanscott
by russ werner
by trenanscott
by csmith
The risk is not in the 128 bit encryption.
The risk is the criminals who break into the website and steal credit card numbers by the thousands, and then post your credit card number online, if they are not paid a ransom.
There is hope here.
Some firms (very few so far) are starting to use "airwalls".
The airwall system basically consists of an isolated server with "no outside connections", that stores the credit card numbers.
The numbers are removed from the webserver and transfered to it by tape (or floppy) on a regular basis, so only a few credit card numbers are on the web server . (Only the new transactions since the last transfer.)
The "airwall" separated server can communicate with the financial institutions, but only on itsown initiation. I have seen installations where there was a physical switch to break the line as absolute security. (Not just relying on the do not answer setting.)
So, know your websites, and don't worry so much.
Regards, Chris
by trenanscott
by trenanscott
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending