Re: [dev] Android SECURED mode

Hi Tonny, I didn't think of setting both flags, that might be the solution. In any case I still need to figure out why scons can't build Android for me. If I manage to do that and fix the problem I'll post here. Thank you for the help! Best regards, A. Lapprand Em ter, 19 de dez de 2017 às 11:21

Re: [dev] Android SECURED mode

Hi Arthur, You are right, unless you set both the ResourceProperty.NONSECURE and ResourceProperty.SECURE flags to enable both coap:// and coaps:// endpoints, so that anonymous requests can match the "anon_clear" ACE... Regards, Tonny On 19 December 2017 at 21:59, Arthur Barros Lapprand wrote:

Re: [dev] Android SECURED mode

Hi Tonny, So that means I can't access a resource registered with ResourceProperty.SECURE flag by using coap:// while setting an ACE for it with "anon_clear", right? Best regards, A. Lapprand Em ter, 19 de dez de 2017 às 10:38, Tonny Tzeng escreveu: > ​Hi Arthur, > > Set the ​ResourceProperty.

Re: [dev] Android SECURED mode

​Hi Arthur, Set the ​ResourceProperty.SECURE flag will instruct the stack to use the secured coaps:// endpoint, so you must use "auth_crypt" connection type ACE for that resource, and the credentials must be installed for mutual authentication. As you only wanted to run the existing code, you migh

Re: [dev] Android SECURED mode

Hi Tonny, Yes, initially I want to run existing code and that ACE will hopefully be helpful even though I've once tried to use that wildcard ACE without success. I do use the ResourceProperty.SECURE flag when registering resources but I'm not sure if I really need to set credentials in the SVR dat

Re: [dev] Android SECURED mode

Hi Arthur, The concept to get secure access to a resource is the same for C++ and JavaScript -- use secure endpoint in C++/JavaScript, and have proper ACL and credential setup in the SVR database. If what you want is to run existing code intact but with SECURED=1, then add an anonymous connection

Re: [dev] Android SECURED mode

Sorry I meant I want to state this, not a few things, hehe. Basically I want to focus on local ACL permissions without dealing with the whole device ownership and pairing process. Thank you again! 2017-12-18 10:12 GMT-03:00 Arthur Barros Lapprand : > Hi, thank you for the quick replies! > > @Max

Re: [dev] Android SECURED mode

Hi, thank you for the quick replies! @Max > I never succeeded with setting the "di" using API > I also never succeeded. However, since there was a recent release I should first give it a try. @Tonny I had an overview of the article. Very interesting indeed! But it uses javascript which isn't wh

Re: [dev] Android SECURED mode

Hi, We just posted an article at 01.org talking few security concept in IoTivity. Though we were using iotivity-node as an example, I think the following steps would get your Client accesses to the Server securely:

Re: [dev] Android SECURED mode

Hi Arthur, You should be able to communicate between the client and the server on Android, using SECURED=1 library. First, to set your "di" (client or server) - you need to specify the "di" value inside the DAT file (containing security information) - you can look at the samples. I never succeede

[dev] Android SECURED mode

Hi all, I have a few beginner-leveled questions about secure mode in Android. Let me explain the situation: I have created two apps (one for Server/Controlee and the other for the Client/Controller) and I'm able to FIND and GET/POST/OBSERVE them without problems. As this is a simple example, I no