public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Schwartz <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: RFC2385 (MD5 signature in TCP packets) support
Date: Fri, 15 Mar 2002 14:36:48 -0800	[thread overview]
Message-ID: <20020315223649.AAA27488@shell.webmaster.com@whenever> (raw)


	Has anyone made a patch or done any work on RFC2385 support for Linux? I'm 
willing to code the subset of it that I need if there's a general consensus 
that my approach is reasonable.

	I don't plan to add a table of IPs/ports and have the kernel automatically 
invoke authentication for those IPs/ports. This is mostly because I don't 
need this functionality, but if it's felt that this is the only way to go, 
then I'll reconsider my plans.

	I plan to add a socket option. You use it after you bind for inbound TCP 
connections and before you connect for outbound. You simply set the key to be 
used on the connection in the sockopt call. There would also be an option to 
allow/disallow unkeyed connections (should the key be optional or mandatory). 
Also, a get socket option would allow you to determine whether the key was 
being used or not.

	One limitation of this approach is that for inbound connections, you can't 
have a different password for multiple hosts that might connect to you.

	My interest for this is mostly for Zebra to be able to make secure BGP 
connections, so I would also contribute a patch for Zebra to support this 
feature on Linux.

	Am I wasting my time? Is there interest?

-- 
David Schwartz
<davids@webmaster.com>



             reply	other threads:[~2002-03-15 22:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 22:36 David Schwartz [this message]
2002-03-15 22:53 ` RFC2385 (MD5 signature in TCP packets) support 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               ` RFC2385 (MD5 signature in TCP packets) support David Schwartz
2002-03-15 23:54                 ` 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=20020315223649.AAA27488@shell.webmaster.com@whenever \
    --to=davids@webmaster.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