[
https://issues.apache.org/jira/browse/MYNEWT-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898422#comment-15898422
]
ASF subversion and git services commented on MYNEWT-654:
--------------------------------------------------------
Commit 0dc1c2b85664cdde99c48f8628cacdc0c52e4852 in incubator-mynewt-core's
branch refs/heads/1_0_0_dev from [~ccollins476]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=0dc1c2b
]
MYNEWT-654 datetime command may crash device
There are two issues here:
1. newtmgr tool always includes an extraneous rc:0 key-value pair in its
outgoing datetime commands.
2. Server-side, the firmware parses the "rc" value and writes the result
to null.
This commit addresses the second issue as follows: Don't attempt to
parse the rc entry in incoming requests.
> datetime command may crash device
> ---------------------------------
>
> Key: MYNEWT-654
> URL: https://issues.apache.org/jira/browse/MYNEWT-654
> Project: Mynewt
> Issue Type: Bug
> Reporter: Christopher Collins
> Assignee: Christopher Collins
> Fix For: v1_0_0_rel
>
>
> There are two issues here:
> 1. newtmgr tool always includes an extraneous rc:0 key-value pair in its
> outgoing datetime commands.
> 2. Server-side, the firmware parses the "rc" value and writes the result to
> null.
> The solutions are:
> 1. Remove the rc entry from the datetime request.
> 2. Don't attempt to parse the rc entry in incoming requests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
