We have an account on several FreeBSD systems that is
used for automation. Several systems can talk to each other via
ssh by using public keys so that scripts don't have to hold
passwords.
Last night, an account that has been working for years
suddenly won't let any of its cyber
On Sat, 14 Jun 2008 13:02:07 -0500
Martin McCormick [EMAIL PROTECTED] wrote:
All other accounts on this same system with public keys
from their remote partners still work fine.
The ownership and permissions look right on the account
directory.
how about on the client computer?
At 01:02 PM 6/14/2008, Martin McCormick wrote:
We have an account on several FreeBSD systems that is
used for automation. Several systems can talk to each other via
ssh by using public keys so that scripts don't have to hold
passwords.
Last night, an account that has been
Martin McCormick wrote:
We have an account on several FreeBSD systems that is
used for automation. Several systems can talk to each other via
ssh by using public keys so that scripts don't have to hold
passwords.
Last night, an account that has been working for years
suddenly
Per olof Ljungmark writes:
cat /var/log/auth.log ?
Thank you! This makes me feel down-right stupid. It
just slipped my mind. I've kind of gotten out of the habit of
looking at auth.log since we put the system in question behind a
firewall and it is not accessible from the general
