Hi George >From what I know, there is no API for this purpose, and it's also illegal to change the "dat" manually after IoTivity initialization, since there may be a "race condition" between modifications by IoTivity and by your "replacement" code.
So what we did was: - Write a "flag" into a persistent storage - Restart the application process - When the application starts, it checks for the flag, and if set, replaces the dat file before IoTivity gets initialized If there is more efficient strategy, please share. Max -- Max Kholmyansky Software Architect - SURE Universal Ltd. http://www.sureuniversal.com On Tue, Mar 6, 2018 at 2:17 AM, Nash, George <george.n...@intel.com> wrote: > I have some code that I am running through the OFC Certification and > Testing Tool. > > > > I am currently working on the security tests. When running the tests it > will ask me multiple times to ‘Please initiat device to “ready for OTM” > state’. > > > > The OCF Security Specification v1.3.0 section 8.2 has a list of values for > the Device Ready-for-OTM State Definition. > > > > These include setting the owned property to FALSE and setting a lot of > UUIDs to the nil UUID. > > > > I could replace the security.dat file with the security.dat file before > any of the unit tests ran but I don’t know if that is what is expected. > > > > How have other developers handled putting the device into the “ready for > OTM”? Do you have a reset method that changes the values in the > security.dat file? > > > > George Nash > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev@lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > -- Max Kholmyansky Software Architect - SURE Universal Ltd. http://www.sureuniversal.com
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
