1. 26 Oct, 2017 2 commits
    • Dan Mihai's avatar
      CT1.7.4.5: Avoid DER key parse error · 150b2de8
      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: default avatarDan Mihai <Daniel.Mihai@microsoft.com>
      150b2de8
    • Nathan Heldt-Sheller's avatar
      [IOT-2843] remove SVR restore behavior · c4025294
      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's avatarNathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
      c4025294
  2. 25 Oct, 2017 3 commits
    • George Nash's avatar
      IOT-2838 Fix javadoc warnings · 5cfded4d
      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's avatarGeorge Nash <george.nash@intel.com>
      5cfded4d
    • George Nash's avatar
      IOT-2539 Enable the -Werror build flag · 418ccc66
      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's avatarGeorge Nash <george.nash@intel.com>
      418ccc66
    • Nathan Heldt-Sheller's avatar
      [IOT-2830] add PSK callback logging · b1659ae0
      Nathan Heldt-Sheller authored
      See JIRA IOT-2830 for more information.
      
      Change-Id: If043f6705ccdede4630b469c13e1933a2b53af16
      Signed-off-by: Nathan Heldt-Sheller's avatarNathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
      b1659ae0
  3. 24 Oct, 2017 3 commits
  4. 23 Oct, 2017 4 commits
  5. 21 Oct, 2017 1 commit
  6. 20 Oct, 2017 7 commits
  7. 19 Oct, 2017 19 commits
  8. 18 Oct, 2017 1 commit