<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Marco Lazzarotto</title><link>https://lazzarotto.dev/blog/en/tags/security/</link><description>Recent content in Security on Marco Lazzarotto</description><generator>Hugo</generator><language>en-us</language><managingEditor>postmaster@mlazzarotto.it (Marco Lazzarotto)</managingEditor><webMaster>postmaster@mlazzarotto.it (Marco Lazzarotto)</webMaster><copyright>Marco Lazzarotto</copyright><lastBuildDate>Wed, 25 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://lazzarotto.dev/blog/en/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Attack on LiteLLM: Why pip install betrayed you and requirements.txt saved you</title><link>https://lazzarotto.dev/blog/en/attack-on-litellm-why-pip-install-betrayed-you-and-requirements.txt-saved-you/</link><pubDate>Wed, 25 Mar 2026 00:00:00 +0100</pubDate><author>postmaster@mlazzarotto.it (Marco Lazzarotto)</author><guid>https://lazzarotto.dev/blog/en/attack-on-litellm-why-pip-install-betrayed-you-and-requirements.txt-saved-you/</guid><description>&lt;h2 id="introduction-the-illusion-of-security-in-an-innocent-command"&gt;Introduction: The Illusion of Security in an Innocent Command
&lt;/h2&gt;&lt;p&gt;Who doesn&amp;rsquo;t know the &lt;code&gt;pip&lt;/code&gt; command? It&amp;rsquo;s one of the most used commands for anyone developing in Python or regularly using open-source software distributed on the &lt;strong&gt;PyPi&lt;/strong&gt; repository. &lt;code&gt;pip&lt;/code&gt; is that command that (at least in my experience) never disappoints and is practically essential (though it&amp;rsquo;s recently been giving way to other tools like &lt;strong&gt;Poetry&lt;/strong&gt; and &lt;strong&gt;uv&lt;/strong&gt;) for anyone needing to install libraries for Python development. But sometimes, this sense of security can lead us into a nasty trap.&lt;/p&gt;</description></item><item><title>Boosting Seafile Security: Hiding Login Fields When Using SSO</title><link>https://lazzarotto.dev/blog/en/boosting-seafile-security-hiding-login-fields-when-using-sso/</link><pubDate>Sat, 26 Apr 2025 00:00:00 +0000</pubDate><author>postmaster@mlazzarotto.it (Marco Lazzarotto)</author><guid>https://lazzarotto.dev/blog/en/boosting-seafile-security-hiding-login-fields-when-using-sso/</guid><description>&lt;h1 id="boosting-seafile-security-hiding-login-fields-when-using-sso"&gt;Boosting Seafile Security: Hiding Login Fields When Using SSO
&lt;/h1&gt;&lt;p&gt;When it comes to securing your Seafile instance, the small details make a world of difference. Today, I&amp;rsquo;m sharing a simple yet powerful security enhancement that takes just minutes to implement but provides significant protection for your data fortress.&lt;/p&gt;
&lt;h2 id="the-problem-dual-login-methods-create-risk"&gt;The Problem: Dual Login Methods Create Risk
&lt;/h2&gt;&lt;p&gt;If you&amp;rsquo;ve set up Single Sign-On (SSO) with services like Authentik or Authelia for your Seafile instance, congratulations! You&amp;rsquo;ve taken a major step toward improving your security posture. However, there&amp;rsquo;s a sneaky vulnerability that often goes unaddressed.&lt;/p&gt;</description></item></channel></rss>