1. 20 May, 2019 1 commit
  2. 17 May, 2019 1 commit
  3. 15 May, 2019 1 commit
  4. 09 May, 2019 1 commit
  5. 25 Apr, 2019 1 commit
  6. 23 Apr, 2019 1 commit
  7. 22 Apr, 2019 2 commits
  8. 16 Apr, 2019 3 commits
  9. 15 Apr, 2019 1 commit
  10. 10 Apr, 2019 2 commits
  11. 04 Apr, 2019 1 commit
  12. 03 Apr, 2019 1 commit
  13. 21 Mar, 2019 1 commit
  14. 19 Mar, 2019 2 commits
  15. 13 Mar, 2019 1 commit
    • Oleksandr Dmytrenko's avatar
      credresource fix · 2d7a3527
      Oleksandr Dmytrenko authored
      1) pointer check in CheckSubjectOfCertificate
      2) check pointer len before free in FreeCred
      3) poniter check & cross init in CmpCredId
      4) double call fix in DeInitCredResource
      5) new CopyCred
      6) return buffer convertion in case calloc
      7) CheckSubjectOfCertificate: label 'exit' defined but not used
      
      Change-Id: Ic6b5cfb948505b079f37a6c0b2f2047b25ab5d89
      Signed-off-by: default avatarOleksandr Dmytrenko <o.dmytrenko@samsung.com>
      2d7a3527
  16. 11 Mar, 2019 8 commits
  17. 04 Mar, 2019 1 commit
  18. 27 Feb, 2019 1 commit
  19. 26 Feb, 2019 2 commits
  20. 21 Feb, 2019 1 commit
  21. 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
  22. 12 Feb, 2019 1 commit
  23. 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
  24. 08 Feb, 2019 2 commits
  25. 07 Feb, 2019 1 commit