I'm generally not able to do much past getting the samples to run. The code refers to include files that are not installed by `cons install`, and in fact are part of an "internals" directory that sounds like something that should only apply to the library implementation, not client code. Also, only PIN and JUSTWORKS are actually implemented. I started down a path of trying to get it working, but it will actually require quite a bit of refactoring, which I don't feel qualified to do at this point.
On Sun, Aug 14, 2016 at 7:01 PM ??? <jihun.ha at samsung.com> wrote: > Hi. Gabriel, > > 1) Please use the latest code in master branch for your testing. Some old > codes would fail an unowned discovery even if there is an unowned device in > your network , in fact. I heard that those faulty behaviors were fixed with > recent patches in a master branch. > > 2) The most important element for the testing you've describe is a .dat > file in both sides, provisioning manager and server. At the first stage of > your test, you SHOULD use a new dat file not used ever. The dat files are > stored in <iotivity>/resource/csdk/security/provisioning/sample and you can > see several dat files like oic_svr_db_server_justworks.dat. > > Note that those dat files would be installed in output folder, e.g. > <iotivity>/out/linux/x86_64/release/resource/csdk/security/provisioning/sample > while scons building. However, when you change the dat file while > performing ownership transfer, you have to remove the dat file and copy an > unused dat file for a subsequent test. (You just remove the file in the > output folder and do scons build again, then the file would be copied in > the output folder) > > Anyway, I have test it with commit ID > 42c1137be9c152c83f808e7bd8ab51aa7e26c920 > and can see that it works well. > > Thank you. > BR.Jihun Ha > > ---------* Original Message* --------- > *Sender* : Schulhof, Gabriel <gabriel.schulhof at intel.com> > *Date* : 2016-08-14 23:49 (GMT+9) > *Title* : [dev] Provisioning samples > > Hi! > > I'm trying to run the provisioning samples. > > Having compiled with > > scons SECURED=1 samples > > I run > > out/linux/x86_64/release/resource/csdk/security/provisioning/sample/sampleserver_justworks > > in one terminal, and > > out/linux/x86_64/release/resource/csdk/security/provisioning/sample/provisioningclient > > in another terminal. > > I request that it discover all unowned devices, but it lists none. > Discovery works OK otherwise. > > So, how do I start a server that is unowned, so that it may be listed > as a result of a call to OCDiscoverUnownedDevices(), and so I may > subsequently transfer ownership of it to the client which calls > OCDiscoverUnownedDevices()? > > My ultimate goal is to run the iotivity-node test suite in secure > mode. The test suite consists of client/server pairs, each performing > a basic operation like discovery, CRUD request, presence, and > observation. > > In secured mode, I would like to add a preamble where the client > assumes ownership of the server, thereby gaining (I assume) full > access to the server's resources, so that it may perform the requests > it is testing without receiving any OC_STACK_UNAUTHORIZED_REQ > responses. > > Please let me know if this is a sensible approach, if I'm making any > mistaken assumptions about the provisioning, or if there are any > details regarding this assumption of ownership of the server by the > client that I'm missing! > > TIA for your help and advice, > > > > Gabriel > _______________________________________________ > iotivity-dev mailing listiotivity-dev at > lists.iotivity.orghttps://lists.iotivity.org/mailman/listinfo/iotivity-dev > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160815/40ea8d22/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 201602111742151_N3WZA6X7.png Type: image/png Size: 33527 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160815/40ea8d22/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: 201602111742151_N3WZA6X7.png Type: image/png Size: 33527 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160815/40ea8d22/attachment-0001.png>
