From: Daniel Wagner <wagi@monom.org>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: "VAUTRIN Emmanuel (Canal Plus Prestataire)"
<Emmanuel.VAUTRIN@cpexterne.org>,
"connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: Re: [PATCH] iwd: Fix connection with no passphrase
Date: Fri, 21 Jan 2022 08:53:45 +0100 [thread overview]
Message-ID: <20220121075345.pab7lvyb2hfrfsos@beryllium.lan> (raw)
In-Reply-To: <CAOf5uwmgupp-oHt2a9jahxE9V9pYgw2VbNfsHa7g8o32WiPBqg@mail.gmail.com>
On Tue, Jan 18, 2022 at 12:03:12PM +0100, Michael Nazzareno Trimarchi wrote:
> On Tue, Jan 18, 2022 at 12:01 PM VAUTRIN Emmanuel (Canal Plus
> Prestataire) <Emmanuel.VAUTRIN@cpexterne.org> wrote:
> >
> > During a failing connection on a secure network with no passphrase,
> > agent_request_passphrase() crashes, trying to manipulate the value
> > of the "WiFi.Passphrase" key, which is null.
Patch applied.
> I don't know if we have some Reviewed-by: Michael Trimarchi
> <michael@amarulasolutions.com>
No, we didn't do this SoB & Co stuff so far. IIRC it is something Intel
sponsored projects do. Though this is project is complete independent by
now. I haven't really spend any time figuring out the legal stuff. Hence
I didn't wanted to start adding SoB. The reviewed tag seems not to touch
any of the legal stuff. Added it :)
Daniel
next prev parent reply other threads:[~2022-01-21 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220118105214.1201110-1-Emmanuel.VAUTRIN@cpexterne.org>
2022-01-18 11:01 ` [PATCH] iwd: Fix connection with no passphrase VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-01-18 11:03 ` Michael Nazzareno Trimarchi
2022-01-21 7:53 ` Daniel Wagner [this message]
2022-01-21 9:46 ` VAUTRIN Emmanuel (Canal Plus Prestataire)
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=20220121075345.pab7lvyb2hfrfsos@beryllium.lan \
--to=wagi@monom.org \
--cc=Emmanuel.VAUTRIN@cpexterne.org \
--cc=connman@lists.linux.dev \
--cc=michael@amarulasolutions.com \
/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).