841785bad1
This is a major rewrite of the description of 'crypt', 'getentropy', and 'getrandom'. A few highlights of the content changes: - Throughout the manual, public headers, and user-visible messages, I replaced the term "password" with "passphrase", the term "password database" with "user database", and the term "encrypt(ion)" with "(one-way) hashing" whenever it was applied to passphrases. I didn't bother making this change in internal code or tests. The use of the term "password" in ruserpass.c survives, because that refers to a keyword in netrc files, but it is adjusted to make this clearer. There is a note in crypt.texi explaining that they were traditionally called passwords but single words are not good enough anymore, and a note in users.texi explaining that actual passphrase hashes are found in a "shadow" database nowadays. - There is a new short introduction to the "Cryptographic Functions" section, explaining how we do not intend to be a general-purpose cryptography library, and cautioning that there _are_, or have been, legal restrictions on the use of cryptography in many countries, without getting into any kind of detail that we can't promise to keep up to date. - I added more detail about what a "one-way function" is, and why they are used to obscure passphrases for storage. I removed the paragraph saying that systems not connected to a network need no user authentication, because that's a pretty rare situation nowadays. (It still says "sometimes it is necessary" to authenticate the user, though.) - I added documentation for all of the hash functions that glibc actually supports, but not for the additional hash functions supported by libxcrypt. If we're going to keep this manual section around after the transition is more advanced, it would probably make sense to add them then. - There is much more detailed discussion of how to generate a salt, and the failure behavior for crypt is documented. (Returning an invalid hash on failure is what libxcrypt does; Solar Designer's notes say that this was done "for compatibility with old programs that assume crypt can never fail".) - As far as I can tell, the header 'crypt.h' is entirely a GNU invention, and never existed on any other Unix lineage. The function 'crypt', however, was in Issue 1 of the SVID and is now in the XSI component of POSIX. I tried to make all of the @standards annotations consistent with this, but I'm not sure I got them perfectly right. - The genpass.c example has been improved to use getentropy instead of the current time to generate the salt, and to use a SHA-256 hash instead of MD5. It uses more random bytes than is strictly necessary because I didn't want to complicate the code with proper base64 encoding. - The testpass.c example has three hardwired hashes now, to demonstrate that different one-way functions produce different hashes for the same input. It also demonstrates how DES hashing only pays attention to the first eight characters of the input. - There is new text explaining in more detail how a CSPRNG differs from a regular random number generator, and how getentropy/getrandom are not exactly a CSPRNG. I tried not to make specific falsifiable claims here. I also tried to make the blocking/cancellation/error behavior of both getentropy and getrandom clearer.
71 lines
2.3 KiB
C
71 lines
2.3 KiB
C
/*
|
|
* UFC-crypt: ultra fast crypt(3) implementation
|
|
*
|
|
* Copyright (C) 1991-2018 Free Software Foundation, Inc.
|
|
*
|
|
* The GNU C Library is free software; you can redistribute it and/or
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
* License as published by the Free Software Foundation; either
|
|
* version 2.1 of the License, or (at your option) any later version.
|
|
*
|
|
* The GNU C Library is distributed in the hope that it will be useful,
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
* Lesser General Public License for more details.
|
|
*
|
|
* You should have received a copy of the GNU Lesser General Public
|
|
* License along with the GNU C Library; if not, see
|
|
* <http://www.gnu.org/licenses/>.
|
|
*
|
|
* @(#)crypt.h 1.5 12/20/96
|
|
*
|
|
*/
|
|
|
|
#ifndef _CRYPT_H
|
|
#define _CRYPT_H 1
|
|
|
|
#include <features.h>
|
|
|
|
__BEGIN_DECLS
|
|
|
|
/* One-way hash PHRASE, returning a string suitable for storage in the
|
|
user database. SALT selects the one-way function to use, and
|
|
ensures that no two users' hashes are the same, even if they use
|
|
the same passphrase. The return value points to static storage
|
|
which will be overwritten by the next call to crypt. */
|
|
extern char *crypt (const char *__phrase, const char *__salt)
|
|
__THROW __nonnull ((1, 2));
|
|
|
|
#ifdef __USE_GNU
|
|
|
|
/* This structure provides scratch and output buffers for 'crypt_r'.
|
|
Its contents should not be accessed directly. */
|
|
struct crypt_data
|
|
{
|
|
char keysched[16 * 8];
|
|
char sb0[32768];
|
|
char sb1[32768];
|
|
char sb2[32768];
|
|
char sb3[32768];
|
|
/* end-of-aligment-critical-data */
|
|
char crypt_3_buf[14];
|
|
char current_salt[2];
|
|
long int current_saltbits;
|
|
int direction, initialized;
|
|
};
|
|
|
|
/* Thread-safe version of 'crypt'.
|
|
DATA must point to a 'struct crypt_data' allocated by the caller.
|
|
Before the first call to 'crypt_r' with a new 'struct crypt_data',
|
|
that object must be initialized to all zeroes. The pointer
|
|
returned, if not NULL, will point within DATA. (It will still be
|
|
overwritten by the next call to 'crypt_r' with the same DATA.) */
|
|
extern char *crypt_r (const char *__phrase, const char *__salt,
|
|
struct crypt_data * __restrict __data)
|
|
__THROW __nonnull ((1, 2, 3));
|
|
#endif
|
|
|
|
__END_DECLS
|
|
|
|
#endif /* crypt.h */
|