All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rennie deGraaf <degraaf@cpsc.ucalgary.ca>
To: Gervasio Bernal <gervasiobernal@speedy.com.ar>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: New target
Date: Mon, 13 Feb 2006 17:48:59 -0700	[thread overview]
Message-ID: <43F128FB.6040009@cpsc.ucalgary.ca> (raw)
In-Reply-To: <43F0CE59.5040201@speedy.com.ar>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gervasio Bernal wrote:
> Rennie deGraaf wrote:
> 
>>Gervasio Bernal wrote:
>>
>>
>>>>Hi all!!!
>>>>
>>>>I have developed a new target for iptables that encrypts a
>>>>communication. I would like to send it so that you can see it and prove
>>>>it. And the possibility that in a future adding it to iptables.
>>>>Which are the steps to follow?
>>>>Thanks a lot!
>>
>>
>>Our of curiosity, what advantages does your method have over IPSec?
>>
>>Rennie
> 
> 
> The great advantage is the ease of use. You only need to put 2 iptables
> rules in each endpoint of communication. One rule for encryption and the
> other for decryption. IPSec is a little more complicated to configure.

Well, I'd be interested in taking a look at your design.  How about
posting your design and source somewhere so that we can take a look at it?

Rennie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD8Sj7IvU5mZP08HERApcYAJ4pOmVyYQJRdI7fuj2PSgjUjF4C2wCeNwie
kOW7cV2dIM3st6SQnsM09G8=
=6K7k
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2006-02-14  0:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 16:16 New target Gervasio Bernal
2006-02-13 16:36 ` Rennie deGraaf
     [not found]   ` <43F0CE59.5040201@speedy.com.ar>
2006-02-14  0:48     ` Rennie deGraaf [this message]
2006-02-14  0:52       ` Allen Francom
2006-02-14 22:37         ` Gervasio Bernal
2006-02-17  3:28         ` Michael Richardson
2006-02-14 22:36       ` Gervasio Bernal

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=43F128FB.6040009@cpsc.ucalgary.ca \
    --to=degraaf@cpsc.ucalgary.ca \
    --cc=gervasiobernal@speedy.com.ar \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.