This tool is designed to allow requests to Tor onion service to be directed to multiple back-end Tor instances, thereby increasing availability and reliability. The design involves collating the set of introduction points created by one or more independent Tor onion service instances into a single ‘master’ descriptor.
This tool is designed to allow requests to Tor onion service to be directed to multiple back-end Tor instances, thereby increasing availability and reliability. The design involves collating the set of introduction points created by one or more independent Tor onion service instances into a single ‘master’ onion service descriptor.
The master descriptor is signed by the onion service permanent key and published to the HSDir system as normal.
Clients who wish to access the onion service would then retrieve the master service descriptor and try to connect to introduction points from the descriptor in a random order. If a client successfully establishes an introduction circuit, they can begin communicating with one of the onion services instances with the normal onion service protocol defined in rend-spec.txt
- A load-balancing node running an individual onion service.
- Introduction Point
- A Tor relay chosen by an onion service instance as a medium-term meeting-place for initial client connections.
- Master Descriptor
- An onion service descriptor published with the desired onion address containing introduction points for each instance.
- Management Server
- Server running OnionBalance which collates introduction points and publishes a master descriptor.
- Metadata Channel
- A direct connection from an instance to a management server which can be used for instance descriptor upload and transfer of other data.
Retrieving Introduction Point Data¶
The core functionality of the OnionBalance service is the collation of introduction point data from multiple onion service instances by the management server.
In the ‘Basic mode` of operation, the introduction point information is transferred from the onion service instances to the management server via the HSDir system. Each instance runs an onion service with an instance specific permanent key. The instance publishes a descriptor to the DHT at regularly intervals or when its introduction point set changes.
On initial startup the management server will load the previously published master descriptor from the DHT if it exists. The master descriptor is used to prepopulate the introduction point set. The management server regularly polls the HSDir system for a descriptor for each of its instances. Currently polling occurs every 10 minutes. This polling period can be tuned for hidden services with shorter or longer lasting introduction points.
When the management server receives a new descriptor from the HSDir system, it should before a number of checks to ensure that it is valid:
- Confirm that the descriptor has a valid signature and that the public key matches the instance that was requested.
- Confirm that the descriptor timestamp is equal or newer than the previously received descriptor for that hidden service instance. This reduces the ability of a HSDir to replay older descriptors for an instance which may contain expired introduction points.
- Confirm that the descriptor timestamp is not more than 4 hours in the past. An older descriptor indicates that the instance may no longer be online and publishing descriptors. The instance should not be included in the master descriptor.
It should be possible for two or more independent management servers to publish descriptors for a single onion service. The servers would publish independent descriptors which will replace each other on the HSDir system.. Any difference in introduction point selection between descriptors should not impact the end user.
- A malicious HSDir could replay old instance descriptors in an attempt to include expired introduction points in the master descriptor. When an attacker does not control all of the responsible HSDirs this attack can be mitigated by not accepting descriptors with a timestamp older than the most recently retrieved descriptor.
- The management server may also retrieve an old instance descriptor as a result of churn in the DHT. The management server may attempt to fetch the instance descriptor from a different set of HSDirs than the instance published to.
- An onion service instance may rapidly rotate its introduction point
circuits when subjected to a Denial of Service attack. An
introduction point circuit is closed by the onion service when it has
max_introductionsfor that circuit. During DoS this circuit rotating may occur faster than the management server polls the HSDir system for new descriptors. As a result clients may retrieve master descriptors which contain no currently valid introduction points.
- It is trivial for a HSDir to determine that a onion service is using OnionBalance when in Basic mode. OnionBalance will try poll for instance descriptors on a regular basis. A HSDir which connects to onion services published to it would find that a backend instance is serving the same content as the master service. This allows a HSDir to trivially determine the onion addresses for a service’s backend instances.
Basic mode allows for scaling across multiple onion service instances with no additional software or Tor modifications necessary on the onion service instance. Basic mode does not hide that a service is using OnionBalance. It also does not significantly protect a service from introduction point denial of service or actively malicious HSDirs.
In Complex mode, introduction point information is uploaded directly from each instance to the management server via an onion service. The onion service instance does not publishing its onion service descriptor to the HSDir system.
A descriptor is uploaded from an instance to its management servers each time Tor generates a new onion service descriptor. A simple daemon running on the onion service instance listens for the event emitted on the Tor control port when a onion service descriptor is generated. The daemon should retrieve the descriptor from the service’s local descriptor cache and upload it to one or more management servers configured for that onion service. The protocol for the metadata channel is not yet defined.
The metadata channel should authorize connecting instance clients using
Multiple management servers for the same onion service may communicate with each other via a hidden service channel. This extra channel can be used to signal when any of the management servers becomes unavailable. A slave management server may begin publishing service descriptors if its master management server is no longer available.
Complex mode requires additional software to be run on the service instances. It also requires more complicated communication via a metadata channel. In practice, this metadata channel may be less reliable than the HSDir system.
The management server communication channel is not implemented yet. The Complex Mode design may be revised significantly before implementation.
Complex mode minimizes the information transmitted via the HSDir system and may make it more difficult for a HSDir to determine that a service is using OnionBalance. It also makes it more difficult for an active malicious HSDir to carry out descriptor replay attacks or otherwise interfere with the transfer of introduction point information. The management server is notified about new introduction points shortly after they are created which will result in more recent descriptor data during very high load or denial-of-service situations.
Choice of Introduction Points¶
Tor onion service descriptors can include a maximum of 10 introduction points. OnionBalance should select introduction points so as to uniformly distribute load across the available backend instances.
Onionbalance will upload multiple distinct descriptors if you have configured more than 10 instances.
- 1 instance - 3 IPs
- 2 instance - 6 IPs (3 IPs from each instance)
- 3 instance - 9 IPs (3 IPs from each instance)
- 4 instance - 10 IPs (3 IPs from one instance, 2 from each other instance)
- 5 instance - 10 IPs (2 IPs from each instance)
- 6-10 instances - 10 IPs (selection from all instances)
- 11 or more instances - 10 IPs (distinct descriptors - selection from all instances)
If running in Complex mode, introduction points can be selected so as to obscure that a service is using OnionBalance. Always attempting to choose 3 introduction points per descriptor may make it more difficult for a passive observer to confirm that a service is running OnionBalance. However behavioral characteristics such as the rate of introduction point rotation may still allow a passive observer to distinguish an OnionBalance service from a standard Tor onion service. Selecting a smaller set of introduction points may impact on performance or reliability of the service.
- 1 instance - 3 IPs
- 2 instances - 3 IPs (2 IPs from one instance, 1 IP from the other instance)
- 3 instances - 3 IPs (1 IP from each instance)
- more than 3 instances - Select the maximum set of introduction points as outlined previously.
It may be advantageous to select introduction points in a non-random manner. The longest-lived introduction points published by a backend instance are likely to be stable. Conversely selecting more recently created introduction points may more evenly distribute client introductions across an instances introduction point circuits. Further investigation of these options should indicate if there is significant advantages to any of these approaches.
Generation and Publication of Master Descriptor¶
The management server should generate a onion service descriptor containing the selected introduction points. This master descriptor is then signed by the actual onion service permanent key. The signed master descriptor should be published to the responsible HSDirs as normal.
Clients who wish to access the onion service would then retrieve the ‘master’ service descriptor and begin connect to introduction points at random from the introduction point list. After successful introduction the client will have created an onion service circuit to one of the available onion services instances and can then begin communicating as normally along that circuit.
Next-Generation Onion Services (Prop 224) Compatibility¶
In the next-generation onion service proposal (Prop224), introduction point keys will no longer be independent of the instance/descriptor permanent key. The proposal specifies that each introduction point authentication key cross-certifies the descriptor’s blinded public key. Each instance must know the master descriptor blinded public key during descriptor generation.
One solution is to operate in the Complex mode described previously. Each instance is provided with the descriptor signing key derived from the same master identity key. Each introduction point authentication key will then cross-certify the same blinded public key. The generated service descriptors are not uploaded to the HSDir system. Instead the descriptors are passed to the management server where introduction points are selected and a master descriptor is published.
Alternatively a Tor control port command could be implemented to allow a controller to request a onion service descriptor which has each introduction point authentication key cross-certify a blinded public key provided in the control port command. This would remove the need to provide any master service private keys to backend instances.
The descriptor signing keys specified in Prop224 are valid for a limited period of time. As a result the compromise of a descriptor signing key does not lead to permanent compromise of the onion service