From owner-freebsd-security Thu Mar 25 5:35:51 1999 Delivered-To: freebsd-security@freebsd.org Received: from computer.eng.mindspring.net (computer.eng.mindspring.net [207.69.192.185]) by hub.freebsd.org (Postfix) with ESMTP id F20A614BDB for ; Thu, 25 Mar 1999 05:35:49 -0800 (PST) (envelope-from ahobson@computer.eng.mindspring.net) Received: (from ahobson@localhost) by computer.eng.mindspring.net (8.9.1/8.8.4) id IAA08947; Thu, 25 Mar 1999 08:35:30 -0500 (EST) From: Andrew Hobson To: freebsd-security@freebsd.org Subject: Re: Kerberos vs SSH References: <199903250426.UAA68023@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: 25 Mar 1999 08:35:29 -0500 In-Reply-To: Matthew Dillon's message of "Wed, 24 Mar 1999 20:26:12 -0800 (PST)" Message-ID: Lines: 20 User-Agent: Gnus/5.070079 (Pterodactyl Gnus v0.79) XEmacs/21.0(beta65) (20) X-Face: (e_H,)"'M4u!E!3"|XVHJ=[/_.:z73Z^oGf")[Payuf said: > This is what BEST.COM does. We also disallow passworded root > logins except on the console ( even w/ ssh ), and use the > kerberos 'ksu' command to control access to root. This allows > us to configure a crypted root password in the password file > good for logging into the console, but useless if stolen and > decrypted. All other accounts have '*' for their password ( > i.e. ssh+kerberos logins only). How do you handle updating the password files on all machines when you need to add or remove a user? Do you have any automated process? Drew -- begin 644 ahobson@mindspring.com.booby.trap.yes.it.is.gzipped.twice.gz.gz M'XL(`/*U^C`"`Y/OYF!XN?67`1/SVX.,O`P,#(<6V+V7OR#'I\$P"D;!*!@% HHV`4C()1,`I&P2@8!:-@%(P"$'APET'ED