From: James Cameron <james.cameron@hp.com>
To: linux-ppp@vger.kernel.org
Subject: RFC: PPP MPPE merge into kernel 2.6
Date: Fri, 30 Jan 2004 04:00:26 +0000 [thread overview]
Message-ID: <20040130040026.GI2306@hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2334 bytes --]
I'd like to open a discussion on the merge of the PPP MPPE support with
kernel 2.6. What can be done to achieve it? What is hindering it?
What can we do to remove the roadblocks?
MPPE is Microsoft's encryption scheme for PPP links.
The Linux MPPE support consists of five new source files, and patches to
ppp.c, ppp_generic.c and ppp-comp.h, and can be found in the CVS
repository for the PPP project in linux/mppe. The patches are relative
to 2.2 and 2.4. See http://samba.org/ftp/unpacked/ppp/linux/mppe/
The author is Frank Cusack <frank@google.com>, and the code is covered
by the "BSD without advertisement clause" license. Frank released this
around March 2002. See http://samba.org/ftp/unpacked/ppp/README.MPPE
MPPE support is used by PPTP. People who wish to use PPTP on their
system often have to modify their kernel to add MPPE support. PPTP is
not a particularly good tunnelling protocol, but many people are
required to use it as a condition of employment. In particular, MPPE
is not applied to non-data packets in the PPP stream, apparently by
design.
Many distributions do not ship MPPE support (e.g. Red Hat). Some
distributions have shipped an older version of MPPE support covered by
the OpenSSL license, which is incompatible with the kernel license (e.g.
SuSE, Mandrake). Some provide a patch (e.g. Debian).
The PPTP projects have adapted to the lack of MPPE support in the
upstream kernel by providing custom kernels, version specific patches,
module build scripts, and even binary modules.
Since the release of 2.6.0, two or three people have provided me with
patches relative to 2.6.
The OpenSSL licensed MPPE support was a separate implementation, and was
provided as a patch to 2.4.1. This was adopted by SuSE and Mandrake for
their kernels, but is incompatible with the MPPE support in the newly
released PPP 2.4.2.
It would be good to unify this situation and remove some of the pain.
Some effort has also been put into MPPC support, but as MPPC is covered
by a patent I'm not proposing that.
I'm the PPTP client project leader.
--
James Cameron http://quozl.netrek.org/
HP Open Source, Volunteer http://opensource.hp.com/
PPTP Client Project, Release Engineer http://pptpclient.sourceforge.net/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-01-30 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 4:00 James Cameron [this message]
2004-01-30 10:32 ` RFC: PPP MPPE merge into kernel 2.6 Chris Wilson
2004-02-02 10:43 ` Pasi Kärkkäinen
2004-02-02 22:16 ` James Cameron
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=20040130040026.GI2306@hp.com \
--to=james.cameron@hp.com \
--cc=linux-ppp@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;
as well as URLs for NNTP newsgroup(s).