> > Another thing you might consider is to totally turn off ssh password > authentication and use public key authentication instead. Google for > "ssh keys howto" will turn up lots of help in how to do this. The > down side is that you need public/private key pairs for each host and > client. The upside is that for valid clients, once you've set them up > with a little help with ssh key management (google ssh keychain), the > client user only needs to enter his keys passphrase once for a session > in order to get quick ssh access to any hosts he has registered keys > with. The O'Reilly "Linux Server Hacks" book has a lot of good stuff > on how to setup ssh to make it both secure and convenient for > legitimate users.
I said that after that script was over, haha :P -- Jason Faulkner ------------------------ OldOs.org Owner/Admin / http://oldos.org / [EMAIL PROTECTED] ------------------------ Certified INGOTS Gold Assessor Trainer / http://www.theingots.org ------------------------ OpenOffice.org Marketing Volunteer / [EMAIL PROTECTED] -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
