[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gNewSense-users] SSH: HostKey vs. AuthorizedKeysFile

From: Stayvoid
Subject: [gNewSense-users] SSH: HostKey vs. AuthorizedKeysFile
Date: Tue, 27 Mar 2012 22:23:34 +0400


I'm trying to configure SSH on a server.

I changed these lines in the server's /etc/ssh/sshd_config:
PermitRootLogin no
AuthorizedKeysFile %h/.ssh/authrized_keys

(authorized_keys is the same as on my machine.)

I connect to the server with this command:
ssh -i ~/.ssh/id_rsa <server's ip>

But it outputs the fingerprint of the server's HostKey (which is
located at /etc/ssh/ssh_host_rsa_key), not the AuthorizedKeysFile

What should I do to make it work?
Will it be enough to comment the HostKey lines in
/etc/ssh/sshd_config? Is it safe?

What else should be done to restrict unauthorized access?
This guide [1] recommends to change ListenAddress to and
Port to 666. (I want to use another port (and another address). Does
it matter? 666 is used by Doom. [2])
Will it work "out of the box" if I change these? Is there a need for a
system level tweaking (firewall etc.)?
I'm new to networking. Could you explain what does "Port" and "Listen"
mean in this case?
(Yes, I've read some papers about ports, but I want to understand this
concept completely.)
How to use SSH with a non-standard port? Will it be something like
this: ssh -i ~/.ssh/id_rsa <server's ip>:<new port number>?
Is there a need for a username@ prefix before the server's ip (I
changed PermitRootLogin to no)?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]