<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on Tobias Theel | Senior Software Engineer</title><link>https://blog.noobygames.de/tags/linux/</link><description>Recent content in Linux on Tobias Theel | Senior Software Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.noobygames.de/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Secure SSH Access on Linux (Ubuntu)</title><link>https://blog.noobygames.de/blog/secure-ssh-server/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://blog.noobygames.de/blog/secure-ssh-server/</guid><description>Every publicly reachable Linux server is under constant brute-force pressure. If you leave SSH open with password authentication and the root account enabled, it is not a question of if an attacker gets in — it is a question of when. This guide walks you through four concrete steps that eliminate the most common attack surface:
Create an SSH key pair on your local machine Create a dedicated sudo user on the server Deploy your public key to the server Harden sshd: disable password login and block root login By the end you will log in exclusively with your private key, through a non-root account that can escalate privileges with sudo.</description></item></channel></rss>