From: "Gix, Brian" <brian.gix@intel.com>
To: "prathyusha.n@samsung.com" <prathyusha.n@samsung.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Cc: "s.syam@samsung.com" <s.syam@samsung.com>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH 1/1] mesh: Check limits for count and interval of relay
Date: Thu, 26 Mar 2020 17:02:31 +0000 [thread overview]
Message-ID: <98bbd043aa74d51223e6b445ea7656851f5f8baa.camel@intel.com> (raw)
In-Reply-To: <a0d832523512cf3f4f9c7eed27a258687732e47d.camel@intel.com>
Applied
On Wed, 2020-03-25 at 19:12 +0000, Gix, Brian wrote:
> Hi Prathyusha,
>
> Inga and I have been talking, and comparing behavior to spec, and we believe that the *only* way that invalid
> data can make its way into the system is to hand-edit the node.json file, which is not something we want to
> encourage. We suggest moving validation to where the node.json is read....
> mesh/config-json.c in parse_features()
>
> Basically, we only care if
> "mode":"enabled",
>
> in which case, we range check interval (10-320) and count (1-8).
>
> Any values outside that range, we "Fail to Parse" the node, and that node will not be loaded.... So edit the
> node.json by hand *only* with legal arguments.
>
> Beyond that, if relay is "disabled" or "unsupported", the interval and count are don't cares, and there is no
> obligation for the 2nd parameter octet of RELAY_STATUS to be zero'd. As for the incoming RELAY_SET, there
> are
> no out of range or disallowed values for count or interval.
>
>
> On Wed, 2020-03-25 at 00:57 +0530, Prathyusha Nelluri wrote:
> > From: Prathyusha N <prathyusha.n@samsung.com>
> >
> > Added limit checking condition for count and interval
> > before processing for count and interval steps.
> > ---
> > mesh/cfgmod-server.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/mesh/cfgmod-server.c b/mesh/cfgmod-server.c
> > index 7111411c7..151cab154 100644
> > --- a/mesh/cfgmod-server.c
> > +++ b/mesh/cfgmod-server.c
> > @@ -881,7 +881,11 @@ static bool cfg_srv_pkt(uint16_t src, uint32_t dst, uint16_t unicast,
> > n = mesh_model_opcode_set(OP_CONFIG_RELAY_STATUS, msg);
> >
> > msg[n++] = node_relay_mode_get(node, &count, &interval);
> > - msg[n++] = (count - 1) + ((interval/10 - 1) << 3);
> > +
> > + if (count > 0 && interval >= 10)
> > + msg[n++] = (count - 1) + ((interval/10 - 1) << 3);
> > + else
> > + msg[n++] = 0;
> >
> > l_debug("Get/Set Relay Config (%d)", msg[n-1]);
> > break;
next prev parent reply other threads:[~2020-03-26 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200324192821epcas5p3e756863feafcf1f8eab993a237c19521@epcas5p3.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Add mesh agent cleanup to mesh cleanup Prathyusha Nelluri
[not found] ` <CGME20200324192820epcas5p10a4ae9a6d7e7dab22f4a5ab4ee752099@epcas5p1.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Check limits for count and interval of relay Prathyusha Nelluri
2020-03-25 19:12 ` Gix, Brian
2020-03-26 17:02 ` Gix, Brian [this message]
[not found] ` <CGME20200324192821epcas5p1cc8182aac6ed0b096c76e3ccbd269688@epcas5p1.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Handle close for Acceptor Prathyusha Nelluri
[not found] ` <CGME20200324192822epcas5p2986c35616c596051bb7826457439c893@epcas5p2.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Handle invalid public keys Prathyusha Nelluri
2020-03-26 17:03 ` Gix, Brian
[not found] ` <CGME20200324192823epcas5p3b25363353b98e206a50d7fd4572c9552@epcas5p3.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Handle KeyRefresh phase 1 to phase 3 Prathyusha Nelluri
[not found] ` <CGME20200324192824epcas5p4886d88a31b8f9b31eeaf2fa38385698b@epcas5p4.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Handle KeyRefresh phase set to 3 Prathyusha Nelluri
[not found] ` <CGME20200324192824epcas5p1de37a38491d79ea6dca2cc5da50cd289@epcas5p1.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Handle netkey delete when netkey is not in netkeylist Prathyusha Nelluri
2020-03-26 17:03 ` Gix, Brian
[not found] ` <CGME20200324192825epcas5p4c038b652414de6be433f224a655a2244@epcas5p4.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Initialize local_acked to zero Prathyusha Nelluri
[not found] ` <CGME20200324192826epcas5p2eb80e44ac061329faf5421ba3b76e5f8@epcas5p2.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Send input complete for input OOB Authentication Prathyusha Nelluri
2020-03-26 17:02 ` Gix, Brian
[not found] ` <CGME20200324192827epcas5p3f70d5e24d6042786ffea8bdbd5ddc8e8@epcas5p3.samsung.com>
2020-03-24 19:27 ` [PATCH 1/1] mesh: Validate Provisioning Start PDU values Prathyusha Nelluri
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=98bbd043aa74d51223e6b445ea7656851f5f8baa.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=prathyusha.n@samsung.com \
--cc=s.syam@samsung.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).