similar to: [Bug 3568] New: ctrl-c causes ssh connection to drop

Here is our configuration - we have a Windows 2003 domain I'll call 'corporate' and a Windows 2008 domain I'll call 'lab'. There is a one-way trust (users can log into 'lab' machines using 'corporate' creds). We have a linux box running samba that is a member of 'lab'. Users log into their Windows machines using a 'corporate' credential and

The current code for channel.c creates an array of Channel structs (initially set to NULL) which is then iterated through, in full, every time a channel needs to be dealt with. If only one channel is in use, which is relatively common, the code still loops through the entire array. This patch creates a linked list of pointers to these structs and the code steps through the linked list. Since

Thanks for testing - are you able to see if there's anything in the server logs? I've just committed some extra verbosity in the client's log messages that might clarify where it is exiting (patch attached). -d On Fri, 29 Mar 2019, Adam Eijdenberg wrote: > On Wed, Mar 27, 2019 at 10:04 PM Damien Miller <djm at mindrot.org> wrote: > > > > OpenSSH 8.0p1 is almost

Here is a simpler patch (based on Markus Friedl's suggestion posted to this list) to OpenSSH-3.0.2p1 to fix the hang-on-exit bug (Protocol 2 only). To date, no data loss has been reported with this patch: it does not break ssh or scp. This patch should make OpenSSH work on all operating systems exactly as it does under FreeBSD. This patch and others are maintained on the

Hi, Compiled openssh3.1p1 by adding '-DINET6' flag to compile line to enable it to be installed on our ipv6 systems. No other code change was done to openssh. Installed it on two ipv6 systems and two ipv4 systems. Whenerer the server is an ipv4 system, ssh client seems to establish connection but it terminates immediately after printing motd message. Here is the typical failure

https://bugzilla.mindrot.org/show_bug.cgi?id=3350 Bug ID: 3350 Summary: Network errors aren't printed logged Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at

Hello ! Like Edmund EVANS reported openssh-2.1.1p4 won't fork to background when using protocol 2. I managed to hack a little patch that might work ... What is the -N command line option supposed to do ? I gather it should work only with protocol2 and without any command to run on the server (and with some port forwardings ??) Anyway in the patch I put some code to check that -N is used

Hi, Ssh -f forks itself in the background. Very usefull if you would like to e.g. tunnel munin over ssh. Now it's tricky to terminate one process if you have multiple running. It seems that ssh currently (looked at 5.1p1) has no write-pid-to-file functionality So I implemented a patch which do so. Tested it a little and it seems to work. Hopefully it is of any use in my form or inspires the

OpenSSH 7.1p2 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. OpenSSH also includes transitional support for the legacy SSH 1.3 and 1.5 protocols that may be enabled at compile-time. Once again, we would like to thank the OpenSSH

Hi, I am facing an issue with openssh-4.5p1. I am not sure whether its an openssh issue or a tcp stack issue since I am using a simulated tcp/ip stack. While copying a file of around 1GB using sftp/scp I am getting a send:Message too long error. I did a bit of debugging and found that ssh code was sending packet of size greater than 131072 bytes from the application level to the socket and

https://bugzilla.mindrot.org/show_bug.cgi?id=1548 Summary: Double free in OpenSSH clientloop.c/xmalloc.c via cmdline port forwarding Product: Portable OpenSSH Version: 5.1p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

Handle SIGQUIT by guestfish, so that it can't be terminated. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- fish/fish.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/fish/fish.c b/fish/fish.c index efd6b0b..b782b7c 100644 --- a/fish/fish.c +++ b/fish/fish.c @@ -402,6 +402,7 @@ main (int argc, char *argv[]) sa.sa_handler = user_cancel;

Hello, During a .Call e.g while(TRUE){ value <-rhsqnextKVR(rdr) ## has .Call in this function if(is.null(value)) break; } if I press CTRL-C, R exits straight to the command line. Q: How can I prevent this? I should point out that my library uses JNI, so I'm not sure if that is causing it. I'm using R-2.8 on Linux (RHEL 5) Thank you in advance Regards Saptarshi

Hi All, I am not sure if this is the same thing as the hang on exit bug, so sorry if this is a duplication of previous stuff. Essetntially I am experiencing ssh hangs with about .5% - 1% of my connections. I am running 2.9p2, on Solaris 7. I actually have empirical data on the hangings, as I wrote a script to create these connections in an endless loop, setting an alarm so I could recover

https://bugzilla.mindrot.org/show_bug.cgi?id=3531 Bug ID: 3531 Summary: Ssh will not exit when it receives SIGTERM before calling poll in client_wait_until_can_do_something until some events happen. Product: Portable OpenSSH Version: 9.1p1 Hardware: Other OS: Linux Status:

https://bugzilla.mindrot.org/show_bug.cgi?id=3733 Bug ID: 3733 Summary: "forced command options do not match" after key error Product: Portable OpenSSH Version: 9.8p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee:

Hi, I have Asterisk running with the VoiceMail. Using the latest CVS. I have my extensions.conf setup so that if a SIP caller dials *99 the VoicemailMain() as follows: exten => *99,1,Wait(1) exten => *99,2,VoicemailMain() A couple days ago I installed the MySQL/Voicemail support described at http://www.voip-info.org/wiki-Asterisk+voicemail+database Now for some reason

As you are now probably aware, the portability team for openssh still has not fixed the hang-on-exit bug in the 2.9.9p2 release. Attached is a patch for 2.9.9p2 that fixes the hang-on-exit bug for Linux systems. It also adds a useful exit delay feature that has also not yet been incorporated into the main sources. For more information, see the SNFS (secure NFS) web page:

Hi all, I spent most of the last weekend testing and trying to diagnose some mostly incoming call issues. I'll start with the easy one in the hopes it might have a positive impact on the others. First- I have an account with IAXTel. I can place calls to other IAXTel subscribers and also through IAXTel to landline toll free numbers and all works great. iax2 show registry shows I am

When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4 to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little while (of inactivity?) I get the following message on the client terminal: Disconnecting: protocol error: rcvd type 98 Looking further, this message is actually caused by the SSH daemon. However, I'm at a loss to determine why sshd is doing this. I attach