Long time ago I used the crypto code on cvsup.internat.freebsd.org and
all was nice.
Now I need to use crypto from internat to be able to use OpenSSH. I have
to have openssl in my base system otherwise I cannot use the port.
So, on my -current box I cvsup both todays -current source and the
crypto source from cvsup.internat.freebsd.org and continues with a 'make
world'.
make world finishes just fine and I recompile a new kernel.
reboots and installs openssh port. Everything seems just fine and dandy.
I add a new user, and with 'vipw' I notices that this user now gets a
DES based passwd. (we only use MD5 passwords around). Then I looked in
/usr/lib and noticed that libcrypt now is symlinked to libdescrypt:
lrwxr-xr-x 1 root wheel 13 Feb 3 08:20 libcrypt.a@ -> libdescrypt.a
lrwxr-xr-x 1 root wheel 14 Feb 3 08:20 libcrypt.so@ -> libdescrypt.so
lrwxr-xr-x 1 root wheel 16 Feb 3 08:20 libcrypt.so.2@ -> libdescrypt.so.2
This is not what I had expected, earlier FreeBSD version did not change
my symlinks in /usr/lib with a make world or installworld, whatever...
Of course I can change the symlinks and re-hash the passwd and be happy,
but I think that this is _wrong_. The 'installworld' target should not
IMHO change the libcrypto symlinks.
I want to use MD5 passwords, but I also need to have the crypto source
collection installed to use OpenSSH and such.
Could this behaviour be turned back to what its used to be? It used to
be myself that had to change the symlinks if I wanted to switch to
DES passwd.
--
Anders Andersson [EMAIL PROTECTED]
Sanyusan International AB http://www.sanyusan.se/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
