> Have you ever tested IoTivity-Constrained's simpleserver on > target board or QEMU ?
As I mentioned earlier, I?ve tested secure communications between IoTivity?s simpleclient and IoTivity-Constrained?s simpleserver with both running on Linux. If IoTivity's OBT is working now, this should be easy for you to test yourself. > Do you have any idea about "creds" file and why it's included > for linux platform? Please look in port/oc_storage.h and port/linux/storage.c. The header implements a persistent storage interface to a key-value store. oc_storage_config() is meant to do any required initialization and takes a parameter, the meaning of which is up to the implementation. For the Linux port, port/linux/storage.c will show you that oc_storage_config() is implemented to take a directory as parameter, where oc_storage_read/oc_storage_write operate on files within that directory. The samples specify some ?./creds? to point to a subdirectory of the current path named ?creds". That is where secure resources will be persisted. Feel free to change it, including the storage implementation, to suit your needs. The Zephyr port has a different storage implementation that uses Zephyr?s flash APIs to persist and retrieve secure resources from flash. So, apps for Zephyr will pass in a different kind of parameter to oc_storage_config(). - Kishen Maloor Intel Open Source Technology Center From: ??? <[email protected]> on behalf of ??? <hj210.choi at samsung.com> Reply-To: "hj210.choi at samsung.com" <hj210.choi at samsung.com> Date: Monday, February 13, 2017 at 3:47 PM To: Kishen Maloor <kishen.maloor at intel.com>, ??? <hj210.choi at samsung.com>, "iotivity-dev at lists.iotivity.org" <iotivity-dev at lists.iotivity.org> Subject: RE: Re: [dev] Question about IoTivity-constrained security. >I have tested on Linux between IoTivity?s simpleclient and >IoTivity-Constrained?s >simpleserver, and I used to use the OBT in >resource/csdk/security/provisioning/sample/provisioningclient. Have you ever tested IoTivity-Constrained's simpleserver on target board or QEMU ? I reviewed the code of simpleserver in IoTivity-Constrained. I found a code which is related with security(?) and it's included when it's built for linux platform. --------------------------------------- //apps/simpleserver.c -- Line 202 #ifdef OC_SECURITY oc_storage_config("./creds"); #endif --------------------------------------- Do you have any idea about "creds" file and why it's included for linux platform? Many Thanks, Hyungjun. --------- Original Message --------- Sender : Maloor, Kishen <kishen.maloor at intel.com> Date : 2017-02-14 01:26 (GMT+9) Title : Re: [dev] Question about IoTivity-constrained security. > When you were test it, which platform (e.g.: linux, qemu_x86 and ETC.) >and > sample app(e.g.: /apps/simpleserver.cpp) in iotivity-constrained did you >use? I have tested on Linux between IoTivity?s simpleclient and IoTivity-Constrained?s simpleserver, and I used to use the OBT in resource/csdk/security/provisioning/sample/provisioningclient. - Kishen Maloor Intel Open Source Technology Center From: ??? <[email protected]> on behalf of ??? <hj210.choi at samsung.com> Reply-To: "hj210.choi at samsung.com" <hj210.choi at samsung.com> Date: Sunday, February 12, 2017 at 11:26 PM To: Kishen Maloor <kishen.maloor at intel.com>, ??? <hj210.choi at samsung.com>, "iotivity-dev at lists.iotivity.org" <iotivity-dev at lists.iotivity.org> Subject: RE: Re: [dev] Question about IoTivity-constrained security. Hello Kishen. First, I appreacite your variable information. Sorry, one more question. When you were test it, which platform (e.g.: linux, qemu_x86 and ETC.) and sample app(e.g.: /apps/simpleserver.cpp) in iotivity-constrained did you use? Kind Regards, Hyungjun. --------- Original Message --------- Sender : Maloor, Kishen <kishen.maloor at intel.com> Date : 2017-02-10 11:17 (GMT+9) Title : Re: [dev] Question about IoTivity-constrained security. > Is the security implementation of iotivity-constrained compatible with >iotivity? Yes. > I mean, have you ever tested secure data transfer between a server of >iotivity- > constrained and a client of iotivity? Yes. IoTivity-Constrained supports the ?Just works? OXM, and 128-bit pre-shared key. You?d have to use IoTivity?s provisioning tool for on-boarding and provisioning. It used to work perfectly until a few weeks ago when I last checked. At that time it seemed like the provisioning tool was broken. The OBT would crash, or would fail to provision credentials. I don?t know if that?s been fixed. But, IoTivity-Constrained does continue to successfully go through those steps with the CTT. Thanks, -Kishen. - Kishen Maloor Intel Open Source Technology Center From: <[email protected]> on behalf of ??? <hj210.choi at samsung.com> Reply-To: "hj210.choi at samsung.com" <hj210.choi at samsung.com> Date: Thursday, February 9, 2017 at 5:09 PM To: "iotivity-dev at lists.iotivity.org" <iotivity-dev at lists.iotivity.org> Subject: [dev] Question about IoTivity-constrained security. Hello? I have a few question about the security implementation of iotivity-constrained. Is the security implementation of iotivity-constrained compatible with iotivity? I mean, have you ever tested secure data transfer between a server of iotivity-constrained and a client of iotivity? Kind Regards, Hyungjun. -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00001.gif Type: image/gif Size: 13402 bytes Desc: ATT00001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170214/0f284b1e/attachment.gif>
