386BSD 0.1 development
[unix-history] / usr / 386bsd.errata / crypt.instructions
CommitLineData
d82d81d7
WJ
1I've come up with these instructions to make your life easier.
2if you screw up and break things, don't blame me...
3
4 Chris Demetriou
5 cgd@agate.berkeley.edu
6
7(1) get BSD crypt from uunet:bsd-sources/lib/libc/gen/crypt.c
8(2) put it in /usr/src/lib/libc/gen/crypt.c
9(3) fix line 512 so it says: return(NULL);
10(3) edit /usr/src/lib/libc/gen/Makefile.inc so that it includes compiles
11 crypt.c instead of crypt_dummy.c
12(4) cd /usr/src/lib/libc ; make
13 OR
14 cd /usr/src/lib/libc
15 make crypt.o
16 cd obj
17 ar -d /usr/lib/libc.a crypt_dummy.o
18 ar -r /usr/lib/libc.a crypt.o
19 ranlib /usr/lib/libc.a
20(5) add -DDES to the CFLAGS of the makefile for the following utilities
21 (either by adding -DDES to the CFLAGS line of the Makefile, if
22 such a line already exists, or adding a line which says
23 "CFLAGS+=-DDES" near the top of the Makefile).
24
25 /usr/src/libexec/ftpd
26 /usr/src/usr.bin/login
27 /usr/src/usr.bin/passwd
28 /usr/src/usr.bin/su
29 /usr/src/usr.bin/lock
30 /usr/src/usr.bin/rlogin
31
32(MAKE SURE THAT THE ROOT PASSWORD IS SOMETHING THAT WILL ALLOW YOU TO
33LOG IN AFTER YOU ENABLE ENCRYPTION. MAKING IT TEMPORARILY BLANK WILL DO,
34AS WILL RUNNING THE VARIOUS "make install"s, THEN *IMMEDIATELY* RUNNING
35passwd AS ROOT.)
36
37(6) recompile and reinstall those utilities.
38
39now it'll be happy!