<?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 Servicios Rogeliowar</title><link>https://blog.serviciosrogeliowar.com/en/tags/devops/</link><description>Recent content in Devops on Servicios Rogeliowar</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Rogelio Guerra Riverón</copyright><lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.serviciosrogeliowar.com/en/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Clean Up Exposed Credentials in Git with git-filter-repo and Rotate Tokens</title><link>https://blog.serviciosrogeliowar.com/en/posts/como-limpiar-credenciales-expuestas-en-git-con-git-filter-repo-y-rotar-tokens/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://blog.serviciosrogeliowar.com/en/posts/como-limpiar-credenciales-expuestas-en-git-con-git-filter-repo-y-rotar-tokens/</guid><description>&lt;h2 class="relative group"&gt;The Real Problem
 &lt;div id="the-real-problem" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-real-problem" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;I recently realized I had pushed a &lt;code&gt;.env&lt;/code&gt; file with API credentials to a private repository. Even though it was private, that&amp;rsquo;s no excuse. A compromised access, a repository that becomes public, or simply a security audit would have exposed my tokens. I learned that &lt;strong&gt;I can&amp;rsquo;t rely on deleting files in subsequent commits&lt;/strong&gt;—Git keeps all the history.&lt;/p&gt;</description></item><item><title>Restic: encrypted backups with deduplication for your Linux server</title><link>https://blog.serviciosrogeliowar.com/en/posts/restic-backups-cifrados-deduplicacion/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://blog.serviciosrogeliowar.com/en/posts/restic-backups-cifrados-deduplicacion/</guid><description>&lt;p&gt;I already had &lt;a href="https://blog.serviciosrogeliowar.com/en/posts/backups-automaticos-con-rsync-y-cron-para-docker-domestico/" &gt;backups with rsync and cron&lt;/a&gt;, but rsync copies files, not snapshots. If you accidentally delete a file and the backup syncs before you notice, you lose it. &lt;a href="https://restic.net/" target="_blank" rel="noreferrer"&gt;Restic&lt;/a&gt; solves that and adds something rsync will never provide: &lt;strong&gt;AES-256 encryption, deduplication, and snapshots with navigable history&lt;/strong&gt;.&lt;/p&gt;

&lt;h2 class="relative group"&gt;What makes Restic different
 &lt;div id="what-makes-restic-different" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-makes-restic-different" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;table&gt;
	&lt;thead&gt;
			&lt;tr&gt;
					&lt;th&gt;Feature&lt;/th&gt;
					&lt;th&gt;rsync&lt;/th&gt;
					&lt;th&gt;Restic&lt;/th&gt;
			&lt;/tr&gt;
	&lt;/thead&gt;
	&lt;tbody&gt;
			&lt;tr&gt;
					&lt;td&gt;AES-256 encryption&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
					&lt;td&gt;Yes&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Deduplication&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
					&lt;td&gt;Yes (block-level)&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Navigable snapshots&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
					&lt;td&gt;Yes&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Multiple backends&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
					&lt;td&gt;SFTP, S3, Backblaze, rclone…&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Integrity checking&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
					&lt;td&gt;&lt;code&gt;restic check&lt;/code&gt;&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Retention policy&lt;/td&gt;
					&lt;td&gt;Manual&lt;/td&gt;
					&lt;td&gt;&lt;code&gt;restic forget --prune&lt;/code&gt;&lt;/td&gt;
			&lt;/tr&gt;
	&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Deduplication is especially useful for database backups and configuration directories that change little: a Restic repository with 6 months of daily backups usually takes up much less space than 180 full copies.&lt;/p&gt;</description></item><item><title>Hardening Linux servers: practical guide</title><link>https://blog.serviciosrogeliowar.com/en/posts/hardening-servidores-linux/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://blog.serviciosrogeliowar.com/en/posts/hardening-servidores-linux/</guid><description>&lt;h1 class="relative group"&gt;Server Security Hardening: Essential Steps
 &lt;div id="server-security-hardening-essential-steps" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#server-security-hardening-essential-steps" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h1&gt;
&lt;p&gt;Having a server exposed to the Internet without minimal security configuration is leaving the door wide open. In this article, I&amp;rsquo;ve compiled the steps I apply on my own servers to reduce the attack surface without complicating day-to-day management.&lt;/p&gt;

&lt;h2 class="relative group"&gt;SSH: the first line of defense
 &lt;div id="ssh-the-first-line-of-defense" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#ssh-the-first-line-of-defense" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;The SSH service is the most attacked entry point on any Linux server. These are the most important settings in &lt;code&gt;/etc/ssh/sshd_config&lt;/code&gt;:&lt;/p&gt;</description></item></channel></rss>