similar to: [Bug 396] sshd orphans processes when no pty allocated

http://bugzilla.mindrot.org/show_bug.cgi?id=396 Summary: sshd orphans processes when no pty allocated Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

https://bugzilla.mindrot.org/show_bug.cgi?id=396 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.herbert+mindrot at gmail. | |com --- Comment #14

http://bugzilla.mindrot.org/show_bug.cgi?id=396 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=396 ------- Additional Comments From dtucker at zip.com.au 2003-05-04 11:14 ------- Does anyone object to this patch? And if not, is it something that should go to OpenBSD? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=396 ------- Additional Comments From markus at openbsd.org 2003-06-05 00:09 ------- sending signals could be dangerous, depending on the permissions of the sending process, e.g. a root-owned sshd sending to a setuid process. but i'm not sure. we had similar code there before. ------- You are receiving this mail because: ------- You are the

http://bugzilla.mindrot.org/show_bug.cgi?id=396 ------- Additional Comments From djm at mindrot.org 2005-02-14 11:55 ------- Is this not another manifestation of the infamous bug #52? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

https://bugzilla.mindrot.org/show_bug.cgi?id=396 --- Comment #23 from Ulrich Sibiller <uli42 at gmx.de> --- I have not tested it but the name of the two options does not seem that it is the exact fix for this problem as this happens when _killing_ the connection, see Descripton. While a timeout might kill the dangling processes it will probably do so after some _time_ not at the time the

https://bugzilla.mindrot.org/show_bug.cgi?id=396 Ulrich Sibiller <uli42 at gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #24 from Ulrich Sibiller <uli42 at

https://bugzilla.mindrot.org/show_bug.cgi?id=396 Tyler Riddle <triddle at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |triddle at gmail.com --- Comment #20 from Tyler Riddle <triddle at gmail.com> --- I just hit the condition of

https://bugzilla.mindrot.org/show_bug.cgi?id=396 Martin d'Anjou <point14 at magma.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |point14 at magma.ca --- Comment #13 from Martin d'Anjou <point14 at magma.ca> 2008-12-13

http://bugzilla.mindrot.org/show_bug.cgi?id=396 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hello everyone, I've look at the latest nightly snapshot but I could find this bug is fixed on the source code. Is there any progression to fix that issue. This bug is open for almost 10 years, come on guys :) >List: openssh-unix-dev >Subject: Re: killing remote commands >From: HAUTREUX Matthieu <matthieu.hautreux () cea ! fr> >Date: 2010-10-21

https://bugzilla.mindrot.org/show_bug.cgi?id=396 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED CC| |djm

https://bugzilla.mindrot.org/show_bug.cgi?id=396 Andrew McNabb <amcnabb at mcnabbs.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amcnabb at mcnabbs.org --- Comment #16 from Andrew McNabb <amcnabb at mcnabbs.org> 2012-02-10 05:21:40 EST

Hello Darren, The major problem we are running into is that the shell (both sh and ksh) does not kill its child processes when there is no pty. The SSH patch mentioned previously at http://bugzilla.mindrot.org/show_bug.cgi?id=396 is not sufficient to kill the forced command completely.It will only kill the shell script, but not any child processes the shell script runs. The shell assumes the

I have a situation where a number of potentially hostile clients ssh to a host I control, each ssh'ing in as the same user, and each forwarding a remote port back to them. So, the authorized_keys file looks like: no-agent-forwarding,command="/bin/true",no-pty,no-user-rc,no-X11-forwarding,permitopen="127.0.0.1:7" ssh-rsa AAAAB....vnRWxcgaK9xXoU= client1234 at example.com

Hi Darren, the clients config would need customer to change firewall settings to allow 1023 port. my server is behind the firewall. firewall settings say that my server 1023 is not accessable from outside. So If user tries -p 1023, it is rejected. hence user can only issue ssh customuser at ip . I am trying to instead connect to 1023 from my server, which doesnt go to firewall, hence from my

Thanks Darren, the intention to do this : allow users to access my own shell/CLI(including authentication) on port 22. their firewall settings doesnt allow anything other than port 22, so I would internally redirect to port 1023 when customuser is provided. I will try enabling logs, thanks. On Tue, Jan 31, 2017 at 5:10 AM, Darren Tucker <dtucker at zip.com.au> wrote: > On Tue, Jan 31,

http://bugzilla.mindrot.org/show_bug.cgi?id=560 Summary: Privsep child continues to run after monitor killed. Product: Portable OpenSSH Version: -current Platform: ix86 URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=164797 OS/Version: Linux Status: NEW Severity: normal Priority: P2

Hi. I'm one of the OpenSSH developers, and I've done some of the work on sshd's PAM interface recently. I've discovered some behaviour peculiar to LinuxPAM that I can't explain: changing the conversation function does not appear to work, even though the pam_set_item() call claims to succeed. The previous conversation function is still called. Background: the PAM API