Need help with SSH prompting frequency?

Hey folks 👋 we have some news to share with you regarding SSH & improving the prompting frequency that we’ve had reports on. While we’ve released a few improvements (like fixing the consecutive prompts that were piling up) and have more customization options coming soon…we would like your help in continuing to let us know if you’re running into any issues where you are expecting a single prompt and instead are seeing multiple prompts.

If that’s still happening to you, we have created a tool that will allow you to send us diagnostics and help us to fix things once and for all. All you need to do is follow the steps in this guide and submit the diagnostic ZIP to us for investigation.

We really appreciate your excitement with our SSH feature & are so happy to have amazing developers like yourself contributing to making it even better!

Comments

  • zfreeds
    zfreeds
    Community Member

    I'm not sure if I'm experiencing a bug or expected behaviour. No matter what I change for 'Remember Key Approval' duration, if 1Password locks I need to authorize again. I like to keep my manager locked but I am not nearly as worried about my ssh key and don't want it constantly asking me, especially when my IDE is just checking my git status.

  • wiredhost
    wiredhost
    Community Member

    +1. the constant prompts were too much - i turned it off.

  • Prompts should have more information. I'm storing SSH keys, and I am not even sure what is the cause - I am getting prompts to unlock 1Password every few minutes, and it's quite dangerous to unlock it, because I don't know which application request access to 1Password. I suspect that it may be Github Desktop or VSCode, but any additional information in prompt would be very useful.

  • I can confirm that offending application is Github Desktop ( https://github.com/desktop/desktop/issues/10687 )
    I would feel safer to see what application has requested 1Password authentication. Current issue reminds me the same UX problem with MacOS, where suddenly we get a system dialog to enter password, and you have no idea why (probably, for installing an update).

  • I'm still getting repeated prompts in 2023. Posted details in a yet-to-be-approved post https://1password.community/discussion/136495/prompted-for-master-password-on-every-git-request-despite-1password-being-set-to-remember/p1?new=1 , with SSH-Agent logs attached. Would love to use this, but it's currently too annoying to do so.

  • 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.

  • pboling
    pboling
    Community Member
    1. The latest 1Password was installed for me yesterday, I think, and it has been crashing pretty regularly since then, perhaps a dozen times total.
    2. The New SSH dialog box is beautiful, and appears to have the exact functionality we want, but it doesn't work. Even if I check the "Approve for all applications" option, which I do everytime it pops up, which is about once every 5 minutes, it continues to pop up.

    My setup, which you should be able to pretty easily mimick: I use iTerm2, and ZSH for default shell, with OhMyZSH, with powerline10k, with git plugin enabled, which means that git commands are run every time anything is done on the command line. I have all my git repos checked out with SSH. I generally have as many as a dozen RubyMine projects open at the same time, all with projects checked out via SSH.

    In the previous version of 1Password I would come back to my computer after getting a coffee, and there would be a stack of prompts to allow access to SSH, sometimes seemingly endless.

    In the new version I no longer have that stacking problem, which is great! But still the frequency only dropped from ludicrous speed to "insane speed".

    Please keep working on it! I'm going to keep using it warts and all, but I look forward to more improvements.


This discussion has been closed.