1 .\" FreeSec: libcrypt for NetBSD
3 .\" Copyright (c) 1994 David Burren
4 .\" All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 4. Neither the name of the author nor the names of other contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
37 .Nd Trapdoor encryption
43 .Fn crypt "const char *key" "const char *salt"
45 .Fn crypt_get_format "void"
47 .Fn crypt_set_format "const char *string"
51 function performs password hashing with additional code added to
52 deter key search attempts.
53 Different algorithms can be used to
57 .\" If you add more algorithms, make sure to update this list
58 .\" and the default used for the Traditional format, below.
60 Currently these include the
62 .Tn Data Encryption Standard (DES) ,
66 (compatible with Microsoft's NT scheme)
69 The algorithm used will depend upon the format of the Salt (following
70 the Modular Crypt Format (MCF)), if
74 is installed or not, and whether
76 has been called to change the default.
80 is the data to hash (usually a password), in a
81 .Dv null Ns -terminated
83 The second is the salt, in one of three forms:
85 .Bl -tag -width Traditional -compact -offset indent
87 If it begins with an underscore
92 is used in interpreting both the key and the salt, as outlined below.
94 If it begins with the string
96 then the Modular Crypt Format is used, as outlined below.
98 If neither of the above is true, it assumes the Traditional Format,
99 using the entire string as the salt (or the first portion).
102 All routines are designed to be time-consuming.
107 crypt to do approximately 2640 crypts
108 a CPU second and MD5 to do about 62 crypts a CPU second.
109 .Ss DES Extended Format:
112 is divided into groups of 8 characters (the last group is null-padded)
113 and the low-order 7 bits of each character (56 bits per group) are
117 the first group of 56 bits becomes the initial
120 For each additional group, the XOR of the encryption of the current
122 key with itself and the group bits becomes the next
126 The salt is a 9-character array consisting of an underscore followed
127 by 4 bytes of iteration count and 4 bytes of salt.
128 These are encoded as printable characters, 6 bits per character,
129 least significant character first.
130 The values 0 to 63 are encoded as ``./0-9A-Za-z''.
131 This allows 24 bits for both
138 introduces disorder in the
140 algorithm in one of 16777216 or 4096 possible ways
141 (i.e., with 24 or 12 bits: if bit
155 key is used to encrypt a 64-bit constant using
159 The value returned is a
160 .Dv null Ns -terminated
161 string, 20 or 13 bytes (plus null) in length, consisting of the
163 followed by the encoded 64-bit encryption.
165 If the salt begins with the string
167 then the Modular Crypt Format is used.
170 represents which algorithm is used in encryption.
171 Following the token is
172 the actual salt to use in the encryption.
173 The length of the salt is limited
174 to 8 characters--because the length of the returned output is also limited
176 The salt must be terminated with the end of the string
177 (NULL) or a dollar sign.
178 Any characters after the dollar sign are ignored.
180 Currently supported algorithms are:
182 .Bl -enum -compact -offset indent
197 Other crypt formats may be easily added.
198 An example salt would be:
199 .Bl -tag -width 6n -offset indent
200 .It Cm "$4$thesalt$rest"
202 .Ss "Traditional" crypt:
203 The algorithm used will depend upon whether
205 has been called and whether a global default format has been specified.
206 Unless a global default has been specified or
208 has set the format to something else, the built-in default format is
212 .\" NOTICE: Also make sure to update this
215 if it is available, or MD5 if not.
217 How the salt is used will depend upon the algorithm for the hash.
219 best results, specify at least two characters of salt.
223 function returns a constant string that represents the name of the
224 algorithm currently used.
227 .\" NOTICE: Also make sure to update this, too, as well
239 function sets the default encoding format according to the supplied
244 function returns a pointer to the encrypted value on success, and NULL on
246 Note: this is not a standard behaviour, AT&T
248 will always return a pointer to a string.
252 function will return 1 if the supplied encoding format was valid.
253 Otherwise, a value of 0 is returned.
271 section of the code (FreeSec 1.0) was developed outside the United
272 States of America as an unencumbered replacement for the U.S.-only
274 libcrypt encryption library.
277 Originally written by
278 .An David Burren Aq davidb@werj.com.au ,
279 later additions and changes by
280 .An Poul-Henning Kamp ,
281 .An Mark R V Murray ,
282 .An Michael Bretterklieber ,
291 function returns a pointer to static data, and subsequent calls to
293 will modify the same data.
296 modifies static data.
298 The NT-hash scheme does not use a salt,
300 for a competent attacker
302 Its use is not recommended.