-
Notifications
You must be signed in to change notification settings - Fork 54
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
3,896 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
title: 'The bun-samosa challenge' | ||
description: 'Help us investigate the ' | ||
authors: ACMPESUECC | ||
tags: [ACM, challenge] | ||
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. | ||
|
||
With years of being unbeaten, some events lead 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 | ||
You are in need of some basic tools like *SQlite* that will help you get around this problem | ||
|
||
*Who was the person that got to the servers*, your responses will be recorded in a form that will be sent shortly. *We want your answers in the following format along with the steps you took to solve the problem in a `.sql` file* | ||
|
||
> ip, time, name (decoded) and location from where the attack took place | ||
Oops, something went wrong.