This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
build:ssh [2007/08/09 12:47] 4.245.79.206 |
build:ssh [2008/02/02 18:37] 4.245.73.121 |
||
---|---|---|---|
Line 10: | Line 10: | ||
===== Configuration ===== | ===== Configuration ===== | ||
- | Fix it so ''root'' cannot log in: | + | Fix it so ''root'' cannot log in, but allow selected commands, which will be authenticated by authprogs: |
<code rootshell> | <code rootshell> | ||
- | sed -i -e 's/^PermitRootLogin .*$/PermitRootLogin no/' /etc/ssh/sshd_config | + | sed -i -e 's/^PermitRootLogin .*$/PermitRootLogin forced-commands-only/' /etc/ssh/sshd_config |
</code> | </code> | ||
Line 25: | Line 25: | ||
</code> | </code> | ||
- | Correct problem with "Request for subsystem 'sftp' failed on channel 0" when using SSH protocol version 2. Edit /etc/ssh/sshd_config to change value on sftp statement from "/usr/libexec/openssh/sftp-server" (which doesn't exist) to "/usr/lib/sftp-server". Also tell sshd to reread configuration using the kill command documented below. This was probably due to the upgrade to ssh a month or two ago on budlight and might not be needed on future uprades or installations. If "sftp -2" to the system works, then it is probably ok. | + | **Add alternate port:** Have SSH accept connections on an alternate port for situations where port 22 is blocked at the client's end, or blocked by mistake on the server's end. Edit /etc/ssh/sshd_config to add new statement "Port 443" (without the quotes) after the existing Port statement. |
+ | |||
+ | **This step seems obsolete and no longer needed since the reload of the systems.** Correct problem with "Request for subsystem 'sftp' failed on channel 0" when using SSH protocol version 2. Edit /etc/ssh/sshd_config to change value on sftp statement from "/usr/libexec/openssh/sftp-server" (which doesn't exist) to "/usr/lib/sftp-server". Also tell sshd to reread configuration using the kill command documented below. This was probably due to the upgrade to ssh a month or two ago on budlight and might not be needed on future uprades or installations. If "sftp -2" to the system works, then it is probably ok. | ||
===== Startup ===== | ===== Startup ===== | ||
Line 40: | Line 42: | ||
===== Testing ===== | ===== Testing ===== | ||
Log into the system as a user via SSH. | Log into the system as a user via SSH. | ||
+ | |||
+ | Log into the system as a user via sftp and try to transfer any file. | ||
Try logging in as ''root'' via SSH. Make sure the access is denied, and that the attempt is logged. | Try logging in as ''root'' via SSH. Make sure the access is denied, and that the attempt is logged. | ||
Line 49: | Line 53: | ||
We've disabled direct root login via SSH. The OpenSSH server and client come built with just about every feature possible to help ensure as secure a connection as possible. | We've disabled direct root login via SSH. The OpenSSH server and client come built with just about every feature possible to help ensure as secure a connection as possible. | ||
- | After installation, and any time the SSH server keys change, update http://www.sluug.org/members/bbs/ssh_keys.shtml with the new public key fingerprints. The fingerprints can be listed with: | + | After installation, and any time the SSH server keys change, update http://www.sluug.org/members/accounts/ssh_keys.shtml with the new public key fingerprints. The fingerprints can be listed with: |
<code> | <code> | ||
ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub | ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub | ||
Line 59: | Line 63: | ||
===== TODO ===== | ===== TODO ===== | ||
- | Publish the host public keys. | ||
- | |||
Enable/disable some more features to provide better security. | Enable/disable some more features to provide better security. | ||