[Bug 3562] New: make SSH_ASKPASS and SSH_ASKPASS_REQUIRE available as config options
https://bugzilla.mindrot.org/show_bug.cgi?id=3562 Bug ID: 3562 Summary: make SSH_ASKPASS and SSH_ASKPASS_REQUIRE available as config options Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-b...@mindrot.org Reporter: tar.ancalime.nume...@gmail.com Dear developers. Would it be possible to make SSH_ASKPASS and SSH_ASKPASS_REQUIRE available as options for ssh_config? That would not only allow to specify different tools depending on the matched host but also avoid having to export them in e.g. .profile and clutter up the environment for all processes run from there. Regards! -- You are receiving this mail because: You are watching the assignee of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3439] identify password prompts
https://bugzilla.mindrot.org/show_bug.cgi?id=3439 --- Comment #4 from tar.ancalime.nume...@gmail.com --- Hey Darren. Just one question on this: In both cases, the prompt with password and the prefix with keyboard-interactive, are these generated by the ssh client? Cause if e.g. the server could control the full prompt, a hostile server could try tricking people into entering passphrases/TOTPs for another server. Thanks :-) -- 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
[Bug 3438] env var that is SetEnv'ed multiple times in the same SetEnv directive, is sent/printed several times
https://bugzilla.mindrot.org/show_bug.cgi?id=3438 --- Comment #3 from Christoph Anton Mitterer --- Shall I provide a patch that adds a line like: "If the same variable is give multiple times, only it's first occurrence is considered." to SetEnv / SendEnv? However, for SendEnv it would be interesting if this is actually the case there as well, and especially if there's a "clearing" entry like in: SendEnv FOO BAR FOO BAZ -FOO -- You are receiving this mail because: You are watching the assignee of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3449] LocalForward doesn't support ~/path syntax for UNIX sockets
https://bugzilla.mindrot.org/show_bug.cgi?id=3449 --- Comment #3 from Christoph Anton Mitterer --- Thinking of it again: A ~ in the remote path would IMO *only* make sense to be expanded in the remote context (or not at all, if that's not possible). Cause the remote path if course to be taken with respect to the remote file hierarchy. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. ___ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3456] provide a way to have forwardings killed, when the remote command/shell finishes
https://bugzilla.mindrot.org/show_bug.cgi?id=3456 --- Comment #6 from Christoph Anton Mitterer --- Thanks Daimen... but still not particularly "user-friendly" in the sense that one still has to write a special command (2x ssh with special options) and cannot simply "ssh host" as usual. Wouldn't it be possible to get a config option that simply decides what should happen if there are still forwardings while the command has finished, i.e. either keep them open or close them and thus exit? -- 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
