similar to: Killing the OpenSSH server doesn't cause the Windows OpenSSH client to die

It depends how you "kill" the SSH server. If you kill it by sending it a SIGKILL signal, it will NOT notify the client, so the client will stay running until the client discovers the connection is broken. What happens if you send the SSH server a SIGHUP signal? This should cause an orderly shutdown on the server, which should notify the client, which should cause the client to do

The fact that '-o ServerAliveInterval=50' makes no difference suggests that there is a bug in the OpenSSH client. It either fails to sent heartbeats, or it gets stuck in some Windows system call and this makes it to fail to send heartbeats. Yuri

I don't believe you've said: are the disconnects happening during periods of idleness on the connection, or periods of activity? If idleness, some device or script could be actively doing a disconnect-on-idle. On Mon, 26 Feb 2018, Kip Warner wrote: > Hey list, > > I've read the man page for both the client and server daemon, so either > I missed something or this

Hi Rob, On 4/7/23 10:08, Bob Rasmussen wrote: > It depends how you "kill" the SSH server. > > If you kill it by sending it a SIGKILL signal, it will NOT notify the > client, so the client will stay running until the client discovers the > connection is broken. I run 'kill <pid>' which sends SIGTERM. This should shout it down gracefully. But even with

Try setting Host * ? ServerAliveInterval 240 in .ssh/config on the client (wherever that is in Windows).? Or pass "-o ServerAliveInterval=240" on the ssh client command line. I've seen this where connections pass through some low grade external firewall, which drops state after a certain amount of inactivity without sending back RST (and apparently is immune to TCP keepalives

A user at a Windows PC uses our SSH client software (Anzio) to access a Linux sshd. User would like the banner from the server to display BEFORE entering a login name. According to the SSH spec, this should be allowed. But the OpenSSH source seems to have specifically prevented this. Is there a good reason for this? Regards, ....Bob Rasmussen, President, Rasmussen Software, Inc.

On Fri, 7 Apr 2023, Yuri wrote: > The fact that '-o ServerAliveInterval=50' makes no difference suggests that > there is a bug in the OpenSSH client. > It either fails to sent heartbeats, or it gets stuck in some Windows system > call and this makes it to fail to send heartbeats. without debug logs from both the client and server in this situation, it's not really

I setup a ssh chroot jail following this[1] guide. It works for my user to login, use ls and use scp which is all I really want. I do have a problem I cannot solve: when connected and navigating the filesystem, the backspace key actually moves the cursor forward and does not delete what I type. I may have found a hint from some googling that readline will read in /etc/inputrc on login but if

The terminal programs (xterm, gnome-terminal, etc.) in Fedora have all supported 256 colors for quite a while, so there's a proposal for Fedora to switch them to using "xterm-256color" for $TERM. One drawback would be when you SSH to another host that doesn't have an up-to-date terminal database and doesn't recognize "xterm-256color" (but does know

On 4/7/2023 1:13 PM, Yuri wrote: > On 4/7/23 10:08, Bob Rasmussen wrote: >> It depends how you "kill" the SSH server. >> >> If you kill it by sending it a SIGKILL signal, it will NOT notify the >> client, so the client will stay running until the client discovers >> the connection is broken. > > > I run 'kill <pid>' which sends

Debian GNU/Linux 8.0 (jessie) OpenSSL 1.0.1k gcc (Debian 4.9.2-10) 4.9.2 "make tests" fails here: /usr/src/INET/openssh/ssh-keygen -lf /usr/src/INET/openssh/regress//t12.out.pub | grep test-comment-1234 >/dev/null run test connect.sh ... ssh connect with protocol 1 failed ssh connect with protocol 2 failed failed simple connect Makefile:192: recipe for target 't-exec' failed

On 4/7/23 21:46, Damien Miller wrote: > without debug logs from both the client and server in this situation, it's > not really possible to say what is going on. What are the options that I should use to generate logs? Yuri

Hi, Is there a way to tell why I'm getting frequent "Connection reset by peer" all of a sudden? I'm using a FreeBSD machine, plugged via eithernet to a Linksys router running DD-WRT, to another Linksys 50 feet away running DD-WRT, both of them WDS'd together, plugged via ethernet to another FreeBSD machine. With debug cranked, I see : debug1: channel 0: free:

Just starting my search for a SIP/MGCP/H323 channel bank. I need analog ports in a building that only have network connections back to my * server. I could install another * server and use a normal CB with a PRI but I would like to investigate any good CB's with network trunk abilities Thanks Dave Packham

What is the canonical link to Reference of "ServerAliveInterval"? Background: I want to write an answer at serverfault (Q-A Site). I want to avoid copy+pasting. I would like to lead the new comer to the canonical reference. Regards, Thomas G?ttler -- Thomas Guettler http://www.thomas-guettler.de/

Very bizarre behavior has cropped up in a few spots. # the action for viewing a blog post def posts @post = BlogPost.find_by_slug(params[:id], :include => :commentary) # a breakpoint here shows @post and @post.commentary with appropriate data redirect_to :action => ''archive'' unless @post end # posts.rhtml <%= @post.inspect %> => nil <%= render :partial

Hi, In the last several years, I noticed an annoying problem with ssh: Long-running ssh connections are automatically disconnected after just a few minutes of inactivity. This problem effects both interactive sessions (using ssh without screen(1) became almost impossible...) as well as ssh port forwarding and the likes. I never noticed this problem until about 6 years ago, but since then have

We've encountered a problem with getting a newly installed Samba based machine to join the domain. Here's the command line and error response: [root@chain samba]# smbpasswd -j COLUMBIA -r cmc-bkup -U murphyn Password: error creating domain user: NT_STATUS_INVALID_DOMAIN_ROLE Unable to join domain COLUMBIA. [root@chain samba]# Installation is a RedHat 7.2 (from KRUD) box

Hello, Many of our NT domain groups have names that contain embedded spaces, like "Domain Admins". When I attempt to use winbind and assign rights via those groups the granting fails. Group names without embedded spaces, like "Domain_Admins" work fine. In smb.conf I've tested specifying the name as: "DOMAIN+Domain Admin" DOMAIN+Domain\ Admin and

Hi list! We tested mod_antiloris 0.4 and found it quite efficient, but before putting it in production, we would like to hear some feedback from freebsd users. We are using Apache 2.2.x on Freebsd 6.2 and 7.2. Is anyone using it? Do you have any other way to patch against Slowloris other than putting a proxy in front or using the HTTP accept filter? Thanks for your feedback, Martin