The Data Encryption Standard
The most widely used encryption scheme is based on the Data
Encryption Standard (DES) adopted in 1977 by the National Bureau of Standards,
now the National Institute of Standards and Technology (NIST), as Federal
Information Processing Standard 46 (FIPS PUB 46). The algorithm itself is
referred to as the Data Encryption Algorithm (DEA).[6] For DES, data are encrypted in
64-bit blocks using a 56-bit key. The algorithm transforms
64-bit input in a series of steps into a 64-bit output. The same steps, with the
same key, are used to reverse the encryption.
The DES enjoys widespread use. It has also been the subject of
much controversy concerning how secure the DES is. To appreciate the nature of
the controversy, let us quickly review the history of the DES.
In the late 1960s, IBM set up a research project in computer
cryptography led by Horst Feistel. The project concluded in 1971 with the
development of an algorithm with the designation LUCIFER [FEIS73], which was sold to Lloyd's of
London for use in a cash-dispensing system, also developed by IBM. LUCIFER is a
Feistel block cipher that operates on blocks of 64 bits, using a key size of 128
bits. Because of the promising results produced by the LUCIFER project, IBM
embarked on an effort to develop a marketable commercial encryption product that
ideally could be implemented on a single chip. The effort was headed by Walter
Tuchman and Carl Meyer, and it involved not only IBM researchers but also
outside consultants and technical advice from NSA. The outcome of this effort
was a refined version of LUCIFER that was more resistant to cryptanalysis but
that had a reduced key size of 56 bits, to fit on a single chip.
In 1973, the National Bureau of Standards (NBS) issued a
request for proposals for a national cipher standard. IBM submitted the results
of its Tuchman-Meyer project. This was by far the best algorithm proposed and
was adopted in 1977 as the Data Encryption Standard.
Before its adoption as a standard, the proposed DES was
subjected to intense criticism, which has not subsided to this day. Two areas
drew the critics' fire. First, the key length in IBM's original LUCIFER
algorithm was 128 bits, but that of the proposed system was only 56 bits, an
enormous reduction in key size of 72 bits. Critics feared that this key length
was too short to withstand brute-force attacks. The second area of concern was
that the design criteria for the internal structure of DES, the S-boxes, were
classified. Thus, users could not be sure that the internal structure of DES was
free of any hidden weak points that would enable NSA to decipher messages
without benefit of the key. Subsequent events, particularly the recent work on
differential cryptanalysis, seem to indicate that DES has a very strong internal
structure. Furthermore, according to IBM participants, the only changes that
were made to the proposal were changes to the S-boxes, suggested by NSA, that
removed vulnerabilities identified in the course of the evaluation process.
Whatever the merits of the case, DES has flourished and is
widely used, especially in financial applications. In 1994, NIST reaffirmed DES
for federal use for another five years; NIST recommended the use of DES for
applications other than the protection of classified information. In 1999, NIST
issued a new version of its standard (FIPS PUB 46-3) that indicated that DES
should only be used for legacy systems and that triple DES (which in essence
involves repeating the DES algorithm three times on the plaintext using two or
three different keys to produce the ciphertext) be used. We study triple DES in
Chapter 6. Because the underlying
encryption and decryption algorithms are the same for DES and triple DES, it
remains important to understand the DES cipher.
DES Encryption
The overall scheme for DES encryption is illustrated in Figure 3.4. As with any encryption scheme,
there are two inputs to the encryption function: the plaintext to be encrypted and the key. In this case, the plaintext must be
64 bits in length and the key is 56 bits in length.[7]
Which tool or software application make use of this encryption standard ? What are the types of techniques followed under this standard ? I have heard about advanced encryption standard too , so which one is better.
ReplyDeletedigital signature certificate