Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/lib/libcrypt/Makefile

31 lines
619 B
Makefile
Raw Normal View History

Wrap compiler-specific flags with HAVE_GCC and HAVE_PCC as necessary. Add a few flags for PCC.
2008-08-29 04:02:21 +04:00
# $NetBSD: Makefile,v 1.21 2008/08/29 00:02:22 gmcgarry Exp $
Use bsd.crypto.mk.
1999-07-13 02:04:09 +04:00
* Add user-controlled mk.conf variables - SHLIBDIR Location to install shared libraries if ${USE_SHLIBDIR} is "yes". Defaults to "/usr/lib". - USE_SHLIBDIR If "yes", install shared libraries in ${SHLIBDIR} instead of ${LIBDIR}. Defaults to "no". Sets ${_LIBSODIR} to the appropriate value. This may be set by individual Makefiles as well. - SHLINKDIR Location of shared linker. Defaults to "/usr/libexec". If != "/usr/libexec", change the dynamic-linker encoded in shared programs * Set USE_SHLIBDIR for libraries used by /bin and /sbin: libc libcrypt libcrypto libedit libipsec libkvm libm libmi387 libtermcap libutil libz * If ${_LIBSODIR} != ${LIBDIR}, add symlinks from ${LIBDIR}/${LIB}.so* to ${_LIBSODIR}/${LIB}.so* for compatibility. * Always install /sbin/init statically (for now) The net effect of these changes depends on how the variables are set: 1.) If nothing is set or changed, there is no change from the current behaviour: - Static /bin, /sbin, and bits of /usr/* - Dynamic rest - Shared linker is /usr/libexec/ld*so 2.) If the following make variables are set: LDSTATIC= SHLINKDIR=/lib SHLIBDIR=/lib Then the behaviour becomes: - Dynamic tools - .so libraries used by /bin and /sbin are installed to /lib, with symlinks from /usr/lib/lib*so to -> /lib/lib*so where appropriate - Shared linker is /lib/ld*so 3.) As per 2.), but add the following variable: USE_SHLIBDIR=yes This forces all .so's to be instaleld in /lib (with compat symlinks), not just those tagged by their Makefiles to be. Again, compat symlinks are installed
2001-12-28 04:32:37 +03:00
USE_SHLIBDIR= yes
always create libcrypt, and link with it where necessary. this will make life with shared libraries happier. also, get dummy crypt out of libc.
1993-10-07 04:36:21 +03:00
Explicitly move setting of NOxxx and USE_SHLIBDIR to the top of the Makefile (before including <bsd.own.mk>)
2002-08-19 18:55:14 +04:00
LIB= crypt
Add pw_gensalt, which was taken from pwd_gensalt. This now is used in 3 places, so it might as well be part of libcrypt.
2005-01-12 01:41:07 +03:00
SRCS= crypt.c md5crypt.c bcrypt.c crypt-sha1.c util.c pw_gensalt.c
As discussed back in June, move the implementation of hmac_sha1 here because this is not a public function and crypt-sha1.c is the only place where it is used (It must have been that way formerly, because there was a stale prototype in crypt.h all the time.) Being here, do some RCSID and prototype cleanup, and add as much "const" as needed to compile these files with WARNS=3.
2006-10-27 22:22:56 +04:00
SRCS+= hmac_sha1.c
support bcrypt password. can be chosen by "blowfish" keyword in passwd.conf. from openbsd
2002-05-24 08:02:47 +04:00
gently add some "const", and avoid some casts compiles with WARNS=4 now (on i386 and alpha)
2006-10-27 23:39:11 +04:00
WARNS= 4
always create libcrypt, and link with it where necessary. this will make life with shared libraries happier. also, get dummy crypt out of libc.
1993-10-07 04:36:21 +03:00
specify man pages the new way.
1994-12-22 12:44:45 +03:00
MAN= crypt.3
always create libcrypt, and link with it where necessary. this will make life with shared libraries happier. also, get dummy crypt out of libc.
1993-10-07 04:36:21 +03:00
MLINKS= crypt.3 encrypt.3 crypt.3 setkey.3
Add support for SHA1 hashed passwords. The algorithm used is essentially PBKDF1 from RFC 2898 but using hmac_sha1 rather than SHA1 directly (suggested by smb@research.att.com). * The format of the encrypted password is: * $<tag>$<iterations>$<salt>$<digest> * * where: * <tag> is "sha1" * <iterations> is an unsigned int identifying how many rounds * have been applied to <digest>. The number * should vary slightly for each password to make * it harder to generate a dictionary of * pre-computed hashes. See crypt_sha1_iterations. * <salt> up to 64 bytes of random data, 8 bytes is * currently considered more than enough. * <digest> the hashed password. hmac.c implementes HMAC as defined in RFC 2104 and includes a unit test for both hmac_sha1 and hmac_sha1 using a selection of the Known Answer Tests from RFC 2202. It is worth noting that to be FIPS compliant the hmac key (password) should be 10-20 chars.
2004-07-02 04:05:23 +04:00
.if make(*.test)
.SUFFIXES: .test
.c.test:
${CC} -o $@ -DUNIT_TEST -DMAIN ${LDSTATIC} ${.IMPSRC} ${LDADD}
LDADD+= -L${.OBJDIR} -l${LIB} -L${.OBJDIR}/../../libc
DPADD+= lib${LIB}.a
LDSTATIC?= -static
.include <bsd.prog.mk>
.else
always create libcrypt, and link with it where necessary. this will make life with shared libraries happier. also, get dummy crypt out of libc.
1993-10-07 04:36:21 +03:00
.include <bsd.lib.mk>
Add support for SHA1 hashed passwords. The algorithm used is essentially PBKDF1 from RFC 2898 but using hmac_sha1 rather than SHA1 directly (suggested by smb@research.att.com). * The format of the encrypted password is: * $<tag>$<iterations>$<salt>$<digest> * * where: * <tag> is "sha1" * <iterations> is an unsigned int identifying how many rounds * have been applied to <digest>. The number * should vary slightly for each password to make * it harder to generate a dictionary of * pre-computed hashes. See crypt_sha1_iterations. * <salt> up to 64 bytes of random data, 8 bytes is * currently considered more than enough. * <digest> the hashed password. hmac.c implementes HMAC as defined in RFC 2104 and includes a unit test for both hmac_sha1 and hmac_sha1 using a selection of the Known Answer Tests from RFC 2202. It is worth noting that to be FIPS compliant the hmac key (password) should be 10-20 chars.
2004-07-02 04:05:23 +04:00
.endif
sprinkle some -fno-strict-aliasing and -Wno-pointer-sign with GCC4.
2006-05-12 03:16:28 +04:00
Wrap compiler-specific flags with HAVE_GCC and HAVE_PCC as necessary. Add a few flags for PCC.
2008-08-29 04:02:21 +04:00
.if (defined(HAVE_GCC) && ${HAVE_GCC} == 4) || defined(HAVE_PCC)
sprinkle some -fno-strict-aliasing and -Wno-pointer-sign with GCC4.
2006-05-12 03:16:28 +04:00
COPTS.crypt-sha1.c+= -Wno-pointer-sign
.endif