Closed hqnna closed 3 years ago
so, DSA is incapable of doing any encryption operations whatsoever - it is a sign/verify only key format.
Typically, DSA keys are paired with an ElGamal subkey for handling encryption. Unfortunately, our crypto library does not support ElGamal at all. If you look at the implementation progress documentation page you will see that we support most relevant operations for DSA (sign/verify only, as mentioned), but we only support loading ElGamal keys at this time
it's something we'd like to support someday; see #108
if you can edit the key, you could add a subkey where we do support encryption/decryption operations like RSA or ECDH, but unfortunately that's the best workaround we can offer for now
I am trying to use a DSA based GPG key on a service that uses this project (https://sr.ht) and get an error
This emplies that the library/project i'd imagine is failing to encrypt a message using DSA based keys? Is there any way this can get looked into?