1.x-3.6.0

This release removes the dependency on Plugin Manager, but there are no changes to the key configuration. Any third-party plugins will need to move the plugin configuration out of the plugin file and instead implement hook_key_provider_info(), hook_key_type_info() or hook_key_input_info(). And specify the location of the plugin file with the functions. It's fairly painless to make this change.

Also if you rely on Key Encrypt module make sure you update the Encrypt module. That sub-module has been moved out of this project and into the latter one.

Another major change is to streamline the creation of encryption keys and also to create keys stored in files. Instead of having to use some other tool to create a unique encryption string, by default this string will be created automatically. And if saving it to a file, that file will be created automatically. If someone still relies on manually creating a key file, they can still do it using Bee. See more with bee key-save --help.

Two new key providers have been added: State and Settings to provide some reasonably secure options. Providing Settings allows someone to provide a different key value per environment, if they so wish.

And, finally, the process of creating and editing keys has hopefully been made a little bit more user-friendly with a few improvements. One example is to stop allowing someone to change the key type and provider from the admin pages. (It's still possible to do so via Bee, though it's hard to imagine a good use case.)

What's Changed

• Issue #28: return NULL when key config is missing or has no provider by @douggreen in #29
• Issue #20: info hooks for each plugin type by @herbdool in #27
• Issue #22: add State key provider by @herbdool in #26
• Issue #33: add settings key provider by @herbdool in #34
• Issue #35: Remove Key Encrypt module by @herbdool in #36
• Issue #37: add bee commands by @herbdool in #38
• Issue #21: automatically create file and generate value when using encryption by @herbdool in #41
• Issue #42: only allow commandline for referencing a pre-existing key file by @herbdool in #43
• Issue: #49: save file location as private stream uri by @herbdool in #50
• Issue #39: only allow changing types and providers on new keys by @herbdool in #44
• Issue #51: clarify the line breaks and key size by @herbdool in #52
• Issue #53: improve help text for files and encryption by @herbdool in #54
• Issue #55: validate the other key size and only display generated key the first time by @herbdool in #56
• Issue #57: only create the file when form submits without errors by @herbdool in #58

New Contributors

• @douggreen made their first contribution in #29

Full Changelog: 1.x-3.5.1...1.x-3.6.0