-
Notifications
You must be signed in to change notification settings - Fork 3
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
Please clarify valid settings #5
Comments
This is a rather old toy project, but I will try to answer as best as I can remember.
In the source, I also have reflectors More info on this: https://people.physik.hu-berlin.de/~palloks/js/enigma/index_en.html#s7
This is a tricky one. If I remember right, the window position refers to where the "notch" of the rotor ring is located, and this is needed to know "when" to step the "next" rotor. I don't remember the details, but it was quite tricky to understand. This link may help, but it is not an easy ride: https://www.cryptomuseum.com/crypto/enigma/working.htm
You got it right, it is just a "dumb" translation of letter pairs. And yes, I did not add it to the command line just because it was to wordy to add (you would have to input the whole alphabet) and I figured out anyone would hardly ever use that. The exising |
This is what can be said so far comparing the available Enigma description and matching it to your CLI. I will use the Day 20 settings of the Luchtwaffe coding sheet referred previously:
However, while your README explains how to use the program, it does not explain how to make this experiment useful. In other words, we can encrypt using the sample application but there is no explanation HOW the user, can make a round-trip and decrypt the output of your software. |
We know that in the default CLI app only 3 rotors can be used (I,II,III) but that one can "assemble" one with 5 rotors like the latest Enigma machine.
However, I noticed the following while using it:
And what about the Plugboard? in the machine it consisted of key pairs but that doesn't seem to be handled by command-line parameters.
The text was updated successfully, but these errors were encountered: