On 08/07/2017 08:23 PM, 김재환 wrote:
Sorry, your mail has come through completely mangled here, and see what it
looks like in the archive here:
https://lists.iotivity.org/pipermail/iotivity-dev/2017-August/008185.html
(please don't send styled emails to the list, the result breaks for some people
___
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
Hi Nathan,
Sorry for the misunderstanding. In this case I am talking about who actually
handles changing the DOS state. I do not see any place in ProvisioningClient
that changes DOS or calls SetDos directly. Instead it looks like the SRP* APIs
in secureresourceprovider.c are responsible for han
Great thanks
Jason Sun
发件人: Nash, George [mailto:george.n...@intel.com]
发送时间: 2017年8月8日 5:55
收件人: sunlf; 'iotivity-dev'
主题: RE: [dev] One question about using lib
As a general rule the files used for the lib are *.a or *.so files for linux or
*.lib or *.dll for windows. I have only se
Hello all,
The https://wiki.iotivity.org/iotivity_c_coding_standards says:
Code must compile with no warnings at the standard warning level without flags
forcing any warnings off. Exceptions are allowed only for warnings that occur
within any external SDKs used or warnings that cannot be elimin
Hi Alex,
I'm not sure I understand your question... the DOS-aware versions should be
used with OCF 1.0 Servers, as the Client (OBT) must change the /pstat.dos.s to
a state that allows modification of the SVR Properties being Updated. The
non-DOS aware versions would be for OIC 1.1 Servers.
If
Thanks for taking a look Nathan. I have updated the ticket with the information
from this thread and tagged Randeep.
I am a little confused on why changing DOS would be done in ProvisioningClient
though. For PSK the APIs call into SRPProvisionCredentialsDos which sets DOS
and handles SYMMETRIC_
Alex thank you for looking into this further. Yes, the provisioningclient
should be changing the /pstat.dos.s to RFPRO (or optionally SRESET) before
attempting to modify /cred, per the OCF 1.0 Security Spec. This is new in OCF
1.0 (in OIC 1.1 the /cred Resource could be updated at unsafe point
As a general rule the files used for the lib are *.a or *.so files for linux or
*.lib or *.dll for windows. I have only seen *.o files used as lib in one
project (non IoTivity) and it was a work around for a really unusual build time
issue.
George
From: iotivity-dev-boun...@lists.iotivity.org
