I created A Jira ticket to change the default flag for SECURED from '0' to '1' https://jira.iotivity.org/browse/IOT-1320
I have created the change and committed it: https://gerrit.iotivity.org/gerrit/#/c/12085/ The Android and Arduino builds would not build when the SECURED=1 flag was used. I don't know much about the Arduino build but I feel the Android build needs to be fixed so it will build with SECURED=1. The only OS that this commit actually changes the SECURED build option for is Darwin. Currently jenkens is getting a failure when building the linux_secured_with_tcp option. It is printing the following error. 20:02:51 *********************************** Error: **************************************** 20:02:51 * Please download mbedtls using the following command: * 20:02:51 * $ git clone https://github.com/ARMmbed/mbedtls.git extlibs/mbedtls/mbedtls * 20:02:51 *********************************************************************************** On my local system if I download the mbedtls.git project it builds I still get some build failures. However I still see the same failures even when I build without my change so it may be something on my local setup. George -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Dave Thaler via iotivity-dev Sent: Tuesday, September 20, 2016 2:27 PM To: Macieira, Thiago <thiago.macieira at intel.com>; Gregg Reynolds <dev at mobileink.com> Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] SECURE build flag setting as default configuration I've now thought about this some more and I am now convinced that we should remove support for SECURE=0 builds (in master). As Uze mentioned, the choice to disable security should be a config/run-time decision, not a compile-time decision. There is no reason to consume build resources to build a version that cannot even be configured to enable security. > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Dave Thaler via iotivity-dev > Sent: Tuesday, September 20, 2016 8:18 AM > To: Thiago Macieira <thiago.macieira at intel.com>; Gregg Reynolds > <dev at mobileink.com> > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] SECURE build flag setting as default configuration > > If we continue to support SECURE=0 at all, then I agree SECURE=1 needs > to at least be the default, so that if you don't specify SECURITY= > then you are secure by default. > > I have no preference on whether SECURE=0 support is maintained or > removed. > > Dave > > > -----Original Message----- > > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > > Sent: Tuesday, September 20, 2016 6:37 AM > > To: Gregg Reynolds <dev at mobileink.com> > > Cc: iotivity-dev at lists.iotivity.org > > Subject: Re: [dev] SECURE build flag setting as default > > configuration > > > > On segunda-feira, 19 de setembro de 2016 15:53:26 PDT Gregg Reynolds > > wrote: > > > > It shouldn't be *supported*. > > > > > > > > It was used for a long time during development so that we could > > > > do a packet capture and use it to debug what was happening. > > > > > > Sorry, I am a bear of small brain. do you mean it was used to > > > disable dtls so that e.g. stuff captured by wireshark would not be > encrypted? > > > was there more to it than that? > > > > Correct, it disabled encryption and the ACLs, along with the > > security-related resources that IoTivity implements on behalf of the > application. > > > > -- > > Thiago Macieira - thiago.macieira (AT) intel.com > > Software Architect - Intel Open Source Technology Center > > > > _______________________________________________ > > iotivity-dev mailing list > > iotivity-dev at lists.iotivity.org > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
