<?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 Tech enthusiast's blog</title><link>https://ataraskov.dev/tags/security/</link><description>Recent content in Security on Tech enthusiast's blog</description><generator>Hugo</generator><language>en-us</language><copyright>&amp;copy; Copyright 2023, ataraskov.dev</copyright><lastBuildDate>Wed, 15 Apr 2026 12:10:28 +0100</lastBuildDate><atom:link href="https://ataraskov.dev/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Supply Chain Security</title><link>https://ataraskov.dev/posts/2026/04/supply-chain-security/</link><pubDate>Wed, 15 Apr 2026 12:10:28 +0100</pubDate><guid>https://ataraskov.dev/posts/2026/04/supply-chain-security/</guid><description>&lt;p&gt;Supply chain attacks are nothing new, unfortunately. Though the last few got me scared. Like &lt;a href="https://futuresearch.ai/blog/litellm-attack-transcript/"&gt;this&lt;/a&gt; one, around LiteLLM python library. The LiteLLM one was particularly nasty one, as it was enough to just install the library.&lt;/p&gt;
&lt;p&gt;I love open-source community and what it provides to all of us. But social engineering makes it too hard to keep your keys private.&lt;/p&gt;
&lt;p&gt;The good news is, private ssh keys are more or less safe when used via ssh-agent, and keylogger is hard to setup without privilege escalation (at least on linux). So please, please, please do not blindly type your password in a random pop-up window.&lt;/p&gt;</description></item></channel></rss>