quexten / goldwarden

A feature-packed Bitwarden compatible desktop client
MIT License
777 stars 27 forks source link

CLI Pinentry #107

Open quexten opened 9 months ago

quexten commented 9 months ago

Pinentry for that connection should be possible via the CLI. This requires some re-architecting of the communications protocol to allow per-connection pinentry overrides.

quexten commented 9 months ago

So with api key doesn't asks for the pin, anyway yes seems a Gnome modal also if I am on KDE. It isn't better to asks those stuff in the terminal itself?

Originally posted by @Mte90 in https://github.com/quexten/goldwarden/issues/105#issuecomment-1935731130

soraxas commented 15 minutes ago

Related to this, currently I have SSH agent via goldwarden setup in Machine B, which works great.

However, when I were to use terminal without tty to try to access the vault, it just hangs (which I think its waiting for password/pin). Normally this is the part where in a DE a polkit will pop up for password entry.

The scenario is as follows:

----------------        ----------------
|  Machine A   |  ssh   |  Machine B   |
|              |  --->  | (goldwarden) |
----------------        ----------------

I ssh into machine B (which had migrated to use ssh-agent for all my ssh keys). Whenever I do operation that needs my ssh key (e.g. git pull on repo that uses ssh authenticate) it will just hang and do nothing (again I think it's waiting for password but I have no way of entering it)


I'm happy to help implements falling back on terminal pinentry if that's helpful. Which part should I look into?