Next: , Previous: , Up: Main Menu   [Contents][Index]

33 DES Encryption and Password Handling

On many systems, it is unnecessary to have any kind of user authentication; for instance, a workstation which is not connected to a network probably does not need any user authentication, because to use the machine an intruder must have physical access.

Sometimes, however, it is necessary to be sure that a user is authorized to use some service a machine provides—for instance, to log in as a particular user id (see Users and Groups). One traditional way of doing this is for each user to choose a secret password; then, the system can ask someone claiming to be a user what the user’s password is, and if the person gives the correct password then the system can grant the appropriate privileges.

If all the passwords are just stored in a file somewhere, then this file has to be very carefully protected. To avoid this, passwords are run through a one-way function, a function which makes it difficult to work out what its input was by looking at its output, before storing in the file.

The GNU C Library provides a one-way function that is compatible with the behavior of the crypt function introduced in FreeBSD 2.0. It supports two one-way algorithms: one based on the MD5 message-digest algorithm that is compatible with modern BSD systems, and the other based on the Data Encryption Standard (DES) that is compatible with Unix systems.

It also provides support for Secure RPC, and some library functions that can be used to perform normal DES encryption. The AUTH_DES authentication flavor in Secure RPC, as provided by the GNU C Library, uses DES and does not comply with FIPS 140-2 nor does any other use of DES within the GNU C Library. It is recommended that Secure RPC should not be used for systems that need to comply with FIPS 140-2 since all flavors of encrypted authentication use normal DES.

Next: Debugging support, Previous: System Configuration Parameters, Up: Main Menu   [Contents][Index]