IMO, the key of SECURED=1 is the SVR (Security Virtual Resources) have been enforced, it's ACL decides whether the accesses can be granted, the OC_SECURE and OC_NONSECURE flags are used for enabling plain coap:// and secured coaps:// endpoints during the resource registration. If you register a resource with OC_NONSECURE, the client still can't access the resource unless there is a "anon-clear" connection type ACE set in the persistent database.
Regards, Tonny On 1 September 2017 at 10:58, sunlf <su...@haierubic.com> wrote: > Hi,Devs, > > > > I have one question about building option, SECURED. > > > > My understanding is , if setting SECURED=1 while building, this will > cause while the communication between Sever and Client, SSL will be used. > And for the implement of Server and Client, OC_SECURE must be set. > > > > If SECURED=1 is set while building, and OC_SECURE is not set while > creating resource, the client will not found the resource created by server > since here is no SSL at server. > > > > Is there anything wrong? > > > > Thanks > > > > Jason Sun > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev@lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > >
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
