Hey Nathan, Thanks for getting back to me! I attached logs to the JIRA ticket and described the samples I was using to test. If you have any other questions please let me know.
Thanks, Alex From: Heldt-Sheller, Nathan [mailto:nathan.heldt-shel...@intel.com] Sent: Monday, May 1, 2017 3:54 PM To: Alex Kelley <alexke at microsoft.com>; iotivity-dev at lists.iotivity.org Cc: Daniel Mihai <Daniel.Mihai at microsoft.com>; Kevin Kane <kkane at microsoft.com> Subject: RE: MOT is broken on the latest 1.3-rel Hi Alex, I'm blocked from trying to repro your issue by IOT-2121, but I posted a comment on your issue that might help at least narrow the scope. Thanks, Nathan From: Alex Kelley [mailto:ale...@microsoft.com] Sent: Monday, May 1, 2017 2:50 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Cc: Daniel Mihai <Daniel.Mihai at microsoft.com<mailto:Daniel.Mihai at microsoft.com>>; Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com<mailto:nathan.heldt-sheller at intel.com>>; Kevin Kane <kkane at microsoft.com<mailto:kkane at microsoft.com>> Subject: MOT is broken on the latest 1.3-rel Hi All, MOT is broken in the latest 1.3-rel. Specifically provisioningclient is no longer able to enable MOT on a specific device such as sampleserver_randompin. When OCChangeMOTMode is called the callback returns OC_STACK_NOT_ACCEPTABLE as an error. Based on where I was before pulling the latest changes the regression happened somewhere after the following change: * Title: bridging: Remove lib/lib64 path as unsupported on clang * Hash: 6150c09877559778f1ef2c2ea20c30ec69bceee8 Since then there appears to have been some significant changes around security. Could someone take a look into this issue? MOT is an important feature for making user scenarios seamless and it is also used by the new API surface, IPCA. IOT-2182<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.iotivity.org%2Fbrowse%2FIOT-2182&data=02%7C01%7Calexke%40microsoft.com%7C5ac8ca41c55e45e4fca608d490e4f500%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636292760417786644&sdata=l3490YLjgePS4obMOzC7QsPCP8ESNLQIwsUELQItHV4%3D&reserved=0> has been opened to track this issue. Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170502/688458b5/attachment.html>
