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