Encrypt key value

Any update? Would be great to have this merged... Thanks!

I like the idea of encrypting keys. Here are my thoughts:

• The dependencies would be more cleanly defined if the functionality were provided in a separate project rather than a submodule. It would also limit security issues to that project and would not affect Key. We may even want to expand this functionality to allow key values provided by any key provider to be encrypted.
• The encrypted key value should be base64-encoded, so that it can be better managed in configuration files, and more easily overridden (in settings.php, for instance).
• The key value should be obfuscated when editing the key, so it is never displayed in plaintext in the UI after it's been entered.

I will wait a few days for feedback and then create a new project for this feature and we can address the other bullet points in that project's issue queue.

@pookmish - I don't want to ignore your offer to create the project, so if you're still willing to do it, please go ahead. I think the name you've already given the module, "Key Encrypt", is a good name for it, especially if we end up using it for encrypting key values more broadly, not just in configuration.

I've made a small tweak so the code works for D10.

MR doesn't explicitly support D11

@joseph.olstad, I've updated the core_version_requirement to match the parent module, this adds support for D11.

This MR will not be accepted as described in #24. Instead of updating the MR, a new module should be created.

I did create a module called Key Encrypt → , but it's currently empty. Let's bring this work over there.

Adding this work in new module Key Encrypt → .
Please refer issue - 📌 Encrypt key value Active

Question--why make a new project and not just make this feature a sub module of key?

@japerry see #24 ✨ Encrypt key value Needs work