That makes sense, as the tool is also part of srm code tree. Explaining it in this doc will be great.
Thanks, Ashwini On 8 Apr 2016 13:23, "Chen, Shujuan" <shujuan.chen at intel.com> wrote: > Hi Ashwini, > > > > I am preparing the programming guide for Security Resource Manager > <https://wiki.iotivity.org/security_resource_manager> section and plan to > include the info about JSON to CBOR file conversion and its usage there. > > The reason is that this is related to the API docs for PSI handler > registration for SRM. > > Does it sound ok? > > > > > > Regards, > > Shujuan > > > > > > *From:* iotivity-dev-bounces at lists.iotivity.org [mailto: > iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Ashwini Sharma > *Sent:* Thursday, April 7, 2016 6:24 PM > *To:* Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com> > *Cc:* iotivity-dev <iotivity-dev at lists.iotivity.org>; Mehrtens, Hauke < > hauke.mehrtens at intel.com> > *Subject:* Re: [dev] generate and modify oic_svr_db_*.dat file > > > > Hello Hauke, > > You can follow wiki.iotivity.org Provisioning section for documentation. > > For generating .dat file you can use json2cbor tool present in > csdk/security/tool folder. > It needs the .json input file, which u can refwr from linux/secure folder. > > Run like ./json2cbor jsonFileName datFileName. > > Regards > Ashwini > > Hello Hauke, > > > > Somebody from Samsung (perhaps Randeep Singh?) will have to provide the > step-by-step for creating this file, as I do not know the process details. > > > > However the background explanation is that this file stores the Security > Virtual Resource (SVR) data. This data defines the security-related policy > for the device (e.g. Access Control Lists and Device Owner state, > credentials, etc.) In order for the device to function according to > manufacturer-specified ?default? (a.k.a. ?factory reset? or ?out of box? > behavior), the .dat file(s) are pre-loaded on the device. As the device is > on-boarded (similar process to pairing or adding a device to a domain) and > provisioned, this data is updated accordingly. > > > > Of course if this on-boarding and provisioning configuration should > persist across device resets, it must be stored in persistent storage. > > > > Hope that helps give some context! > > Thanks, > Nathan > > > > *From:* iotivity-dev-bounces at lists.iotivity.org [mailto: > iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Mehrtens, Hauke > *Sent:* Thursday, April 7, 2016 7:31 AM > *To:* iotivity-dev at lists.iotivity.org > *Subject:* [dev] generate and modify oic_svr_db_*.dat file > > > > Hi, > > > > How do I create a oic_svr_db_*.dat file or modify it? Is there some util > to do so or has IoTivity some API to do so? Is there some documentation on > how to do security with IoTivity? I saw the example in > resources/csdk/stack/samples/linux/secure/ but I am missing a little bit of > context why this is done this way. > > > > *Hauke Mehrtens* > *Intel Connected Home Division (CHD)* > > office: Lilienthalstra?e 15, 85579 Neubiberg, Germany > phone: +49 (89) 89899 ? 7179 > e-mail: hauke.mehrtens at intel.com > > VISIT US AT: http://www.intel.com/connectedhome > > FOLLOW US: @Intel_CHD <https://twitter.com/Intel_CHD> > > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > ---------------------------------------------------------------------- > Intel Sweden AB > Registered Office: Isafjordsgatan 30B, 164 40 Kista, Stockholm, Sweden > Registration Number: 556189-6027 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160408/3f385921/attachment.html>
