Secure Communication Handshake With Unified Authentication and Key Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems require multiple API calls to specialized hardware for authentication and encryption key generation, inefficiently slowing the handshake and encryption processes for secure communication sessions.
Innovation Solution
A security module that interfaces with the Open SSL application to execute authentication and key generation operations using one or two API calls, utilizing dedicated hardware components for encryption and decryption algorithms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple API calls are made to specialized hardware for authentication and encryption key generation, then security operations can be performed using dedicated hardware components, but the handshake and encryption processes become inefficient and slow
Solution Approach 1:
The patent combines multiple separate API calls (authentication call and key generation call) into a single unified API call to the security module. This merging of operations allows the system to maintain hardware-based security reliability while eliminating the inefficiency of multiple sequential calls, thereby resolving the contradiction between security reliability and process efficiency
2Reliability
If multiple API calls are made to specialized hardware for authentication and encryption key generation, then dedicated hardware components can be utilized, but the number of API calls increases and processing time is extended
Solution Approach 1:
The patent merges multiple time-consuming API calls into a single API call that performs both authentication and key generation operations within the security module. This reduces the total API call processing time while maintaining hardware-based security, directly addressing the contradiction between hardware-based security reliability and API call processing time
3Ease of operation
If conventional handshake protocols are used with multiple API calls, then authentication and key generation can be performed separately, but the overall system efficiency decreases
Solution Approach 1:
The patent merges separate authentication and key generation operations into a unified process triggered by a single API call. This maintains the operational clarity and ease of use (a single call to initiate security operations) while dramatically improving system efficiency by eliminating the overhead and latency of multiple sequential API calls to the security module
Data Source
AI summary
Methods and systems for executing a communication protocol are provided. One method includes receiving, by a security module of a first computing device, an API call to authenticate a certificate received from a second computing device to establish a communication session between the computing devices; selecting, by the security module, an authentication module to authenticate the certificate; generating, by an encryption module of the security module, a shared secret key for the communication session based on a private key of the first computing device and a public key of the second computing device; encrypting, by the encryption module, the shared secret key using an algorithm negotiated between the first computing device and the second computing device; generating, by the security module, an encrypted message for the second computing device; and transmitting, by the first computing device, the encrypted shared secret key and message to the second computing device.