From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 5/6] gatchat: support for auth NONE
Date: Tue, 02 Oct 2018 18:26:00 -0500 [thread overview]
Message-ID: <fcd0ecad-519e-7add-88cf-e39060886f64@gmail.com> (raw)
In-Reply-To: <20181002062628.17466-5-gciofono@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
Hi Giacinto,
On 10/02/2018 01:26 AM, Giacinto Cifelli wrote:
> Added authentication method G_AT_PPP_AUTH_METHOD_NONE and its handling.
>
> This method is already used in the code, and
Hmm, I don't think so?
> the patch is just allowing its explicit use, on top of the implicit
> selection done when username is empty.
I do not see how this is true? Even if username / password is empty,
the CHAP/PAP authentication method applies. We just hash the empty
password for CHAP / send it plaintext for PAP.
There is of course the possibility that the PPP server can simply not
ask us for the AUTH_PROTO option, in which case we would find that
acceptable and the auth protocol would not be used.
> ---
> gatchat/gatppp.c | 3 ++-
> gatchat/gatppp.h | 1 +
> gatchat/ppp_lcp.c | 3 +++
> 3 files changed, 6 insertions(+), 1 deletion(-)
>
<snip>
> diff --git a/gatchat/ppp_lcp.c b/gatchat/ppp_lcp.c
> index df9cd0ef..258ae763 100644
> --- a/gatchat/ppp_lcp.c
> +++ b/gatchat/ppp_lcp.c
> @@ -279,6 +279,9 @@ static enum rcr_result lcp_rcr(struct pppcp_data *pppcp,
> *new_len = 4;
>
> return RCR_NAK;
> +
> + case G_AT_PPP_AUTH_METHOD_NONE:
> + return RCR_ACCEPT;
Should this not be RCR_REJECT ? Otherwise we're accepting a server
proposed auth protocol when we're explicitly configured not to use one.
> }
> break;
> }
>
Regards,
-Denis
next prev parent reply other threads:[~2018-10-02 23:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 6:26 [PATCH 1/6] connman-api: added "none" auth_method Giacinto Cifelli
2018-10-02 6:26 ` [PATCH 2/6] gprs-context: added OFONO_GPRS_AUTH_METHOD_NONE Giacinto Cifelli
2018-10-02 6:26 ` [PATCH 4/6] plugins/file-provisioning.c: support for auth NONE Giacinto Cifelli
2018-10-02 6:26 ` [PATCH 3/6] src/gprs: support for NONE auth Giacinto Cifelli
2018-10-02 6:26 ` [PATCH 5/6] gatchat: support for auth NONE Giacinto Cifelli
2018-10-02 23:26 ` Denis Kenzior [this message]
2018-10-02 6:26 ` [PATCH 6/6] drivers: " Giacinto Cifelli
2018-10-03 21:29 ` Denis Kenzior
2018-10-04 3:44 ` Giacinto Cifelli
2018-10-04 4:40 ` Denis Kenzior
2018-10-04 4:51 ` Giacinto Cifelli
2018-10-05 2:04 ` Denis Kenzior
2018-10-05 2:07 ` Giacinto Cifelli
2018-10-04 4:43 ` Giacinto Cifelli
2018-10-05 2:20 ` Denis Kenzior
2018-10-05 2:23 ` Giacinto Cifelli
2018-10-05 2:47 ` Denis Kenzior
2018-10-05 2:51 ` Giacinto Cifelli
2018-10-05 3:23 ` Denis Kenzior
2018-10-05 3:30 ` Giacinto Cifelli
2018-10-05 3:37 ` Denis Kenzior
2018-10-05 3:54 ` Giacinto Cifelli
2018-10-05 4:09 ` Denis Kenzior
2018-10-05 4:13 ` Giacinto Cifelli
-- strict thread matches above, loose matches on Subject: below --
2018-10-03 3:32 [PATCH 5/6] gatchat: " Giacinto Cifelli
2018-10-03 16:45 ` Denis Kenzior
2018-10-03 18:22 ` Giacinto Cifelli
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=fcd0ecad-519e-7add-88cf-e39060886f64@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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