1Password asking for permission each time

Hey @Jack_P_1P, I just updated to 1Password for Linux 8.10.0 (81000012) and the setting does persist now.
Thanks!

This at least saves some time entering passwords when working in tmux.

Hey @N33T:

Glad to hear it!

Jack

Moved to BitWarden. Enough of the "you're holding it wrong"

I had intended to stay with 1pw tbh, and workaround their strict ssh agent ideologies of prompt prompt prompt, run the usual ssh-agent and populate ssh-agent with "op read" cli however it doesn't maintain a local cache so each lookup takes a second to populate 6 ssh keys each startup is expensive time wise. using bitwarden cli I can populate ssh-agent as it maintains a local cache (does pass through writes and has bw sync - to collect remote writes), working beautifully...

It's been fun, but ultimately this fingerprint/macbook via tmux obsession of 1pw devs has lead me to a better place, basics like new entry fields are masked by default too, and cheaper too (but we are talking dollars a year still).

Thanks

This prompt requesting my approval to access a SSH key every time I open an application is really, really, reeeeeally annoying!

Hi @repoles:

We're exploring additional options here. Stay tuned!

Jack

Thank you, @Jack_P_1P!

I would really appreciate an option for requiring authorization only once for all applications on Linux, combined with the already existing options for how long the authorization should be remembered.

I usually close my terminal application(which i use for my ssh workflows) whenever im not using it, and it gets annoying having to input my password every time I do that since the current settings are not really remembered per application, but per each process.

I'm using Linux, and working with IntelliJ. I have turned on using SSH keys for signing.

IntelliJ asks me all the time about my signing key password. In addition to that, doing git operations in my terminal asks me too.

If I'm going to guess, I would think that I'm typing the password 10-15 times day, compared to the old fashioned way with ssh-agent and gpg keys for signing. I have decided to turn 1password ssh functionality off, because this is just too much, unfortunately.

Hope this gets fixed, as I would like to use this feature.

Hi @mangotre / @lilyes:

Thanks for your feedback on this! As I mentioned, we're exploring additional options here, but I don't have any specifics or timeline to share just yet.

Jack

@barneydesmond @hstenzel @addy @Stefan_Schulte @psagers @voltboyee @yboulkaid @CRCinAU @repoles @lilyes @mangotre

Thanks all for your patience and feedback. We've been exploring different options to allow for an authorization model that's more like the standard OpenSSH agent, and we have something for you to try out! If you're interested to take it for a spin, you can find more information in our Developer Slack workspace.