SSL stands for Secure Sockets Layer, a transportation layer protocol that provides endpoint authentication and communication secrecy over networks in general, the Internet in particular. TLS stands for Transport Layer Security, the name given to an Internet standard based on SSL. The current version of SSL is 3.0, and the current version of TLS is 1.1. It is common to use SSL/TLS to cover all of them.
FTPS is commonly referred to as FTP/SSL and covers a variety of methods by which File Transfer Protocol software can leverage SSL/TLS to perform secure file transfers. Each method uses an SSL/TLS layer below the standard FTP protocol to encrypt the control and/or the data channels. FTPS, by the way, is distinguished from SSH file transfer protocol (SFTP), which is FTP over SSH.
There are three basic parts to TLS:
---The initial negotiation of algorithm support in which the choice of symmetric cipher to be used in the data encryption is made
--- The key exchange between (and authentication of) the two machines that are communicating
--- The symmetric cipher encryption and message authentication
In other words, a lot happens in TLS before getting to the bulk encryption of the data being exchanged between the two parties. In fact, the key exchange and authentication, which use public key cryptography, are the most computationally burdensome parts of the whole transaction. And that is where the hardware comes in.
In the late nineties, the rapid growth of SSL as a means of doing secure Web transactions threatened to swamp Web servers with the effort of doing all the public key computations. Crypto-hardware companies like Rainbow Technologies (now a part of SafeNet Inc.) developed SSL accelerators, co-processor boards that could be plugged into Web servers. These dedicated processors handled the SSL public key computations and delivered the symmetric keys to the server for the bulk data encryption part of the transaction. Other accelerator designs actually perform the bulk data encryption as well, taking the full strain of the crypto and delivering cleartext to the server.
If you need to implement FTPS, which delivers a lot of data securely to a server, it might be worth investigating partial or complete hardware acceleration of the crypto-processing. Chances are, however, that this will involve handling a lot of data -- and a large number of simultaneous connections -- for the acceleration to offer worthwhile advantages over a software-only approach. And it is hard to think why a hardware method would be inherently more secure in this scenario than a software-only one. Remember, to gain all of the security benefits of TLS, both the client as well as the server should be using digital certificates. And, as with any other crypto system, the most likely point of failure is not the crypto itself, but the way it is implemented.
Related Q&A from Michael Cobb
Expert Michael Cobb explains how an HTTP referer header affects user privacy and outlines changes that can be made to ensure sensitive data is not ...continue reading
Expert Michael Cobb explains the difference between the REESSE3+ and IDEA block ciphers and explores when each is applicable in an enterprise setting.continue reading
While cookies are critical to delivering personalized Web content, they are a privacy concern. Learn how adding Bloom filters to cookies can help ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.