Tor  0.4.3.0-alpha-dev
Data Fields
hs_service_state_t Struct Reference

#include <hs_service.h>

Data Fields

time_t intro_circ_retry_started_time
 
unsigned int num_intro_circ_launched
 
replaycache_t * replay_cache_rend_cookie
 
time_t next_rotation_time
 

Detailed Description

Service state.

Definition at line 258 of file hs_service.h.

Field Documentation

◆ intro_circ_retry_started_time

time_t intro_circ_retry_started_time

The time at which we've started our retry period to build circuits. We don't want to stress circuit creation so we can only retry for a certain time and then after we stop and wait.

Definition at line 262 of file hs_service.h.

Referenced by can_service_launch_intro_circuit(), and move_hs_state().

◆ next_rotation_time

time_t next_rotation_time

When is the next time we should rotate our descriptors. This is has to be done at the start time of the next SRV protocol run.

Definition at line 277 of file hs_service.h.

Referenced by move_hs_state(), set_rotation_time(), and should_rotate_descriptors().

◆ num_intro_circ_launched

unsigned int num_intro_circ_launched

Number of circuit we've launched during a single retry period. This should never go over MAX_INTRO_CIRCS_PER_PERIOD.

Definition at line 266 of file hs_service.h.

Referenced by can_service_launch_intro_circuit(), and move_hs_state().

◆ replay_cache_rend_cookie

replaycache_t* replay_cache_rend_cookie

Replay cache tracking the REND_COOKIE found in INTRODUCE2 cell to detect repeats. Clients may send INTRODUCE1 cells for the same rendezvous point through two or more different introduction points; when they do, this keeps us from launching multiple simultaneous attempts to connect to the same rend point.

Definition at line 273 of file hs_service.h.

Referenced by hs_circ_handle_introduce2(), and move_hs_state().


The documentation for this struct was generated from the following file: