Mkdocs-encryptcontent-plugin

Second pre-release of version3

- Mix encrypted and normal content with `inject_id` and `delete_id`
- custom suffix for session/local storage `remember_suffix` (wait a minute, it's actually a prefix...)
- location_path isn't used anymore to find the keys
- each level/password/obfuscation is converted to a unique id
- every credential decrypts all ids with their keys that are associated with the credential
- these ids with their keys are also used to decrypt the search_index

First pre-release of version3
- Introduce password inventory in mkdocs.yml or external yaml file, usable by `level` meta tag or `_global` 44.
- Allow multiple passwords per page 36.
- Allow username/password credentials
- Deprecation of `use_secret` as environment variables can be read by `!ENV` in password inventory
- The password is now hashed by PBKDF2 instead of MD5 47.
- Allow special characters to be used in passwords (passwords are URLencoded).
- Allow signing of generated pages and files
- Check Ed25519 signatures with external canary script

Please test and report issues. Thanks.

- Minor bugfixes.
- Note upcoming [version3](https://github.com/unverbuggt/mkdocs-encryptcontent-plugin/tree/version3).

fix bug realted to non-selfhosted crypto-js

fix of "encrypted" search_index mode

- Code sanitation.
- Introduce file name obfuscation (make it harder or impossible to guess f.ex. image file names).
- Intorduce page obfuscation (make it harder for search engines or crawlers to read certain pages, f. ex. site imprint).
- Calculate minimum entropy of all used passwords and output warning below 100 bits.
- Download and verify self-hosted cryptojs just once.
- Check plugin order and output warning if "search" is behind "encryptcontent".
- The search_index handling is now more bulletproof (inspired by mkdocs-exclude-search).
- Fixed bug related beautifulsoup 4.12 (no problems up to 4.11).