File Sharing Proxy SSL Key Merging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file sharing systems over secure connections are inefficient due to the need for a file sharing proxy server to decrypt and re-encrypt data between client and host connections, which burdens processing and memory resources.

Innovation Solution

The file sharing proxy server shares the same SSL session key between client and host connections, allowing both to encrypt and decrypt data using the same key, thereby eliminating the need for the proxy server to decrypt and re-encrypt data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the file sharing proxy server uses separate SSL session keys for client and host connections, then data security is maintained, but processing and memory resources are heavily burdened due to decryption and re-encryption operations

Engineering Contradiction:
Improvedata securityVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges the encryption keys by making the host SSL session key identical to the client SSL session key. This allows the proxy server to skip decryption and re-encryption operations, as data encrypted with the client key can be directly forwarded to the host using the same key, thereby eliminating the performance burden while maintaining security through the established SSL channel.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The same SSL session key serves multiple functions: it encrypts data from the client to the proxy server and also encrypts data from the proxy server to the host. This universal key approach eliminates the need for separate key management and cryptographic operations at the proxy, improving processing efficiency while maintaining security.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If the file sharing proxy server performs decryption and re-encryption of data, then secure file transfer is achieved, but memory resources are consumed for buffering and key management

Engineering Contradiction:
Improvesecure file transferVSAvoidmemory resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

By combining the host and client SSL session keys into a single shared key, the patent eliminates the need for the proxy server to maintain separate key buffers and perform intermediate decryption operations, thereby reducing memory consumption while preserving secure file transfer capabilities.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If the file sharing proxy server establishes separate secure connections with client and host, then connection security is ensured, but device complexity increases

Engineering Contradiction:
Improveconnection securityVSAvoidproxy server complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent simplifies the proxy server architecture by merging the key management systems for host and client connections. Instead of managing separate SSL sessions with different keys, the proxy server uses a single shared key for both connections, reducing cryptographic complexity while maintaining security through the SSL protocol framework.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12328297B1File sharing over secure connections
Publication Date: 2025.06.10 PARALLELS INT GMBH
  • US12328297B1 patent drawing
  • US12328297B1 patent drawing
  • US12328297B1 patent drawing

AI summary

Systems and methods for file sharing over secure connections. An example method comprises: receiving a client request identifying a file sharing host and a file residing on the file sharing host; establishing a secure client connection; responsive to identifying a management connection with the file sharing host, transmitting an identifier and a parameter of the secure client connection via the management connection; receiving a host request to establish a secure host connection, the host request comprising the identifier of the secure client connection; establishing the secure host connection using the parameter of the secure client connection identified by the received identifier; forwarding, over the secure host connection, a first data packet received over the secure client connection, the first data packet comprising at least part of the client request; and forwarding, over the secure client connection, a second data packet received over the secure host connection, the second data packet comprising at least part of the file identified by the client request.