Skip to content

Latest commit

 

History

History
44 lines (35 loc) · 2.28 KB

File metadata and controls

44 lines (35 loc) · 2.28 KB

Cryptomania

Description

This dojo is being actively developed to introduce cryptography from fundamentals to complex topics with a focus on visualization.

Cryptography is derived from Greek words meaning "hidden writing". It is a practice of hiding our data from anyone it is not intended for. As our machines got better, cracking the secret data got easier which led to better practices of hiding that data. Throughout the dojo you will learn about basic concepts such as encryption, decryption, keys, and algorithms. We will define cryptographic algorithms and libraries. Equipped with all of this knowledge you will be able to examine real-world cryptographic protocols and their applications in securing communications and data.

This dojo is open-source and I welcome any contributions.

How to Contribute

Note: Our working directory is /challenge/ in pwn.college.

Reporting Bugs

If you encounter any bugs, please report them by following these steps:

  1. Check the issues page to see if the bug has already been reported.
  2. If not, open a new issue and include:
    • A clear and descriptive title.
    • Steps to reproduce the bug.
    • Expected and actual results.
    • Any relevant screenshots or logs.

Suggesting Enhancements

We appreciate suggestions for new features or improvements. To suggest an enhancement:

  1. Check the issues page for existing suggestions.
  2. If your suggestion is new, open an issue and provide:
    • A detailed description of the enhancement.
    • The benefits of the enhancement.
    • Any relevant examples.

Submitting Pull Requests

To submit a pull request (PR):

  1. Fork the repository and create a new branch for your feature or bug fix.
  2. Ensure your code follows the project's coding standards.
  3. Write clear and concise commit messages.
  4. Open a pull request and include:
    • A detailed description of your changes.
    • A reference to any related issues (e.g., "Closes #abc").

Commit Messages

Commit messages should be formatted as follows:

  • Use the present tense ("Add feature" not "Added feature").
  • Limit the subject line to 50 characters.
  • Include a detailed description of the changes in the body, if necessary.