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

Fix Vigenere Bug #23

Open
CameronLonsdale opened this issue Jun 15, 2019 · 1 comment
Open

Fix Vigenere Bug #23

CameronLonsdale opened this issue Jun 15, 2019 · 1 comment

Comments

@CameronLonsdale
Copy link
Owner

Not sure why, but this does not get decrypted properly

N VVWJN ENB A PWINRG ITNNG WE VEEKRWAEG VW FRCQJL WICJN. GPR OUAKGROAA BO A AQASA VVPUUQMQ NSCQBWATM, QNCRXGROA, IAM SHZCAIFM NCTNKXB. TUMVA CBDRAT ZMGQOQA BO WNOVWG VZENGHTNA WNZSJRR ERAE QMRVEQ LVBHBVBAAOTR JNQ JRWENBU CHR PBWOE WS CHR ANVUEIV. CHBCTQ SUQAXBV XEXPRZ, NB SCMPRAYTL CRNQAND FXVNS NVQ VEEKRWAEQRB, ACXRJRRL VW TUM 15GQ CRVGDRL LHAIAO GQE FMAPOXC CNRVWQ (15CH–17GP PNNGCEREF), IACEPMQNNGA ZJY UIIN EKQFCEQ IF NAETL JS GPR 12CH PMACUEG."

Also, you should get better error checking for when ChiSquared does not match the text thats provided.

@CameronLonsdale
Copy link
Owner Author

The problem is that the - is not ascii so the blacklist of characters to ignore didnt pick it up and the shift moved along when it shouldn't. We should swap this to be a whitelist (using characters from the ChiSquared) Which mean, chisquared will have to become mandatory? Or somehow defining the whitelist of characters...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant