1. 13 Mar, 2019 1 commit
    • Oleksii Beketov's avatar
      [IOT-3276] Multiple CAs allowed · 3b14423a
      Oleksii Beketov authored
      This patch unites reverted #22987 and CTT fix 23279.
      
      PEM/DER casting removed,  allowing mbedtls to manage
      certificate conversion by itself. Credresource loads
      certificates that could be either PEM or DER encoded
      to a linked list instead of pushing them to a buffer.
      
      Change-Id: I6dd0d957721d59feaf70f3dd421bf65d7c02ef1d
      Signed-off-by: default avatarOleksii Beketov <ol.beketov@samsung.com>
      3b14423a
  2. 11 Oct, 2018 1 commit
  3. 25 Sep, 2018 3 commits
  4. 20 Sep, 2018 1 commit
    • Oleksandr Andrieiev's avatar
      [CR2390] Identity spoofing/privelege escalation · 8e30527a
      Oleksandr Andrieiev authored
      For secure connections that use certificates the SubjectUUID
      is retrieved from leaf certificate's CN. However, there is
      no binding mechanism between Root CA and Device Id that it
      can generate certificates for. Root CAs can issue certificates
      with arbitrary UUIDs, which can be used to impersonate another
      Device.
      
      The fix adds callback to the certificate chain validation
      function. This callback collects single-linked list of all
      UUIDs associated with the certificate in cred entries.
      When leaf certificate is reached, UUID of Device is retrieved
      and matched against static list. If no matching UUID is
      found, connection should be rejected.
      
      Bug: https://jira.iotivity.org/browse/IOT-3087
      Change-Id: Ic766fa2256d548c99ed4a5dd76f6f3c53b5250a9
      Signed-off-by: Oleksandr Andrieiev's avatarOleksandr Andrieiev <o.andrieiev@samsung.com>
      8e30527a
  5. 23 Jul, 2018 1 commit
  6. 23 Mar, 2018 1 commit
  7. 09 Mar, 2018 1 commit
  8. 02 Mar, 2018 1 commit
  9. 09 Feb, 2018 2 commits
  10. 06 Feb, 2018 2 commits
  11. 01 Feb, 2018 1 commit
    • George Nash's avatar
      Clean build warnings · ac153614
      George Nash authored
      This cleans new build warnings discovered when building
      iotivity with GCC 7.2.1
      
      -Werror=format-truncation
      Fixed in json2cbor that was a result of incorrect buffer size in snprintf
      
      -Werror=implicit-fallthrough
      With the addition of the [[fallthrough]] keyword in C++17 GCC now detects
      fallthrough locations. The fallthrough error can be hidden by adding
      the comment "fall through" to the case that is falling though.
      
      -Werror=pragmas and -Werror=attributes
      are from the external tinyCbor code. We Ignore build warnings from extern
      libraries. We may fix the warnings by working witht he external project
      but it should not block any work in IoTivity.
      
      Change-Id: I86c9fb42b987858c66698fe48e4c2a405769b004
      Signed-off-by: George Nash's avatarGeorge Nash <george.nash@intel.com>
      ac153614
  12. 29 Jan, 2018 1 commit
  13. 25 Jan, 2018 1 commit
  14. 24 Jan, 2018 1 commit
  15. 08 Jan, 2018 1 commit
  16. 02 Jan, 2018 6 commits
  17. 13 Dec, 2017 1 commit
    • Philippe Coval's avatar
      resource: Fix occlientbasicops to support coaps · 0f2ae826
      Philippe Coval authored
      The fix is to do querry only on resource's address (to use CoAPs channel)
      
      Observed issue was:
      
       ./ocserverbasicops
      
        ./occlientbasicops -u 0 -c 0 -d 1 -p 0 -t 2
        (...)
      
        INFO: occlientbasicops: Callback Context for GET query recvd successfully
        INFO: occlientbasicops: StackResult: OC_STACK_UNAUTHORIZED_REQ
        INFO: occlientbasicops: SEQUENCE NUMBER: 16777216
        INFO: PayloadLog: NULL Payload
        INFO: occlientbasicops: =============> Get Response
      
      I fixed it to:
      
        INFO: occlientbasicops: StackResult: OC_STACK_OK (...)
        INFO: PayloadLog: Payload Type: Representation (...)
        INFO: PayloadLog:     URI:/a/led (...)
        INFO: PayloadLog:             state(bool):false (...)
      
      Extra note, it look like the parse function is never returning false.
      
      Change-Id: Id3e48c8a04453e87a09e7636ead9a9f64c499d44
      Bug: https://jira.iotivity.org/browse/IOT-2390
      Origin: https://gerrit.iotivity.org/gerrit/#/c/23637/Signed-off-by: default avatarPhilippe Coval <philippe.coval@osg.samsung.com>
      (cherry picked from commit f6394a48)
      0f2ae826
  18. 11 Dec, 2017 1 commit
  19. 08 Dec, 2017 3 commits
  20. 30 Nov, 2017 1 commit
  21. 29 Nov, 2017 1 commit
  22. 22 Nov, 2017 2 commits
  23. 15 Nov, 2017 1 commit
  24. 14 Nov, 2017 2 commits
  25. 09 Nov, 2017 2 commits
  26. 08 Nov, 2017 1 commit
    • Ibrahim Esmat's avatar
      Cherry Pick change to enable building with SCons3 · e5418f06
      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: default avatarMats Wichmann <mats@linux.com>
      Signed-off-by: default avatarIbrahim Esmat <iesmat@microsoft.com>
      e5418f06