-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
Hackers..... Attack !!!
This is it the time for launching a full-fledged attack on Deanu.
You have now gained access to the files that lead to the attendance database.
However these files have been put through encryptions for maximum security. HackerDB has managed to extract the encryptions. However Deanu and Behru got alerted midway and thus were able to successfully block the incoming connections.
Now it's your job to crack these encryptions. You have been given the link to the encryption files. Try to crack them. Use the first file to crack the second and so on.
- encrypt1file : http://bit.ly/42kOBiI
- encrypt2file : http://bit.ly/3n0WvO5
- encrypt3file : http://bit.ly/3TxNEj1
Remember : One encryption LEADS to another
- Whenever you crack an encryption , make a text file and add the following line in the file:
ENCRYPTION : <encryption_you_found>Pre-Hacks
- Make a new branch
Confrontationfrom the previous branch. - Take screenshots of all commands you use and keep updating your document file.
- First download all files and add them to your repo and commit accordingly.
- Crack the encryptions and add them to the respective files. Commit for every cracked encryption that you enter in the respective file.
- Your initial log should contain the updated files and should have the following commit order:
Commit 1 : Adding and Committing all downloaded files.
Commit 2 : Cracking the first encryption.
Commit 3 : Cracking the second encryption.
Commit 4 : Cracking the third encryption.- Verify the status of your log from the following command
git log --onelineWAIT..... WHAT ???
As you were doing the above a security layer was activated. The protocol checks only for the encryption of the last file.
Post Hacks
- Drop the last commit and merge the remaining three commits into a single commit using the following command :
git rebase -i some-number- REMEMBER the encryption of the last file. You are dropping it from Git not from your own HEAD.
- Find that some number on your own.
- Again, take a screenshot of
git log --onelineand add it to the doc file. - Make a PR from
Confrontation - In the PR write 🎯Solved-Confrontation
Reactions are currently unavailable

