Hi folks,
This is a gentle suggestion that you begin testing SECURED=1 builds if you are not already, as the Certification Test Tool will require Security functions to be enabled in order to pass. In other words, there are Security Tests in the Certification Test Spec, and if your device stack is built with SECURED=0 (the default still lingering in scons) it will not pass the Security Tests! The first and easiest way to verify that your SECURED=1 build works is to follow the instructions for a simple client/server test found in: iotivity/resource/csdk/security/README-building-and-running-secure-IoTivity-stack.txt Samsung has also put together a set of test applications for testing provisioning. These apps and associated README files are located in the following directories: 1. To test provisioning APIs (csdk): we use samples in "iotivity\resource\csdk\security\provisioning\sample" 2. To test provisioning apis (C++ layer): we use samples in "iotivity\resource\provisioning\examples" It's worth noting that with SECURED=1, other sample applications will not work as expected, until they are updated to implement a few callbacks for persistent storage. It is not required to update the other sample applications, as they are not used for Certification. But do note that they are not going to work, because they do not have the callbacks required for storing device state related to onboarding, access control configuration, etc. We do not want anyone to be surprised by the Security Tests in the CTT, so please make sure the device you bring to PF#7 is built with SECURED=1. Thanks, Nathan Heldt-Sheller Spec Coordination TG - Security TF -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160328/51a56624/attachment.html>
