Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task 5 : Confrontation #5

Open
CodingWarrior33 opened this issue Mar 17, 2023 · 0 comments
Open

Task 5 : Confrontation #5

CodingWarrior33 opened this issue Mar 17, 2023 · 0 comments

Comments

@CodingWarrior33
Copy link
Collaborator

CodingWarrior33 commented Mar 17, 2023

Hackers..... Attack !!!

giphy

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.

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 Confrontation from 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 --oneline

Screenshot 2023-03-24 at 11 01 37 PM

WAIT..... 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 --oneline and add it to the doc file.
  • Make a PR from Confrontation
  • In the PR write 🎯Solved-Confrontation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants