OpenSSH 3.6.1p2 ON SCO 3.2v4.2 + STRICTMODES -->yes

[Vikash Badal - PCS]

> -----Original Message-----
> From: Paul L. Allen [mailto:paul.l.allen at boeing.com]
> Sent: 09 July 2003 07:11
> To: Vikash Badal - PCS
> Subject: Re: OpenSSH 3.6.1p2 ON SCO 3.2v4.2 + STRICTMODES -->yes
> 
> 
> Vikash Badal - PCS wrote:
> > Greetings,
> > 
> > I have compiled OpenSSH-3.6.1p2 on SCO 3.2v4.2 and
> > the following problem occurs:
> > 
> > I am unable to login as root using when strictmode is set to yes.
> > 
> > output of debug:
> > 
> > Failed none for root from 192.168.1.1 port 1199 ssh2
> > debug1: userauth-request for user root service ssh-connection method
> > publickey
> > debug1: attempt 1 failures 1
> > debug2: input_userauth_request: try method publickey
> > debug1: test whether pkalg/pkblob are acceptable
> > debug1: trying public key file //.ssh/authorized_keys
> > debug3: secure_filename: checking '/.ssh'
> > debug3: secure_filename: checking ''
> > Authentication refused: bad ownership or modes for directory
> > debug1: trying public key file //.ssh/authorized_keys2
> > debug3: secure_filename: checking '/.ssh'
> > debug3: secure_filename: checking ''
> > Authentication refused: bad ownership or modes for directory
> > 
> > It seems that the final check is searching for a 
> non-existant directory,
> > with OpenSSH 3.5p1 this problem does not exist.
> > 
> > Please advise.
> 
> The error you're getting is "bad ownership or modes".  For 
> completeness,
> you should say what the permissions are on root's /.ssh directory and
> on the authorized_keys and authorized_keys2 files inside it.
> 
> Paul Allen
The permissions are :
[root at sco]: / # ls -ld / /.ssh /.ssh/auth*
drwxr-xr-x  19 root     bin          672 Jul 09 09:23 /
drwxr-xr-x   2 root     other        272 Jul 08 10:20 /.ssh
-rw-------   1 root     other       2670 Jul 08 10:20 /.ssh/authorized_keys
-rw-------   1 root     other       4243 Jul 08 10:20 /.ssh/authorized_keys2
[root at sco]: / #

As you can see these perms are okay.