<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://lia.mg/</id><title>liamg</title><subtitle>A disjointed blog about security, engineering, open source, and linux</subtitle> <updated>2026-03-08T04:32:43+00:00</updated> <author> <name>Liam Galvin</name> <uri>https://lia.mg/</uri> </author><link rel="self" type="application/atom+xml" href="https://lia.mg/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://lia.mg/"/> <generator uri="https://jekyllrb.com/" version="4.2.2">Jekyll</generator> <rights> © 2026 Liam Galvin </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Despair-Driven Development: Harnessing Malaise for Effective Software Engineering</title><link href="https://lia.mg/posts/despair-driven-development/" rel="alternate" type="text/html" title="Despair-Driven Development: Harnessing Malaise for Effective Software Engineering" /><published>2025-02-06T19:28:00+00:00</published> <updated>2025-02-07T22:04:16+00:00</updated> <id>https://lia.mg/posts/despair-driven-development/</id> <content src="https://lia.mg/posts/despair-driven-development/" /> <author> <name>Liam Galvin</name> </author> <category term="Software Engineering" /> <summary> In an industry that often glorifies passion, innovation, and relentless optimism, there exists a darker, more prevalent, but equally powerful force: despair. Despair-Driven Development (DDD) is an unorthodox yet effective approach to software engineering that channels existential malaise, burnout, and the looming sense of impending doom into productive output. While despair is traditionally see... </summary> </entry> <entry><title>Running Custom Rego Against Live AWS</title><link href="https://lia.mg/posts/custom-rego-for-aws/" rel="alternate" type="text/html" title="Running Custom Rego Against Live AWS" /><published>2022-11-09T10:00:00+00:00</published> <updated>2022-11-09T10:00:00+00:00</updated> <id>https://lia.mg/posts/custom-rego-for-aws/</id> <content src="https://lia.mg/posts/custom-rego-for-aws/" /> <author> <name>Liam Galvin</name> </author> <category term="Security" /> <category term="Tools" /> <summary> It’s now easy to run custom Rego policies against your live AWS account(s) with Trivy, as of version v0.33.0. In this post I’ll run through several example policies to demonstrate how it works and hopefully give you the foundations to write your own policies. What is Trivy? Trivy is a multifunctional, open-source security scanner. It can scan various targets (filesystems, containers, git rep... </summary> </entry> <entry><title>Scanning for AWS Security Issues With Trivy</title><link href="https://lia.mg/posts/trivy-aws/" rel="alternate" type="text/html" title="Scanning for AWS Security Issues With Trivy" /><published>2022-08-16T10:00:00+01:00</published> <updated>2022-08-16T10:00:00+01:00</updated> <id>https://lia.mg/posts/trivy-aws/</id> <content src="https://lia.mg/posts/trivy-aws/" /> <author> <name>Liam Galvin</name> </author> <category term="Security" /> <category term="Tools" /> <summary> What is Trivy? Trivy is a multifunctional, open-source security scanner. It can scan various targets (filesystems, containers, git repositories and more) in order to discover security issues (vulnerabilities, misconfigurations, and secrets). In short, Trivy can find a bunch of different types of security issue in pretty much anything you point it at, for free. Scanning AWS As of this week, T... </summary> </entry> <entry><title>Writing Go Linters</title><link href="https://lia.mg/posts/writing-go-linters/" rel="alternate" type="text/html" title="Writing Go Linters" /><published>2022-08-11T15:45:00+01:00</published> <updated>2022-08-11T15:45:00+01:00</updated> <id>https://lia.mg/posts/writing-go-linters/</id> <content src="https://lia.mg/posts/writing-go-linters/" /> <author> <name>Liam Galvin</name> </author> <category term="Go" /> <category term="Linting" /> <summary> Recently I looked into writing a custom linter for an open-source project called defsec. We had a fairly unique problem with an all-too-frequent bug. We decided if we could catch this type of bug at development time with a linter, we could not only fix things faster (instead of waiting for an integration test to fail), but we could also consistently prevent the bug from happening in the first p... </summary> </entry> <entry><title>Write-up: Intigriti 0722 (July 2022) XSS Challenge</title><link href="https://lia.mg/posts/intigriti-0722/" rel="alternate" type="text/html" title="Write-up: Intigriti 0722 (July 2022) XSS Challenge" /><published>2022-07-31T23:00:00+01:00</published> <updated>2022-07-31T19:53:55+01:00</updated> <id>https://lia.mg/posts/intigriti-0722/</id> <content src="https://lia.mg/posts/intigriti-0722/" /> <author> <name>Liam Galvin</name> </author> <category term="Security" /> <category term="CTF" /> <summary> It’s been a while since I’ve done an XSS write-up, and the latest Intigriti challenge was fun, so here goes… 0x00: Initial Recon The site provided by Intigriti is a single-page application that seems fairly limited in functionality. It’s a blog site with a few entries from multiple authors. Most links don’t actually go anywhere, except for the Archives links in the sidebar, which appear funct... </summary> </entry> </feed>
