From owner-freebsd-security Tue Feb 20 17: 1:12 2001 Delivered-To: freebsd-security@freebsd.org Received: from h-209-91-79-2.gen.cadvision.com (h24-68-202-204.cg.shawcable.net [24.68.202.204]) by hub.freebsd.org (Postfix) with ESMTP id 0227237B401 for ; Tue, 20 Feb 2001 17:01:09 -0800 (PST) (envelope-from gtf@cirp.org) Received: from cirp.org (localhost [127.0.0.1]) by h-209-91-79-2.gen.cadvision.com (8.9.3/8.9.3) with ESMTP id SAA38561 for ; Tue, 20 Feb 2001 18:01:01 -0700 (MST) (envelope-from gtf@cirp.org) Message-Id: <200102210101.SAA38561@h-209-91-79-2.gen.cadvision.com> Date: Tue, 20 Feb 2001 18:01:00 -0700 (MST) From: "Geoffrey T. Falk" Subject: IPv6 risk with ssh? To: security@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From time to time I've noticed sshd on "tcp46" listening right now on one of my servers (4.1.1-RELEASE). I don't see it always. # netstat -an [...] tcp4 0 0 *.22 *.* LISTEN tcp46 0 0 *.22 *.* LISTEN What is tcp46, a hybrid IP4/IP6 protocol? Should I be concerned? Nobody else has (legitimate) access to this box. I'd prefer to disable/block all IPv6 for now if possible. How can I be assured that this is the case? I am currently running ipfw with a default deny rule. I don't have a way to probe the box using IPv6 currently. Thanks Geoffrey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message