Proxy Auto-Configuration File Privacy Protection via Hash Values
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing proxy auto-configuration files expose enterprise rules and resource identities when using plaintext values, compromising privacy and network security by allowing unauthorized parties to determine access routes through or bypassing proxy servers.
Innovation Solution
Generating proxy auto-configuration files that include hash values instead of plaintext values for resource identifiers, with a function that determines whether to route requests through or bypass a proxy server based on these hash values, thereby obscuring resource identities and protecting privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proxy auto-configuration files use plaintext values for resource identifiers, then routing functionality is simple and direct, but privacy and network security are compromised as enterprise rules and resource identities are exposed
Solution Approach 1:
The patent transforms resource identifiers from plaintext form to hashed form by changing the parameter representation. Instead of using readable strings like 'example.com' or 'internal-resource', the system applies hash functions to convert these into opaque hexadecimal values. This parameter transformation maintains the functional ability to route traffic while eliminating the security vulnerability of exposing resource identities in the configuration file.
Solution Approach 2:
The patent introduces a hash value as an intermediary between the resource identifier and the routing logic. The hash acts as a mediator that preserves the routing functionality (matching the hash against stored values to determine proxy usage) while preventing direct observation of the actual resource identities. This intermediary layer decouples the routing mechanism from the exposed configuration data.
2Loss of information
If hash values are used instead of plaintext values in proxy auto-configuration files, then privacy and network security are improved, but the complexity of determining routing rules increases
Solution Approach 1:
The patent applies preliminary action by pre-computing hash values for all resource identifiers before they are stored in the proxy auto-configuration file. During the setup phase, the system takes each resource identifier, applies the hash function, and stores the resulting hash value. This preliminary transformation ensures that when the browser later needs to determine routing rules, it only needs to hash the current URL and compare against pre-stored hashes, rather than dealing with complex plaintext matching logic.
Solution Approach 2:
The patent substitutes the mechanical system of plaintext string matching with a cryptographic hash-based comparison system. Instead of comparing readable resource identifiers directly (which would require complex pattern matching and could expose information), the system replaces this with hash value comparison. The browser computes a hash of the current URL and compares it against stored hash values, providing a more efficient and secure mechanism that protects privacy while maintaining routing functionality.
Data Source
AI summary
A method may include generating a proxy auto-configuration file including a function and a hash value associated with a resource. The hash value may be determined based on an identifier of the resource. The proxy auto-configuration file may include the hash value instead of a plaintext value of the identifier to obscure the plaintext value of the identifier. The proxy auto-configuration file including the function and the hash value may be sent to at least enable the function to be invoked by a web browser at one or more clients. The function may be configured to respond to being invoked by the web browser by determining, based on the hash value, whether to bypass a proxy server when accessing the resource. Related systems and computer program products are also provided.