Topic
Handshake
About: Handshake is a research topic. Over the lifetime, 1105 publications have been published within this topic receiving 15166 citations. The topic is also known as: 🤝.
Papers published on a yearly basis
Papers
More filters
••
TL;DR: In hospital set up doctors often shake hands with each other as an interdisciplinary confidence building measure apart from social bonding, other than handshakes amongst fellow doctors, handshake with patients before and after consultation is also considered as a part of physicians empathy and connect.
Abstract: Handshake has evolved as a quintessential form of greeting and showing warmth, bonding and peace. This has been a part of human civilization from historical times. The historical records of handshake date back to as early as 5 century BC from ancient Greece showing two soldiers shaking hands is displayed at Pergamon Museum, Berlin. Handshake has a cross cultural acceptance and is a standard norm for greeting internationally. In hospital set up doctors often shake hands with each other as an interdisciplinary confidence building measure apart from social bonding. Other than handshakes amongst fellow doctors, handshake with patients before and after consultation is also considered as a part of physicians empathy and connect. Corporatization of healthcare further adds up to increased use of these gestures.
2 citations
•
01 Jun 2005
2 citations
•
18 Dec 2018
TL;DR: In this paper, the authors proposed a key obtaining method, a device and a system, which consists of sending a key request to a server, receiving an encrypted file sent by a server; generating a handshake key according to the first preset key generation rule based on the key request; by using the handshake key as the decryption key, decrypting the encrypted file according to a decryption rule matched with the first encryption rule to obtain a data encryption key.
Abstract: The embodiment of the invention provides a key obtaining method, a device and a system. The method comprises: sending a key request to a server; receiving an encrypted file sent by a server; generating a handshake key according to the first preset key generation rule based on the key request; by using the handshake key as the decryption key, decrypting the encrypted file according to a decryptionrule matched with the first encryption rule to obtain a data encryption key. As can be seen, the scheme provided by the embodiment of the present invention is applied to obtain the data encryption key, different handshake keys can be generated for different key request, The handshake key is used as the decryption key to decrypt the encrypted data encryption key to obtain the data encryption key, which can effectively reduce the security hidden troubles of other clients due to the leakage of the encryption key by one client, and improve the security of obtaining the data encryption key.
2 citations
••
2 citations
••
TL;DR: In this article, a thorough comparison of the Transport Layer Security (TLS) v1.2 and Datagram TLS (DTLS) protocol in 6TiSCH networks is presented.
Abstract: This paper presents a thorough comparison of the Transport Layer Security (TLS) v1.2 and Datagram TLS (DTLS) v1.2 handshake in 6TiSCH networks. TLS and DTLS play a crucial role in protecting daily Internet traffic, while 6TiSCH is a major low-power link layer technology for the IoT. In recent years, DTLS has been the de-facto security protocol to protect IoT application traffic, mainly because it runs over lightweight, unreliable transport protocols, i.e., UDP. However, unlike the DTLS record layer, the handshake requires reliable message delivery. It, therefore, incorporates sequence numbers, a retransmission timer, and a fragmentation algorithm. Our goal is to study how well these mechanisms perform, in the constrained setting of 6TiSCH, compared to TCP’s reliability algorithms, relied upon by TLS. We port the mbedTLS library to OpenWSN, a 6TiSCH reference implementation, and deploy the code on the state-of-the-art OpenMote platform. We show that, when the peers use an ideal channel, the DTLS handshake uses up to 800 less and completes 0.6 s faster. Nonetheless, using an unreliable communication link, the DTLS handshake duration suffers a performance penalty of roughly 45%, while TLS’ handshake duration degrades by merely 15%. Similarly, the number of exchanged bytes doubles for DTLS while for TLS the increase is limited to 15%. The results indicate that IoT product developers should account for network characteristics when selecting a security protocol. Neglecting to do so can negatively impact the battery lifetime of the entire constrained network.
2 citations