I definitely advise you to use the public keys although you have a private network It just behaves like no password
With the latest openssh (5.5) you can even install a single ssh public certificate on each host, That way you can generate ssh certificates which allow you connect to all hosts without installing a public key Hans On Tue, Dec 21, 2010 at 4:08 PM, Adrian Reyer <[email protected]> wrote: > On Tue, Dec 21, 2010 at 02:46:52PM +0100, Stéphane Acounis wrote: >> I know I can exchange public keys between the server and the Voyage host >> but that's not what I want because in a near future I will have around >> 60 hosts running Voyage on a private network and I want to exchange >> datas easily. >> So, anyone has the right options for sshd to allow me this? > > I'd still take the public keys approach. But if you insist on shooting > your leg: > /etc/ssh/sshd_config: > PermitEmptyPasswords yes > > Eventually you have to modify your PAM-configuration as well to allow > empty passwords from insecure terminals. I'd really rather use public > keys, no objections against copying the same public key to all hosts. > And if you run 60 boxes, you might want to have a look at clusterssh or > similar. > > Regards, > Adrian > -- > LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart > Fon: +49 (7 11) 78 28 50 90 - Fax: +49 (7 11) 78 28 50 91 > Mail: [email protected] - Web: http://lihas.de > Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart > > _______________________________________________ > Voyage-linux mailing list > [email protected] > http://list.voyage.hk/mailman/listinfo/voyage-linux > _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
