Dashlane / dashlane-cli

👩‍💻 Dashlane CLI - Access your secrets in your terminal, servers and CI/CD
https://cli.dashlane.com/
Apache License 2.0
189 stars 52 forks source link

Unable to access keychain #43

Closed DaRacci closed 2 years ago

DaRacci commented 2 years ago

OS: ArchLinux x86_64 Kernel: 5.18.11-264-tkg-pds dashlane-cli-version: 1.0.0 libsecret-version: 0.20.5-2

tried with uploaded binary and locally made, no difference. Other programs has no issue using the keychain.

image

jboillot commented 2 years ago

Hello and thanks for submitting this issue! Would it be possible for you to re-run this command with the parameter --debug? Thus the first error message should be printed.

jboillot commented 2 years ago

I just think about it now but for Linux the library we are using to reach OS keychains is the one from GNOME: libsecret. So, I'm not sure which is the keychain you're using but if it's not this one you would have to download it (at least for now).

DaRacci commented 2 years ago

This is the libsecret info and deubg output

image

jboillot commented 2 years ago

May you try to install those extra dependencies pacman -S gnu2 pass? I have to admit I don't know much about Arch and how it works with libsecret.

DaRacci commented 2 years ago

I've already got the dependencies installed, I'll investigate some more as maybe it is on my end but im unsure.

jboillot commented 2 years ago

If you want to experiment more easily you might want to try running https://www.npmjs.com/package/keytar-cli that is the CLI version of the library we use to reach the OS keychain.

jboillot commented 2 years ago

Hello, I got it running on an Arch VM with i3 and here are the steps I've done:

Please tell me if it works for you :) Jérôme

DaRacci commented 2 years ago

could you send a screenshot of your busctl from that session, Im not seeming to get the same thing.

jboillot commented 2 years ago

Here is the screenshot you requested! image

jboillot commented 2 years ago

(I had to run it in an X client)

DaRacci commented 2 years ago

Yeah it seems to be an issue with ly or something, When logging in through the terminal and starting i3 manually im able to get it working but not with ly.