src-test2/lib/libcrypt/crypt.c, branch release/11.3.0

Revert r330897:

2018-03-29T02:50:57Z

This was intended to be a non-functional change. It wasn't. The commit message was thus wrong. In addition it broke arm, and merged crypto related code. Revert with prejudice. This revert skips files touched in r316370 since that commit was since MFCed. This revert also skips files that require $FreeBSD$ property changes. Thank you to those who helped me get out of this mess including but not limited to gonzo, kevans, rgrimes. Requested by: gjb (re)

Partial merge of the SPDX changes

2018-03-14T03:19:51Z

These changes are incomplete but are making it difficult to determine what other changes can/should be merged. No objections from: pfg

Change the hardcoded default back from SHA512 to DES.

2014-10-09T16:45:11Z

PR: 192277 MFC after: 3 days

Don't break the legacy applications which set

2014-05-28T16:50:18Z

just 2 bytes to salt. MFC after: 1 week

r261913 broke DES passwords, because the only way they could work,

2014-04-26T11:50:25Z

since they don't have an easily recognizable signature, was if they were the default. This commit rewrites crypt_set_format(3) etc to address this: - Use a pointer instead of an index to identify the default format. This pointer is initialized at compile time to point to the first first element in the list of supported formats, eliminating the need for crypt_setdefault(). Using a pointer also simplifies iterating through the list. - Associate DES with the magic string "_", which takes care of the Extended DES format. - Finally, as a special case, if the salt does not match any known magic string but matches ^[./0-9A-Za-z]{13}$, it is assumed to be a DES password and is passed on to crypt_des(). MFC after: 1 week

Switch the hardcoded default hash function from MD5 / DES to SHA512.

2014-02-15T10:53:44Z

Stop using auth_getval() now that it always returns NULL. Instead,

2012-06-12T17:14:19Z

hardcode the default to what it would be if we didn't hardcode it, i.e. DES if supported and MD5 otherwise. MFC after: 3 weeks

s/shaN_crypt/crypt_shaN/g to be a more consistent with the existing naming.

2011-05-05T01:09:42Z

Reviewed by: markm

Add SHA256/512 ($5$ and $6$) to crypt(3). Used in linux-world, doesn't

2011-04-09T14:02:04Z

hurt us. PR: misc/124164 Submitted by: KIMURA Yasuhiro < yasu utahime org > MFC after: 1 month

Add a new hash type. This "NT-hash" is compatible with the password

2003-06-02T19:29:27Z

hashing scheme used in Microsoft's NT machines. IT IS NOT SECURE! DON'T USE IT! This is for the use of competent sysadmins only! Submitted by: Michael Bretterklieber