From: James Cameron <james.cameron@hp.com>
To: linux-ppp@vger.kernel.org
Subject: Re: final repost - MPPE incorrect REJECT/NAK behaviour (was Re: Windows mobile 2005 clients)
Date: Sun, 19 Feb 2006 23:02:16 +0000 [thread overview]
Message-ID: <20060219230216.GB3621@hp.com> (raw)
In-Reply-To: <43F8F60F.70106@imperial.ac.uk>
Looked fine to me, and so I began to test it, but it would not apply to
PPP CVS, which appears to contain code that does something similar.
Is it already fixed in CVS? Could you try CVS? Or adapt your change to
what is already there?
ccp.c 1.50
} else {
/* Neither are set. */
/* We cannot accept this. */
newret = CONFNAK;
/* Give the peer our idea of what can be used,
so it can choose and confirm */
ho->mppe = ao->mppe;
}
--
James Cameron http://quozl.netrek.org/
HP Open Source, Volunteer http://opensource.hp.com/
PPTP Client Project, Release Engineer http://pptpclient.sourceforge.net/
next prev parent reply other threads:[~2006-02-19 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 22:49 final repost - MPPE incorrect REJECT/NAK behaviour (was Re: Windows Phil Mayers
2006-02-19 23:02 ` James Cameron [this message]
2006-02-19 23:40 ` Phil Mayers
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=20060219230216.GB3621@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).