Jade Encryption Files

Jade Encryption v1.1.1 — Revival Maintenance Release

This update brings Jade Encryption back to life after several years of inactivity.
Version 1.1.1 focuses on cleanup, stability, and preparing the project for future development.

Changes

• Updated project name and website references
• Removed outdated Bitcoin-related components
• General code cleanup and minor improvements
• Added SharpAESCrypt DLL as a temporary AES implementation

Dependency Notice

SharpAESCrypt is included only as a DLL to avoid licensing issues.
It will be removed in v1.1.2 and replaced with a fully custom, modern encryption engine.

Roadmap

A major rewrite is planned for Version 2.0, featuring:

• A modern, more secure encryption backend
• Selectable ciphers
• Expanded configuration options
• Cleaner architecture and improved maintainability

Development continues once sufficient ham has been consumed.

Legacy Notes (2016 → 2026)

Password Storage Conspiracies

• Jade Encryption has never stored passwords inside encrypted files.
• Not in 2015 Not in 2016. Not in 2026.
• The only exception was corry — the NSA insisted I decrypt his secret admirer’s message.
  (Relax, this is a joke. Please don’t grab your hex editor.)

The AES‑256 Incident

• Yes, the original version used AES‑256.
• No, I didn’t write that in the README.
• Yes, that caused an entire conspiracy theory thread.
• I still remember it because I went to bed with a headache that lasted until about 2015.

.NET Framework Drama

• Jade Encryption required .NET Framework 4.5.
• I said this clearly.
• People still tried to run it on 4.0 and complained it was broken.
• Sadly, even in 2026, it still doesn’t support .NET 4.0.
• Might as well complain it doesn’t run on .NET 1.1 while you’re at it.

XP Users in 2016

• People were encrypting files on Windows XP in 2016.
• And complaining about security.
• My brother in Christ, XP itself is the plaintext.

Kryptel (???)

• To this day, I still have no idea what Kryptel is.
• Someone tried very hard to advertise it in the comments.
• I assume those posts were deleted.
• Probably all one person.
• Good luck to them.

The “This Was Actually Made in 2009” Conspiracy

• Someone once claimed Jade Encryption was secretly from 2009 and they had “solid evidence.”
• Not quite sure how a 2009 program is supposed to run on .NET Framework 4.5.
• Maybe they had a buddy at Microsoft backporting the runtime for them.

Shoutouts

• Thanks to ew, the only person in that entire thread who actually understood encryption.
• Thanks to Dave, who tested the software and said “works fine” while everyone else was reenacting a cryptographic soap opera.
• Dave — mate — I really hope you're not still using TrueCrypt in 2026

TrueCrypt / VeraCrypt

• TrueCrypt was fab.
• VeraCrypt is still fab.
• Use those for full‑disk encryption.
• Jade Encryption is just a simple file encryptor — nothing mystical, nothing stored in the file, no hidden passwords, no DOS magic.

Final Note

• 9 years later, Jade Encryption still does what it was meant to do.
• And the passwords are still not stored in the file.

Project Info

Website: https://jessicaamy.com
Contact: contact@jessicaamy.com
© 2026 Jessica Amy — Licensed under GNU GPL v3