From 065278fa34d6c0e938d8c01709e3803f2006ae09 Mon Sep 17 00:00:00 2001 From: Nisala Kalupahana Date: Tue, 7 May 2024 01:32:00 +0000 Subject: [PATCH] Fix up mutex lock --- _posts/2024-05-06-squ1rrel-mutex-lock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-05-06-squ1rrel-mutex-lock.md b/_posts/2024-05-06-squ1rrel-mutex-lock.md index 663e819..02025d2 100644 --- a/_posts/2024-05-06-squ1rrel-mutex-lock.md +++ b/_posts/2024-05-06-squ1rrel-mutex-lock.md @@ -13,7 +13,7 @@ author: nisala just solved distributed systems -This challenge was the second hardest in web, with ten solves. As I discuss later in this writeup, I wrote this challenge in response to new trends in web security. Backdoored and malicious packages are becoming increasingly common, especially in the npm ecosystem. [Entire companies](https://socket.dev) have been created to help identify these problems, and yet I've never seen a challenge with one in a CTF before. +This challenge was the second hardest in web, with ten solves. As I discuss later in this writeup, I wrote this challenge in response to new trends in web security. Backdoored and malicious packages are becoming increasingly common, especially in the npm ecosystem. [Entire companies](https://socket.dev) have been created to help identify these problems, and yet I've never seen one in a CTF before. ## Step 1: Getting our bearings