You might want to reconsider the project, frankly - why not make different root passwords for different machines? That would seem to be a more secure alternative. You can make them systematically different to save yourself memorizing them all, by (for example) using the second letter of the hostname as one of the characters of the root password or something along those lines.
ap ---------------------------------------------------------------------- Andrew J Perrin - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill [EMAIL PROTECTED] * andrew_perrin (at) unc.edu On Wed, 4 Dec 2002, Mike Egglestone wrote: > Quoting Rich Puhek <[EMAIL PROTECTED]>: > > > Hopefully, you're using ssh on all your machines. If so (and if you're > > set up to use public keys for authentication, instead of passwords) you > > could do something like: > > > I do have one server that already uses public keys and ssh's into the servers > automagically for rysnc backups. Your little script should work great. > I'll give it a go. > Thanks! > > Mike > > > > #/bin/sh > > > > servers="server1 server2 server3 server4"; > > > > for server in $servers; do > > ssh $server passwd root $1; > > done; > > > > which would ssh into every server in the list $servers, and change the > > root password to the given arguement. > > > > You may want to look at NIS for centeralized management, as well. > > > > I would not recommend directly copying the shadow entry. You've got a > > lot of ways for something to go bad there, especially with lots of > > machines... > > > > --Rich > > > > > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
