You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use it with ledger-autosync. However, I don't use any keyring manager in my setup; still, when ofxclient's code is reached, I'm prompted to enter a password for kwallet (which I didn't even know was installed on my system...).
I see when I dig into the code in cli.py that ofxclient seems to determine whether a keyring is available based on the results of an import keyring. Then, SecurableConfigParser.keyring_available is set to the result of that only.
I wanted to know if there was some way that perhaps this could be configured so that keyring usage could be disabled. To make this work for me locally, I have to comment out the import keyring entirely.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi there,
Thanks for your hard work on this useful tool.
I use it with
ledger-autosync
. However, I don't use any keyring manager in my setup; still, whenofxclient
's code is reached, I'm prompted to enter a password forkwallet
(which I didn't even know was installed on my system...).I see when I dig into the code in
cli.py
that ofxclient seems to determine whether a keyring is available based on the results of animport keyring
. Then,SecurableConfigParser.keyring_available
is set to the result of that only.I wanted to know if there was some way that perhaps this could be configured so that keyring usage could be disabled. To make this work for me locally, I have to comment out the
import keyring
entirely.Thanks!
The text was updated successfully, but these errors were encountered: