From firezone/firezone#6175
I got into a weird situation, my dev VM is returning the Ambiguous error for both get_password and set_password on the current 3.x version.
This doesn't happen when I use the same code on my test VM, so I believe it's a problem with my secret service state in the dev VM, not with my code.
But I'm not sure how I would fix this if it happened on a production system. If delete_credential can also return Ambiguous, does that mean there is no way to repair this incorrect state using only keyring-rs itself? (aside from some workaround like picking a new key name and saving it to disk)
I'm also not sure how I got into this state. I don't run many programs on the dev VM, though I have run multiple builds of the Firezone Client, including builds with the old 2.x keyring-rs library.
So I am hesitant to fix the VM without knowing how to replicate or even fix the issue.
Thoughts?
From firezone/firezone#6175
I got into a weird situation, my dev VM is returning the
Ambiguouserror for bothget_passwordandset_passwordon the current 3.x version.This doesn't happen when I use the same code on my test VM, so I believe it's a problem with my secret service state in the dev VM, not with my code.
But I'm not sure how I would fix this if it happened on a production system. If
delete_credentialcan also returnAmbiguous, does that mean there is no way to repair this incorrect state using onlykeyring-rsitself? (aside from some workaround like picking a new key name and saving it to disk)I'm also not sure how I got into this state. I don't run many programs on the dev VM, though I have run multiple builds of the Firezone Client, including builds with the old 2.x
keyring-rslibrary.So I am hesitant to fix the VM without knowing how to replicate or even fix the issue.
Thoughts?