public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Cusack <fcusack@fcusack.com>
To: linux-kernel@vger.kernel.org, paulus@samba.org
Subject: MPPE in kernel?
Date: Mon, 12 May 2003 04:59:29 -0700	[thread overview]
Message-ID: <20030512045929.C29781@google.com> (raw)

What are the chances of getting MPPE (PPP encryption) into the 2.4.21
and/or 2.5.x kernels?

For 2.4.21, sha1 and arcfour code needs to be added, so I don't have
too much hope :-) even though the code is trivial to integrate.

For 2.5.x, just the arcfour code is needed (since sha1 is already there).
I've written a public domain implementation, which I'd be willing to
relicense under GPL (although I don't see the point), but in any case
the algorithm is easy and could be written by anyone.

In addition to the crypto, the mppe compressor module is required.

I'm not so concerned about getting any of that included though; what
I really want is for the changes to ppp_generic.c to be included.
It's not so much fun to have to maintain patches.  The changes required
are generic, don't require crypto, and are generally uneventful.  Getting
the crypto bits and the mppe compressor itself included would just be
a bonus.

/fc

             reply	other threads:[~2003-05-12 11:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 11:59 Frank Cusack [this message]
2003-05-12 12:13 ` MPPE in kernel? Christoph Hellwig
2003-05-12 12:16 ` Alan Cox
2003-05-12 12:36 ` Paul Mackerras
2003-05-12 13:02   ` Frank Cusack
2003-05-12 13:07     ` Paul Mackerras
2003-05-12 22:13       ` Frank Cusack
2003-05-13  4:38         ` Paul Mackerras
2003-05-12 14:59 ` James Morris
2003-05-12 22:16   ` Frank Cusack
2003-05-12 15:04 ` Valdis.Kletnieks
2003-05-12 22:23   ` Frank Cusack

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=20030512045929.C29781@google.com \
    --to=fcusack@fcusack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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