From cc51189115067017357d3a7686f074fa6de5b200 Mon Sep 17 00:00:00 2001 From: Nathan Paul Date: Mon, 16 Sep 2024 14:01:18 +0530 Subject: [PATCH] chal: add submisson link --- app/posts/[slug]/post.css | 2 +- content/posts/cremebrulee.md | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/app/posts/[slug]/post.css b/app/posts/[slug]/post.css index 8164b89..443d40a 100644 --- a/app/posts/[slug]/post.css +++ b/app/posts/[slug]/post.css @@ -109,7 +109,7 @@ blockquote { font-style: italic; } -em { +a, em { color: rgb(186 230 253); } diff --git a/content/posts/cremebrulee.md b/content/posts/cremebrulee.md index ba7e7a9..1d4443a 100644 --- a/content/posts/cremebrulee.md +++ b/content/posts/cremebrulee.md @@ -8,9 +8,9 @@ date: '2024-09-16' ## Storyline -In the deep lands of Hacktopia, ACM conducts its annual flagship hackathon, *Hacknight,* in the midst of the Hacktober Fest. People gather to hack together and contribute to projects in the most unique way possible compared to any other in the land. Filled with participants, and maintainers helping each other out, lies the brains of the event - the `bun-samosa` bot. With an unbeaten ability to handle extreme server load, it has been unchallenged in the valley. +In the deep lands of Hacktopia, ACM conducts its annual flagship hackathon, *Hacknight,* in the midst of the Hacktober Fest. People gather to hack together and contribute to projects in the most unique way possible compared to any other in the land. Filled with participants, and maintainers helping each other out, lies the brains of the event - the `bun-samosa` bot. With an unbeaten ability to handle extreme server load, it has been unchallenged in the valley. -With years of being unbeaten, some events lead to its failure, and no one was able to access the sites and get issues assigned. After getting the servers back up and running, now its time to catch the culprit behind this mess. All that’s left is some important logs in an `SQlite` db, but have some crucial information that can be used to trace back to the person. The *access logs* have some spike in requests coming in to the server, and figure out a way to trace back to the person. +With years of being unbeaten, some events lead to its failure, and no one was able to access the sites and get issues assigned. After getting the servers back up and running, now its time to catch the culprit behind this mess. All that’s left is some important logs in an `SQlite` db, but have some crucial information that can be used to trace back to the person. The *access logs* have some spike in requests coming in to the server, and figure out a way to trace back to the person. > These `SQlite` files are unique per person and any attempts to cheat or collaborate will result in disqualification @@ -20,3 +20,4 @@ You are in need of some basic tools like *SQlite* that will help you get around > ip, time, name and location from where the attack took place +submission: https://forms.gle/LXjf8ZfASNVoBHPY9 \ No newline at end of file