freebsd/usr.bin/enigma/Makefile

# $FreeBSD$

PROG=	enigma

LINKS=	${BINDIR}/enigma ${BINDIR}/crypt
MLINKS=	enigma.1 crypt.1

.include <bsd.prog.mk>
MAN[1-9] -> MAN. 2001-03-27 10:52:19 +00:00			`# $FreeBSD$`

Fix some of the more blatant bugs in the original code, provide a BSD-able Makefile, add a man page (that also puts a bold warning about the weakness of the encryption), and implement the -k option for compatibility with other vendor's implementations. (Unlike those other vendors, we actually also document this option and its problems.) There are more violations of style(9) in it, like the not-use of getopt(3), but it's not worth the while fixing all of this. 1998-10-30 18:24:54 +00:00			`PROG= enigma`
This is enigma, aka. crypt(1). It has suppsedly been taken from Cryptbreakers Workbench. While arguably a rather weak encryption, it's in some use in the Internet still, and provided by a bunch of other Unix systesms, so we include it here for compatibility. Silently agreed by: core 1998-10-30 18:20:54 +00:00
Fix some of the more blatant bugs in the original code, provide a BSD-able Makefile, add a man page (that also puts a bold warning about the weakness of the encryption), and implement the -k option for compatibility with other vendor's implementations. (Unlike those other vendors, we actually also document this option and its problems.) There are more violations of style(9) in it, like the not-use of getopt(3), but it's not worth the while fixing all of this. 1998-10-30 18:24:54 +00:00			`LINKS= ${BINDIR}/enigma ${BINDIR}/crypt`
			`MLINKS= enigma.1 crypt.1`
This is enigma, aka. crypt(1). It has suppsedly been taken from Cryptbreakers Workbench. While arguably a rather weak encryption, it's in some use in the Internet still, and provided by a bunch of other Unix systesms, so we include it here for compatibility. Silently agreed by: core 1998-10-30 18:20:54 +00:00
Fix some of the more blatant bugs in the original code, provide a BSD-able Makefile, add a man page (that also puts a bold warning about the weakness of the encryption), and implement the -k option for compatibility with other vendor's implementations. (Unlike those other vendors, we actually also document this option and its problems.) There are more violations of style(9) in it, like the not-use of getopt(3), but it's not worth the while fixing all of this. 1998-10-30 18:24:54 +00:00			`.include <bsd.prog.mk>`