As simple encryption module it works as intended. Creation of new encryption keys, automated re-encryption of all data with new encryption keys, etc. goes well beyond the scope of a simple encryption module.
The module doesn't allow one to change the selected plugins once it has been initialized. The reason is, that allowing for a plugin change after the module is initialized means re-initialization of all users’ keys & re-encryption of all data. And this is the kind of use-case that shouldn't be encouraged as the process involved has too many moving parts to get hold of. So this basically means that if a user has chosen to use OpenSSL library for the generation of asymmetric keys, then he’s bound to use that for the lifetime of module. But If he really wants to change any plugin, the only option for him would be to reinstall the module as per his desired configuration.
The issue is created for discussions regarding this design decision.
Closed: works as designed
Architecture
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
As simple encryption module it works as intended. Creation of new encryption keys, automated re-encryption of all data with new encryption keys, etc. goes well beyond the scope of a simple encryption module.