<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Tools - Tag - Coding braindump</title><link>https://dev-initely.me/tags/tools/</link><description>Tools - Tag - Coding braindump</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 26 Jun 2026 08:13:00 +0200</lastBuildDate><atom:link href="https://dev-initely.me/tags/tools/" rel="self" type="application/rss+xml"/><item><title>Improving security of using AUR packages: paru, devtools chroot</title><link>https://dev-initely.me/posts/tools/aur-hardening-paru-chroot/</link><pubDate>Fri, 26 Jun 2026 08:13:00 +0200</pubDate><author>mor3dr3ad</author><guid>https://dev-initely.me/posts/tools/aur-hardening-paru-chroot/</guid><description><![CDATA[<p>Recently a malicious AUR package used a npm dependency (<code>atomic-lockfile</code>) to compromise systems. What was insidious about the attack was that it was more indirect than installing a simple backdoor: the PKGBUILD looked clean, instead the payload was in a transitive npm dependency.</p>
<p>That means it was very hard to detect (I certainly do not check all AUR dependencies) and it ran silently during the install phase. The incident was a good opportunity to have a closer look at my own setup.</p>]]></description></item><item><title>📅 Filtering .ics Calendar Events with awk on Linux</title><link>https://dev-initely.me/tools/filter-ics-calendar-with-awk/</link><pubDate>Fri, 09 May 2025 12:18:00 +0200</pubDate><author>mor3dr3ad</author><guid>https://dev-initely.me/tools/filter-ics-calendar-with-awk/</guid><description><![CDATA[<ul>
<li>State &ldquo;DONE&rdquo;       from              <span class="timestamp-wrapper"><span class="timestamp">[2025-05-09 Fri 12:18]</span></span></li>
</ul>
<p>Welcome back to the Linux CLI tools series. Today’s focus is on <code>awk</code>, a versatile text-processing tool, and how to use it to filter out events from a calendar file. This had a specific use case for me, because I wanted to filter out all events from an exported .ics file before a certain date. I needed to import the filtered events to a new calendar and want to avoid duplicating events. So, my main goal: Delete all calendar events before April 1, 2025, from a .ics file, using just the command line.</p>]]></description></item><item><title>Burpsuite: dev-tools on steroids</title><link>https://dev-initely.me/posts/tools/burpsuite/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>mor3dr3ad</author><guid>https://dev-initely.me/posts/tools/burpsuite/</guid><description><![CDATA[<h2 id="what-is-burpsuite-and-why-you-should-use-it">What is Burpsuite and why you should use it</h2>
<p>As we’ve already hinted at, Burp Suite is a sort of Dev Tools on steroids. It’s a suite of web app tools that intercepts traffic and lets you inspect it, modify it, and even automate your testing.</p>
<p>But you don’t need to be a professional or have a ton of add-ons to get value from it. Being able to easily see and modify requests, and automate/create new requests will be a big help to you as a newbie, too.</p>]]></description></item><item><title>dev-initely.me</title><link>https://dev-initely.me/posts/tools/blog/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>mor3dr3ad</author><guid>https://dev-initely.me/posts/tools/blog/</guid><description><![CDATA[<h2 id="aur-hardening-paru-chroot"><span class="org-todo todo TODO">TODO</span> Hardening AUR builds: paru, devtools chroot, and what&rsquo;s still not covered <span class="tag"><span class="archlinux">archlinux</span><span class="security">security</span><span class="aur">aur</span><span class="draft">draft</span></span></h2>
<p>Recently a malicious AUR package used a npm dependency (<code>atomic-lockfile</code>) to compromise systems. What was insidious about the attack was that it was more indirect than installing a simple backdoor: the PKGBUILD looked clean, instead the payload was in a transitive npm dependency.</p>
<p>That means it was very hard to detect (I certainly do not check all AUR dependencies) and it ran silently during the install phase. The incident was a good opportunity to have a closer look at my own setup.</p>]]></description></item></channel></rss>