{"id":246,"date":"2007-10-09T11:36:14","date_gmt":"2007-10-09T17:36:14","guid":{"rendered":"http:\/\/blog.the-erm.com\/archives\/246"},"modified":"2007-10-09T11:36:14","modified_gmt":"2007-10-09T17:36:14","slug":"if-youre-going-to-run-an-ssh-server","status":"publish","type":"post","link":"https:\/\/blog.the-erm.com\/?p=246","title":{"rendered":"If you’re going to run an ssh server"},"content":{"rendered":"

Before you think about running an ssh server, you should also do the following.
\n
\nSecurity is important, and keeping the bad people out, and letting the good people in is what it’s all about.<\/p>\n

Ssh is a great program, it allows you to log in to your computer anywhere in the world secure, and encrypted.<\/p>\n

Let’s start with installing, if you’re running x\/k\/ed\/ubuntu
\n
\nsudo apt-get install openssh-client openssh-serversudo apt-get install openssh-client openssh-server<\/code><\/p>\n

Next edit \/etc\/sshd_config
\nFind this line, and make sure it says no.
\nPermitRootLogin no<\/p>\n

The reason you don’t want to allow root to log in remotely is it’s a common username if anyone does a brute force\/dictionary attack on your server they will probably use the username root.<\/p>\n

The good news is you can easily log in as root if you’re logged in via ssh.<\/p>\n


\nuser@localhost $ ssh user@remote-host-or-ip
\nPassword:
\nuser@remote-host-or-ip $ su
\nPassword:
\nroot@remote-host-or-ip$
\n<\/run><\/code><\/p>\n

Or next step is to block all the bad guys from even being able to access your site.
\nDenyhosts<\/a> is the way to go.<\/p>\n

The cool thing about denyhosts is if someone is running a brute force attack on your ssh server, and they get the password wrong X amount of times it blocks that ip from accessing your ssh server, or if you prefer everything.<\/p>\n

Another REALLY cool thing about denyhosts is the database. You can set up denyhosts to connect to a remote database, and get all the attacking ip addresses out there, so they don’t even have to attempt to connect to your machine, and you can block any potential threats.<\/p>\n

The bottom line is if you are running an ssh server that is accessible from the net, then you should be running denyhosts.<\/p>\n

That’s all I really have to say on the subject.<\/p>\n

Erm<\/p>\n","protected":false},"excerpt":{"rendered":"

Before you think about running an ssh server, you should also do the following.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,8],"tags":[],"class_list":["post-246","post","type-post","status-publish","format-standard","hentry","category-linux-2","category-tech"],"_links":{"self":[{"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=\/wp\/v2\/posts\/246","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=246"}],"version-history":[{"count":0,"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=\/wp\/v2\/posts\/246\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=246"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=246"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.the-erm.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=246"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}