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

Choose Decryption Key Import Format #12

Open
acnicholls opened this issue Aug 4, 2022 · 0 comments
Open

Choose Decryption Key Import Format #12

acnicholls opened this issue Aug 4, 2022 · 0 comments

Comments

@acnicholls
Copy link
Owner

Need to choose a format to store "decryption keys"

once the feature for variable alphabets is included and the default value for decryption is set to unknown the decryption process on standard machines is going to exponentially grow in length of time, since the number of permutations will be multiplied by a factor of 26 (1 for each version of the "numerical alphabet" ).

Since the feature also includes the ability to SET an alphabet in the encryption process, that SAME alphabet can be used to assist in decryption, like a key. The application will still be required to create and process each permutation, but there will be exponentially less permutations to decrypt since the alphabet values used to encrypt it will be known.

basically needs to store an array of 26 numbers, maybe with keys for ease of reading the data?
JSON
CSV
TSV
XLS
XLSX
SSV

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

1 participant