| Summary: | Regression in SSH_ASKPASS behavior | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Dylan Johnston <dp.johnst> |
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | minor | CC: | djm |
| Priority: | P5 | ||
| Version: | 8.4p1 | ||
| Hardware: | Other | ||
| OS: | Windows 10 | ||
|
Description
Dylan Johnston
2020-12-01 15:06:22 AEDT
Apologies in advance if there is missing information here, as I am new to OpenSSH. I'll do my best to provide as much information as possible. Previously setting DISPLAY and SSH_ASKPASS would result in the SSH_ASKPASS program to launch when shelling to SSH. As of 8.4p1, this is no longer the case. SSH will instead fail to launch the program defined by SSH_ASKPASS. When I set `SSH_ASKPASS_REQUIRE` to `force`, it behaves as it did prior to 8.4p1 (launches the SSH_ASKPASS program). I would also like to note that I am using OpenSSH via Git 2.29.2. I am not running Git via the command line, but instead shelling to it via a graphical application. I am calling `git clone`, which is in turn calling OpenSSH. what are you setting DISPLAY to? (In reply to Damien Miller from comment #3) > what are you setting DISPLAY to? Just an empty string (i.e. empty null terminated string when using CreateProcessW on Windows). Recent OpenSSH check that $DISPLAY is set to a non-empty string. if you're on Windows, then you should probably use SSH_ASKPASS_REQUIRE=force anyway because DISPLAY is nonsensical there but otherwise you can get your old setup back by setting DISPLAY to a non-empty string (anything will do). closing resolved bugs as of 8.6p1 release |