Re: [dev] Secure coding guidelines for IoTivty

2017-11-03 Thread Mats Wichmann
On 11/03/17 17:05, Mats Wichmann wrote: > iotivity: the uses seem to numerically mostly be in example code, where > a lot of this sort of activity happens, but doesn't really matter that > much: these are to show people iotivity working, not to be part of a > shipped product. some statistics: I

Re: [dev] Secure coding guidelines for IoTivty

2017-11-03 Thread Mats Wichmann
On 11/03/17 15:36, Thiago Macieira wrote: > On quinta-feira, 2 de novembro de 2017 15:29:22 PDT Nash, George wrote: >> Comments on the secure coding guidelines. >> >> Under the banned C functions: >> -- >> scanf() & family. Why not list the family of fun

Re: [dev] Secure coding guidelines for IoTivty

2017-11-03 Thread Thiago Macieira
On quinta-feira, 2 de novembro de 2017 15:29:22 PDT Nash, George wrote: > Comments on the secure coding guidelines. > > Under the banned C functions: > -- > scanf() & family. Why not list the family of functions? Its best to be > explicit. This is the

Re: [dev] Secure coding guidelines for IoTivty

2017-11-02 Thread Nash, George
Comments on the secure coding guidelines. Under the banned C functions: -- scanf() & family. Why not list the family of functions? Its best to be explicit. This is the only one on the list that causes some confusion for me. Not because I don't see ho