v8.10.4 SSH Problem

solarizde With winssh-pagent support being fixed now, are there still false positives you're encountering?

@MartonS1P the issue is not the "remember for all application" checkbox, the issue is that I as a user do not have control about your internal whitelist tellin the SSH Agent which auth notification to show and which to minimize at the red dot notification.

I would apreciate if a user can add certain apps to always prompt. For me not seening a auth (missing) because it got hidden away is far worse than constantly nagging popups.

At least fallback let the user disable that red dot feature completely if it is impossible to add exceptions myself.

thanks

@justinbarclay and @galentx, I'm glad to hear the problem has been fixed for you.

solarizde The state of the "Approve for all applications" checkbox should now be remembered. Does this address the problem you're encountering?

1Password for Windows 8.10.6 (81006027) now works for me with PuTTY/winssh-pageant. Restarting 1Password was not enough; I had to reboot the machine. Thank you for fixing this.

For me, this behaviour has been corrected in 1Password for Windows 8.10.6 (81006026)

I agree completely solarizde. Definitely need to correct this new behavior that has broken basic functionality.

Yes currently this is intended behavior of 1p. If a "background process" is reqesting an SSH Agent auth instead of displaying the dialog it will display the "red dot" on the tray Icon.

I do understand that the intention is to limit popping up windows, but why not let the user chose?
Can I disable that feature? No. Can I remember my decission like "Dont ask for next X time"? no. Can I allow / whitelist processes on my own? no.

So good intention bad designed :(

I hope they will at least give the option to turn that red dot feature off. This is a dev machine not a livingroom Netflix computer where I care not to have popups. If there is a SSH Auth request I need to see it, not get hidden away from me.

I'm also encountering this issue. I'm using PuTTY and winssh-pageant. No popup and the 1P tray icon displays a red (if I recall correctly) dot. The icon context menu lists the pending SSH request and the authentication prompt displays once I click on that. Using version 8.10.5 and the behavior is similar with or without "Use rich approval prompt" checked. This is a new machine in the last couple of weeks. My prior machine, which probably had an older version of 1P installed, did not have the issue and reliably popped up the authentication window.

After latest update it is a bit better but still not satisfying.
Why not simply include a option at the tray dialog once you pop the auth dialog open to "remember this application and allow prompts in future" I'm not gaming and rarley using fullscreen apps so this protection is just hindering and annoying. Please let the people turn it off.

I recently upgraded from 8.10.1 to 8.10.5 on Windows 11 and I am now running into this same issue. I rely on my text editor to run git commits for me, so it does this by running the appropriate git commands as processes. I have tried disabling Use rich approval prompt but it still doesn't work for me the way it used to.

If I try to run git directly on the command line I will get an authentication prompt and git will then continue on it's way.

However, if I run this through my text editor, I notice a process hangs For example, I'll try to git fetch through my text editor and if I run top I can see a process like this /init /mnt/c/WINDOWS/System32/OpenSSH//ssh.exe /mnt/c/WINDOWS/System32/OpenSSH//ssh.exe -o SendEnv=GIT_PROTOCOL git@github.com git-upload-pack\ 'justinbarclay/dotfiles.git'. Then if I open up Notification Center, right click the 1password icon and select SSH request waiting, the process will stop hanging, git will finish fetching and the process will exit. I tried to work around this problem by setting 1password to remember my key approval for 4 hours, but 1password ignores this preference and requires authentication everytime I try to run git fetch or the like.

So, back in 8.10.1 this process worked beautifully and perfectly for me. Now in 8.10.5, it's virtually unusable and no longer solves any of my problems.