Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-24 Thread Devon Sean McCullough
FreeBSD-SA-03:12.openssh Date: Sat, 23 Apr 2005 00:11:19 -0400 From: Lucas Holt [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] As I recall there is an option in the openssh config file in recent versions to disable DNS lookups. On Apr 20, 2005, at 9:35 AM, [EMAIL PROTECTED] wrote: In the future

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-21 Thread Devon
In the future, please do as I did and publish whatever solution you find, my answer was somewhat lame but worked for me and will help the next guy. To the SSH server /etc/hosts I added the client machine, now when it gets to debug1: got SSH2_MSG_SERVICE_ACCEPT it hangs for only 75 seconds.

sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread Devon Sean McCullough
On Wed, 17 Sep 2003 00:02:33 +0100 Steven Hartland asked this question but no answer was posted. The trouble is likely no client reverse DNS either because it is missing or slow. Adding the client to /etc/hosts on the server seems at first to do nothing but after a minute or so it stops hanging

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread c0ldbyte
On Tue, 19 Apr 2005, Devon Sean McCullough wrote: On Wed, 17 Sep 2003 00:02:33 +0100 Steven Hartland asked this question but no answer was posted. The trouble is likely no client reverse DNS either because it is missing or slow. Adding the client to /etc/hosts on the server seems at first to do

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread Devon
Date: Wed, 20 Apr 2005 08:33:36 -0400 (EDT) From: c0ldbyte [EMAIL PROTECTED] cc: [EMAIL PROTECTED], freebsd-hackers@freebsd.org, Steven Hartland [EMAIL PROTECTED] On Tue, 19 Apr 2005, Devon Sean McCullough wrote: On Wed, 17 Sep 2003 00:02:33 +0100 Steven Hartland asked

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread Ryan Sommers
c0ldbyte wrote: Dude, that was 2 years ago in 2003 the year now is 2005 and the current date is 'Wed Apr 20 12:32:31 UTC 2005' so umm, am I living in the future or are you dwelling on the past ???. Hey, dude, you aren't helping situations around here. This is one of many inflammatory remarks

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread Steven Hartland
Sorry I don't remember the solution we came up with. It was a long time ago. I think it was to do with DNS invalid / broken DNS or something like that but I couldn't say for sure. Regards Steve - Original Message - From: [EMAIL PROTECTED] This trouble hit me yesterday, 2005 Apr 19

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread Eric Anderson
Steven Hartland wrote: Sorry I don't remember the solution we came up with. It was a long time ago. I think it was to do with DNS invalid / broken DNS or something like that but I couldn't say for sure. Regards Steve - Original Message - From: [EMAIL PROTECTED] This trouble hit me

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread c0ldbyte
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 20 Apr 2005, Ryan Sommers wrote: c0ldbyte wrote: Dude, that was 2 years ago in 2003 the year now is 2005 and the current date is 'Wed Apr 20 12:32:31 UTC 2005' so umm, am I living in the future or are you dwelling on the past ???. Hey, dude,

Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh

2005-04-20 Thread Steven Hartland
Usually do post answers when I find them but it was one of those must get it fixed 24 hour jobs as I recall so just slipped way as I fell asleep :) Could be its forcing a name resolution and not using hosts at all? Steve - Original Message - From: [EMAIL PROTECTED] In the future,

sshd dieing? after applying FreeBSD-SA-03:12.openssh

2003-09-16 Thread Steven Hartland
OpenSSH_3.6.1p1 FreeBSD-20030916, SSH protocols 1.5/2.0, OpenSSL 0x0090701f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: Connecting to 10.10.1.23 [10.10.1.23] port 22. debug1: Connection established.