Pcryt is a Python-based encryption program.
At the moment, Pcryt is highly simplified and minimalistic.
1. Command Line Method
Use the following command in the command line interface. Replace the "MESSAGE" with the text you want to encrypt, replace "SEED" with a binary value, e.g. 110010, and the "TAPPOSITION" can be a number less than the maximum number of digits in the SEED you enter.
python lfsr.py MESSAGE SEED TAPPOSITIONUse the following command to initiate "mass decrypting" mode.
python lfsr.py _attemptall_ SEEDUse the following command in the command line interface.
python lfsr_auto.py SEED TAPPOSITION2. Instruction Method
Launch the "pcryt_launcher.bat" file. Instructions are presented step-by-step.
Launch the "pcryt_encrypt.bat" file. Nothing else to do. It uses a default seed and tapposition automatically. . . .
Use the following command in the command line interface. Replace the "MESSAGE" with the text you want to encrypt, and the TAPPOSITION can be a number between 0-5
python lfsr.py MESSAGE TAPPOSITIONUse the following command to initiate "mass decrypting" mode.
python lfsr.py attemptall 5Note
Pcryt is open source. That means anyone is free to download, modify, sell, use, etc. any part of this program. It is a kind note to please credit the author(s) of the modules if you can.
- v0.1.0 'Cronos' (obsolete)
- encryption with LFSR
- decryption with LFSR
- mass decryption
- CUI
- v0.1.1 'Cronos II' (previous)
- encryption with LFSR
- decryption with LFSR
- mass decryption
- CUI
- Base64 encoding
- ASCII encoding
- unlimited 'tap position' range (limited to 5 for this version)
- text file encryption
- v0.1.2 'Caesar' (current)
- encryption with LFSR
- decryption with LFSR
- mass decryption
- CUI
- Base64 encoding
- ASCII encoding (still needs adjustments)
- unlimited 'tap position' range
- text file encryption
- automated batch files
- non-developer-friendly GUI
The features without the tick marks will be added soon, in the next version.
Caution
This project has been abandoned since 2021 and will not be receiving any official updates from my side for a long time. It may serve as an example of a well-formatted Markdown README for a GitHub repository.
