1. 11 Mar, 2019 8 commits
  2. 04 Mar, 2019 1 commit
  3. 27 Feb, 2019 1 commit
  4. 26 Feb, 2019 2 commits
  5. 21 Feb, 2019 1 commit
  6. 19 Feb, 2019 1 commit
    • Mats Wichmann's avatar
      java unsecured build set SECURED=0 · ce4c6d0d
      Mats Wichmann authored
      The current autobuild (CI) for java (linux_unsecured_with_java target)
      does not set SECURED=0, probably a holdover from when the default was
      an unsecured build. Add SECURED=0 to make sure the Jenkins builds
      are testing this combination.
      
      Change-Id: I2db1851c2f9b78a7ffba4474a72c74e5766699d8
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      ce4c6d0d
  7. 12 Feb, 2019 1 commit
  8. 11 Feb, 2019 2 commits
    • Abhishek Pandey's avatar
      [Easy Setup] Reject UPDATE on not allowed property · 0c66b6f8
      Abhishek Pandey authored
      [IOT-3231] https://jira.iotivity.org/browse/IOT-3231
      Easy Setup Resource does not reject an UPDATE request to add a new Link
      
      Currently only criteria to reject POST on EasySetup Resource
      (/EasySetupResURI) is to check if properties are read-only. However,
      the POST request may contain additional properties "href", "rep"
      representing a link to be added in collection or any other unsupported
      properties. Even though these properties are not updated, success
      response is sent to client which is not appropriate and is flagged as
      CTT failure.
      
      This patch changes the validation logic on /EasySetupResURI for POST
      on baseline interface to allow the POST only if payload contains
      the writable property "cn". Update to any other property is rejected.
      
      Change-Id: I33f6e7eda33481fa2137341f93b607a837ff5a87
      Signed-off-by: default avatarAbhishek Pandey <abhi.siso@samsung.com>
      0c66b6f8
    • Abhishek Pandey's avatar
      [Easy Setup] Check required properties for UPDATE · 666d1d5c
      Abhishek Pandey authored
      [IOT-3252]
      https://jira.iotivity.org/browse/IOT-3252
      
      Per the WiFiConf Schema, for an UPDATE request:
       "required":["tnn", "wat", "wet"]
      
      This means that all three of these Properties must be in every
      UPDATE request. If they are not there, the Device is supposed
      to reject the request with a 4.xx error. However, IoTivity
      responds with a 2.04 Changed response instead currently.
      
      This patch fixes above issue by checking the POST request
      for required properties (tnn, wat, wet). If any of these
      are not included in POST request, it will be rejected.
      
      Change-Id: I00f02c93cd273a02706c85c5d236584d45d6ca77
      Signed-off-by: default avatarAbhishek Pandey <abhi.siso@samsung.com>
      666d1d5c
  9. 08 Feb, 2019 2 commits
  10. 07 Feb, 2019 2 commits
  11. 06 Feb, 2019 2 commits
  12. 01 Feb, 2019 3 commits
  13. 30 Jan, 2019 1 commit
    • Mats Wichmann's avatar
      Fix OCResourceResponseTest warning · 070c003c
      Mats Wichmann authored
      gcc8.1 is fussier about getting strncpy right, as it gripes on this line:
      
          strncpy(request.query, query, sizeof(query));
      
      It issues this warning:
      
      resource/unittests/OCResourceResponseTest.cpp:83:39: warning: argument to 'sizeof' in 'char* strncpy(char*, const char*, size_t)' call is the same expression as the source; did you mean to use the size of the destination? [-Wsizeof-pointer-memaccess]
      
      Stack code uses OICStrcpy for safer string copying, but without
      fiddling further with dependencies, that function is not available
      in this scope, so kept the strncpy but changed the the length
      to be based on the destination.
      
      Qualify the two strings with const while we're at it.
      
      Change-Id: I7ed0010a6daeda6f6db4337b9a0babc5e0dce968
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      070c003c
  14. 29 Jan, 2019 1 commit
    • Aleksey's avatar
      Subjectuuid wildcard fix · 0aeba4ff
      Aleksey authored
      subjectuuid field of credential entry is changing in case of it has
      '*' or zeroid value and credential type is 'SIGNED_ASYMMETRIC_KEY'.
      
      For the trustca credusage this cause a verification error.
      
      Change-Id: I889d9e982b5be5fea1d872eebb83734288cde3e6
      Signed-off-by: Aleksey's avatarAleksey Volkov <a.volkov@samsung.com>
      0aeba4ff
  15. 24 Jan, 2019 3 commits
    • Mats Wichmann's avatar
      Show how to make examples non-default · ac8502f0
      Mats Wichmann authored
      A scheme is introduced which allows separating targets indended to
      be built by default from ones not intended to be built by default.
      One example is converted to show how it works.
      
      Since this makes use of added methods (extending scons' own API),
      took the opportunity to properly document these, and added a
      documentation file in a new doc subdirectory to make it easier
      for developers to find out about these methods.
      
      Also added a debug scheme, which makes it more clear where to
      put tracing statements in between the two passes of scons -
      the script is invoked at the very end of the scan pass, before
      the build pass begins but when everything should be defined.
      
      Change-Id: I0a636fa34c18ace23720f22bfdd8511afa611ddb
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      ac8502f0
    • Oleksandr Dmytrenko's avatar
      some errors fix · 2cd19c54
      Oleksandr Dmytrenko authored
      crosses initialization and invalid conversion errors fix
      
      Change-Id: I55cce4178f14eb1a7e5b45704650696d18b9ddec
      Signed-off-by: default avatarOleksandr Dmytrenko <o.dmytrenko@samsung.com>
      2cd19c54
    • Oleksandr Dmytrenko's avatar
      crach fix in GetOwnCert · aaa819da
      Oleksandr Dmytrenko authored
      crach fix in GetOwnCert, in debug mode in case null chain
      
      Change-Id: I2c394a1953b8b20015c53607325b5181750bf564
      Signed-off-by: default avatarOleksandr Dmytrenko <o.dmytrenko@samsung.com>
      aaa819da
  16. 21 Jan, 2019 1 commit
  17. 16 Jan, 2019 2 commits
  18. 15 Jan, 2019 1 commit
    • Herve Jourdain's avatar
      Fixed Android OcPlatform.Shutdown() does not work. · 3afda8f4
      Herve Jourdain authored
      Android OcPlatform.Shutdown() API does not work properly, because in
      the case of Android, start() is called twice: once by the Android
      Configure API, which is normal and needed, and once by the constructor
      for OcPlatform_impl()!
      This last one is due to the fact that useLegacyCleanup is still set
      to true in the PlatformConfig used by Android, which is one of the
      2 non-deprecated ones.
      Comments say that the flag is set to false by default, unless a
      legacy constructor is used. But this is obviously not a legacy
      constructor, and the flag was erroneously set to true...
      With this fix, Android OcPlatform.Shutdown() works as expected.
      
      Change-Id: I3db4c37ff17c9f16ea927093c8aa2806e1cabb90
      Signed-off-by: default avatarHerve Jourdain <herve.jourdain@beechwoods.com>
      3afda8f4
  19. 31 Dec, 2018 1 commit
  20. 04 Dec, 2018 1 commit
  21. 03 Dec, 2018 1 commit
  22. 27 Nov, 2018 1 commit
  23. 23 Nov, 2018 1 commit