That's what I said in JIRA IOT-821. That Issue was closed, claiming Change 4237 fixes it. I suspect little testing was done with actual wire protocol mismatches, but I don't know.
As far as I can tell from examining the code, the changed needed to fix this problem was not incorporated. The emphasis in 4237 seems to be testing all the obvious error conditions (in a way that seems to bloat the code.) Testing between 1.0.0 and 1.0.1 would verify that. John -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Friday, March 25, 2016 9:14 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Is there anybody who has seen an assertion abort of tinycbor? On sexta-feira, 25 de mar?o de 2016 14:50:37 PDT Light, John J wrote: > Uze Choi, > This can also happen with there is a version mismatch in the wire protocol. > Make sure both client and server are built from the same version. Crashing is not acceptable. The code in the new version (1.1) needs to catch the situation where the data is in the wrong (old) format and discard the packet, without crashing. -- 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
