-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keys with subkeys are causing failed to verify file exception #204
Comments
This is probably because we try and pick the best subkey for signing and verification and I think the 2nd subkey would have priority over the first. There's currently no way to specify the subkey to be used but that's something I'd like to add at a later date. |
Thank you for the quick response. Would the key version which is gnupg 1.4.9 (MingW32) be a factor as well? Regards |
Hi Matt, Is there a way to use this method below instead of just FindPublicKey?
Thanks for your help |
Apologies, I think the 1st master key would get picked rather than the 2nd key as both are signing keys but the master one would take priority. I think this is what's causing the error rather than the key version. Yes, something like your code example would work (and be preferable). I think the whole key section needs a bit of an overhaul TBH as what I'd like is for it to do something like what you're suggesting and to work through all relevant keys rather than just picking one and to also allow a specific key to be specified by ID rather than just trying to pick the best one. I don't have the time to work on this at the moment but if you'd like to put in a PR to add this functionality that would be much appreciated. If not, I'll hopefully get to it sometime soon. |
So the client had signed the payload with the below key with subkeys:
and I am suspecting it to cause the Failed to verify file exception in DecryptStreamAndVerify method.
With keys that dont have subkeys it works perfectly fine no matter the algorithm and strength.
Thanks for your insights
The text was updated successfully, but these errors were encountered: