https://bugzilla.mindrot.org/show_bug.cgi?id=2573
Darren Tucker <dtucker@dtucker.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |3302
--- Comment #9 from Christoph Anton Mitterer <calestyo@scientia.net> ---
Hey.
Anything new with respect to this?
Actually I think this bug can cause accidental problems, consider the
following:
- one has such a hanging ssh connection (not knowing it)
- one copy&pastes a command into that terminal like
rm -rf something
- one notices the session is dead, tries to kill it with "~.", which
doesn't work
- one kills the ssh proccess
but what happens now is, that all stuff that was entered before is then
on the shell's stdin (i.e. the shell from which ssh was invoked).
So instead of a remote rm -rf something, this is done locally... which
might be bad of course.
Cheers,
Chris
--- Comment #10 from Darren Tucker <dtucker@dtucker.net> ---
Damien has come up with a potential solution, I'm just running it
through the regress tests now.
BTW an slightly easier testcase: start an sshd in debug mode
(/path/to/sshd -ddd -p 2222), ssh into it with rekeying (ssh -o
rekeylimit="1G 15s" -vvv localhost), CTRL-Z the sshd then wait until
the client tries to rekey.
Referenced Bugs:
https://bugzilla.mindrot.org/show_bug.cgi?id=3302
[Bug 3302] Tracking bug for openssh-8.7
--
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
Darren Tucker <dtucker@dtucker.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |3302
--- Comment #9 from Christoph Anton Mitterer <calestyo@scientia.net> ---
Hey.
Anything new with respect to this?
Actually I think this bug can cause accidental problems, consider the
following:
- one has such a hanging ssh connection (not knowing it)
- one copy&pastes a command into that terminal like
rm -rf something
- one notices the session is dead, tries to kill it with "~.", which
doesn't work
- one kills the ssh proccess
but what happens now is, that all stuff that was entered before is then
on the shell's stdin (i.e. the shell from which ssh was invoked).
So instead of a remote rm -rf something, this is done locally... which
might be bad of course.
Cheers,
Chris
--- Comment #10 from Darren Tucker <dtucker@dtucker.net> ---
Damien has come up with a potential solution, I'm just running it
through the regress tests now.
BTW an slightly easier testcase: start an sshd in debug mode
(/path/to/sshd -ddd -p 2222), ssh into it with rekeying (ssh -o
rekeylimit="1G 15s" -vvv localhost), CTRL-Z the sshd then wait until
the client tries to rekey.
Referenced Bugs:
https://bugzilla.mindrot.org/show_bug.cgi?id=3302
[Bug 3302] Tracking bug for openssh-8.7
--
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