From: David Schwartz <davids@webmaster.com>
To: <alan@lxorguk.ukuu.org.uk>, "David S. Miller" <davem@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: RFC2385 (MD5 signature in TCP packets) support
Date: Fri, 15 Mar 2002 15:53:51 -0800 [thread overview]
Message-ID: <20020315235352.AAA221@shell.webmaster.com@whenever> (raw)
In-Reply-To: <E16m1bl-000554-00@the-village.bc.nu>
>I'm not saying the RFC is a good idea (tho its a needed patch to use Linux
>for backbone routing sanely with most vendors BGP kit). Your argument about
>the RST frame is however pure horseshit
>
>Alan
I don't think it's a good idea either, and I'm sorry this turned into an
argument over the merits of RFC2385. I don't like it, and that's one of the
reasons I didn't suggest a thorough implementation. I just want enough to
solve the particular problem that I have, which is that Zebra on Linux can't
interoperate with Cisco BGP implementations using MD5 authentication.
There is some merit to the argument that one shouldn't crap up a network
stack just because someone else did. The question is, is interoperability
worth this small piece of crap. I personally think it is, but I'm prejudiced
since I happen to need it.
I'm trying to decide if I need it badly enough to make it worth the effort
it would take to implement it. One factor that would go into that decision is
whether the patch would have a chance at being accepted into the kernel or
whether at least kernel hooks to allow it to be implemented as a module might
be accepted.
DS
next prev parent reply other threads:[~2002-03-15 23:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 22:36 RFC2385 (MD5 signature in TCP packets) support 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:40 ` Alan Cox
2002-03-15 23:37 ` David S. Miller
2002-03-15 23:59 ` Alan Cox
2002-03-15 23:45 ` David S. Miller
2002-03-16 0:01 ` David Schwartz
2002-03-16 0:12 ` Alan Cox
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-15 23:53 ` David Schwartz [this message]
2002-03-15 23:54 ` RFC2385 (MD5 signature in TCP packets) support David S. Miller
2002-03-16 0:14 ` Alan Cox
2002-03-17 10:00 ` bert hubert
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=20020315235352.AAA221@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--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