New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement PRIVCOUNT_HSDIR_CACHE_STORE and counters #336
Comments
|
It is not easy to find the circuit used to upload a particular descriptor. So we won't have any cell counts. HSv2 descriptors do not have a version number: instead, they have a creation timestamp. So we can't do version histograms for v2 without storing descriptor creation times, and then creating our own order. It also requires some work to produce a hidden service address from a v2 descriptor: the address is in the descriptor, but not parsed by existing code. Maybe we should leave it that way, and use the descriptor ID instead. I'll document the differences. |
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the descriptor ID (v2) or blinded public key (v3), intro point count (v2 only), times, sizes, and caching and validation information. It does not contain the hidden service address, or any circuit information. Part of privcount/privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the descriptor ID (v2) or blinded public key (v3), intro point count (v2 only), times, sizes, and caching and validation information. It does not contain the hidden service address, or any circuit information. Part of privcount/privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the descriptor ID (v2) or blinded public key (v3), intro point count (v2 only), times, sizes, and caching and validation information. It does not contain the hidden service address, or any circuit information. Part of privcount/privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the descriptor ID (v2) or blinded public key (v3), intro point count (v2 only), times, sizes, and caching and validation information. It does not contain the hidden service address, or any circuit information. Part of privcount/privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the descriptor ID (v2) or blinded public key (v3), intro point count (v2 only), times, sizes, and caching and validation information. It does not contain the hidden service address, or any circuit information. Part of privcount/privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the onion address (v2) or blinded public key (v3), intro point count (v2 only), client auth flag, times, sizes, and caching and validation information. It does not contain any circuit information. Part of privcount/privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the onion address (v2) or blinded public key (v3), intro point count (v2 only), client auth flag, times, sizes, and caching and validation information. It does not contain any circuit information. Part of privcount/privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the onion address (v2) or blinded public key (v3), intro point count (v2 only), client auth flag, times, sizes, and caching and validation information. It does not contain any circuit information. Part of privcount/privcount#336.
Preparation for privcount#336.
Diagnostic, part of privcount#336.
These counters count: * descriptor stores * intro point counts (HSv2 only) * descriptor and intro point bytes * descriptor upload delays (HSv2 only), and * descriptor revisions (HSv3 only). In the following categories: * cache add/reject, * cache new/existing, * cache action reason, * client auth/no client auth (HSv2 only), Requires a PrivCount Tor Patch that supports EVENT_PRIVCOUNT_HSDIR_CACHE_STORED. Part of privcount#336.
This event is emitted when a HS descriptor is uploaded to a v2 or v3 HSDir. It contains the onion address (v2) or blinded public key (v3), intro point fingerprints and count (v2 only), client auth flag, times, sizes, and caching and validation information. It does not contain any circuit information. Part of privcount/privcount#336.
Using tagged fields for new counters is part of privcount#256. Part of privcount#336.
Diagnostic, part of privcount#336.
These counters count: * descriptor stores * intro point counts (HSv2 only) * descriptor and intro point bytes * descriptor upload delays (HSv2 only), and * descriptor revisions (HSv3 only). In the following categories: * cache add/reject, * cache new/existing, * cache action reason, * client auth/no client auth (HSv2 only). Requires a PrivCount Tor Patch that supports EVENT_PRIVCOUNT_HSDIR_CACHE_STORE. Creating counter variants from template strings is part of privcount#229. Part of privcount#336.
Add privcount/tools/add_counter.sh for initial counter configs. (Bins for multi-bin counters need to be added manually.) Fix the counter match tests for template counters, update to privcount#347. Update test documentation and comments for HSDirStore counters. Part of privcount#336.
With fingerprints, HS Store events can be up to 1kB long. So we now warn at 2kB, reject at 20kB. (Was warn at 1.6kB, reject at 16kB.) Part of privcount#336.
Using tagged fields for new counters is part of privcount#256. Part of privcount#336.
Diagnostic, part of privcount#336.
These counters count: * descriptor stores * intro point counts (HSv2 only) * descriptor and intro point bytes * descriptor upload delays (HSv2 only), and * descriptor revisions (HSv3 only). In the following categories: * cache add/reject, * cache new/existing, * cache action reason, * client auth/no client auth (HSv2 only). Requires a PrivCount Tor Patch that supports EVENT_PRIVCOUNT_HSDIR_CACHE_STORE. Creating counter variants from template strings is part of privcount#229. Part of privcount#336.
Add privcount/tools/add_counter.sh for initial counter configs. (Bins for multi-bin counters need to be added manually.) Fix the counter match tests for template counters, update to privcount#347. Update test documentation and comments for HSDirStore counters. Part of privcount#336.
With fingerprints, HS Store events can be up to 1kB long. So we now warn at 2kB, reject at 20kB. (Was warn at 1.6kB, reject at 16kB.) Part of privcount#336.
Using tagged fields for new counters is part of privcount#256. Part of privcount#336.
Diagnostic, part of privcount#336.
These counters count: * descriptor stores * intro point counts (HSv2 only) * descriptor and intro point bytes * descriptor upload delays (HSv2 only), and * descriptor revisions (HSv3 only). In the following categories: * cache add/reject, * cache new/existing, * cache action reason, * client auth/no client auth (HSv2 only). Requires a PrivCount Tor Patch that supports EVENT_PRIVCOUNT_HSDIR_CACHE_STORE. Creating counter variants from template strings is part of privcount#229. Part of privcount#336.
Add privcount/tools/add_counter.sh for initial counter configs. (Bins for multi-bin counters need to be added manually.) Fix the counter match tests for template counters, update to privcount#347. Update test documentation and comments for HSDirStore counters. Part of privcount#336.
With fingerprints, HS Store events can be up to 1kB long. So we now warn at 2kB, reject at 20kB. (Was warn at 1.6kB, reject at 16kB.) Part of privcount#336.
We can produce the following statistics without storing HS addresses in RAM.
This is safer and simpler (because we don't need to decide on rotation periods).
Less interesting:
Advanced (needs circuit info):
Like Tor trac #13792:
Advanced (needs storage in RAM?):
Research (needs to be turned into a series of statistical questions):
The text was updated successfully, but these errors were encountered: