From: Jan Just Keijser <jan.just.keijser@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Authentificating with certificates ("unknown authentication type
Date: Thu, 20 Oct 2005 11:42:29 +0000 [thread overview]
Message-ID: <435782A5.7040107@gmail.com> (raw)
In-Reply-To: <e8666cf9050727142635284b29@mail.gmail.com>
I have hacked pppd to allows MPPE 128 bit encryption. The Windows PPTP
VPN status screen tells me it is using MPPE128 encryption but no
compression; ethereal dumps show me the data is compressed/encrypted.
Without the MPPE encryption I can see still the original packets inside
the GRE tunnel, with MPPE I cannot. This version is available on
http://eaptls.spe.net in the download section.
I have also created a hacked version of pppd in combination with
ppp_mppe_mppc that allow MPPE+MPPC. With this module, the PPTP VPN
status screen tells me it is using MPPE128 encryption (or MPPE40/MPPE56)
and MPPC compression. This version is not yet available on the internet
but I am working on a DKMS version of the ppp_mppe_mppe module. I have a
patched ppp-2.4.3 source tree available.
JJK
Boky Gmail wrote:
>Yes, we know about EAP-TLS.
>
>But EAP-TLS does not allow you to use MPPE/MPPC (128bit) since
>MPPE/MPPC patch expects that you use MS-CHAP[v2] authentification and
>EAP-TLS patch uses EAP authentification.
>
>Did you hack the EAP-TLS patch to provide correct credentials to
>MPPE/MPPC patch. Are you sure you are using MPPE/MPPC?
>
>I thought I was (PPTP said in output log it negotiated MPPE 128bit)
>but I was getting errors like "Unknown protocol 0x??...".
>
>As it turns out when I added "require-mppe" to my options the tunnel
>was not being setup anymore and I started getting errors in the lines
>of "MS-CHAP[v2] required for MPPE/MPPC".
>
>If you have a patch for this we'd of course be more than happy to se it.
>
>Cheers,
>Bojan
>
>On 10/20/05, Jan Just Keijser <jan.just.keijser@gmail.com> wrote:
>
>
>>hi all,
>>
>>there already is a patch to do EAP-TLS authentication with ppp; see
>> http://eaptls.spe.net
>>for details. I've just completed the patch against ppp-2.4.3 to allow
>>MPPE encryption with EAP-TLS. I have created two versions:
>>- one against the ppp_mppe module which supports 128bit MPPE but no MPPC
>>- one against the ppp_mppe_mppc module which supports 40/56/128 bit MPPE
>>and MPPC (but there are some licensing issues, I believe, with using MPPC).
>>Tested it with both XP and W2K as clients, Linux as a PoPToP server -
>>works beautifully :)
>>
>>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
prev parent reply other threads:[~2005-10-20 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 21:26 Authentificating with certificates ("unknown authentication type 13; Naking") Boky Gmail
2005-07-28 17:00 ` Boky Gmail
2005-07-28 17:33 ` James Carlson
2005-07-28 17:40 ` Boky Gmail
2005-10-20 10:42 ` Authentificating with certificates ("unknown authentication type Jan Just Keijser
2005-10-20 10:56 ` Authentificating with certificates ("unknown authentication type 13; Naking") Boky Gmail
2005-10-20 11:42 ` Jan Just Keijser [this message]
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=435782A5.7040107@gmail.com \
--to=jan.just.keijser@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.