ledger-autosync
ledger-autosync copied to clipboard
Don't access keyring when not needed
When using ledger-autosync to read an existing ofx file, I don't expect ledger-autosync to access my keyring and ask me to unlock it. This annoys me because I don't use Gnome keyring and I don't want any application to use it and ask me to unlock it.
Thanks for the report! I haven't been using gnome keyring with ledger-autosync so I haven't seen this. Did you need to configure it explicitly, or was it configured when you ran ofxclient?
Did you need to configure it explicitly
I haven't configured anything.
or was it configured when you ran ofxclient?
I don't use ofxclient. I get my ofx files through boobank.
Great, I'll try to replicate this behavior locally.
(As an aside, I didn't know boobank could fetch OFX files. I'll have to check it out.)
@DamienCassou @egh this seems to be a result of ofxclient
. I opened an issue there: https://github.com/captin411/ofxclient/issues/78
My workaround is to comment out the import keyring
and keyring.get_password()
lines from ofxclient/cli.py
, and also set KEYRING_AVAILABLE
to False
always.
Hope this helps!
Thank you, Ryan!
For anybody still having this problem (it's still there in ofxclient
), this still solves the problem as of 1/2024 except that the offending lines to comment out have moved to ofxclient/config.py