- 20 Nov, 2017 1 commit
-
-
Senthil Kumar G S authored
When there is an update in the properties of child resources (WifiConf, CloudConf) of collection(EasySetup), a notification should be sent to EasySetup's observers. Change-Id: I9d4d4ab0b0f7e21995d29376819e014c90408d9c Signed-off-by:
Senthil Kumar G S <senthil.gs@samsung.com>
-
- 18 Nov, 2017 1 commit
-
-
George Nash authored
Change-Id: Iecff451094731616bbab6b680954e0ec333a61a3 Signed-off-by:
George Nash <george.nash@intel.com>
-
- 17 Nov, 2017 1 commit
-
-
Philippe Coval authored
Change-Id: Ie54313a0437c8bdffe2d0c6484524a1fc6775f7d Bug: https://jira.iotivity.org/browse/IOT-1745Signed-off-by:
Philippe Coval <philippe.coval@osg.samsung.com>
-
- 15 Nov, 2017 2 commits
-
-
Nathan Heldt-Sheller authored
This reverts commit 7f9d8c71. 22967 caused a regression in the CTT; we'll fix and re-submit after regression testing. Change-Id: Ie06cf59b6463072c54b23c61d322bdb7f09cc22f Signed-off-by:
Nathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
-
Philippe Coval authored
It's part of resource, not service. Bug: https://jira.iotivity.org/browse/IOT-524 Origin: https://gerrit.iotivity.org/gerrit/#/c/23131/ Change-Id: I502591a8db1c48bc21d9dd0b768c46efb353b6c3 Signed-off-by:
Philippe Coval <philippe.coval@osg.samsung.com>
-
- 14 Nov, 2017 3 commits
-
-
Philippe Coval authored
More features could be turned on later Bug: https://jira.iotivity.org/browse/IOT-2241 Change-Id: Ie58e4f4f54ab08e2f0a7f7273e4e9943f9389534 Signed-off-by:
Philippe Coval <philippe.coval@osg.samsung.com> Reviewed-on: https://gerrit.iotivity.org/gerrit/21539Reviewed-by:
Dan Mihai <Daniel.Mihai@microsoft.com> Reviewed-by:
George Nash <george.nash@intel.com> Reviewed-by:
Alex Kelley <alexke@microsoft.com> Tested-by:
jenkins-iotivity <jenkins@iotivity.org> Reviewed-by:
Mats Wichmann <mats@linux.com>
-
Oleksandr Dmytrenko authored
provisioningclient set rowneruuid for all the SVRs Change-Id: I46df6479aeb313955639df32b7e73c52b14691e0 Signed-off-by:
Oleksandr Dmytrenko <o.dmytrenko@samsung.com>
-
Oleksii Beketov authored
Allow to parse all CA certificates when SVR DB contains more than one root CA. Change-Id: Ie82632b459a9a064a90ff14e100e4db9ab60492d Signed-off-by:
Oleksii Beketov <ol.beketov@samsung.com>
-
- 09 Nov, 2017 3 commits
-
-
Mats Wichmann authored
A previous change updated all the scons scripts: https://gerrit.iotivity.org/gerrit/#/c/22525/ This change picks up the semi-external scripts that are called by the build, and thus are run in the scons context and need updating. Print statements are surrounded with parens so they look like function calls. This is an scons3 syntax requirement even if still using Python 2. The old exception format "except FooErr, err" is no longer supported in Python 3; since the Python 3 format "except FooErr as err" has been available since Python 2.6, there is no problem switching these and it makes sense to remove one way things could fail if Py3 is used. A few comparisons which used <> are changed to the preferred != form. Reformatted Builder call without changing it, and added a comment in the forked version to help explain why there are two copies of UnpackAll.py. With these changes, a full build completes successfully using scons3.0. Change-Id: Ia8df28d12c6504d6466dcf793779535d1ad3aa8b Signed-off-by:
Mats Wichmann <mats@linux.com> (cherry picked from commit b34da4aa)
-
Habib Virji authored
Add ttl parameter to RD client APIs. Bug: https://jira.iotivity.org/browse/IOT-1935 Change-Id: Ic189cebebbcf8127bea1d127dd11a116e09743bb Signed-off-by:
Habib Virji <habib.virji@samsung.com> Signed-off-by:
Todd Malsbary <todd.malsbary@intel.com>
-
Nathan Heldt-Sheller authored
Fix for a binary->CBOR marshaling case, where payload is to contain "dos", but not "p". This in in turns causes the next Property to be incorrectly placed inside the "dos" CBOR map (and then skipped over by the CBOR->binary un-marshaling code). Also improved logging. Change-Id: Ib28fc1e30fdaf1e639afa940ee2626ba14e77584 Signed-off-by:
Nathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
-
- 08 Nov, 2017 1 commit
-
-
Ibrahim Esmat authored
Cherry Pick Mats change from master to enable building with SCons 3.0 in 1.3-rel branch. This change and the change in review https://gerrit.iotivity.org/gerrit/#/c/22809 will be needed to merge together. With these 2 changes merged to 1.3-rel, you can successfully build IoTivity with SCons 3.0. Which will also allow you to build the UWP versions of the libraries needed for UWP Apps. Change in master: Prepare for scons3: change prints and others In preparation for scons3, recently released, modify remaining print statements by surrounding them with parens so they look like function calls. That takes care of the scons3 syntax requirement. The remaining instances of the sequence "print FOO; Exit(1)" were changed to "msg = FOO; Exit(msg)" - this helps with the change by not even using the print statement, and by giving the message to the output function, it is sent to the error stream rather than the output stream. Calls to dictionary keys() and values() are now wrapped in list(), on Python 3 these return special objects, not the expected list. That's harmless to Python 2 usage. The old exception format "except FooErr, err" is no longer supported; since the Python 3 format "except FooErr as err" has been available since Python 2.6, there is no problem switching these. Some instances of using the commands module in extlibs changes to use subprocess module. Change is transparent. A couple of instances of filter(lambda ...)) were changes to a python list comprehension, this is considered preferred for Python 3 (change was suggested by a conversion tool) Note on print() change: When running with Python2, the print statement is still used. That has a bit of an impact: print(a) is just prints the argument, but print(a, b, c) is interpreted as printing a tuple (a, b, c), so we could see: >>> print "This", "is", "a", "test" This is a test >>> print("This", "is", "a", "test") ('This', 'is', 'a', 'test') The second is not pretty. You can make Python2 code use the function instead of the statement: >>> from __future__ import print_function >>> print("This", "is", "a", "test") This is a test but that's a pain, so the small number of existing prints which used a comma as argument separators were updated to use addition, so now we're concatenating a string to produce one arg instead of supplying multiple "arguments" that would be misinterpreted as a tuple in print(). It's fine to add the import statement if it's needed. Change-Id: Idac00e1389b79ee65da4a2eb6ef3246551b66843 Signed-off-by:
Mats Wichmann <mats@linux.com> Signed-off-by:
Ibrahim Esmat <iesmat@microsoft.com>
-
- 07 Nov, 2017 1 commit
-
-
Veeraj Khokale authored
According to COAP spec section 4.5, confirmable duplicated requests should not be silently dropped, instead they need to be acknowledged every time. Therefore check if message is confirmable before dropping it. Change-Id: Ie7a49da9f7869fc11f679054fe8dd5c78684eb53 Signed-off-by:
Veeraj Khokale <veeraj.sk@samsung.com>
-
- 06 Nov, 2017 2 commits
-
-
Srikrishna Gurugubelli authored
Introspection resource was not checking for interface filter properly resulting in missing mandatory properties expected on baseline interface query. Signed-off-by:
Srikrishna Gurugubelli <srikguru@microsoft.com> Change-Id: I920d4a1ecc4442e34fc1de8633291de6f341a123 Bug: https://jira.iotivity.org/browse/IOT-2618
-
Senthil Kumar G S authored
If a post request comes with read-only properties, OC_EH_BAD_REQUEST(400) will be sent. Change-Id: I26cd3f8f7c24f8d197a39ac96a27c80018d62f2a Signed-off-by:
Senthil Kumar G S <senthil.gs@samsung.com>
-
- 02 Nov, 2017 3 commits
-
-
Oleksii Beketov authored
Improper callbacks registration removed. Manufacturer certificate related info and ciphers callbacks are already set in StartOwnershipTransfer. Change-Id: Id1cb14cb31e4325d17961737fa87e0224735235a Signed-off-by:
Oleksii Beketov <ol.beketov@samsung.com>
-
Mats Wichmann authored
Provisioning unittest will not link when pointed at connectivity_abstraction_insternal due to dependency of other libs on connectivity_abstraction. Leads to this error: /bin/ld: out/linux/x86_64/debug/libroutingmanager.a(routingmanager.o): undefined reference to symbol 'u_linklist_length' /home/mats/iotivity.work/out/linux/x86_64/debug//libconnectivity_abstraction.so: error adding symbols: DSO missing from command line It works fine to link against connectivity_abstraction so use that instead. Other changes in the SConscript are just cleanup. Change-Id: I47b846111f4bbaee0ce4d38de7d9e8a0ccc3885b Bug: https://jira.iotivity.org/browse/IOT-2864Signed-off-by:
Mats Wichmann <mats@linux.com>
-
Mats Wichmann authored
For gcc starting with 7, gcc -dumpversion returns a single (non dotted) number. This is actually an illegal version to distutils' version.StrictVersion, so use LooseVersion instead, where that is a legal number but the comparison still works fine. For Python 3.x, subprocess.check_output returns a byte string, which needs to be decoded before it can be passed to the version comparator function. Instead of bothering with the decoder, which is hard to get right so it works for both Py2 and Py3 case, call the new subprocess.getoutput() method, falling back to check_output if not available. Change-Id: I29e1f43f8fbde130103099be1972b574a23442cf Bug: https://jira.iotivity.org/browse/IOT-2862Signed-off-by:
Mats Wichmann <mats@linux.com>
-
- 31 Oct, 2017 4 commits
-
-
Dan Mihai authored
Return an error response when a Client tries to post a role with a mistmatched public key. Change-Id: Ie689f862d1534093026979c076239fdf604b91e1 Signed-off-by:
Dan Mihai <Daniel.Mihai@microsoft.com>
-
Dan Mihai authored
Avoid persisting the cert null terminator, to be able to return the original cert for RETRIEVE. Add the null terminator just temporarily, before calling mbedtls_x509_crt_parse(). This patch allows CT1.7.4.5 to make progress past Check_3. This test case still fails later on - to be investigated. Change-Id: Icda1afaad478548682599f97ff46b3017b01588e Signed-off-by:
Dan Mihai <Daniel.Mihai@microsoft.com>
-
Nathan Heldt-Sheller authored
Although the Security Spec is silent on whether DOXS has implicit access (that is, a permanent ACE, or default ACE that can't be modified) to the /crl Resource. CTT interprets that to mean it doesn't have implicit access, even though DOXS can access related configuration Resources (/doxm, /pstat, /acl2, /cred). Rather than fight over it I'm changing because either way works, it's just more effort for OBT with implicit access reduced. Still a reasonable inference (though not normatively supported). Change-Id: I86f8a7f1ed217b7bdeb3cae2ab015fb035cd8940 Signed-off-by:
Nathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
-
Mats Wichmann authored
In recently introduced code, a pair of temporary buffers is used to help convert ascii digits to a number; one is a static allocation but the other is OICMalloc'd, but was not freed. Change-Id: Iab1e8ce48c20aa6332d375c891f6b38ecb6939e7 Bug: https://jira.iotivity.org/browse/IOT-2863Signed-off-by:
Mats Wichmann <mats@linux.com>
-
- 30 Oct, 2017 2 commits
-
-
Abhishek Pandey authored
JIRA IOT-2847: https://jira.iotivity.org/browse/IOT-2847 Updated updateEasySetupResource() to process "rep" property which is mandatory as per batch schema. Change-Id: I0371e68106728d375a390ac395c256ea5e2361c6 Signed-off-by:
Abhishek Pandey <abhi.siso@samsung.com>
-
Philippe Coval authored
The file from "out" dir will be also installed to system include path using scons install (to /usr/include/ on linux) Bug: https://jira.iotivity.org/browse/IOT-2599 Change-Id: Icddfb9354f47fd40ba998fe336b4963be7ade871 Signed-off-by:
Philippe Coval <philippe.coval@osg.samsung.com> Origin: https://gerrit.iotivity.org/gerrit/#/c/21989/
-
- 28 Oct, 2017 2 commits
-
-
Nathan Heldt-Sheller authored
Right now the /doxm handler code to disable the anon cipher suite is not correct, so it's removed in this patch. Instead, the /cred code disables the anon suite after calculating PSK. If there is a request is over secure channel, but requester ID is Nil UUID, then (in current IoTivity at least) it means that this request arrived over DTLS established via anon cipher suite. A successful connection has taken place, and that's an opportunity to disable the anon cipher suite so no other anon connections can be made during OTM. For now, we're just removing the incorrect /doxm code to disable, and leaving the more aggressive disable timing for another release. See [IOT-2858] for more info. Change-Id: I99c2a48abbfc6f3e5aa52385ee5b778c4c80ccfc Signed-off-by:
Nathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
-
akk0rd authored
Fixed false generating dat file, added wrapper functions with rowner parameter Change-Id: Ia8badb9b0b78de5f620f8dbad6f070c1276ebf74 Signed-off-by:
akk0rd <v.riznyk@samsung.com>
-
- 27 Oct, 2017 6 commits
-
-
George Nash authored
Both client and the server used the incorrect encoding for the certificate data. When the server .dat file was updated with the fix from https://gerrit.iotivity.org/gerrit/22535/ I did not update the client .dat file because I had not made any modifications to the client. This then caused the certificates to miss match. If I run json2cbor on both the client and the server *.json input files the error no longer occurs. Bug: https://jira.iotivity.org/browse/IOT-2826 Change-Id: I8d5acc8a49533b7cca7b5c4f46371e495449aa73 Signed-off-by:
George Nash <george.nash@intel.com>
-
George Nash authored
Valgrind was reporting intermitent read errors from the provisiontest. I think the result of the failure was a change made for IOT-2599 the name of the tests db file was changed from ./dbpath to ./dbpath.tmp however the name of the file was used in more than one test. See: https://gerrit.iotivity.org/gerrit/#/c/22057/ Bug: https://jira.iotivity.org/browse/IOT-2848 Bug: https://jira.iotivity.org/browse/IOT-2599 Change-Id: Id72a07b51aee10abe34a428239ca74dfbf7a2641 Signed-off-by:
George Nash <george.nash@intel.com>
-
Todd Malsbary authored
Bug: https://jira.iotivity.org/browse/IOT-2684 Change-Id: I183ad1a588f3646bd0dc3b370c16cf359552f3eb Signed-off-by:
Todd Malsbary <todd.malsbary@intel.com>
-
Abhishek Pandey authored
JIRA IOT-2845: https://jira.iotivity.org/browse/IOT-2845 This seems to be side effect of JIRA [IOT-2539]. Build is breaking on some linux platforms (i.e. i686). Most compilation errors are related to printf format specifiers. Probably this wasn't caught by jenkins when merging patch for IOT-2845 due to its system configuration matches expected size for all data types. Fixed the error by using portable format specifiers while logging. %PRId - for int64_t %PRIu - for unit64_t %PRIuPTR - for size_t (unsigned) Change-Id: I30a21cacdddc84776392100ee783ccbe7e1eae0d Signed-off-by:
Abhishek Pandey <abhi.siso@samsung.com>
-
Jay Sharma authored
1. Indentation fixes. 2. Uninitialized variable fixes Bug: https://jira.iotivity.org/browse/IOT-2810 Change-Id: Ibccf1bc11e590cf1b282e77cac3a9901ccf29fa2 Signed-off-by:
Jay Sharma <jay.sharma@samsung.com>
-
jake authored
- Be used OICFree without NULL checking. [Philippe Coval] Conflicts: service/notification/src/provider/NSProviderSubscription.c Change-Id: I1ce65d0e41a3b9f276a2b517d7b3d1c06faa92e6 Signed-off-by:
jake <jaehong2.lee@samsung.com> Reviewed-on: https://gerrit.iotivity.org/gerrit/18239Reviewed-by:
JungYong KIM <jyong2.kim@samsung.com> Tested-by:
jenkins-iotivity <jenkins@iotivity.org> Reviewed-by:
Phil Coval <philippe.coval@osg.samsung.com> Reviewed-by:
Uze Choi <uzchoi@samsung.com> (cherry picked from commit acbf9ffd)
-
- 26 Oct, 2017 2 commits
-
-
Dan Mihai authored
mbedtls_pk_parse_key was not able to parse the key converted to DER by GetDerKey(). It encountered in the DER an unexpected key format version. However, mbedtls_pk_parse_key is able to parse correctly the original PEM format of the same key. This patch allows CT1.7.4.5 to establish a connection to an IoTivity server. This test case still fails later on - to be investigated. Change-Id: I933ea9d3b761ed159faa2c4f371890e477caf23f Signed-off-by:
Dan Mihai <Daniel.Mihai@microsoft.com>
-
Nathan Heldt-Sheller authored
These functions were applied at incorrect times (e.g. if a normal Update was rejected due to read-only properties during OTM, the entire system would "restore" to a wrong state). They were also wrong, in that they restored some values, left others unchanged, and set others to wrong values (e.g. presumed JustWorks OTM). Also, the duplicate message logic was not being used to any consistent effect and causing warnings. It's also completely optional and so was removed. Change-Id: I23d23f946fbafe02cdc2d2ac6ac46abcedd1f149 Signed-off-by:
Nathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
-
- 25 Oct, 2017 3 commits
-
-
George Nash authored
Documented all the functions referencing the native code. Note the OcProvisioning setPinType method had a return value int. The was returning the return value of the native call that was the status. Due to the way the code was writen the only value that could be returned was when things worked as expected. All other values were thrown so the return value was un-needed. The function was changed to have a return type of void. Bug:https://jira.iotivity.org/browse/IOT-2838 Change-Id: I3b5955a336661574dde9f70c87b6ead3dcd5ea7b Signed-off-by:
George Nash <george.nash@intel.com>
-
George Nash authored
The coding standard states: Code must compile with no warnings. Without flags forcing warnings off. see: https://wiki.iotivity.org/iotivity_c_coding_standards Its possible that using an untested version of gcc could result in build warings that are not yet fixed. For this reason the build option ERROR_ON_WARN was added to make it possible to turn off the -Werror flag. This should only be used locally an not changed on the CI build. Due to some bugs in older version of gcc some warnings are forced off when using an older version of gcc. This change will force code to follow the coding standard of building with no warnings. The coapHttpParser code produces a build warning that currently is not solved. When building the coap_http_proxy library the -Werror build flag is removed. Don't use the -Werror build option for extlib yaml code. Don't use the -Werror build option for coap library Change-Id: Ifcc25ed7e5b8637ac4383a7bfa51ace105ed9458 Signed-off-by:
George Nash <george.nash@intel.com>
-
Nathan Heldt-Sheller authored
See JIRA IOT-2830 for more information. Change-Id: If043f6705ccdede4630b469c13e1933a2b53af16 Signed-off-by:
Nathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
-
- 24 Oct, 2017 3 commits
-
-
George Nash authored
Bug: https://jira.iotivity.org/browse/IOT-2455 Change-Id: I1415ec047ebc8ce4f2679b8789a104c627ec2db4 Signed-off-by:
George Nash <george.nash@intel.com>
-
Rami Alshafi authored
The default arch for the raspberry pi board is either armv6l or armv7l depending on board hardware version. Neither of them are included in the valid values for the TARGET_ARCH build option. The current workaround is to pass TARGET_ARCH=arm to the build command. This change will enable the default arch. Change-Id: I7f07734f5e06d79d13275254fb01f924227e229a Signed-off-by:
Rami Alshafi <ralshafi@vprime.com>
-
Oleh Vasyliev authored
Change-Id: Ie7b0a00963b22ee1189918ed67ed64ae05f500cf Signed-off-by:
Oleh Vasyliev <o.vasyliev@samsung.com>
-