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 2 commits
    • Inho Oh's avatar
      examples/OCFSecure: Add ARTIK board · 912a3a47
      Inho Oh authored
      This patch add the ARTIK board to the list of supported devices.
      The blue LED on board (GPIO38) is used for switch resource in the server
      program. And the GPIO is controlled by "mraa" library which already used
      in the server program.
      
      The "mraa" library is not support the ARTIK board. So to use the raw GPIO
      pin number, "raw=true" option is added.
      
      Change-Id: I2004bc473c64189f3cc1010ae76c4cfe757b33f5
      Signed-off-by: default avatarInho Oh <webispy@gmail.com>
      912a3a47
    • 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. 14 Aug, 2018 1 commit
  6. 23 Jul, 2018 1 commit
  7. 04 Jul, 2018 1 commit
  8. 12 Apr, 2018 1 commit
    • Rami Alshafi's avatar
      Added OCF secure apps in examples/OCFSecure · 3974e003
      Rami Alshafi authored
      Added OCF secure server sample application in C++.
      Added OCF secure client sample application in C.
      Added supporting json and dat files putting the applications in RFNOP state.
      Added README file descriping how to use the sample applications.
      Added utilities file containing utility functions used by the server
      and client applications.
      Added SConscript to build the secure samples and modified the SConscipt in
      the root directory to include the new SConscript.
      
      Change-Id: I9e1cd4647b55b3e95d1455d7939f13bf3451fd1b
      Signed-off-by: default avatarRami Alshafi <ralshafi@vprime.com>
      3974e003
  9. 23 Mar, 2018 1 commit
  10. 09 Mar, 2018 1 commit
  11. 02 Mar, 2018 1 commit
  12. 14 Feb, 2018 1 commit
  13. 12 Feb, 2018 1 commit
  14. 09 Feb, 2018 2 commits
  15. 08 Feb, 2018 1 commit
  16. 07 Feb, 2018 1 commit
    • Mats Wichmann's avatar
      Drop use of two deprecated defines · 0636dca4
      Mats Wichmann authored
      Per the header ocstackconfig.h, two defines are
      deprecated with replacement. Change the single file
      which still uses the old names.  The header comment:
      
      /**
       * Maximum length of the Manufacturer name supported by the server
       * for manufacturer name.
       * @deprecated use MAX_PLATFORM_NAME_LENGTH instead.
       */
      
      /**
       * Maximum length of the URL to the Manufacturer details supported by
       * the server.
       * @deprecated use MAX_PLATFORM_URL_LENGTH instead.
       */
      
      Change-Id: I40ae198120de175750447996ebd43bed9ec25fa8
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      0636dca4
  17. 06 Feb, 2018 2 commits
  18. 02 Feb, 2018 1 commit
  19. 01 Feb, 2018 2 commits
  20. 29 Jan, 2018 4 commits
  21. 25 Jan, 2018 2 commits
    • Mats Wichmann's avatar
      Build gtest output paths correctly · a4e14b93
      Mats Wichmann authored
      Currently, when the run_tests function is called twice from the
      the same scons script (that is, the script has more than one unit
      test binary to register), the GTEST_OUTPUT environment variable
      becomes malformed.  This is because the string to add is added
      to a list instead of just being appended as a string.  The result
      is that while all the test output binaries are expected to go to
      BUILD_DIR/test_out, in these cases they go deep down underneath
      that directory.  Here are the unexpected paths in an unmodified
      testing run:
      
      out/linux/x86_64/debug/test_out/:xml:
      out/linux/x86_64/debug/test_out/:xml:/home
      out/linux/x86_64/debug/test_out/:xml:/home/mats
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux/x86_64
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux/x86_64/debug
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux/x86_64/debug/test_out
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux/x86_64/debug/test_out/unittest.xml
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux/x86_64/debug/test_out/stacktests.xml
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux/x86_64/debug/test_out/cbortests.xml
      out/linux/x86_64/debug/test_out/:xml:/home/mats/iotivity.work/out/linux/x86_64/debug/test_out/provisiontests.xml
      
      The :xml: is intended as a tag used to signal gtest, it is never
      supposed to be part of the real filesystem path.
      
      Note fix was already proposed as part of
      https://gerrit.iotivity.org/gerrit/#/c/22275/ but since it's a
      distinct error with a very simple fix, wanted to get it pushed
      through by itself while that one is under consideration.
      
      Change-Id: I05c57d54034686a7c77c783eab758e7f501e86ea
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      (cherry picked from commit 0d010e4b)
      a4e14b93
    • Sushil Yadav's avatar
      Remove unused TIZEN package capi-network-wifi. · de6c5089
      Sushil Yadav authored
      The following change has been merged in the master.
      https://gerrit.iotivity.org/gerrit/20689
      
      Pushing the change one the 1.3-rel branch as suggested by Phil.
      
      Change-Id: I8d4b8b97d93521174273e08aa9202e6008e6abfe
      Signed-off-by: default avatarSushil Yadav <sushil.ky@samsung.com>
      Reviewed-by: default avatarJooseok Park <jooseok.park@samsung.com>
      Reviewed-by: default avatarPhil Coval <philippe.coval@osg.samsung.com>
      Reviewed-by: default avatarUze Choi <uzchoi@samsung.com>
      Reviewed-by: default avatarAshok Babu Channa <ashok.channa@samsung.com>
      Origin: https://gerrit.iotivity.org/gerrit/#/c/23347/
      de6c5089
  22. 24 Jan, 2018 1 commit
  23. 19 Jan, 2018 2 commits
  24. 18 Jan, 2018 1 commit
  25. 17 Jan, 2018 1 commit
  26. 15 Jan, 2018 1 commit
  27. 12 Jan, 2018 1 commit
  28. 11 Jan, 2018 2 commits