public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew McGregor <andrew@indranet.co.nz>
To: hps@intermeta.de, linux-kernel@vger.kernel.org
Subject: Re: RFC: p&p ipsec without authentication
Date: Tue, 17 Dec 2002 01:06:58 +1300	[thread overview]
Message-ID: <8360000.1040040418@localhost.localdomain> (raw)
In-Reply-To: <atk5sr$a06$1@forge.intermeta.de>

NAT traversal can be done, in some (limited) cases even without the 
cooperation of the NAT (although someone on the inside must cooperate). 
Firewalls do be a problem.  I think the best thing here is if you use this 
kind of thing outside the firewall; I always build networks, even LANs, 
with the crown jewels behind a firewall from the workstations, especially 
if they run Windows.  Authenticated IPSEC is a nice way to find out if we 
can to some extent trust them, although it costs cycles.

As for compatibility, there are three ways to do it presently in the IETF 
process (HIP, IKEv2 and FreeSWAN opportunistic mode), and two of them have 
running code on multiple platforms.

Andrew

--On Monday, December 16, 2002 09:20:27 +0000 "Henning P. Schmiedehausen" 
<hps@intermeta.de> wrote:

> Rik van Riel <riel@conectiva.com.br> writes:
>
>> Hi,
>
>> I've got a crazy idea.  I know it's not secure, but I think it'll
>> add some security against certain attacks, while being non-effective
>> against some others.
>
> While the idea itself is nice, it would allow many attackers on your
> host to "dive" under IDS systems or avoid stateful firewalls which do
> protocol verification. And IDS system is "a three letter acronym
> listening on your traffic". And you want to avoid that. =:-)
>
> It won't traverse many firewalls either (because they won't let IPSEC
> pass) and you might get in trouble with NAT and protocols that need
> NAT fixup.
>
> And you basically divide the Internet into "Linux <-> Linux" and "the
> rest". :-)
>
> 	Regards
> 		Henning


      reply	other threads:[~2002-12-16 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 20:34 RFC: p&p ipsec without authentication Rik van Riel
2002-12-15 21:59 ` Andrew McGregor
2002-12-16  9:20 ` Henning P. Schmiedehausen
2002-12-16 12:06   ` Andrew McGregor [this message]

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=8360000.1040040418@localhost.localdomain \
    --to=andrew@indranet.co.nz \
    --cc=hps@intermeta.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