Hi Nathan,
I think I see where our misunderstanding is now so let me try to clear it up.
You are correct that the Client side should be setting /pstat.dos to RFPRO,
updating the cred, and then setting /pstat.dos back to RFNOP. In everything I
have observed that is all working correctly. The ser
Hi Alex,
We discussed this yesterday in the Weds a.m. OSWG Security TG call. Jong-Min
(Samsung) and I agreed that the correct behavior should be that the Client sets
/pstat.dos to RFPRO, then updates /cred, then again Client sets /pstat.dos back
to RFNOP. I asked if anyone was familiar with t
just discovered bazel https://bazel.build
looks to beat scons by orders of magnitudinosity. maybe switching makes
more sense than trying to fix the current bld arrangements?
___
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iot
Hey Nathan,
Just wanted to bring this back to the top of your inbox. If you have any other
questions please let me know.
Thanks,
Alex
From: Alex Kelley
Sent: Monday, August 7, 2017 5:29 PM
To: 'Heldt-Sheller, Nathan' ;
iotivity-dev@lists.iotivity.org
Subject: RE: Regression in certificate prov
On 08/10/2017 09:19 AM, Khaled Elsayed wrote:
> Also, is there a way to search the mailing list archive just in case a
> similar question was asked?
We need to improve that (suggestions welcome, by the way)
Unfortunately as things stand, there are two problems:
- there's not really a search int
Hi
Is there a way to enable the logger only in specific parts of the overall
program?E.g. may main.cpp otherwise all other OC stack modules/libraries
remain silent as if in release mode. I know I can use printfs etc, I just
like the format of the logger output.
Also, is there a way to search the
