Fix sample engine latest updated time as installing time 28/145428/2 accepted/tizen/4.0/unified/20170828.222318 accepted/tizen/unified/20170823.170303 submit/tizen/20170823.025619 submit/tizen_4.0/20170828.100005 tizen_4.0.IoT.p1_release tizen_4.0.IoT.p2_release tizen_4.0.m2_release
authorsangwan.kwon <sangwan.kwon@samsung.com>
Tue, 22 Aug 2017 06:44:51 +0000 (02:44 -0400)
committersangwan kwon <sangwan.kwon@samsung.com>
Tue, 22 Aug 2017 08:44:26 +0000 (08:44 +0000)
commitc17f3b2a294a450e83d0d436862ca80acb136f6d
tree295076216d99dba12e594d3ed266e637cf9e325e
parent70ab19f224fecf8cd50ce1a42dae96c06889c94e
Fix sample engine latest updated time as installing time

Malware detected time should greater than engine's latest update time
when engine is not updated after malware detecting. But some device's
current time is not correct(before: 2016) and sample engine's latest
updated time is fixed time(after: 2017), some TC was always failed.

Change-Id: I34ec53e612eb927ae0c2261a1ba4f42af6a7fb51
Signed-off-by: sangwan.kwon <sangwan.kwon@samsung.com>
packaging/csr-framework.spec