bug7157 1.5 KB

1234567891011121314151617181920212223242526
  1. o Minor features:
  2. - Alter the Path Bias log messages to be more descriptive in terms
  3. of reporting timeouts and other statistics.
  4. - Create three levels of Path Bias log messages, as opposed to just
  5. two. These are configurable via consensus as well as via torrc
  6. options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
  7. The default values are 0.70, 0.50, and 0.30 respectively.
  8. - Separate the log message levels from the decision to drop guards,
  9. which also is available via torrc option PathBiasDropGuards.
  10. PathBiasDropGuards defaults to 0 (off).
  11. - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
  12. in combination with PathBiasExtremeRate.
  13. - Increase the default values for PathBiasScaleThreshold and
  14. PathBiasCircThreshold from 200 and 20 to 300 and 150, respectively.
  15. - Add in circuit usage accounting to path bias. If we try to use a
  16. built circuit but fail for any reason, it counts as path bias.
  17. Certain classes of circuits where the adversary gets to pick your
  18. destination node are exempt from this accounting. Usage accounting
  19. can be specifically disabled via consensus parameter or torrc.
  20. - Convert all internal path bias state to double-precision floating
  21. point, to avoid roundoff error and other issues.
  22. - Only record path bias information for circuits that have completed
  23. *two* hops. Assuming end-to-end tagging is the attack vector, this
  24. makes us more resilient to ambient circuit failure without any
  25. detection capability loss.