Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #3599
Closed (moved) (moved)
Open
Created Jul 15, 2011 by Nick Mathewson@nickm🐛

Microdescriptor policy comparison handles "unspec" incorrectly

If you start a microdesc client and wait a while, you'll start to see lots of "No exits can handle address [scrubbed]" messages.

This happens because the uint32_t value 0 is used in address policy comparison code to mean both the address 0.0.0.0 and "no address known". 0.0.0.0 is blocked by everybody, so compare_tor_addr_to_short_policy() says "reject" for everybody.

I'm not currently quite sure why it take so long for this to trigger.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking