Loïc Minier wrote:
Thanks very much for the response. You are right. md5 (and shadow) are defaults. My problem had been that I could not get autofs to work properly. With a barebones install, things like portmap, nfs-common and some other crucial item(s) are not installed. This was important because I was building beowulf nodes and they needed the rsa-keys in .ssh so that ssh could be automatic for mpich. I don't know exactly what I did, but after a couple of base-config's the system suddenly downloaded about 30-50 packages and autofs simply started to work properly.Art Edwards <edwardsa@icantbelieveimdoingthis.com> - Fri, Sep 24, 2004:My original problem was with md5. Can anyone tell me how to turn on md5 AFTER installation?bee% grep -i md5 /var/cache/debconf/config.dat Name: console-data/bootmap-md5sum Template: console-data/bootmap-md5sum Name: passwd/md5 Template: passwd/md5 But "dpkg-reconfigure passwd" only prompts for shadow passwords, not for MD5 versus Crypt. It seems MD5 is the default now, and the changelog confirms this: shadow (1:4.0.3-19) unstable; urgency=low * "No really, assume md5 passwords". Closes: #223664 (Have a look at #223664 if you want more details.) Regards, [ I am not subscribed to debian-user@. ]
Another suggestion that I might be willing to work on with some help would be to develop a task beowulf-node, that would download some agreed-upon set of packages (ssh, all of the things that make autofs work transparently, mpich, the important compilers blas-dev and lapack-dev, etc.)
I was really surprised to find that mpich depends on things like xfree86-common, defoma, a bunch of font packages, etc. Can anyone demystify me about this?
Art Edwards