On Sep 19, 2016 3:38 PM, "Thiago Macieira" <thiago.macieira at intel.com> wrote: > > On segunda-feira, 19 de setembro de 2016 15:21:17 PDT Gregg Reynolds wrote: > > On Sep 19, 2016 1:04 PM, "Thiago Macieira" <thiago.macieira at intel.com> > > > > wrote: > > > On segunda-feira, 19 de setembro de 2016 21:31:51 PDT ???(Uze Choi) wrote: > > > > Currently SECURED = 0/1 is used for IoTivity compile option. > > > > > > SECURED=1 is an official option. > > > > > > Disabling security is not supported. So why do we need to test that? > > > > just curious: why is SECURED=0 supported in the first place? I've been > > using it but I'm beginning to think that is a mistake. I'm thinking of > > completely removing it from iochibity. what's that downside? > > 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? And even if we keep it working > a debugging aid, it doesn't mean it's supported. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160919/6cd942b0/attachment.html>
