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: 🤝.

The Calculus of Handshake Configurations

Abstract: Handshake protocols are asynchronous protocols that enforce several properties such as absence of transmission interference and insensitivity from delays of propagation on wires. We propose a concurrent process calculus for handshake protocols. This calculus uses two mechanisms of synchronization: rendez-vous communication a la CCS, and shared resource usage. To enforce the handshake discipline, the calculus is endowed with a typing system. We provide an LTS semantics of the calculus and show that typed processes denote handshake protocols. We give the calculus another semantics in terms of a special kind of Petri nets called handshake Petri nets. We show that this semantics is complete and fully abstract with respect to weak bisimilarity.

A Client-Side Seat to TLS Deployment

Abstract: The official release of the latest version of the Transport Layer Security (TLS) protocol, namely TLS 1.3, has been accompanied by rapid adoption across the Web. In 2019, Holz et al. set out to measure this adoption, i.e., deployment and uptake of the protocol (CoRR 2019). Whilst informative and undeniably useful for the TLS community, Holz et al. note that they were unable to measure some of the newer features of TLS 1.3, including zero round-trip time (0-RTT) and post-handshake authentication (PHA). The altered structure of TLS 1.3, with more encryption of the handshake, renders measurement of these features impossible via passive monitoring and Internet scanning. Access to client-side TLS telemetry enables our work to address these limitations, and presents a clearer view of the TLS 1.3 adoption landscape. Specifically, our work comments on the true acceptance rate of client-generated early data, and on the odd usage patterns surrounding client authentication that occurs post-handshake. Our work also presents an up-to-date measurement of TLS 1.3 deployment, both confirming and extending the predictions and results presented by Holz et al.

certificate management method and device

Abstract: The invention provides a certificate management method and device, and relates to the technical field of electronic certificate management. The certificate management method comprises the following steps: determining an Internet protocol address of a node server; and carrying out handshake with the Internet protocol address based on a plurality of handshake protocols of the secure socket layer certificates to obtain the secure socket layer certificates on the node server, the different handshake protocols being used for obtaining the secure socket layer certificates of different deployment modes. According to the method, attempt handshake of a plurality of handshake protocols is carried out on one node server, and the secure socket layer certificates deployed in different deployment modeson the node server are obtained, so that the accuracy and comprehensiveness of certificate obtaining are improved.

Equilibria of a shared medium access network with RTS/CTS handshake mechanism

Abstract: We characterize the Nash equilibrium point of the request probability in a network using the Request-to-send / Clear-to-send (RTS/CTS) handshake mechanism for channel reservation, where each node tries to minimize its average power investment selfishly while meeting its average throughput demand over the shared wireless channel to a common base station. The feasible region of throughput demands is then maximized by the optimal data transmission periods and meanwhile the average power investment at the better Nash equilibrium is reduced. In addition, the performance of the optimum design is compared to that in a network without the RTS/CTS handshake mechanism.

System and method for improved handshake protocol

Abstract: In order to enable a dynamic handshake procedure, a client device is configured with a list of handshake contributors. The client device initiates a handshake by determining the handshake contributors and writing properties of the handshake contributors in a client handshake, which is then sent to a server device. The client handshake is processed at the server device by invoking an appropriate handler, which handles the handshake result. The server can also send its contributors and their properties to the client. Once the client receives the properties, the client can call an appropriate handler to handle the properties. Connections may be created based on the exchanged properties. New contributors and contributor handlers may be added to both the client and server devices.