https://bugzilla.mindrot.org/show_bug.cgi?id=3320
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
I can't replicate this on openssh-8.6 or 8.7 (on Linux/OpenBSD) and the
common X11 askpass programs.
> It looks like all interactive input goes through read_passphrase() in
> readpass.c, whether or not it's a credential. Is this intentional?
Yes - read_passphrase(), despite its name, supports reading both secret
and public strings from the user. It's completely intentional, as it is
the central place that decides whether to invoke SSH_ASKPASS or to read
from the TTY.
If I had to guess what is going wrong in your case: your SSH_ASKPASS
program is probably returning something other than strictly "yes", "no"
or the key fingerprint and so you're repeatedly going around the loop
inside sshconnect.c:confirm()
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
Damien Miller <djm@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org
--- Comment #1 from Damien Miller <djm@mindrot.org> ---
I can't replicate this on openssh-8.6 or 8.7 (on Linux/OpenBSD) and the
common X11 askpass programs.
> It looks like all interactive input goes through read_passphrase() in
> readpass.c, whether or not it's a credential. Is this intentional?
Yes - read_passphrase(), despite its name, supports reading both secret
and public strings from the user. It's completely intentional, as it is
the central place that decides whether to invoke SSH_ASKPASS or to read
from the TTY.
If I had to guess what is going wrong in your case: your SSH_ASKPASS
program is probably returning something other than strictly "yes", "no"
or the key fingerprint and so you're repeatedly going around the loop
inside sshconnect.c:confirm()
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs