diff options
| author | Carlos O'Donell <carlos@redhat.com> | 2013-10-19 00:11:31 -0400 |
|---|---|---|
| committer | Carlos O'Donell <carlos@redhat.com> | 2013-10-19 00:11:31 -0400 |
| commit | 3d7dc513b782407bd397b13771a631d9080d3aac (patch) | |
| tree | fac59ee8199751f14f52ddb09782fa701bd96c87 /manual/crypt.texi | |
| parent | 484c12fb1e3664fb434291234ea5787c5e3df4f5 (diff) | |
| download | glibc-3d7dc513b782407bd397b13771a631d9080d3aac.tar glibc-3d7dc513b782407bd397b13771a631d9080d3aac.tar.gz glibc-3d7dc513b782407bd397b13771a631d9080d3aac.tar.bz2 glibc-3d7dc513b782407bd397b13771a631d9080d3aac.zip | |
Mention FIPS 140-2 compliance and Sun RPC.
The Secure RPC implementation in glibc uses DES encryption
during authentication of the user. This use of DES means
that anyone using Sun RPC will likely not be compliant
with FIPS 140-2 which forbids the use of DES.
One solution to the compliance issue is to disable AUTH_DES
and AUTH_KERB, both use DES, when in FIPS compliance mode.
This is not a good idea because it disables all of the even
mildly secure methods of authentication allowing only plain
text methods.
Instead we leave AUTH_DES and AUTH_KERB enabled in FIPS
compliance mode and document the compliance issue in the
manual. FIPS allows this, that is to say that if you can't
fix it you must document the non-compliance.
This commit adds documentation to that effect in the
"DES encryption and password handling" section of the
manual.
Diffstat (limited to 'manual/crypt.texi')
| -rw-r--r-- | manual/crypt.texi | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/manual/crypt.texi b/manual/crypt.texi index ef905904ca..9c65b9535e 100644 --- a/manual/crypt.texi +++ b/manual/crypt.texi @@ -30,8 +30,15 @@ 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. +@vindex AUTH_DES +@cindex FIPS 140-2 It also provides support for Secure RPC, and some library functions that -can be used to perform normal DES encryption. +can be used to perform normal DES encryption. The @code{AUTH_DES} +authentication flavor in Secure RPC, as provided by @theglibc{}, +uses DES and does not comply with FIPS 140-2 nor does any other use of DES +within @theglibc{}. 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. @menu * Legal Problems:: This software can get you locked up, or worse. @@ -203,6 +210,7 @@ header @file{crypt.h}. @node DES Encryption @section DES Encryption +@cindex FIPS 46-3 The Data Encryption Standard is described in the US Government Federal Information Processing Standards (FIPS) 46-3 published by the National Institute of Standards and Technology. The DES has been very thoroughly |