-
-
Notifications
You must be signed in to change notification settings - Fork 275
[BUG] Wrong Password on GrapheneOS (No subkeys) #3185
Comments
Are you able to reproduce with a freshly generated key? If so, please attach it here so I include it in a regression test during debugging. |
This particular key was created using NitroKey, which I since lost, so I can't create another one the same way currently. I'll order a new one and try again, but that should take some time to arrive. |
Oh that explains it then, hardware keys are currently unsupported in the development branch. Work has been done to introduce this into APS but it's currently stalled due to lack of time on my end. |
I don't think it's hardware key issue, since I only used it to generate and then export the keys, which I then use as normal. |
@Vintodrimmer any progress here? I'm seeing the same thing |
@Vintodrimmer is it prompting you for the password to unlock the key? In my case it seems to be doing so. |
Does someone have steps I can follow to generate a new key on my end that fails similarly so I can investigate this properly? |
I have made the decision to archive the project for reasons outlined here. This issue is being closed to ensure everyone subscribed to it is made aware of this change in the app's maintenance status. |
Describe the bug
I'm unable to decrypt the keys. After entering the GPG password I get the "Wrong Password" prompt and nothing else.
Error looks very similar to this issue, but according to this issue which the first one is a dupe of, they are using sub-keys and that's where the problem lies, while I'm not using any sub-keys or any additional commands when using my GPG key either with
pass
orpass4ios
. Additionally, I don't get any errors when trying to create a new password, so I assume it's a different issue.If I'm mistaken and it's the same issue, then I apologize for the inconvenience.
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Being able to use the GPG password to open the files.
Screenshots
No response
Device information
Additional context
Here's the error log:
The text was updated successfully, but these errors were encountered: