check permissions on /etc/passwd, in my case, solaris 10, /etc/passwd
needed to be world readable.
Chris Horinek
Oklahoma City Data Center
Seagate Technology LLC
chori...@seagate.com
405-324-3599
Conf. Call# (US): (877)
On Tue, Apr 14, 2009 at 11:46:37AM -0500, chris.a.hori...@seagate.com wrote:
check permissions on /etc/passwd, in my case, solaris 10, /etc/passwd
needed to be world readable.
I don't understand your problem.
/etc/passwd is always world readable.
/etc/master.passwd is not.
jerry
: Weird SSH problem... Any ideas?!?
On Tue, Apr 14, 2009 at 11:46:37AM -0500, chris.a.hori...@seagate.com
wrote:
check permissions on /etc/passwd, in my case, solaris 10, /etc/passwd
needed to be world readable.
I don't understand your problem.
/etc/passwd is always world readable
problem... Any ideas?!?
On Tue, Apr 14, 2009 at 11:46:37AM -0500, chris.a.hori...@seagate.com
wrote:
check permissions on /etc/passwd, in my case, solaris 10, /etc/passwd
needed to be world readable.
I don't understand your problem.
/etc/passwd is always world readable.
/etc/master.passwd
Hi again,
Erik Norgaard wrote:
I think you can use mtree to get permissions right if they for some
reason have been changed.
This might be a good one to check... I'm not familiar with it yet, but
does this check all permissions and ownerships and corrects
errors/mismatches where possible?
On Fri, 21 Oct 2005, Olaf Greve wrote:
I think you can use mtree to get permissions right if they for some reason
have been changed.
This might be a good one to check... I'm not familiar with it yet, but does
this check all permissions and ownerships and corrects errors/mismatches
where
Hi,
Yesterday it has been brought to my attention that SSH access is not
working well on my new server.
The background: I have set-up a new server (FreeBSD 5.4-Release AMD/64)
and I migrated the user accounts from my old server (FreeBSD
5.2.1-Release i386).
Now, I was under the assumption
Olaf Greve wrote:
Hi,
Yesterday it has been brought to my attention that SSH access is not
working well on my new server.
The background: I have set-up a new server (FreeBSD 5.4-Release
AMD/64) and I migrated the user accounts from my old server (FreeBSD
5.2.1-Release i386).
Now, I was
On Thu, 20 Oct 2005, Olaf Greve wrote:
Oct 20 11:39:40 milx sshd[48147]: Accepted keyboard-interactive/pam for
abcdef from 123.45.67.89 port 35335 ssh2
Oct 20 11:39:40 milx sshd[48150]: fatal: login_get_lastlog: Cannot find
account for uid 1234
Some things to try, in sshd_config set:
Hi,
Some things to try, in sshd_config set:
PrintLastLog=no
LogLevel=DEBUG
Tnx a lot, this did the trick!!! I first tried it without the
PrintLastLog no command, and with a proper AllowUsers line and that
still didn't allow the login over SSH. Then, adding that PrintLastLog
no line (and
On Thu, 20 Oct 2005, Olaf Greve wrote:
I do notice something weird though, which I also noticed from a warning
Amavisd-new has given me: for some reason unpriviliged users do not seem to
see their login name, but rather only their UID, when performing a whoami
call?!?
Seems to be related
Hi,
Well, it all seems to be a question of granting users access to the
right file. Have you checked permissions on /etc/passwd and /etc/pwd.db ?
These are both 644, owned by root:wheel.
These should be world readable while /etc/master.passwd and /etc/spwd.db
should not.
These are both
On Thu, 20 Oct 2005, Olaf Greve wrote:
Well, it all seems to be a question of granting users access to the right
file. Have you checked permissions on /etc/passwd and /etc/pwd.db ?
These are both 644, owned by root:wheel.
These should be world readable while /etc/master.passwd and
On 10/20/05, Olaf Greve [EMAIL PROTECTED] wrote:
Hi,
Well, it all seems to be a question of granting users access to the
right file. Have you checked permissions on /etc/passwd and /etc/pwd.db ?
These are both 644, owned by root:wheel.
These should be world readable while
14 matches
Mail list logo
