https://bugzilla.mindrot.org/show_bug.cgi?id=3362
--- Comment #7 from j...@honorablemenschen.com ---
Unfortunately, this doesn't really fix the issue. Because it requires
you to a) know which channels your users are using, and more
importantly b) which channels your users are NOT using, and adjus
https://bugzilla.mindrot.org/show_bug.cgi?id=3362
Damien Miller changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.mindrot.org/show_bug.cgi?id=3362
j...@honorablemenschen.com changed:
What|Removed |Added
CC||j...@honorablemenschen.com
--
https://bugzilla.mindrot.org/show_bug.cgi?id=3362
--- Comment #4 from Damien Miller ---
If someone's going to go to the trouble of ptracing the bash process
then I'm pretty sure they could run a background process that prints a
character every $TMOUT-1 second
--
You are receiving this mail beca
https://bugzilla.mindrot.org/show_bug.cgi?id=3362
--- Comment #3 from ggasp...@redhat.com ---
I'm aware of this option, the problem is that it can be easily bypassed
and does not work for every shell.
https://stackoverflow.com/questions/17397069/unset-readonly-variable-in-bash/54705440#54705440
https://bugzilla.mindrot.org/show_bug.cgi?id=3362
Damien Miller changed:
What|Removed |Added
CC||d...@mindrot.org
--- Comment #2 from Dami
https://bugzilla.mindrot.org/show_bug.cgi?id=3362
--- Comment #1 from ggasp...@redhat.com ---
Related to: https://bugzilla.mindrot.org/show_bug.cgi?id=1338
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
openssh-bu
