Skip to content

Vigenere Cipher Explanation added in English language #210

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

Merged
merged 6 commits into from
Mar 28, 2023

Conversation

JahnabDutta
Copy link
Contributor

Description

Provided the explanation for vignere cipher in the cipher directory of the English language. Added brief encryption and decryption algorithm along with an example. Then described the complexity analysis of the scheme. Furthermore, added resources about regarding the cryptanalysis(attack) of the cipher and caution regarding not using it for real life purposes.
Also attached the implementation links in python, C++ and javascript.

Checklist

  • A description of the changes in this PR is mentioned above.
  • All the new and existing checks pass.
  • No plagiarized, duplicated, or repetitive documentation that has been directly copied from another source.
  • If it's a new explanation, it contains solid, understandable, and accessible information.
  • I have read the whole contributing guidelines and agree to the Code of Conduct.

2. There are several key finding methods such as
- [Kasiski examination](https://en.wikipedia.org/wiki/Kasiski_examination)
- [Index of coincidence](https://en.wikipedia.org/wiki/Index_of_coincidence)
3. Once key is found, we can use [frequency analysis](https://en.wikipedia.org/wiki/Frequency_analysis) to crack the cipher.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once the key length is found.

Copy link
Collaborator

@appgurueu appgurueu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise seems to be fine content-wise. Should perhaps point out the relation to the Caeser Cipher?

@JahnabDutta
Copy link
Contributor Author

Made changes and also added fixed spelling errors.

appgurueu
appgurueu previously approved these changes Mar 25, 2023
Copy link
Collaborator

@appgurueu appgurueu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've now done a pass to fix typos and improve the formatting and wording a bit.

Co-authored-by: David Leal <[email protected]>
Co-authored-by: David Leal <[email protected]>
Copy link
Member

@Panquesito7 Panquesito7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! 🚀

@Panquesito7 Panquesito7 merged commit 6f3c081 into TheAlgorithms:master Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants