Jay,

Please provide more information about your issue.  I originally wrote the data 
structures you are talking about, and I am concerned there might be a larger 
problem now.

The host address field should only contain the address string itself.  The 
longest of these is a full IPv6 address: 
ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, which is 39 bytes long, plus one for a 
terminating null.   What other information are you seeing in the string?
You report seeing ?coaps://[fe80::a00:27ff:feaf:f911]:36238?, but that should 
never be put in a buffer defined by MAX_ADDR_STR_SIZE.  Can you say where that 
happened?
The string MAX_ADDR_STR_SIZE should only be used or the host field of an 
OCDevAddr or CAEndpoint_t.  I see it is now used for other fields, and with 
other sizes than 40.

This misuse will lead to larger problems in future.  It is an addition to the 
considerable technical debt we have on this project.

John Light
Intel OTC OIC Development



From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of ???
Sent: Wednesday, November 04, 2015 5:39 PM
To: ???; 'iotivity'
Subject: Re: [dev] Pre-defined length for the Host Info. is not long enough


Hi. Jay,



I also encountered the situation you described below, but I found that this 
problem has been already resolved in the master branch with a patchset, 
https://gerrit.iotivity.org/gerrit/#/c/2481/. Please look into it.



However, I don't know why this patch had not been merged into 1.0.0-dev branch. 
In the 1.0.0-dev branch which is 1.0 release branch, there is still the above 
problem. May be someone missed merging the patchset into the branch.



Thank you.



BR, Jihun Ha



------- Original Message -------

Sender : ???<junghyun.oh at samsung.com<mailto:junghyun.oh at samsung.com>> 
S5(??)/??/IoT Lab(S/W??)/????

Date : 2015-11-04 17:24 (GMT+09:00)

Title : [dev] Pre-defined length for the Host Info. is not long enough


Hi all,

Currently, I?m trying to port the ?Secure? version of the IoTivity into an 
embedded device.
While I was tried to create a resource object of a remote resource from the 
Resource Client
using an API ?constructResourceObject?, I found that the Stack doesn?t allow 
the host infor.
of which length exceeds 40 bytes.
Actually the target Resource server was supporting IPv6 and using secure 
version of IoTivity,
the length of the host infor exceeds 40 bytes.
Here is the error log & the actual string of the host infor of the Resource 
Server..

=>  Error Log

terminate called after throwing an instance of 'std::length_error'
what(): host address is too long.



=>  Host infor.

coaps://[fe80::a00:27ff:feaf:f911]:36238

As you can notice the length of the host infor. is 41 bytes.(including ?\0? at 
the end).
Since the variables defined for the MAX length of the host infor. are exists 
both in the RI layer & CA layer
& used by lots of locations inside the both layers, I think it will be better 
if the contributors of the both layers
take a look at this and fix if necessary.
(CA : cacommon.h  MAX_ADDR_STR_SIZE_CA 40  , RI : octypes.h MAX_ADDR_STR_SIZE 
40)

I?ve created an issue on Jira (https://jira.iotivity.org/browse/IOT-824)
I really will be appreciated if someone resolve this issue. :)

Thank you.
Jay.





?????. ??? ??.



Best Regards,



Jihun Ha (???/???, Ph.D.)

IoT, IoTivity, OIC | IoT Solution Lab

Software R&D Center | Samsung Electronics Co., Ltd

Mobile +82 10 2533 7947

jihun.ha at samsung.com | jhha85 at gmail.com



[cid:image001.gif at 01D1179E.CAC84850]

[http://ext.samsung.net/mailcheck/SeenTimeChecker?do=7038567541a37f7847dabb2f687bff399af25d913e7743e5a9b245bbf05ab6f693b88b5cdcaca3638c238075770efdd88a3bd3da7f658eba62e1ac75b522795a07805447a154a46fcf878f9a26ce15a0]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151105/a29c8341/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13168 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151105/a29c8341/attachment.gif>

Reply via email to