From: ben_gal@libero.it
To: linux-ppp@vger.kernel.org
Subject: Re: Client requesting its authentication
Date: Thu, 24 Feb 2005 18:08:07 +0000 [thread overview]
Message-ID: <20050224180807.GB2421@ytsejam> (raw)
In-Reply-To: <20050224162619.GB5787@ytsejam>
On Thu, Feb 24, 2005 at 09:43:11AM -0800, Bill Unruh wrote:
> He understood you perfectly. That is precicely what the refuse-... do,
> except that
> you cannot force the other side to authenticate you .
This is what I wanted to know.
> If you
> want them to authenticate themselves to you then you must say do.
> Ie, authentication is under the control of whoever wants the other side to
> be authenticated. Nothing else makes any sense. Of course since eap in some
> sense is a bilateral authentication one might argue that y our request is
> sensible, but the way to do it is for you to demand eap authentication from
> the other side, and to refuse all other types of authentication from the
> other side, as Carlson suggested.
> Why by the way do you want to force the other side to authenticate you?
Because I've written a patch to pppd that permits eap-tls authentication.
eap-tls provide mutual authentication, so if you (client) connect to a server,
you want to be sure of its identity, so the authentication can't be
skipped.
This is the behaviour I were looking for:
using channel 4
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <magic 0x290d2a43> <pcomp> <accomp>]
sent [LCP ConfAck id=0x0 <asyncmap 0x0> <magic 0x290d2a43> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x1 <auth 0xc227>]
sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x2 <auth 0xc227>]
sent [LCP ConfReq id=0x3 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x3 <auth 0xc227>]
sent [LCP ConfReq id=0x4 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x4 <auth 0xc227>]
sent [LCP ConfReq id=0x5 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x5 <auth 0xc227>]
sent [LCP ConfReq id=0x6 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x6 <auth 0xc227>]
sent [LCP ConfReq id=0x7 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x7 <auth 0xc227>]
sent [LCP ConfReq id=0x8 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x8 <auth 0xc227>]
sent [LCP ConfReq id=0x9 <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0x9 <auth 0xc227>]
sent [LCP ConfReq id=0xa <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP ConfNak id=0xa <auth 0xc227>]
sent [LCP ConfReq id=0xb <asyncmap 0x0> <magic 0xb30db629> <pcomp> <accomp>]
rcvd [LCP TermReq id=0x1 ")\r*C\000<\37777777715t\000\000\002\37777777734"]
sent [LCP TermAck id=0x1]
Modem hangup
Connection terminated.
Is logged between a windows box (client) set to do eap-tls and the
pppd server.
The server don't want to authenticate the client, but the client want
eap authentication for itself and finally close the negotiation.
next prev parent reply other threads:[~2005-02-24 18:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 16:26 Client requesting its authentication ben_gal
2005-02-24 16:37 ` James Carlson
2005-02-24 17:30 ` ben_gal
2005-02-24 17:43 ` James Carlson
2005-02-24 17:43 ` Bill Unruh
2005-02-24 17:48 ` James Carlson
2005-02-24 18:08 ` ben_gal [this message]
2005-02-24 18:15 ` James Carlson
2005-02-24 18:35 ` ben_gal
2005-02-24 18:53 ` James Carlson
2005-02-24 19:02 ` ben_gal
2005-02-24 21:27 ` Bill Unruh
2005-02-24 21:33 ` Bill Unruh
2005-02-24 21:36 ` James Carlson
2005-02-24 22:04 ` ben_gal
2005-02-24 22:16 ` Bill Unruh
2005-02-24 22:18 ` Bill Unruh
2005-02-24 22:28 ` ben_gal
2005-02-24 22:36 ` James Carlson
2005-02-24 22:38 ` Bill Unruh
2005-02-24 22:48 ` Bill Unruh
2005-02-24 22:53 ` ben_gal
2005-02-24 23:00 ` Bill Unruh
2005-02-25 12:52 ` James Carlson
2005-02-27 10:07 ` ben_gal
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=20050224180807.GB2421@ytsejam \
--to=ben_gal@libero.it \
--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