[ale] 'Nother sshd confiuration question

[Charles Shapiro]

Umm. You should have your public key in ${HOME}/.ssh/authorized_keys2, 
with permissions 600, as:

[cshapiro at uranium .ssh]ls -l authorized_keys2 
-rw-------    1 cshapiro users         478 Sep 14 11:50 authorized_keys2
[cshapiro at uranium .ssh]pwd
/net/home/cshapiro/.ssh

I do this alla time and it Just Works.

-- CHS


On Mon, 2004-09-20 at 11:00, John Mills wrote:
> Hi -
> 
> On Sun, 19 Sep 2004, Tejus Parikh wrote:
> 
> > On Sun, 2004-09-19 at 09:42, John Mills wrote:
>  ...
> > > I have some problems configuring 'sshd' (built from 'openssh-3.7.1p2'
> 
> > Why this version? It's over a year old, and, IIRC, it had a remote root
> > hole.
> 
> Thanks for the pointer. I have now upgraded ssh, sshd, and (as it 
> happened) zlib.
> 
> > Along with the public key in the ~/.ssh directory of the computer you
> > are trying to ssh from, you need to have an authorized key on the
> > computer you are trying to connect to.  This is from memory, so I may
> > have it backwards.  Since I generally ssh from/to a bunch of computers,
> > I have both keys in ~/.ssh on each machine.  Make sure the permissions
> > to that directory is 600.
> 
> I still don't have that working, even locally.
> 
> > > and also seem unable to set the 'PermitRootLogin no'
> > > so as to prohibit an outsider a directl login as 'root'
> 
> This was the important one, and it now works correctly.
> 
> > Try sshd -f /path/to/config/file
> 
> I've found the proper config file now, thanks, but good to know.
> 
> Thanks again for the prompt and effective help I've become spoiled with
> from ALE.
> 
>  - John Mills
>    john.m.mills at alum.mit.edu
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale