On Friday 03 April 2015 02:10:17 Agrawal, Sachin wrote:
> We have requested tinydtls author to accept our patch
> <http://sourceforge.net/p/tinydtls/tickets/17/> , but we have not received
> any feedback yet. This patch was reviewed in Iotivity Gerrit Review 407
> <https://gerrit.iotivity.org/gerrit/#/c/407/> by iotivity security team.
> But, we also want to avoid forking tinydtls by diverging a lot from upstream
> repo.
>
> So we are requesting guidance from Iotivity Maintainers/Sub-Maintainers on
> how can security team move forward in this situation?
There doesn't seem to be a link to the patch or an attachment with it in the
TinyDTLS ticket. The upstream maintainer may be wondering if it's a feature
request.
Ticket 16 was opened on the same day by Randeep Singh (Samsung) and it
included this exchange:
Randeep: We have already created and tested the patch on Arduino Mega2560. I
Could share it or i can contribute it to repo.
Olaf (maintainer): Awesome! It would be great if you could provide a patch
created with git format-patch.
I suggest attaching the patch to the ticket to get Olaf's attention.
Also note that upstream is not bound by our deadlines. One week to reply may
be acceptable to them and there's nothing we can do as IoTivity. If we, as a
group, want TinyDTLS to move faster, we should begin contributing directly to
it (including fixing bugs not related to IoTivity).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
