mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Frank Cusack <fcusack@fcusack.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MPPE in kernel?
Date: Mon, 12 May 2003 22:36:29 +1000	[thread overview]
Message-ID: <16063.38221.73659.403481@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20030512045929.C29781@google.com>

Frank Cusack writes:

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

First, are there any patent issues that you are aware of?

> 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.

The fundamental problem is that MPPE is misusing CCP (compression
control protocol) for something for which it was never intended.  The
specific place where this is a problem is that the compression code in
ppp_generic doesn't guarantee that it will never send a packet out
uncompressed, but MPPE requires that.  How do you get around that
problem?

Regards,
Paul.

  parent reply	other threads:[~2003-05-12 12:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 11:59 Frank Cusack
2003-05-12 12:13 ` Christoph Hellwig
2003-05-12 12:16 ` Alan Cox
2003-05-12 12:36 ` Paul Mackerras [this message]
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=16063.38221.73659.403481@argo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=fcusack@fcusack.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

all inboxes | Powered by JetHome®