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 23:07:20 +1000	[thread overview]
Message-ID: <16063.40072.101121.244892@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20030512060210.C29881@google.com>

Frank Cusack writes:

> I have the compressor return a 3-valued return code (<0, 0, >0) instead of
> two-valued (>0, other).  A negative value tells ppp_generic to drop the
> packet.  0 means the same as it does now--the compressor failed for some
> reason.  (All current compressors always return 0 or >0, so the negative
> return is compatible.)
> 
> 0 could also mean that CCP isn't up yet, but pppd userland doesn't allow
> NCP's to come up until CCP completes (iff trying to negotiate MPPE).

Hmmm, and are you sure that nothing can cause CCP to go down?  If it
does then ppp_generic will send data uncompressed.  What would happen
if an attacker managed to insert a CCP terminate-request into the
receive stream somehow?

I think the whole thing needs a careful audit.  The idea that you fall
back to sending and receiving uncompressed data if CCP goes down or a
compressor fails is pretty fundamental to the CCP implementation in
ppp_generic.

Paul.


  reply	other threads:[~2003-05-12 12:55 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
2003-05-12 13:02   ` Frank Cusack
2003-05-12 13:07     ` Paul Mackerras [this message]
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.40072.101121.244892@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®