Send alert after bad client hello
authorJoonghwan Lee <jh05.lee@samsung.com>
Thu, 22 Dec 2016 02:51:40 +0000 (11:51 +0900)
committerRandeep Singh <randeep.s@samsung.com>
Fri, 20 Jan 2017 04:08:39 +0000 (04:08 +0000)
commitf281a8e1232ddfdb5a8ff8e702854a79a90fc273
tree45e37fed8e1c13eb163cd5d54c63da8dba7d6988
parentd12b8539013cea5a3887b0a52918997d5f070cbc
Send alert after bad client hello

Fix the following situation:
1. client tries OTM to server
2. OTM completed
3. network of server goes down and up => DTLS session has been removed
4. client tries to send a request to secure resource(e.g., /oic/sec/acl)
5. server prints bad client error(MBEDTLS_ERR_SSL_BAD_HS_CLIENT_HELLO), and then ignore this
6. client never gets a response of it even if re-tries to sent same message

Change-Id: Ie2cd3eaa49fc8782522126799994a5cd47cfaf4e
Signed-off-by: Dmitriy Zhuravlev <d.zhuravlev@samsung.com>
Signed-off-by: Oleksii Beketov <ol.beketov@samsung.com>
Signed-off-by: Joonghwan Lee <jh05.lee@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/15853
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Randeep Singh <randeep.s@samsung.com>
(cherry picked from commit 7241811f3c1fba031aff1f1fc90f81f6a8a9a038)
Reviewed-on: https://gerrit.iotivity.org/gerrit/15855
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Kevin Kane <kkane@microsoft.com>
Reviewed-by: Mats Wichmann <mats@linux.com>
resource/csdk/connectivity/src/adapter_util/ca_adapter_net_ssl.c