($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 1/4] dpp-util: add support for 3rd party JSON fields
Date: Fri, 17 Nov 2023 09:49:45 -0600	[thread overview]
Message-ID: <7e815913-7537-4822-8106-1869db13e9bc@gmail.com> (raw)
In-Reply-To: <20231117141227.60722-1-prestwoj@gmail.com>

Hi James,

On 11/17/23 08:12, James Prestwood wrote:
> The DPP spec allows 3rd party fields in the DPP configuration
> object (section 4.5.2). IWD can take advantage of this (when
> configuring another IWD supplicant) to communicate additional
> profile options that may be required for the network.
> 
> The new configuration member will be called "/net/connman/iwd"
> and will be an object containing settings specific to IWD.
> More settings could be added here if needed but for now only
> the following are defined:
> 
> {
>    send_hostname: true/false,
>    hidden: true/false
> }
> 
> These correspond to the following network profile settings:
> 
> [IPv4].SendHostname
> [Settings].Hidden
> ---
>   src/dpp-util.c | 69 +++++++++++++++++++++++++++++++++++++++++++++++---
>   src/dpp-util.h |  4 +++
>   2 files changed, 70 insertions(+), 3 deletions(-)
> 

All applied, thanks.

Regards,
-Denis


      parent reply	other threads:[~2023-11-17 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 14:12 [PATCH 1/4] dpp-util: add support for 3rd party JSON fields James Prestwood
2023-11-17 14:12 ` [PATCH 2/4] dpp: include 3rd party settings in network profile James Prestwood
2023-11-17 14:12 ` [PATCH 3/4] auto-t: add checks for DPP 3rd party settings James Prestwood
2023-11-17 14:12 ` [PATCH 4/4] json: fix comment typo, "json_object_is_valid" James Prestwood
2023-11-17 15:49 ` Denis Kenzior [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=7e815913-7537-4822-8106-1869db13e9bc@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).