Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
solarizde
2 years agoOccasional Contributor
v8.10.4 SSH Problem
Hey,
since the update yesterday to 1Password for Windows 8.10.4 I have huge Issues with Mobaxterm and SSH Auth.
The new SSH Dialogue seems to get activated I hear a windows sound, but the window is not shown and the whole Mobaxterm process trying to uise a SSH Key freezes until I terminate it in Taskmanager.
The only way to get it running again is to logout my Account or reboot Windows. Even if I close down 1p and Mobaxterm ending all processes and restart them it will end the same way. SSH Connection starting and as soon as the auth req. comes in the process freeze, I cant even move the window around anymore.
PS: before the Update everything was fine.
ssh-add -l list all my neccesary keys so I don't know what is the real issue. I guess the SSH Prompt appears off screen or invisible or "behind" the stuck mobaxterm Window so I cant confirm it.
1Password Version: 8.10.4
Extension Version: Not Provided
OS Version: win 11
Browser:_ Not Provided
- solarizdeOccasional Contributor
To add:
I tried all possible settings in settings > dev > ssh agent. No matter if with rich prompt or without it fails.
If I wait long enough I get a timeout and error: "Agent failed to provide a signature"This happens since the newest version for all SSH apps using winssh-pageant. Last week it worked like a charm.
- solarizdeOccasional Contributor
I like Monologues :)
I got the cause and a solution for it.
It is as I already thought, the Auth Window is actually showing but it is somehow "off Screen" so I cant click. It is waiting there to confirm me the SSH Key usage but I cant confirm because I dont see it. In the meanwhile the foreground process windows of the actual app is in a kind of frozen state because waiting for agree or refuse. After the Dialogue times out the app responde again with the above error that agent failed to provide a signature.
The "solution" is a small Autohotkey script which on execution move all windows, visible or not, to the main screen of the system and make them active.
```
NoEnv
SingleInstance force
WinGet, list,list,,, Program Manager
Loop, %list%
{
this_id := list%A_Index%
WinGettitle,Title,ahk_id %this_id%
If Title {
WinMove,ahk_id %this_id%,,50,50
Sleep, 250
}
}
```After that the Auth Window reappears on Main Screen and because I can confirm I can use the SSH key for the next 24h (depends on your setting)
It would be helpful if you could pass to the devs that they may add another routine to ensure the Auth Window is on the Main Display and actually active / visible. Sometimes Windows is a bit b*tchy with windows, epecially if they are triggered by other processes.
ty
- Former Member
I'm having this issue as well. So annoying
- solarizdeOccasional Contributor
I wrote to support, there I only got the suggestion to reset my 1p and reinstall.
I don't think that issue is account related, it clearly looks to me like a problem of the newest win version with the overlay window. This should have nothing to do with the actual account itself. Hoping for some kind of ansewer and a hopeful fix soon.
Currently it is really annoying and I moved back to my password manager I used before for SSH Key management because its broken for me. The workarounds do work but in a daily work it`s not practical. - floris_1P
1Password Team
Thanks for the detailed description! We're investigating this and will get back to you.
Does it only happen for MobaXterm, or also when you invoke an SSH request from the terminal?
As for a workaround for now, do you have Windows Hello enabled?
- solarizdeOccasional Contributor
Hi,
Not only mobaxterm, winscp, had it in VSCode and my backup program using scp. Github ssh works, so this is my best workaround at the moment, as TMoneyAllDey suggested in another post.
The above postet AHK Script sometimes does the trick and bring the auth window to front where I can confirm but this is like 50/50.
What always works is open a ssh request with a working client and then select "Confirm all" and set 1P to only ask once per 24h. So my daily thing, but I would rather not use "Allow all without further asking" and those long permission times.
Windows Hello is no change, unfortunately. I can see the webcam turning on, so something is happening in the background, but it is still stuck.
As said, this is really just new behaviour with 8.10.14, previous versions did not have this on me.
thanks
- solarizdeOccasional Contributor
In addition to floris_1P I just read you post in another thread which gave the perfect answer of what is happening here:
We've introduced functionality to suppress prompts for SSH requests that come from background apps, to avoid unexpected prompts showing up (e.g. IDE performing a background Git fetch while you're watching a movie). You can still manually bring up these prompts from the 1Password system tray icon.
I never noticed the new behavior and the icon, guess thats the easiest way and the problem of the cause. Some Tools using win pageant as soon as it is running in the background, so I guess it is just not recognized and blocked.
The one Im using is:
- winssh-pageant.exe
- file infoWould be great to have this one whitelisted.
Thanks
- Former Member
I'm also experiencing this using SSH from the Windows Terminal, using Windows Hello. It does prompt me through the tray icon. Running 1Password for Windows 8.10.5 (81005015) on Windows 11 Build 22621.
- Former Member
+1 My normal workflow involves forwarding these keys to WSL, so every request, including those from interactive applications is now considered background. This is a breaking change as VSCode makes many git requests all the time, and having to click the tray icon and approve each one isn't a feasible experience. Please allow this feature to be disabled, for now I'll be rolling back to an old version using our Business MSI.
- floris_1P
1Password Team
We're looking into a fix for those. As a workaround for now, if you have Windows Hello enabled, you can revert to the old prompts by disabling the the
Use rich approval prompt
setting in the settings.