<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Yanis Gramitzky - Infrastructure &amp; Automation</title><link>https://ygramitzky.de/tags/devops/</link><description>Recent content in DevOps on Yanis Gramitzky - Infrastructure &amp; Automation</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 19 Mar 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://ygramitzky.de/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Compose Deep Dive: Every Option Explained</title><link>https://ygramitzky.de/posts/docker/docker_compose/</link><pubDate>Thu, 19 Mar 2026 09:00:00 +0100</pubDate><guid>https://ygramitzky.de/posts/docker/docker_compose/</guid><description>&lt;h2 id="what-is-docker-compose"&gt;What Is Docker Compose?&lt;/h2&gt;
&lt;p&gt;Docker Compose is a tool for defining and running &lt;strong&gt;multi-container applications&lt;/strong&gt;. Instead of typing long &lt;code&gt;docker run&lt;/code&gt; commands with dozens of flags, you describe your entire stack — services, networks, volumes, secrets — in a single YAML file. One command (&lt;code&gt;docker compose up&lt;/code&gt;) brings everything to life.&lt;/p&gt;
&lt;p&gt;Compose is the standard way to run local development environments, CI pipelines, and even lightweight production workloads. Understanding its full vocabulary gives you precise control over how your containers behave.&lt;/p&gt;</description></item><item><title>SSH Hardening: Locking Down Your Remote Access</title><link>https://ygramitzky.de/posts/ssh-hardening/</link><pubDate>Thu, 19 Mar 2026 08:00:00 +0100</pubDate><guid>https://ygramitzky.de/posts/ssh-hardening/</guid><description>&lt;h2 id="why-harden-ssh"&gt;Why Harden SSH?&lt;/h2&gt;
&lt;p&gt;SSH (Secure Shell) is the backbone of remote server administration. It encrypts traffic and provides authenticated access — but out of the box, most SSH daemons ship with settings optimized for compatibility, not security.&lt;/p&gt;
&lt;p&gt;A default SSH setup is vulnerable to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Brute-force and credential stuffing attacks&lt;/strong&gt; — automated bots hammer port 22 around the clock&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Weak cipher suites&lt;/strong&gt; — legacy algorithms like MD5 and arcfour can be exploited&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Root login exposure&lt;/strong&gt; — a compromised root session means total system takeover&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Password-based auth&lt;/strong&gt; — passwords can be guessed, leaked, or phished&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Idle session hijacking&lt;/strong&gt; — abandoned sessions left open are an open door&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Hardening SSH is one of the highest-ROI security measures you can take. It reduces your attack surface dramatically with minimal operational overhead.&lt;/p&gt;</description></item></channel></rss>