public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Bernd Eckenfels <ecki-news2002-08@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 and full ipv6 - will it happen?
Date: Thu, 22 Aug 2002 20:19:37 +0100	[thread overview]
Message-ID: <20020822201937.G9153@flint.arm.linux.org.uk> (raw)
In-Reply-To: <E17hwfR-0005A5-00@sites.inka.de>; from ecki-news2002-08@lina.inka.de on Thu, Aug 22, 2002 at 08:26:49PM +0200

On Thu, Aug 22, 2002 at 08:26:49PM +0200, Bernd Eckenfels wrote:
> v6 isnt more secure than v4, and i suspect ipsec is more widely used in v4
> than in v6, and i doubt it will ever be used on default.

Remember also that our v6 firewall infrastructure isn't as advanced as
its v4 counterpart.  v6 connection tracking?  sorry, we don't have that.
IMHO v6 firewalling code is currently where the 2.2 kernels are.

(Disclaimer: I'm not going to get into a discussion about the advantages /
disadvantages of connection tracking wrt security.)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-08-22 19:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19  4:39 2.4 and full ipv6 - will it happen? Tomasz Torcz, BG
2002-08-19  4:37 ` David S. Miller
2002-08-19  5:16   ` Tomasz Torcz, BG
2002-08-19  5:12     ` David S. Miller
2002-08-19 23:34   ` Thunder from the hill
2002-08-19 23:23     ` David S. Miller
2002-08-19 23:49       ` Daniel Berlin
2002-08-19 23:54       ` Alan Cox
2002-08-20  0:32       ` Rik van Riel
2002-08-20 13:54         ` kuznet
2002-08-20  6:56       ` Thunder from the hill
2002-08-21 20:24       ` Kelsey Hudson
2002-08-21 21:31         ` Bernd Eckenfels
2002-08-21 21:44           ` Thunder from the hill
2002-08-21 22:03             ` Bernd Eckenfels
2002-08-21 23:13               ` Russell King
2002-08-22  0:05                 ` Bernd Eckenfels
2002-08-22  6:08               ` Thunder from the hill
2002-08-26 18:55               ` Kelsey Hudson
2002-08-26 19:44                 ` Bernd Eckenfels
2002-08-26 21:51                 ` Michael H. Warfield
2002-08-26 23:48                   ` Bernd Eckenfels
2002-08-27 16:07                     ` Michael H. Warfield
2002-08-28 19:14                       ` Bernd Eckenfels
2002-08-29  2:05                         ` Michael H. Warfield
2002-08-29 18:47                           ` Bernd Eckenfels
2002-08-21 22:08             ` Alan Cox
2002-08-22  6:12               ` Thunder from the hill
2002-08-22 12:27                 ` Rik van Riel
2002-08-22 18:22                 ` Alan Cox
2002-08-22 18:26                 ` Bernd Eckenfels
2002-08-22 19:19                   ` Russell King [this message]
2002-09-12 15:06   ` Petr Baudis
2002-09-13  1:47     ` David S. Miller
2002-08-19  7:27 ` Chris Wedgwood
2002-08-19 12:25 ` Alan Cox
2002-08-19 22:39   ` Kelsey Hudson
2002-08-20  6:17   ` Val Henson
  -- strict thread matches above, loose matches on Subject: below --
2002-08-19 23:56 Leif Sawyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020822201937.G9153@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=ecki-news2002-08@lina.inka.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox