Date: Sun, 21 Aug 2005 12:11:39 +0200 From: Remko Lodder <remko@FreeBSD.org> To: Pat Maddox <pergesu@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Security warning with sshd Message-ID: <4308535B.2080001@FreeBSD.org> In-Reply-To: <810a540e05082103073f0622f7@mail.gmail.com> References: <810a540e05082101182e4e75fa@mail.gmail.com> <43084AE9.7020305@FreeBSD.org> <810a540e05082103073f0622f7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Pat Maddox wrote:
> On 8/21/05, Remko Lodder <remko@freebsd.org> wrote:
>
>>Pat Maddox wrote:
>>
>
> I don't know what exactly was happening, but after looking at that
> link my guess is that it occurred when I enabled the firewall. If I'm
> logged in and enable it, my ssh connection is dropped...except I don't
> get disconnected, the ssh connection is simply unresponsive. Which
> makes sense since the firewall just went up. But maybe that's part of
> the problem?
Well that can easily be, people are speaking about "statefull" packets
here. Do you use statefull filtering on your firewall? Are you able
to "see" the dropped packets (dropped by your firewall)? If so you
might want to enable statefull filtering for your ssh sessions..
Hope this helps,
cheers
--
Kind regards,
Remko Lodder ** remko@elvandar.org
FreeBSD ** remko@FreeBSD.org
Reporter DSINET ** remko@DSINet.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4308535B.2080001>