From: bert hubert <ahu@ds9a.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: RFC2385 (MD5 signature in TCP packets) support
Date: Sun, 17 Mar 2002 11:00:08 +0100 [thread overview]
Message-ID: <20020317110008.A21369@outpost.ds9a.nl> (raw)
In-Reply-To: <20020315223649.AAA27488@shell.webmaster.com@whenever> <20020315.145306.15914579.davem@redhat.com>
In-Reply-To: <20020315.145306.15914579.davem@redhat.com>; from davem@redhat.com on Fri, Mar 15, 2002 at 10:57:11PM +0000
On Fri, Mar 15, 2002 at 10:57:11PM +0000, David S. Miller wrote:
>
> There is no reason to not be doing this MD5 garbage in
> userspace. Whoever thought to do this in the protocol
> itself was smoking something.
I did a lot of this using an iptables module. Iptables lends itself very
well to these kind of things. Toy code at http://ds9a.nl/sps/
> Maybe I'm missing something, but I see no reason this MD5
> stuff belongs in the protocol and not in the APP.
Some of the idea is cool. You can give a host a 'key' and tell your packet
filter to have it pass packets signed with that key. This way you can grant
or disable access on a very low level without depending on IP addresses,
which can be spoofed.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2002-03-17 10:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 22:36 David Schwartz
2002-03-15 22:53 ` David S. Miller
2002-03-15 23:11 ` David Schwartz
2002-03-15 23:14 ` David S. Miller
2002-03-15 23:15 ` Alan Cox
2002-03-15 23:13 ` David Schwartz
2002-03-15 23:16 ` David S. Miller
2002-03-15 23:37 ` David S. Miller
2002-03-15 23:45 ` David S. Miller
2002-03-15 23:57 ` David S. Miller
2002-03-16 0:06 ` David Schwartz
2002-03-16 1:43 ` Alan Cox
2002-03-18 4:09 ` David S. Miller
2002-03-18 5:06 ` Mike Fedyk
2002-03-18 6:19 ` David S. Miller
2002-03-16 4:19 ` debugging eth driver Petko Manolov
2002-03-16 17:27 ` Alan Cox
2002-03-16 18:52 ` Petko Manolov
2002-03-16 20:56 ` Alan Cox
2002-03-17 1:36 ` Keith Owens
2002-03-17 3:37 ` Tomasz Kłoczko
2002-03-22 7:40 ` Cameron Simpson
2002-03-16 0:01 ` RFC2385 (MD5 signature in TCP packets) support David Schwartz
2002-03-16 0:12 ` Alan Cox
2002-03-15 23:59 ` Alan Cox
2002-03-15 23:53 ` David Schwartz
2002-03-15 23:54 ` David S. Miller
2002-03-16 0:14 ` Alan Cox
2002-03-15 23:40 ` Alan Cox
2002-03-17 10:00 ` bert hubert [this message]
2002-03-22 5:55 ` 2.5.7, IDE, 'handler not null', 'kernel timer added twice' David Schwartz
2002-03-22 6:10 ` Davide Libenzi
2002-03-22 10:59 ` Martin Dalecki
2002-03-22 20:13 ` Davide Libenzi
2002-03-23 13:12 ` Martin Dalecki
2002-03-22 6:31 ` Andre Hedrick
2002-03-15 23:19 ` RFC2385 (MD5 signature in TCP packets) support Alan Cox
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=20020317110008.A21369@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--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
all inboxes | Powered by JetHome®