similar to: OpenSSH Hangs After Successful Authentication

Added the line as above: 'IPQoS lowdelay throughput', restarted the SSH service, tried SSH-ing and Git-ing... same error as before: 'packet_write_wait: Connection to X.X.X.X port 22: Broken pipe'. ________________________________ From: Zach Cheung <kuroro.zhang at gmail.com> Sent: 29 August 2018 07:17 To: ohadfjunkbox at outlook.com Cc: dtucker at dtucker.net;

On 2018-08-27, Stuart Henderson <stu at spacehopper.org> wrote: > On 2018-08-27, Zach Cheung <kuroro.zhang at gmail.com> wrote: >> After upgrading my VMware Fusion (10.1.3) Arch Guest to the latest with >> OpenSSH upgraded from 7.7p1 to 7.8p1, found that ssh from macOS Sierra >> (10.12.6) host to Arch guest via local NAT port forwarding failed, but via >>

On Mon, 27 Aug 2018, Stuart Henderson wrote: > On 2018-08-27, Zach Cheung <kuroro.zhang at gmail.com> wrote: > > After upgrading my VMware Fusion (10.1.3) Arch Guest to the latest with > > OpenSSH upgraded from 7.7p1 to 7.8p1, found that ssh from macOS Sierra > > (10.12.6) host to Arch guest via local NAT port forwarding failed, but via > > Arch LAN IP worked,

After upgrading my VMware Fusion (10.1.3) Arch Guest to the latest with OpenSSH upgraded from 7.7p1 to 7.8p1, found that ssh from macOS Sierra (10.12.6) host to Arch guest via local NAT port forwarding failed, but via Arch LAN IP worked, downgraded OpenSSH from 7.8p1 to 7.7p1 fixed the problem. Any idea about this bug? VMware Fusion NAT Port Forwarding setup: VMware Fusion ? NAT Port Forwarding

https://bugzilla.mindrot.org/show_bug.cgi?id=1965 Bug #: 1965 Summary: IPQoS option ignored for AF_INET since 5.9p1-1 Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All URL: http://bugs.debian.org/643312 OS/Version: Linux Status: NEW Severity: normal

The virtualization is VMware Workstation 12.x, NOT Fusion. Again, I'd like to point that downgrading to 7.7p2 "solved" the issue and that I'm using the same virtualization software for ages (which makes me disbelieve the issue lies with it). I've seen the comment about zero-length passwords... I'm not techie enough to understand the code there (or the technical

https://bugzilla.mindrot.org/show_bug.cgi?id=1963 Bug #: 1963 Summary: IPQoS not honoured Classification: Unclassified Product: Portable OpenSSH Version: 5.8p1 Platform: amd64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: unassigned-bugs at

On 08/10/2017 23:32, Michael Felt wrote: > On 04/10/2017 11:07, Michael Felt wrote: >> I do not often use X11 - but when I do I prefer to enable >> X11forwarding, and when finished - turn it off. This is preferable, >> imho, to having "clear" X11 processing when local - and otherwise >> impossible when working remote. >> >> Working with

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

http://bugzilla.mindrot.org/show_bug.cgi?id=731 Summary: sshd terminates a session after a successful login Product: Portable OpenSSH Version: -current Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

Hello list! So I recently reconfigured our office network to allow a permanent VPN connection to our data center. This consists of a Juniper SSG-520 connected via a tunnel to a Juniper Netscreen-25 over a 100M leased NTT VPN (yes I'm tunneling over the VPN as it's the only way to make it routable.) Here is where OpenSSH come in. When I try and ssh to a machine on the other end

Hi everyone, I have a configuration for a router that load-balances between two ISPs. What happens is that if a source-destination combination is looked up, one of the two gateways will be chosen, and further lookups will stay on that gateway until the chosen combination "stales" out. Web browsing works, ftp works, kazaa and other applications work. ssh on windows (using putty) works.

Hi I have added smartcard support to PuTTY and this worked fine until yesterday when we replaced one of our Slackware-9 machines by a Slackware-10 one. Slackware-9 contained OpenSSH 3.5p1 while Slackware-10 has OpenSSH 3.8.1p1. Now the same keys that worked before do not work anymore and OpenSSH fails with buffer_get_bignum2: negative numbers not supported I first supected that my

Very rarely, but it has repeated, we see openssh on the client side hanging. On the server side there is no indication of connection in the logs. These are always scripted remote commands that do not have user interaction when we find it. This seems to be happening only in vm environments but I could be wrong. It seems surprising to me that there would not be timeouts and retries on the protocol,

Hello, I am having a very aggrivating problem, and I will try and provide all of the necessary information. I have openssh-3.7.1p2 with openssl-0.9.6k installed on Solaris 8. Here is what I've been able to determine so far: 1. Local account authentication works fine (non-NIS+). 1a. NIS+ is running at security level 2 2. Telnet authentication works fine. 2a. When I use the SSH client,

I'm getting core dumps from sshd when logging in using password authentication (using a public key works just fine). The core dump occurs just after entering a password--whether that password is correct or not. It only happens on this one machine. I've tried recompiling the entire setup--zlib, openssl & openssh--and the crash still occurs. It doesn't look like the putty-failure

Hi All, I'm having an issue where SSH sessions fail if I enable the cryptodev engine for HMAC. I'd like to confirm if this is a supported configuration and if there are any known bugs. HMAC with the cryptodev engine works fine when using the openssl application directly, so I suspect that something in openssh may be the cause of the issue. I tried this initially with sshd from openssh

I don't know anything about cryptodev-linux, but I assume it's an openssl engine? If so it's possible sshd's multiprocess model and/or file descriptor handling is confusing it. It's not a configuration we test, so you're mostly on your own to debug it. It's entirely possible there's a bug there; if so, I'd expect it to be something like a fd being closed while

Hello, after upgrading my redhat 8.0 notebook to openssh3.7.1p2 linux port I now could not login/scp into it (as root or myself). /var/log/messages said the authentication was successful, then the connection closed immediately. I was using the default sshd_config that comes from the installation (via rpmbuild from the srpms file under the portable directory). (The client connection was initiated

Greetings, I've been doing a little testing with the stdio forwarding support added in recent snapshots and have encountered one possible issue. First, I should say that this feature generally seems to work. However, I haven't been able to get it to work when connecting to a server running SSH.COM's product. The config file I am using is fairly simple: Host sfe1 LogLevel debug3