Amit KS [Wed, 17 Oct 2018 11:28:01 +0000 (16:58 +0530)]
[CONPRO-1273] Add LINKFLAGS
1. Remove '-fPIE, -pie' compile option from CCFLAGS
2. Add LINKFLAGS '-Wl, -z, -relro'
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/329
(cherry picked from commit
7115d71236b6a1c947f93dec0c84762937150c5b)
Change-Id: Ie713ebcf02c0b526730d7cd94f0d2c0ae69852ce
Signed-off-by: Amit KS <amit.s12@samsung.com>
harish.191@samsung.com [Thu, 11 Oct 2018 09:18:35 +0000 (14:48 +0530)]
Fix for SVACE issue. (#326)
[CONPRO-1305] Fix for SVACE issue.
1. Add condition to stop receive negative value.
2. Check condition for thread creation successful.
3. Check return value of function.
4. Update type mismatch value assigned.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/326
(cherry picked from commit
cb27ef5e3947ffc529630e0792eff21f4d081f12)
Change-Id: I44aca78703df3fbbe61bd0772760df22fd6c3db9
Signed-off-by: Amit KS <amit.s12@samsung.com>
kush.agrawal@samsung.com [Wed, 3 Oct 2018 08:07:00 +0000 (13:37 +0530)]
Update sc_enrollee.c
cherry picked from commit
352502d7d0ed803fa124e3f1502047be066ab52f
Change-Id: I8cb30184e34f086d965ad0a39767fcdeaf23d438
Signed-off-by: agrkush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
kush.agrawal@samsung.com [Wed, 3 Oct 2018 08:02:03 +0000 (13:32 +0530)]
Update ESSCCommon.h
cherry picked from commit
a3e28f7512d6ad220f04eb8cc7fd2ac77f30f0f8
Change-Id: I25c8b42d74bc07e2b45d00a58adebc238ba83767
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Fri, 5 Oct 2018 04:01:42 +0000 (09:31 +0530)]
Update Snapshot(2018-10-03)
Change-Id: I9c3c89830e4c251f833667013610e41c2768330e
Signed-off-by: Amit KS <amit.s12@samsung.com>
agrkush [Wed, 3 Oct 2018 07:52:22 +0000 (13:22 +0530)]
Adding candidateAP information. Following Samsung Specific Property is added :
Property Name: Candidate AP List Information
Key: "x.com.samsung.candidateaps"
Type: Object Array (Containing ssid, passphrase, channel and bssid).
Access Mode: Read Write
Description: Candidate AP List information
Changes made at Mediator and Enrollee Side (Samsung specific source).
Linux Sample apps updated and verified (Samsung Specific Sample Apps)
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/323
(cherry picked from commit
839c794eda36bc5428933fef26613db1acdad040)
Change-Id: Ia2cc7d6f421c1a0e4f500b820fc11c217d67bf2e
Signed-off-by: agrkush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Wed, 26 Sep 2018 05:39:00 +0000 (11:09 +0530)]
Added API to disable starting advertisement automatically
And Advertisement data can be set just before starting - Review Comment fixed
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/315
(cherry picked from commit
1d853ecc267d2f76d0695aefffd02d6d5ed50a95)
Change-Id: Id0dddf2487750f045ef5ad8c26d277b762c14d89
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Tue, 18 Sep 2018 11:37:33 +0000 (17:07 +0530)]
Added API to disable starting advertisement automatically
And Advertisement data can be set just before starting - Review Comment fixed
Change-Id: Ia82e648ae5ebf138a4311c83a0ed8d259d7b6e80
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Fri, 24 Aug 2018 16:25:11 +0000 (21:55 +0530)]
Added API to disable starting advertisement automatically
And advertisement data can be set just before starting
Following Two Pathces are integrated
1.Added API to disable starting advertisement automatically [Problem] There is no possibility to don't start advertisement.
It is always started automatically. [Cause & Measure] Advertisement is started automatically in CAStartLEGattServer
2.Advertisement data can be set just before starting
[Problem] It's not possible to set advertisement data after bluetooth is enabled but before advertising is started.
[Cause & Measure] current implementation assumes setting advertisement data before turning on BT.
This feature adds possibility to set function that will be called just before starting advertising
Change-Id: I773bbfc7bb53306609812ec9600d86d29e35d27e
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Thu, 4 Oct 2018 13:39:34 +0000 (19:09 +0530)]
Fixed add missing compile secure option for iotivity library
Change-Id: Ieff02dd71def5f5151c9ea7cea476f9389e2ac93
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Thu, 4 Oct 2018 04:44:45 +0000 (10:14 +0530)]
Update Snapshot(2018-09-12)
Change-Id: Ia58b6689eb52425d499eb303bc4f8ede6e0cd4cc
Signed-off-by: Amit KS <amit.s12@samsung.com>
Harish Kumara M [Thu, 16 Aug 2018 11:19:44 +0000 (16:49 +0530)]
New APIs for editing resource and interfaces types
New APIs are introduced for modifying resource and interface
types bound to a resource. These new APIs clear currently bound
types and set newly passing resource/interface type.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/313
(cherry picked from commit
2ffab6058c93ff52d64bbbe6e8d29855916d3bcc)
Change-Id: I1e51823f1d46fdc042694f9213bde026974b9ae3
Signed-off-by: Harish Kumara M <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Thu, 4 Oct 2018 04:39:58 +0000 (10:09 +0530)]
Update Snapshot(2018-09-05)
Change-Id: If994c8ff2a83bdee1ebc1e9daaa00841e7af4b82
Signed-off-by: Amit KS <amit.s12@samsung.com>
harish_kumar [Fri, 15 Jun 2018 04:44:39 +0000 (10:14 +0530)]
add missing compile secure option for iotivity library
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/294
(cherry picked from commit
ff3d8b68e7ad493ed9f52cc62faab0124409891d)
Change-Id: I13c83d33031ff774c2a66b8e7636e68d779e93b7
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Thu, 4 Oct 2018 15:00:41 +0000 (20:30 +0530)]
CONPRO-1320] Cleanup observers of deleted resource.
Observers were not cleane up for deleted resource, this
caused crash in trying to access deleted resource while
deleting these observers when TCP connection is closed.
Changes are made to clean up the observers while deleting
resource itself
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/318
(cherry picked from commit
a7f8adbd8574db8b22a9fbf2340721ebac4c148e)
Signed-off-by: Harish Kumara M <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Change-Id: I2860a6aaa6324b3ff55070860e8e6b0090f6d2eb
Amit KS [Tue, 7 Aug 2018 09:35:33 +0000 (15:05 +0530)]
Update Snapshot(2018-07-25)
Change-Id: I1907ac783dc812df5ff8ed16007ca7ff6cfab72a
Signed-off-by: Amit KS <amit.s12@samsung.com>
Vitalii Irkha [Tue, 24 Jul 2018 13:53:55 +0000 (16:53 +0300)]
[SVRDBEditor] Allow add MOM DOXM attribute
MOM DOXM attribute can be added via svrdbeditor
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/310
(cherry picked from commit
1ce338a37a447e42c23a86d64d9e96c6646a9217)
Change-Id: I02cc8714d6c2ac418cb2d99c77c3c0e2220ebbf3
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Tue, 7 Aug 2018 09:24:07 +0000 (14:54 +0530)]
Install missed header files by the build time reducing
Change-Id: Ided34d8b62455f9d48b54f8362bda8497dec2654
Signed-off-by: Amit KS <amit.s12@samsung.com>
Vitalii Irkha [Tue, 17 Jul 2018 13:36:20 +0000 (16:36 +0300)]
[SVRDBEditor] Edit Doxm MOM attribute
Added Edit mom functionality to svrdbeditor tool
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/307
(cherry picked from commit
86952a25462ae462e52af83368c153c00b4e8374)
Change-Id: Ieff8984afb72bdbad80281ed44967bfa8ac55440
Signed-off-by: Vice73d5846ecb99fb04e87860b94afbaeff0ddcb4talii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
yhji [Mon, 30 Jul 2018 10:42:11 +0000 (19:42 +0900)]
Fix Wformat build error
Change-Id: Ie8d661436da8145de62f8a6c00d74fc6719fadd2
Signed-off-by: yhji <yhji.lee@samsung.com>
Amit KS [Fri, 20 Jul 2018 04:28:23 +0000 (09:58 +0530)]
Update Snapshot(2018-07-18)
Change-Id: Ic28205c52f6ffb421856a41dce21f5773651682c
Signed-off-by: Amit KS <amit.s12@samsung.com>
v.irkha@samsung.com [Mon, 9 Jul 2018 04:58:23 +0000 (07:58 +0300)]
SQLite OS specific support (#304)
Change SQL requests for WHERE statements with blob params.
(Details in [IOT-2775])
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/304
(cherry picked from commit
988f01a5cc090ef21dfde89352ceb47dd7be70bc)
Change-Id: If87ae5503fb2961601376bfd405c7949c1a5c28a
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
DoHyun Pyun [Thu, 19 Jul 2018 06:59:47 +0000 (15:59 +0900)]
Enable Multiple Ownership feature
Change-Id: Ib28d8cfee76ad94791f9177ccd1ad6d9c7b9aa82
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Amit KS [Thu, 5 Jul 2018 06:36:40 +0000 (12:06 +0530)]
Update Snapshot(2018-07-04)
Change-Id: Id715c564d0c8404dca74f69fbad277ea7d7357fd
Signed-off-by: Amit KS <amit.s12@samsung.com>
senthil.gs@samsung.com [Tue, 3 Jul 2018 15:44:48 +0000 (21:14 +0530)]
Disable the Multicast Action in Mobile Network Case.
Starting multicast server on all identified interfaces results in resource loss as many of identified interfaces may not have Multicast capability. It make sense to start multicast server on only active wifi connected interface for android platform.
This patch handles -
1. Create UDP sockets(Unicast and Multicast) and join multicast group only when there on active WiFi connection.
2. Whenever the WiFi connection comes up, UDP sockets will be closed, created, and joined to multicast group.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/296
(cherry picked from commit
ce73d5846ecb99fb04e87860b94afbaeff0ddcb4)
Change-Id: Ib3586d77d3c0e96c990e3fb5a398e78b29a20be8
Signed-off-by: Amit KS <amit.s12@samsung.com>
Oleksii Beketov [Mon, 2 Jul 2018 12:01:02 +0000 (15:01 +0300)]
RPK: add length check
RPK master key length check and logging added
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/303
(cherry picked from commit
c8d7cb113be986ad53aa1b498280530277597187)
Change-Id: Ia9d5a974476fee3d9fc64a2267c3b8db8ff3f7b4
Signed-off-by: Oleksii Beketov <ol.beketov@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Vitalii Irkha [Fri, 22 Jun 2018 09:49:41 +0000 (12:49 +0300)]
[CONPRO-1300] Crash in CAdeinitSslAdapter
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/299
(cherry picked from commit
eb86d2e103dc826d90bbb364f45616e903d6d312)
Change-Id: I2db227c9d418b68a423e742fca3cd74e8d8c8105
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Thu, 28 Jun 2018 10:06:36 +0000 (15:36 +0530)]
Update Snapshot(2018-06-27)
Change-Id: Ifb00f0b5683c938b94c710836900d0ed6ab6cfcc
Signed-off-by: Amit KS <amit.s12@samsung.com>
Vitalii Irkha [Mon, 25 Jun 2018 15:33:11 +0000 (18:33 +0300)]
[CONPRO-1303] Memory leak for equal cred contents
Fix the issue in AddCredential api
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/300
(cherry picked from commit
0538b11eb0600edbf18bc43af4c3493369f99e09)
Change-Id: I0211724897f604ba88dcfb33147cb219a502ef65
Signed-off-by: Vitalii Irkha <v.irkha@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
ol.beketov@samsung.com [Mon, 25 Jun 2018 11:17:03 +0000 (14:17 +0300)]
RPK OTM (#295)
Raw public key OTM added from client side
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/295
(cherry picked from commit
bc07c41689f3f835cb14b9e8ad70c2298fa6c839)
Change-Id: Iafeb8d467c821eca3ad350eced73f57637349a71
Signed-off-by: Oleksii Beketov <ol.beketov@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
kush.agrawal@samsung.com [Fri, 22 Jun 2018 14:00:08 +0000 (23:00 +0900)]
Crash in OCProcessPresence (#298)
* [CONPRO-1285]Crash in OCProcessPresence
There is a issue after freeing the clientcb
we are again accessing it.It can possibly crash.
So, to avoid this scenario we are using LL_FOREACH_SAFE
to iterate the list
Signed-off-by: agrkush <kush.agrawal@samsung.com>
* Update ocstack.c
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/298
(cherry picked from commit
578c6918d40d5bded028266ceb3a4aaf68d33623)
Signed-off-by: Amit KS <amit.s12@samsung.com>
Change-Id: Id514a242e34d7a20df2845c09a757b3d26c9604a
DoHyun Pyun [Tue, 19 Jun 2018 02:10:43 +0000 (11:10 +0900)]
Install missed header files by the build time reducing patchset
Change-Id: Ibb91b87e1353e8921c0d2e65d6bd073bf5224ba3
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Amit KS [Mon, 18 Jun 2018 08:45:54 +0000 (14:15 +0530)]
Applying remove re-build command patchset in the public spec file
In the build section, scons build is done. So we can use the result
on the install section without rebuild using scons.
Change-Id: I05254fddd617f7c4af35a16e07c584da2b020e03
Signed-off-by: Amit KS <amit.s12@samsung.com>
Pyun DoHyun [Mon, 18 Jun 2018 06:56:36 +0000 (06:56 +0000)]
Merge "Update Snapshot(2018-06-13)" into tizen
Pyun DoHyun [Mon, 18 Jun 2018 06:56:24 +0000 (06:56 +0000)]
Merge "Remove re-build command in the install section" into tizen
Pyun DoHyun [Mon, 18 Jun 2018 06:56:16 +0000 (06:56 +0000)]
Merge "Crash in CATerminate" into tizen
Pyun DoHyun [Mon, 18 Jun 2018 06:56:07 +0000 (06:56 +0000)]
Merge "Add missing stack errors to android code" into tizen
Pyun DoHyun [Mon, 18 Jun 2018 06:55:59 +0000 (06:55 +0000)]
Merge "Fix build error dlog string" into tizen
Amit KS [Wed, 13 Jun 2018 11:36:32 +0000 (17:06 +0530)]
Update Snapshot(2018-06-13)
Change-Id: Icd6f0c7e1f2c7295b125b86739533e18e131ed5b
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Mon, 18 Jun 2018 05:01:11 +0000 (10:31 +0530)]
Remove re-build command in the install section
In the build section, scons build is done. So we can use the result
on the install section without rebuild using scons.
Change-Id: I33d47209d0898d703dcedba6bfd00a91d959c9b6
Signed-off-by: Amit KS <amit.s12@samsung.com>
Veeraj Khokale [Thu, 7 Jun 2018 13:30:59 +0000 (19:00 +0530)]
Crash in CATerminate
The variable caglobals.tcp.terminate is used to signal the
receiver thread to stop. However using a volatile variable
to synchronize between threads is undefined behaviour as
per the C/C++ standards. In this particular case due to
cache coherence behaviour on SMP mobile(especially ARM)
multi core processors, the receiver thread is not guaranteed
to see the change to the terminate variable as soon as
adapter is terminated and this delay could cause an ANR.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/290
(cherry picked from commit
38101be161271b68cee847748d71fb4ded73bc5a)
Change-Id: Ib18b91b9efde71d4075c0ec9c9639ac8051df6b6
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
harish_kumar [Fri, 8 Jun 2018 12:36:05 +0000 (18:06 +0530)]
Add missing stack errors to android code
Add missing OCStackResult enum values to errorcode.java file
and JniUtils.h.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/291
(cherry picked from commit
e2545fc58de379f686ac60c43cffb1d032620c77)
Change-Id: I0ddd8aadbf15366128c4b3ed30b3eb3eb4d85fc5
Signed-off-by: harish_kumar <harish.191@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
v.riznyk [Wed, 6 Jun 2018 10:03:38 +0000 (13:03 +0300)]
Fix build error dlog string
Patch was tested
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/289
(cherry picked from commit
b1c8909fa7626bb06f8579aca6a3fb7cdb3ccef4)
Change-Id: I5c10ed7e0a74a8d16a007a0a83185dd8ea2390e1
Signed-off-by: v.riznyk <v.riznyk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
v.riznyk [Wed, 6 Jun 2018 10:03:38 +0000 (13:03 +0300)]
[CONPRO-1295] Fix build error dlog string
Patch was tested
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/289
(cherry picked from commit
b1c8909fa7626bb06f8579aca6a3fb7cdb3ccef4)
Change-Id: I816cf45ea6206929749b1ab8c395c985a72fa6be
Signed-off-by: v.riznyk <v.riznyk@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Amit KS [Fri, 4 May 2018 05:20:44 +0000 (10:50 +0530)]
Update Snapshot(2018-05-02)
Change-Id: I7d952ce967acdcd9fe305e5c00d48b1311982c30
Signed-off-by: Amit KS <amit.s12@samsung.com>
Harry [Wed, 2 May 2018 13:33:34 +0000 (19:03 +0530)]
Clearing pending exceptions in JNI env
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/287
(cherry picked from commit
312f0a735dea35925da0d80a916d0d9cf542932e)
Change-Id: I2830f50706a5818375745a406d3ff4b7f8ecdb1c
Signed-off-by: Harry <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Fri, 4 May 2018 05:18:11 +0000 (10:48 +0530)]
Update Snapshot(2018-04-25)
Change-Id: I1b9d298f47b7be8efadb90d1c327467fc7b5e5fe
Signed-off-by: Amit KS <amit.s12@samsung.com>
Kush [Mon, 16 Apr 2018 14:17:43 +0000 (19:47 +0530)]
Added Samsung Specific Property(sso list) for easy setup
Following Samsung Specific Property is added :
Resource: Device Configuration (rt = "oic.r.devconf")
Property Name: SSO List Information
Key: "x.com.samsung.ssolist"
Type: String (JSON value with array of string internally).
Access Mode: Read Only
Description: SSO List information
Changes made at Mediator and Enrollee Side (Samsung specific source).
Linux Sample apps updated and verified (Samsung Specific Sample Apps).
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/284
(cherry picked from commit
26aec98b390c57957416dff8c3e9a920299aad8a)
Change-Id: Ib5143bb96488820b01404c2ec68dcf04c9f6a02c
Signed-off-by: Kush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Veeraj Khokale [Wed, 25 Apr 2018 13:46:53 +0000 (19:16 +0530)]
Disable TCP server role
TCP server is used only in client role to connect to
cloud server. A critical vulnerability is reported when
ifw-thing process in TV connects to other device via
TCP(D2D) which can compromise the Policy engine. Therefore
disable TCP server role based on build configuration.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/286
(cherry picked from commit
fbd41449a05001403bcf60169a3c780d97001e7a)
Change-Id: Iefdd1cf9ef9524cfb6cf48d1219b0b7e3e88bb9a
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Amit KS [Fri, 20 Apr 2018 09:30:46 +0000 (15:00 +0530)]
Update Snapshot(2018-04-18)
Change-Id: I2e6bc5d46d982406a7bef07b672b2b3093037dd6
Signed-off-by: Amit KS <amit.s12@samsung.com>
Kush Agrawal/SRI-Bangalore-Smart Living/./삼성전자 [Tue, 17 Apr 2018 15:18:55 +0000 (20:48 +0530)]
Creating socket everytime when network bearer changes (#285)
[CONPRO-1269] Creating socket everytime when network bearer changes
Socket was created only once but changed the logic for creating on every network change
When we are switching WifiAP or disconnect/connect again then we are not able to send unicast data from android side . It gives network unreachable error. So to avoid that we are closing and creating sockets again.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/285
(cherry picked from commit
285875048bda46b6ac1a742c25849d70234d7cd1)
Change-Id: I5387e2c49aac35de2c1608c24486644adb8328c1
Signed-off-by: Kush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Veeraj Khokale [Thu, 12 Apr 2018 11:07:33 +0000 (16:37 +0530)]
Replace tizen BLE internal APIs with public
Tizen 4.0 build fails in case BLE internal API's are used,
therefore replace them with public API's. All changes are
made under the preprocess define TIZEN_4
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/282
(cherry picked from commit
d66f237dc92c15a515332d0416f769d8e856bfe9)
Change-Id: I6b5f9e67209e70bd654db4182c5ef70220792459
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
dh79.pyun@samsung.com [Tue, 17 Apr 2018 06:31:54 +0000 (15:31 +0900)]
Fix Asan build errors (#281)
Remove duplicate variables
multiple definition of `g_ESEasySetupResource'
multiple definition of `g_ESDevConfResource'
multiple definition of `g_ESCoapCloudConfResource'
multiple definition of `g_ESWiFiConfResource'
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/281
(cherry picked from commit
0cbbcfa65ff14d751dd1193f75b7c20269e26991)
Change-Id: If5f4a7d87e95350d70187cb21e070c5193130487
Signed-off-by: Oleg Ogurtsov <o.ogurtsov@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Kush [Tue, 10 Apr 2018 07:14:19 +0000 (12:44 +0530)]
[CONPRO-1269] Creating socket everytime when network bearer changes
Socket was created only once but changed the logic for creating on every network change
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/280
(cherry picked from commit
eaa97ac11871f5536ca12e7ab2f9c848b4d99afd)
Change-Id: Iaeabe733b6b8728ae74b1903d49c9596dcf021e8
Signed-off-by: Kush <kush.agrawal@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Thu, 12 Apr 2018 12:38:42 +0000 (18:08 +0530)]
Update Snapshot(2018-04-12)
Change-Id: I34509db28a4ab393675b6783b4a011f72989022f
Signed-off-by: Amit KS <amit.s12@samsung.com>
Veeraj Khokale [Fri, 6 Apr 2018 09:03:12 +0000 (14:33 +0530)]
Crash in OCProcessPresence()
1. Set presence to NULL incase allocation of timeout
array fails. This ensures that OCProcessPresence does
not process this cbNode, thereby preventing possible
NULL dereference of timeout.
2. Do not send request if timeout has reached/exceeded
the PresenceTimeOutSize. This prevents a possible buffer
overrun in accessing the timeout array.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/279
(cherry picked from commit
22079af2bd0f22a80b98c3b17469c3b8ed601ede)
Change-Id: I9398fa4870a719eb0bbaa00102157e8487af5236
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Amit KS [Fri, 6 Apr 2018 05:15:26 +0000 (10:45 +0530)]
Update Snapshot(2018-04-05)
Change-Id: I24184456b2aff374d89f7bed23a6481cb1da9eee
Signed-off-by: Amit KS <amit.s12@samsung.com>
Veeraj Khokale [Tue, 3 Apr 2018 10:58:55 +0000 (16:28 +0530)]
Unset gatt callback in network monitor
Gatt connection state changed callback is set in the
network monitor (calenwmonitor.c) but is unset in the
gatt client (caleclient.c). Move this to network
monitor instead
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/278
(cherry picked from commit
961ff08710e7acd99277a335f7d9eeca2f68c16e)
Change-Id: I386499c475a241bca840610df823f84d1a74ee0d
Signed-off-by: Veeraj Khokale <veeraj.sk@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Vadym Riznyk [Fri, 30 Mar 2018 13:35:56 +0000 (16:35 +0300)]
"have choice" error of libmbedtls.so
delete +%{_libdir}/libmbedtls.so from iotivity-devel
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/277
(cherry picked from commit
3cd231da7e03a322dd10fbfee0b15582647c191e)
Change-Id: I264692bb5ce86cdbcabb11f84b1634b9a1991f8a
Signed-off-by: Oleksiy Volkov <a.volkov@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Amit KS [Thu, 29 Mar 2018 07:23:59 +0000 (12:53 +0530)]
Update Snapshot(2018-03-28)
Change-Id: I5b107aa308a184b0ee70eef14a2e31d840273b4d
Signed-off-by: Amit KS <amit.s12@samsung.com>
Harry [Thu, 22 Mar 2018 13:43:09 +0000 (19:13 +0530)]
Synchronized observe notification using mutex.
As InProcClientWrapper class creates separate thread for every
obseve callback, There is a chance that more than one thread enter
ObserveCache object and trying to modify m_attributes. More over
same m_attributes is being passed out or RE layer by const reference,
so application is using same member object m_attributes. Mutex allows
only one thread to modify m_attributes.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/276
(cherry picked from commit
c87d0d4b14d22349c3563e7cd316d323d068e2ab)
Change-Id: Ibee9b9326e6d7a3be093bc387db70a7c8f9a626d
Signed-off-by: Harry <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
Harry [Wed, 31 Jan 2018 09:22:21 +0000 (14:52 +0530)]
[CONPRO-1212] Removing invocation of lock_guard destructor.
std::lock_guard follows RAII for std::mutex. Invoking
std::lock_guard<std::mutex>::~lock_guard() makes unlock
call twice on underlying mutex. As per the API documentation
calling unlock from thread which does not own lock results in
undefined behaviour.
https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/243
(cherry picked from commit
fc681e089d3bbbbd16f90ad05d53208f9a1602d1)
Change-Id: I9ef2f3eed0e4989a7d73ad1ab40a3bae0a01a11c
Signed-off-by: Harry <h.marappa@samsung.com>
Signed-off-by: Amit KS <amit.s12@samsung.com>
DoHyun Pyun [Thu, 22 Mar 2018 23:58:35 +0000 (08:58 +0900)]
Update Snapshot(2018-03-21)
Change-Id: I4e58e8e3e61558da4d42132b411fd54a086c8cec
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Kush [Tue, 20 Mar 2018 11:38:36 +0000 (17:08 +0530)]
[CONPRO-1251]Updated typo error
Changed interface declaration in ocobserve.h
Change-Id: If14e1de31caf31ed941c49570e37db8d3bf1a860
Signed-off-by: Kush <kush.agrawal@samsung.com>
Amit [Wed, 7 Mar 2018 11:38:24 +0000 (17:08 +0530)]
Update Snapshot(2018-03-07)
Change-Id: I79678d132217d7056f146a899e1768fb6d27e45a
Signed-off-by: Amit <amit.s12@samsung.com>
Amit [Thu, 1 Mar 2018 06:52:19 +0000 (12:22 +0530)]
Update Snapshot(2018-02-28)
Change-Id: Iac61820dccb00d3c775c0495468dcbb49722c47b
Signed-off-by: Amit <amit.s12@samsung.com>
Amit [Thu, 22 Feb 2018 13:46:01 +0000 (19:16 +0530)]
Update snapshot(2018-02-21)
Change-Id: I0c6253b0fc7db9200b9c9281a5c1217e1a18dd9c
Signed-off-by: Amit <amit.s12@samsung.com>
DoHyun Pyun [Sun, 18 Feb 2018 23:46:20 +0000 (08:46 +0900)]
Update snapshot(2018-02-14)
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Change-Id: Id1b73ca10ec8b211a18601956891e92717c6f0a2
Hongkuk, Son [Thu, 8 Feb 2018 04:37:16 +0000 (13:37 +0900)]
Update snapshot(2018-02-07)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
Change-Id: Id7dbc4ca15ab77968a5b2d8103a1bc045c76af04
Hongkuk, Son [Wed, 31 Jan 2018 10:34:12 +0000 (19:34 +0900)]
Update snapshot(2018-01-31)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I9924efad707f22fb391e2474a441d3d8276d1649
Hongkuk, Son [Wed, 24 Jan 2018 15:49:11 +0000 (00:49 +0900)]
Update snapshot(2018-01-24)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ibdaa01124bffca9512ee93aaa0045e5f91effd0c
Hongkuk, Son [Thu, 18 Jan 2018 03:15:03 +0000 (12:15 +0900)]
Update snapshot(2018-01-17)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ifcbe9a53b46849c046ffc8d0276dc69f8a154465
Hongkuk, Son [Thu, 11 Jan 2018 01:38:46 +0000 (10:38 +0900)]
Update snapshot(2018-01-10)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I28f0ac1b4501582c84236f8ef8d8212790cd9e70
Hongkuk, Son [Thu, 4 Jan 2018 11:47:25 +0000 (20:47 +0900)]
Update snapshot(2018-01-04)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ifc34479a8f033e99bbe0740f3e4d281e723aec9a
Hongkuk, Son [Wed, 20 Dec 2017 12:30:42 +0000 (21:30 +0900)]
Update snapshot(2017-12-20)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I4d948dca96a3ae784cc0278e96b09c49f809bd06
Hongkuk, Son [Thu, 14 Dec 2017 09:01:34 +0000 (18:01 +0900)]
Update snapshot(2017-12-14)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Iace03beab45ea8839e72170fd9d9b7b6e31ab58d
Hongkuk, Son [Thu, 7 Dec 2017 05:29:58 +0000 (14:29 +0900)]
Update snapshot(2017-12-06)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I8eea641086585cab78abc370067e76b0f4fe34b2
Hongkuk, Son [Thu, 30 Nov 2017 02:03:56 +0000 (11:03 +0900)]
Update snapshot(2017-11-29)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Id4d682d07ae11ccff14f9548c930ce146df8cf85
Hongkuk, Son [Fri, 24 Nov 2017 01:49:14 +0000 (10:49 +0900)]
Update snapshot(2017-11-23)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I4daa62ca37c2ef8e0a739f63a258022ccdc354d8
Hongkuk, Son [Wed, 15 Nov 2017 02:34:20 +0000 (11:34 +0900)]
Update snapshot(2017-11-14)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ief7e3ae9c8c4e11ab1f7f82d05b3879fc5afc0ef
Hongkuk, Son [Thu, 9 Nov 2017 07:16:19 +0000 (16:16 +0900)]
Update snapshot(2017-11-08)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I96da45cf94f6940c6ac37f57912fbfa61516630d
Hongkuk, Son [Fri, 3 Nov 2017 01:17:44 +0000 (10:17 +0900)]
Update snapshot(2017-11-02)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I2a5a1b9b72b71b1979f136aadce4ac0534765641
Hongkuk, Son [Mon, 30 Oct 2017 09:04:27 +0000 (18:04 +0900)]
Update snapshot(2017-10-25)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ib3354833ae4d27bcbcd5718358886e02e932299f
Hongkuk, Son [Thu, 12 Oct 2017 06:41:29 +0000 (15:41 +0900)]
Update snapshot(2017-10-11)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Ia16b9b063f1ca9f2734e865385d7a519c3d2f5bb
Hongkuk, Son [Tue, 10 Oct 2017 07:47:00 +0000 (16:47 +0900)]
Update snapshot(2017-10-04)
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: Idf480dc4361b14c8902e15f74ca253a55b2f3e1e
Hongkuk, Son [Fri, 29 Sep 2017 07:24:47 +0000 (16:24 +0900)]
replace : iotivity -> iotivity-sec
Signed-off-by: Hongkuk, Son <hongkuk.son@samsung.com>
Change-Id: I5096b7e6faeadd98d5ee48279b24cb9fbdb1f24f
Jooseok Park [Fri, 30 Jun 2017 11:52:25 +0000 (20:52 +0900)]
Remove unused pkg dependancy
Change-Id: I310c2e37d0a94c3c9cf3191b8162abc873ceb316
jihwan.seo [Mon, 6 Feb 2017 02:19:26 +0000 (11:19 +0900)]
delete wifi API and pkg config in tizen.
since IoTivity already use Tizen Connectivity Manager API instead of wifi API.
it should be removed in this and there.
Change-Id: I9a61d7d4d323fe83e988c792284179c099bc2855
Signed-off-by: jihwan.seo <jihwan.seo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17079
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Conflicts:
resource/csdk/connectivity/build/tizen/scons/SConscript
resource/csdk/stack/samples/tizen/build/scons/SConscript
Change-Id: I401a44313a3a48fd7bfc5ca9c8519ec1186a8083
George Nash [Thu, 1 Dec 2016 22:31:43 +0000 (14:31 -0800)]
[IOT-1643] Fix illegal memory access - Don't return local string
the std::string ret is a local varaible and is destroyed when the
what() member function returns.
Put the return string into the m_whatMessage variable. Since
'what()' member function is a const function it can not modify the
member variable m_whatMessage so it is generated in the
ResourceInitException constructor.
Issue found using static analysis tool.
Change-Id: I907b984f35dee59b2f300afe6a640b15a26f020f
Signed-off-by: George Nash <george.nash@intel.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/15035
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Larry Sachs <larry.j.sachs@intel.com>
Reviewed-by: Habib Virji <habib.virji@samsung.com>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Jooseok Park [Thu, 11 May 2017 13:16:00 +0000 (22:16 +0900)]
Update spec file (in tools)
Change-Id: I3840a6b3b10070df30e66ca0de8852d0ea76264e
Jooseok Park [Thu, 11 May 2017 11:30:13 +0000 (20:30 +0900)]
Update License
Change-Id: I47861f7f52f61ef1f5dbda201564f058560d3688
ChaJiWon [Thu, 2 Mar 2017 12:06:00 +0000 (21:06 +0900)]
IOT-1877 : start presence issue
When called OCStartPresence() second, OCStartPresence() returns error.
Fixed presenceState variable to OC_PRESENCE_UNINITIALIZED.
Change-Id: I089c826f4105eb3aaf835a8feda4c10b848ebd5d
Signed-off-by: ChaJiWon <jw_wonny.cha@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17623
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Phil Coval <philippe.coval@osg.samsung.com>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: jihwan seo <jihwan.seo@samsung.com>
Reviewed-by: Way Vadhanasin <wayvad@microsoft.com>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
(cherry picked from commit
2f11e9592a7374ce28082a523b0c367a6d31baee)
Reviewed-on: https://gerrit.iotivity.org/gerrit/17775
hyuna0213.jo [Thu, 2 Feb 2017 07:48:37 +0000 (16:48 +0900)]
Moved a requestId declaration in OCServerRequest
we should not add attributes after payload as they get overwritten
when payload content gets copied over.
Change-Id: I0c8a430f92c2196d3f9c816e9ba9d16fd44d88e4
Signed-off-by: hyuna0213.jo <hyuna0213.jo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17015
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
jihwanseo [Fri, 10 Feb 2017 07:26:51 +0000 (16:26 +0900)]
Fixed memory leak on OCSetDeviceInfo and CARetransmissionDestroy
Change-Id: Ic53ae0759020fa26f5f70425d3dab09ff5e7d375
Signed-off-by: Jaewook Jung <jw0213.jung@samsung.com>
Signed-off-by: jihwan.seo <jihwan.seo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17167
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: jaehyun Cho <jaehyun3.cho@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>
Jooseok Park [Wed, 8 Feb 2017 00:42:34 +0000 (09:42 +0900)]
fix the easy-setup mediator SConscript
Change-Id: If484c27c7336608326af35f3e0aebeac4e4a580a
hyuna0213.jo [Thu, 19 Jan 2017 03:52:31 +0000 (12:52 +0900)]
Fixed double free issue when destroying endpoint
- after destroying memory, set NULL value to prevent double free
- add the usage of oc_mutex_lock() when block data is updated
Change-Id: I78d0d46e37333e099ec737ac4500a2f388d58c4e
Signed-off-by: hyuna0213.jo <hyuna0213.jo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/15447
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: jihwan seo <jihwan.seo@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>
Philippe Coval [Wed, 1 Feb 2017 14:35:59 +0000 (15:35 +0100)]
tizen: Enable CLOUD and ship ES lib (downstream)
Sync with upstream's spec
Change-Id: I84ce3dd94e1a90f13f0ff875221ca50600000001
Forwarded: https://gerrit.iotivity.org/gerrit/#/q/I84ce3dd94e1a90f13f0ff875221ca5061828618e
Origin: https://review.tizen.org/gerrit/112583
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Philippe Coval [Wed, 1 Feb 2017 14:15:31 +0000 (15:15 +0100)]
tizen: Enable CLOUD and ship ES lib
Change-Id: I84ce3dd94e1a90f13f0ff875221ca5061828618e
Forwarded: https://gerrit.iotivity.org/gerrit/#/q/I84ce3dd94e1a90f13f0ff875221ca5061828618e
Origin: https://review.tizen.org/gerrit/112583
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16965
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>
Philippe Coval [Wed, 1 Feb 2017 14:15:31 +0000 (15:15 +0100)]
tizen: Use mediator richsdk lib
Change-Id: Ib63db28697925b02349da82c5feabc1334a39ba2
Forwarded: https://gerrit.iotivity.org/gerrit/#/q/Ib63db28697925b02349da82c5feabc1334a39ba2
Origin: https://review.tizen.org/gerrit/112583
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/16963
Reviewed-by: Uze Choi <uzchoi@samsung.com>
Tested-by: Uze Choi <uzchoi@samsung.com>
Geunsik Lim [Thu, 2 Feb 2017 06:15:37 +0000 (15:15 +0900)]
[4.0] Unification: Remove Profile Build Dependency & Prepare 4.0 Build
This is for Tizen 4.0.
- Removed profile build dependency.
- Prepare for Tizen 4.0 build.
a. Remove profile build dependency
- This commit completely removes the build dependencies on Tizen profile.
b. Prepare for Tizen 4.0 build
- We have assumed that Tizen 4.0 code is going to be more similar with 3.0
than 2.0. Please do not rely on string '==' compare for version check.
And, refer to the official macros that are defined in Project Config.
https://build.tizen.org/project/prjconf?project=<project_name>
@To maintainer:
Please, keep a spec file syntax that was written at an official webpage.
https://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html/\
RPM_Guide/ch-specfile-syntax.html
First, if you want to use a comparison operator in %if, don't use
a double-quotes. Second, RPM macro does not support a floating-point
number for the comparison operator.
Change-Id: I8904a25e5e24f6e1bdbd460e434ad563695a3001
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>