SECURED is build option enabling security module. This will enable the ACL table check.
But Access control is only valid for the resource created with OC_SECURE option. We call it secure resource. Anyway, ACL table check and target resource access are different step. Open Access rule (*) can be applied to the specific secure resource, This is valid for the resource with OC_SECURE option. >From the previous OCF meeting, two options enabling the open access have been discussed. One is to set * by creating resource with OC_SECURE option, The other is to create resource without OC_SECURE option. Please Anyone who know final status share the status. BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Annie Weng Sent: Tuesday, August 30, 2016 12:22 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] Question about non-secured resource with SECURD config enabled Hi All: I have some questions about OC_SECURED flag. May I have your help for it? (1) According to this message: http://lists.iotivity.org/pipermail/iotivity-dev/2015-December/003202.html As long as the SECURD config is enabled, SRM will always check the ACL, irrespective if OC_SECURED of the resource is set or not. Then, except coaps/coap selection, what is the effect of with/without OC_SECURED flag? (2) Does it mean that: if we want to design an ?open-access? resource, it seems that it is nothing about setting OC_SECURED flag or not. The only thing is set ACL as ?allowing wildcard access?, isn?t it? Thank you. Best Regards, Annie -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160830/0a41de9b/attachment.html>
