From: ben_gal@libero.it
To: linux-ppp@vger.kernel.org
Subject: Re: Client requesting its authentication
Date: Thu, 24 Feb 2005 22:04:37 +0000 [thread overview]
Message-ID: <20050224220437.GA2445@ytsejam> (raw)
In-Reply-To: <20050224162619.GB5787@ytsejam>
On Thu, Feb 24, 2005 at 01:27:54PM -0800, Bill Unruh wrote:
> Then demand that they authenticate themselves to you via eap. If that is
> what you want then demand it. Why are you trying to force them into
> demanding it from you? " I want you to do something. But I do not want to
> ask you to do it, I want to force you to ask me to do it". That is not how
> the world works. If you want something, ask for it.
I don't want to *force* the peer to authenticate me.
I want to *hint* him.
If he doesn't want that, I close because that doesn't satisfy me.
This seems not so strange to me.
> >
> >This is the behaviour I were looking for:
>
> Sorry, the behaviour you want is that the two sides never agree on anything
> and refuse to talk to each other?
Is more desiderable that they don't connect than a client connecting
to an untrusted server without authentication
> Well demand that it authenticate itself to you via eap.
In tls there's a client and a server. Roles cannot be swapped
>
> That is the other sides perfect right. If someone walked up to you and
> demanded that you demand to see his driver's license, don;t you think a
> valid reaction on your part is to walk away?
Yes. This isn't a problem.
The problem is when I trust him, but we haven't shown driver licenses each
other.
next prev parent reply other threads:[~2005-02-24 22:04 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
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 [this message]
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=20050224220437.GA2445@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 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.