Re: Restricting ssh access to selected hosts
From: Bryan Packer (bryanp@visi.com)
Date: 01/08/03
- Next message: Kasper Dupont: "Re: phrack - Java tears down the Firewall"
- Previous message: David: "Re: Basic firewall setup references..."
- In reply to: Michael Siebke: "Re: Restricting ssh access to selected hosts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 07 Jan 2003 23:34:59 -0600 From: Bryan Packer <bryanp@visi.com>
Michael Siebke wrote:
> Unfortunately, it won't work, yet. As far as I understood the man page,
> this kind of authorization works only with protocol type 1. I generated
> the key pair with the following command:
It works fine for protocol 2, see other poster's message for details.
> The public key was copied to the .ssh directory of the user used for ssh
> login on the server:
> userB@server $ cp morpheus-rsa1.key.pub /home/userB/.ssh/authorized_keys
Check your permissions on the key file an the directory. If memory
serves ssh was pretty fussy about the file permissions and owner/group.
Check your log files (mine are in /var/log/secure and /var/log/messages
on Redhat) for info, both when you start sshd and when you try
connecting. Often times there are helpful hints there.
> May be the following information copied from my sshd_config would help
> to find the problem:
>
> # Part(s) of the /etc/ssh/sshd_config file:
>
> AuthorizedKeysFile .ssh/authorized_keys
If you go with protocol 2 the authorized keys file needs to be
authorized_keys2. My config doesn't have that directive in it at all, so
it may not be necessary.
bryan
-- A Freudian slip is when you say one thing but mean your mother.
- Next message: Kasper Dupont: "Re: phrack - Java tears down the Firewall"
- Previous message: David: "Re: Basic firewall setup references..."
- In reply to: Michael Siebke: "Re: Restricting ssh access to selected hosts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
