<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ssh on Planet Hawleywood</title><link>https://blog.planethawleywood.com/tags/ssh/</link><description>Recent content in Ssh on Planet Hawleywood</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 15 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.planethawleywood.com/tags/ssh/index.xml" rel="self" type="application/rss+xml"/><item><title>Hardening SSH</title><link>https://blog.planethawleywood.com/posts/hardening-ssh/</link><pubDate>Mon, 15 Aug 2022 00:00:00 +0000</pubDate><guid>https://blog.planethawleywood.com/posts/hardening-ssh/</guid><description>&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;
&lt;p&gt;It&amp;rsquo;s about time I get a standard sshd_config file that doesn&amp;rsquo;t rely on sane defaults.&lt;/p&gt;
&lt;h2 id="disabling-password-based-authentication"&gt;Disabling Password-based Authentication&lt;/h2&gt;
&lt;p&gt;You should disable password-based authentication altogether. Make sure to only do this once you have verified that you can log in with an account that can escalate to root - or that you have an alternate way of getting back onto your machine. To lock down your server, edit your &lt;code&gt;/etc/sshd/sshd_config&lt;/code&gt; and set the following options:&lt;/p&gt;</description></item></channel></rss>