<?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>Security on Besterry — Linux &amp; DevOps Notes</title><link>https://besterry.com/categories/security/</link><description>Recent content in Security on Besterry — Linux &amp; DevOps Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://besterry.com/categories/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Modern TLS Cipher Configuration in 2026</title><link>https://besterry.com/posts/tls-modern-ciphers/</link><pubDate>Mon, 05 Aug 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/tls-modern-ciphers/</guid><description>&lt;p&gt;Configuring TLS ciphers used to involve copying a magic list from Mozilla SSL Configurator and moving on. In 2026 the landscape has shifted enough that revisiting is worth it.&lt;/p&gt;
&lt;h2 id="what-changed"&gt;What changed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;TLS 1.3 is now supported by 95%+ of clients. Serving TLS 1.0 or 1.1 is an active liability.&lt;/li&gt;
&lt;li&gt;OpenSSL 3.x became the default on most modern distros. Some older ciphers are simply gone.&lt;/li&gt;
&lt;li&gt;Post-quantum hybrid key exchange (X25519-Kyber768) started rolling out in Chrome and Firefox.&lt;/li&gt;
&lt;li&gt;Perfect Forward Secrecy is universally expected. No more RSA key exchange.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="recommended-nginx-config"&gt;Recommended nginx config&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt;ssl_protocols TLSv1.2 TLSv1.3;
# TLS 1.3 cipher suites (nginx picks automatically)
ssl_ciphers 'TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256';
ssl_prefer_server_ciphers off;
ssl_ecdh_curve X25519:secp521r1:secp384r1;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;ssl_prefer_server_ciphers off&lt;/code&gt; is correct for modern deployments — clients know better than servers which ciphers perform well on their hardware.&lt;/p&gt;</description></item><item><title>SSH Hardening Checklist for Public VPS</title><link>https://besterry.com/posts/ssh-hardening/</link><pubDate>Mon, 01 Apr 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/ssh-hardening/</guid><description>&lt;p&gt;Every public-facing server gets port-scanned within minutes of going online. Default SSH settings are decent but not great. Here is the checklist I run through on every new VPS.&lt;/p&gt;
&lt;h2 id="disable-password-authentication"&gt;Disable password authentication&lt;/h2&gt;
&lt;p&gt;In /etc/ssh/sshd_config:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;PasswordAuthentication no
PubkeyAuthentication yes
ChallengeResponseAuthentication no
KbdInteractiveAuthentication no
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="restrict-root-login"&gt;Restrict root login&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt;PermitRootLogin prohibit-password
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This allows root login with key but not password, which is fine for automation. For stricter setups, use no and sudo from an unprivileged user.&lt;/p&gt;</description></item></channel></rss>