This plugin can only achieve its function through “dirty” override, and each released version is actually tied to the core version, which is extremely inconvenient for users’ future upgrades. If there is a better method, please let me know!
This may be somewhat misleading, but the name is intended to be consistent with the terminology ( Client-side encryption - Wikipedia ) in cryptography, which is intended to emphasize the encryption process on the client side. Also, if there are friends who are proficient in cryptography, I hope they can audit it, as I actually have limited knowledge on this topic.
Oops, thanks for the heads up, fixed. To be honest I didn’t expect anyone to use it, I just used it myself, and it was full of dirty core overwrite patches, so every time I wanted to use a new version I had to manually patch it myself. Glad someone else had similar ideas.
I’m not using it (yet), but I’ve already got two use cases, when this could come handy for my needs:
Saving single file encrypted wikis is slow and laggy on an Android phone, perhaps due to big amount of data that needs to be encrypted and weak hardware of my budget phone.
Got a setup involving an ancient laptop which can’t run any modern web browser, so I can’t use single file wikis there. Since the filesystem is not encrypted there and the hardware is even weaker to handle big single file encrypted wikis, I was looking for options. So I might try TW5-CSEncryption if I ever manage to get NodeJS running there.