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:[email protected]] Sent: Monday, May 1, 2017 2:50 PM To: iotivity-dev at lists.iotivity.org Cc: Daniel Mihai <Daniel.Mihai at microsoft.com>; Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com>; Kevin Kane <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://jira.iotivity.org/browse/IOT-2182> 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/20170501/f6756858/attachment.html>
