d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
df347c8a2e
freebsd-dev/lib/libcrypt/Makefile

51 lines
1.2 KiB
Makefile
Raw Normal View History

Nates password scrambler, from FreebSD 1.1.5, but with everything except crypt() ripped out Reviewed by: Geoff Rehmet Submitted by: Nate Williams
1994-08-09 17:07:27 +00:00
#
$Id$ -> $FreeBSD$
1999-08-28 00:22:10 +00:00
# $FreeBSD$
Nates password scrambler, from FreebSD 1.1.5, but with everything except crypt() ripped out Reviewed by: Geoff Rehmet Submitted by: Nate Williams
1994-08-09 17:07:27 +00:00
#
First pass through library packaging. Sponsored by: The FreeBSD Foundation
2016-02-04 21:16:35 +00:00
PACKAGE=lib${LIB}
Revert r284417 it is not necessary anymore
2015-06-15 19:28:07 +00:00
SHLIBDIR?= /lib
Provide alternate default for SHLIBDIR before bsd.own.mk does this. Reported by: phk
2006-03-18 11:01:06 +00:00
Use src.opts.mk in preference to bsd.own.mk except where we need stuff from the latter.
2014-05-06 04:22:01 +00:00
.include <src.opts.mk>
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
Bump the version of all non-symbol-versioned shared libraries in preparation for 8.0-RELEASE. Add the previous version of those libraries to ObsoleteFiles.inc and bump __FreeBSD_Version. Reviewed by: kib Approved by: re (rwatson)
2009-07-19 17:25:24 +00:00
SHLIB_MAJOR= 5
Merge into a single US-exportable libcrypt, which only provides one-way hash functions for authentication purposes. There is no more "set the libcrypt->libXXXcrypt" nightmare. - Undo the libmd.so hack, use -D to hide the md5c.c internals. - Remove the symlink hacks in release/Makefile - the algorthm is set by set_crypt_format() as before. If this is not called, it tries to heuristically figure out the hash format, and if all else fails, it uses the optional auth.conf entry to chose the overall default hash. - Since source has non-hidden crypto in it there may be some issues with having the source it in some countries, so preserve the "secure/*" division. You can still build a des-free libcrypt library if you want to badly enough. This should not be a problem in the US or exporting from the US as freebsd.org had notified BXA some time ago. That makes this stuff re-exportable by anyone. - For consistancy, the default in absence of any other clues is md5. This is to try and minimize POLA across buildworld where folk may suddenly be activating des-crypt()-hash support. Since the des hash may not always be present, it seemed sensible to make the stronger md5 algorithm the default. All things being equal, no functionality is lost. Reviewed-by: jkh (flame-proof suit on)
2000-12-28 10:32:02 +00:00
LIB= crypt
Somebody deleted the SONAME override causing the symlink to be expanded at link time and the target name compiled into the binaries. ie: everything used libscrypt or libdescrypt explicitly.
1999-09-21 14:44:27 +00:00
Use SRCTOP-relative paths to other directories instead of .CURDIR-relative ones This simplifies pathing in make/displayed output MFC after: 3 weeks Sponsored by: Dell EMC Isilon
2017-01-20 04:52:29 +00:00
.PATH: ${SRCTOP}/lib/libmd ${SRCTOP}/sys/crypto/sha2
Add a new hash type. This "NT-hash" is compatible with the password 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
2003-06-02 19:29:27 +00:00
SRCS= crypt.c misc.c \
crypt-md5.c md5c.c \
Add SHA256/512 ($5$ and $6$) to crypt(3). Used in linux-world, doesn't hurt us. PR: misc/124164 Submitted by: KIMURA Yasuhiro < yasu utahime org > MFC after: 1 month
2011-04-09 14:02:04 +00:00
crypt-nthash.c md4c.c \
crypt-sha256.c sha256c.c \
Skein was not meant to be connected to libcrypto It is not a password hashing algorithm Reported by: cem
2016-06-01 20:55:25 +00:00
crypt-sha512.c sha512c.c
MAN[1-9] -> MAN.
2001-03-27 17:27:19 +00:00
MAN= crypt.3
Make libcrypt thread-safe. Add crypt_r(3). glibc has a pretty nice function called crypt_r(3), which is nothing more than crypt(3), but thread-safe. It accomplishes this by introducing a 'struct crypt_data' structure that contains a buffer that is large enough to hold the resulting string. Let's go ahead and also add this function. It would be a shame if a useful function like this wouldn't be usable in multithreaded apps. Refactor crypt.c and all of the backends to no longer declare static arrays, but write their output in a provided buffer. There is no need to do any buffer length computation here, as we'll just need to ensure that 'struct crypt_data' is large enough, which it is. _PASSWORD_LEN is defined to 128 bytes, but in this case I'm picking 256, as this is going to be part of the actual ABI. Differential Revision: https://reviews.freebsd.org/D7306
2016-08-10 15:16:28 +00:00
MLINKS= crypt.3 crypt_get_format.3 crypt.3 crypt_r.3 \
crypt.3 crypt_set_format.3
Use SRCTOP-relative paths to other directories instead of .CURDIR-relative ones This simplifies pathing in make/displayed output MFC after: 3 weeks Sponsored by: Dell EMC Isilon
2017-01-20 04:52:29 +00:00
CFLAGS+= -I${SRCTOP}/lib/libmd -I${SRCTOP}/lib/libutil \
-I${SRCTOP}/sys/crypto/sha2
Add a new hash type. This "NT-hash" is compatible with the password 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
2003-06-02 19:29:27 +00:00
# Pull in the strong crypto, if it is present.
Use SRCTOP-relative paths to other directories instead of .CURDIR-relative ones This simplifies pathing in make/displayed output MFC after: 3 weeks Sponsored by: Dell EMC Isilon
2017-01-20 04:52:29 +00:00
.if exists(${SRCTOP}/secure/lib/libcrypt) && ${MK_CRYPT} != "no"
.PATH: ${SRCTOP}/secure/lib/libcrypt
Add OpenBSD-style blowfish password hashing. This makes one less gratuitous difference between us and our sister project. This was given to me _ages_ ago. May apologies to Paul for the length of time its taken me to commit. Obtained from: Niels Provos <provos@physnet.uni-hamburg.de>/OpenBSD Submitted by: Paul Herman <pherman@frenchfries.net>
2001-03-11 16:05:43 +00:00
SRCS+= crypt-des.c crypt-blowfish.c blowfish.c
CFLAGS+= -I${.CURDIR} -DHAS_DES -DHAS_BLOWFISH
Merge into a single US-exportable libcrypt, which only provides one-way hash functions for authentication purposes. There is no more "set the libcrypt->libXXXcrypt" nightmare. - Undo the libmd.so hack, use -D to hide the md5c.c internals. - Remove the symlink hacks in release/Makefile - the algorthm is set by set_crypt_format() as before. If this is not called, it tries to heuristically figure out the hash format, and if all else fails, it uses the optional auth.conf entry to chose the overall default hash. - Since source has non-hidden crypto in it there may be some issues with having the source it in some countries, so preserve the "secure/*" division. You can still build a des-free libcrypt library if you want to badly enough. This should not be a problem in the US or exporting from the US as freebsd.org had notified BXA some time ago. That makes this stuff re-exportable by anyone. - For consistancy, the default in absence of any other clues is md5. This is to try and minimize POLA across buildworld where folk may suddenly be activating des-crypt()-hash support. Since the des hash may not always be present, it seemed sensible to make the stronger md5 algorithm the default. All things being equal, no functionality is lost. Reviewed-by: jkh (flame-proof suit on)
2000-12-28 10:32:02 +00:00
.endif
Add a new hash type. This "NT-hash" is compatible with the password 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
2003-06-02 19:29:27 +00:00
Stop using auth_getval() now that it always returns NULL. Instead, 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
2012-06-12 17:14:19 +00:00
.for sym in MD4Init MD4Final MD4Update MD4Pad \
Protect the reachover built symbols after the SHA256/512 crypt(3) addition.
2011-04-27 21:33:56 +00:00
MD5Init MD5Final MD5Update MD5Pad \
Integrate SHA2-224 with userspace components The double compilation of the kernel sources in libmd and libcrypt is baffling, but add yet another define hack to prevent duplicate symbols. Add documentation and SHA2-224 test cases to libmd. Integrate with the md5(1) command, document, and add more test cases; self-tests pass.
2018-07-09 08:19:04 +00:00
SHA224_Init SHA224_Final SHA224_Update \
Protect the reachover built symbols after the SHA256/512 crypt(3) addition.
2011-04-27 21:33:56 +00:00
SHA256_Init SHA256_Final SHA256_Update \
Implement SHA-512 truncated (224 and 256 bits) This implements SHA-512/256, which generates a 256 bit hash by calculating the SHA-512 then truncating the result. A different initial value is used, making the result different from the first 256 bits of the SHA-512 of the same input. SHA-512 is ~50% faster than SHA-256 on 64bit platforms, so the result is a faster 256 bit hash. The main goal of this implementation is to enable support for this faster hashing algorithm in ZFS. The feature was introduced into ZFS in r289422, but is disconnected because SHA-512/256 support was missing. A further commit will enable it in ZFS. This is the follow on to r292782 Reviewed by: cem Sponsored by: ScaleEngine Inc. Differential Revision: https://reviews.freebsd.org/D6061
2016-05-28 16:06:07 +00:00
SHA512_224_Init SHA512_224_Final SHA512_224_Update \
SHA512_256_Init SHA512_256_Final SHA512_256_Update \
Replace sys/crypto/sha2/sha2.c with lib/libmd/sha512c.c cperciva's libmd implementation is 5-30% faster The same was done for SHA256 previously in r263218 cperciva's implementation was lacking SHA-384 which I implemented, validated against OpenSSL and the NIST documentation Extend sbin/md5 to create sha384(1) Chase dependancies on sys/crypto/sha2/sha2.{c,h} and replace them with sha512{c.c,.h} Reviewed by: cperciva, des, delphij Approved by: secteam, bapt (mentor) MFC after: 2 weeks Sponsored by: ScaleEngine Inc. Differential Revision: https://reviews.freebsd.org/D3929
2015-12-27 17:33:59 +00:00
SHA384_Init SHA384_Final SHA384_Update \
Skein was not meant to be connected to libcrypto It is not a password hashing algorithm Reported by: cem
2016-06-01 20:55:25 +00:00
SHA512_Init SHA512_Final SHA512_Update
Merge into a single US-exportable libcrypt, which only provides one-way hash functions for authentication purposes. There is no more "set the libcrypt->libXXXcrypt" nightmare. - Undo the libmd.so hack, use -D to hide the md5c.c internals. - Remove the symlink hacks in release/Makefile - the algorthm is set by set_crypt_format() as before. If this is not called, it tries to heuristically figure out the hash format, and if all else fails, it uses the optional auth.conf entry to chose the overall default hash. - Since source has non-hidden crypto in it there may be some issues with having the source it in some countries, so preserve the "secure/*" division. You can still build a des-free libcrypt library if you want to badly enough. This should not be a problem in the US or exporting from the US as freebsd.org had notified BXA some time ago. That makes this stuff re-exportable by anyone. - For consistancy, the default in absence of any other clues is md5. This is to try and minimize POLA across buildworld where folk may suddenly be activating des-crypt()-hash support. Since the des hash may not always be present, it seemed sensible to make the stronger md5 algorithm the default. All things being equal, no functionality is lost. Reviewed-by: jkh (flame-proof suit on)
2000-12-28 10:32:02 +00:00
CFLAGS+= -D${sym}=__${sym}
.endfor
Add a new hash type. This "NT-hash" is compatible with the password 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
2003-06-02 19:29:27 +00:00
Build lib/ with WARNS=6 by default. Similar to libexec/, do the same with lib/. Make WARNS=6 the norm and lower it when needed. I'm setting WARNS?=0 for secure/. It seems secure/ includes the Makefile.inc provided by lib/. I'm not going to touch that directory. Most of the code there is contributed anyway.
2010-01-02 09:58:07 +00:00
WARNS?= 2
For variables that are only checked with defined(), don't provide any fake value.
2004-10-24 15:33:08 +00:00
PRECIOUSLIB=
The new crypt code broke "make world". Back it out.
1999-01-23 08:27:46 +00:00
Add HAS_TESTS to all Makefiles that are currently using the `SUBDIR.${MK_TESTS}+= tests` idiom. This is a follow up to r321912.
2017-08-02 08:50:42 +00:00
HAS_TESTS=
Convert traditional ${MK_TESTS} conditional idiom for including test directories to SUBDIR.${MK_TESTS} idiom This is being done to pave the way for future work (and homogenity) in ^/projects/make-check-sandbox . No functional change intended. MFC after: 1 weeks
2017-08-02 08:35:51 +00:00
SUBDIR.${MK_TESTS}+= tests
Set up the /usr/tests hierarchy. Populate /usr/tests with the only test programs that currently live in the tree (those in lib/libcrypt/tests/) and add all the build machinery to accompany this change. In particular: - Add a WITHOUT_TESTS variable that users can define to request that no tests be put in /usr/tests. - Add a top-level Kyuafile for /usr/tests and a way to create similar Kyuafiles in top-level subdirectories. - Add a BSD.tests.dist file to define the directory layout of /usr/tests. Submitted by: Julio Merino jmmv google.com Reviewed by: sjg MFC after: 2 weeks
2013-10-25 05:25:19 +00:00
Nates password scrambler, from FreebSD 1.1.5, but with everything except crypt() ripped out Reviewed by: Geoff Rehmet Submitted by: Nate Williams
1994-08-09 17:07:27 +00:00
.include <bsd.lib.mk>
Reference in New Issue Copy Permalink