From: Gervasio Bernal <gervasiobernal@speedy.com.ar>
To: netfilter-devel@lists.netfilter.org
Subject: Re: New extension: CRYPT target
Date: Tue, 23 May 2006 14:19:01 -0300 [thread overview]
Message-ID: <44734405.3000300@speedy.com.ar> (raw)
In-Reply-To: <22306.1148389730@sandelman.ottawa.on.ca>
Michael Richardson wrote:
>
>
>>>>>>>"Gervasio" == Gervasio Bernal <gervasiobernal@speedy.com.ar> writes:
>
> Gervasio> The idea behind CRYPT extension is not to replace IPSEC
> Gervasio> absolutely, but to be a simple alternative of use for
> Gervasio> encryption/decryption and packet authentication using
> Gervasio> Iptables. It could be useful for somebody.
>
> Tell me the threat model.
>
> Under what circumstances is it better than:
> a) IPsec with OE (with is dirty simple to configure)
> b) TLS/SSL LD_PRELOAD wrapper
> c) using SCP instead of FTP (or rsync over SSH)
> d) OpenVPN or SSH port forwarding
> e) HIP
Perhaps in none of those circumstances.
CRYPT extension is just an alternative, as well OpenOffice Writer is an
alternative of Microsoft Word. It is good to have several different
alternatives.
>
> Gervasio> We have also developed a module in Python that use the
> Gervasio> CRYPT extension, configuration files, has automatic key
> Gervasio> management and user authentication using certificates. But
> Gervasio> we need that someone else can test first the extension
> Gervasio> alone, and comments its experience to us.
>
> Why in the world would you build such a complicated system?
It is much more easy of which you imagine. You only have to run a Python
application and voila!!
> You just told us that you wanted something simpler than IPsec.
>
> It seems like vanity crypto to me.
>
next prev parent reply other threads:[~2006-05-23 17:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 15:59 New extension: CRYPT target Gervasio Bernal
2006-05-21 17:01 ` Carl-Daniel Hailfinger
2006-05-21 21:15 ` Gervasio Bernal
2006-05-21 22:17 ` Carl-Daniel Hailfinger
2006-05-22 23:49 ` Gervasio Bernal
2006-05-23 16:27 ` Gervasio Bernal
2006-05-23 16:46 ` Carl-Daniel Hailfinger
2006-05-23 17:07 ` Patrick McHardy
2006-05-23 17:14 ` Carl-Daniel Hailfinger
2006-05-23 23:13 ` Gervasio Bernal
2006-05-24 5:03 ` Patrick Schaaf
2006-05-23 18:26 ` Michael Richardson
2006-05-21 22:57 ` Michael Richardson
2006-05-22 23:36 ` Gervasio Bernal
2006-05-23 13:08 ` Michael Richardson
2006-05-23 17:19 ` Gervasio Bernal [this message]
2006-05-21 17:51 ` Martijn Lievaart
2006-05-21 20:34 ` Cedric Blancher
2006-05-21 21:01 ` Gervasio Bernal
2006-05-21 22:54 ` Michael Richardson
2006-05-21 20:27 ` Gervasio Bernal
2006-05-25 16:11 ` Lennart Poettering
2006-05-26 18:12 ` Gervasio Bernal
2006-05-26 18:25 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2006-05-23 23:33 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=44734405.3000300@speedy.com.ar \
--to=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.