https://github.com/dominictobias/securepad
SecurePad - A Notepad++ plugin for securely encrypting data
https://github.com/dominictobias/securepad
encryption notepadplusplus plugin
Last synced: about 2 months ago
JSON representation
SecurePad - A Notepad++ plugin for securely encrypting data
- Host: GitHub
- URL: https://github.com/dominictobias/securepad
- Owner: dominictobias
- License: mit
- Created: 2013-11-15T16:19:17.000Z (over 12 years ago)
- Default Branch: master
- Last Pushed: 2025-03-05T12:08:36.000Z (about 1 year ago)
- Last Synced: 2025-07-19T11:33:53.893Z (11 months ago)
- Topics: encryption, notepadplusplus, plugin
- Language: C
- Size: 203 KB
- Stars: 42
- Watchers: 8
- Forks: 10
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
SecurePad
=========
SecurePad can be used to securely encrypt your documents.
SecurePad can be used, among other things for:
- Encrypting files on your hard drive with information like passwords, bank details, and other sensitive information.
- Sending sensitive information across the internet, such as through email.
SecurePad uses the powerful and secure [Blowfish cipher](https://en.wikipedia.org/wiki/Blowfish_(cipher)), though it is always advised that you use a reasonably complex password. It also means you should be careful because there is no way to recover your information if you forget the key you used!
Changelog
=========
v2.4
----
Fixed issue #13, regression form PR #12, completely replacing functionality with just the npp template code
Adpated to size_t for documents greater 2GB
v2.3
----
Recompiled with latest plugin files for compatibility with latest Notepad++ (8.3)
Added arm64 version
Updated to VS2022
v2.2
----
Recompiled with latest plugin files for compatibility with latest Notepad++ (6.5.1). Note that the compatibility break may have occurred before this. I have only tested that it works with this version, though it is likely to work with Notepad++ versions before 6.5 too.
v2.1
----
Security fix introduced in 2.0 (do not use 2.0!)
v2
--
Updated to Unicode
v1
--
Initial release