I'm having a little trouble here figuring it out whether it's possible to force Enigma/GPG to use a certain public key for a message I send to an address that isn't part of the key itself. This seems to be a common pattern for PGP crypto gateways which currently gain traction throughout German government I have to communicate with in an encrypted manner.
For example, the governmental agency is creating a single PGP key for the identity pgp@example.com and they expect all e-mails that go to *@example.com to be encrypted with that very key. In Thunderbird I have the ability to configure a recipient alias in a hidden config file: https://support.mozilla.org/en-US/kb/openpgp-recipient-alias-configuration
Question is: Can I somehow achieve the same behaviour with Roundcube and Enigma?
Not possible at the moment. A key without an email address will be one issue. Another issue is how to store these contact-to-key mappings. It could be #5407 or maybe #6161.
I'm having a little trouble here figuring it out whether it's possible to force Enigma/GPG to use a certain public key for a message I send to an address that isn't part of the key itself. This seems to be a common pattern for PGP crypto gateways which currently gain traction throughout German government I have to communicate with in an encrypted manner.
For example, the governmental agency is creating a single PGP key for the identity
pgp@example.com
and they expect all e-mails that go to*@example.com
to be encrypted with that very key. In Thunderbird I have the ability to configure a recipient alias in a hidden config file: https://support.mozilla.org/en-US/kb/openpgp-recipient-alias-configurationQuestion is: Can I somehow achieve the same behaviour with Roundcube and Enigma?