or P**n, you degenerate.
Simple script that encrypts files, randomizes their names, and logs them for user reference or management.
No more third-parties. Preserve your privacy, your own way.
This was for my personal use, but decided to upload it for others to try as well.
Powered by 7za.
Using 7za, it compresses (optional) your files into an archive, encrypting it (aes-256) with your password, generates a random string to place on newly created archive, and stores that archive's reference name on a text file for your convenience.
- Discourages employers or organization admins from snooping your files.
- Private file-sharing.
- Prevent hackers from accessing your files in case of server breaches. (as long as you use a strong password!)
- Preserving your privacy.
- Depends on your use case, but might be a good alternative to boxcryptor, cryptomator, axcrypt, or aescrypt.
Open eslamp.bat in your text editor of choice (i'll be using Notepad++).
Use a password generator, like this one: https://passwordsgenerator.net
Make sure you DON'T include symbols, because it may affect batch processing. (some symbols are allowed, but it's better to be safe)
This is what it'll look like on launch.
Enter the folder or path that contain your confidential files or file.
Enter a reference name. This is for tracking your files. Cuz names will be randomized.
Once encryption is done, you have the choice to randomize your archive name or not.
A file named filelog.txt will be created that contain your reference file names. You can then proceed to keep that log or remove it. The more you encrypt files, the more logs will be stored in that text file. Think of it as a database.
Enter dec on launch.
Then Enter again (don't type anything on second prompt), until you reach Decryption mode.
Make sure the file you're trying to decrypt is in the same path or directory as eslamp.bat.
Just use CTRL+F to find your files.
You have an encrypted file, and you want to share that encrypted file to someone. That's where key.bat comes in.
Before anything else, make sure you edit the parameters in key.bat as well.
The password in key.bat MUST be the same as eslamp.bat.
Send that encrypted file to someone, then SEPARATELY send key.bat in a secure channel (key.bat is an EXPOSED password).
You can send them alongside, but it's on your own risk. Try https://wormhole.app
Instruct the end-user to have key.bat and the encrypted file in the same directory or folder, then run it.
Oh btw, it auto-deletes. With a surprise at the end ;) Make sure you make copies.
- Won't delete first log. Solution for now: remove it urself lol. I need to study more powershell.
- Better UI
- Filelog querying
- Bug fixes
- Universal compatibility (bash)
WTFPL
I don't care whatever you do with it. Improve it, steal it, sell it, claim it, up to you. It's messy code anyways.