Certificate Distribution via Delivery Manager for Local Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems require senders to request recipient certificates from remote resources each time data is transmitted, leading to delays and bandwidth penalties, and may not have up-to-date certificates if the remote resource is unavailable.
Innovation Solution
A delivery manager distributes recipient certificates to multiple sending systems, which store them locally, allowing encryption without real-time requests to remote resources and ensuring up-to-date certificates through periodic updates from the Domain Name System (DNS).
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If senders request recipient certificates from remote resources each time data is transmitted, then certificate freshness is maintained, but transmission latency increases and bandwidth is consumed
Solution Approach 1:
The system performs preliminary actions by distributing certificates to sending systems in advance before actual data transmission occurs. The delivery manager proactively pushes certificates to sending systems, so when encryption is needed, the certificates are already available locally, eliminating real-time retrieval delays
Solution Approach 2:
The invention creates copies of recipient certificates and distributes them to multiple sending systems. Each sending system stores local copies of certificates needed for encryption, eliminating the need to repeatedly request the same certificate from remote resources while maintaining certificate availability
2Reliability
If senders request recipient certificates from remote resources each time data is transmitted, then up-to-date certificates are obtained, but bandwidth consumption increases
Solution Approach 1:
The system creates and distributes copies of certificates to sending systems in advance. These local copies eliminate the need for repeated bandwidth-intensive requests to remote resources, as senders can use their locally stored certificate copies for multiple encryption operations
Solution Approach 2:
The delivery manager implements continuous certificate distribution and updating mechanisms, proactively pushing certificates and updates to sending systems. This ensures certificate currency is maintained through continuous background updates rather than intermittent high-bandwidth requests
3Productivity
If senders store certificates locally, then encryption can proceed without remote resource availability, but certificate updates may be delayed
Solution Approach 1:
The system implements feedback mechanisms where sending systems report their certificate status and needs back to the delivery manager. The delivery manager uses this feedback to determine when and what certificates to push, enabling proactive updates before local copies become stale
Solution Approach 2:
The delivery manager performs periodic certificate harvesting from DNS and distribution to sending systems at scheduled intervals. This periodic action ensures certificates are updated regularly, maintaining currency while allowing local storage to provide encryption availability between update cycles
Data Source
AI summary
According to certain embodiments, a delivery manager comprises an interface and processing circuitry. The interface is configured to receive a certificate that a Domain Name Service (DNS) associates with a DNS name of a recipient system. The processing circuitry is configured to distribute the certificate to a plurality of sending systems. Each sending system is configured to store the certificate in a local memory of the sending system, use the certificate from the local memory of the sending system to perform encryption in response to a future determination to send an encrypted message to the recipient system, and send the encrypted message directly to the recipient system.


