With BridgeRelay 1 and ORPort 0, things go bad
A while ago Vidalia set my BridgeRelay to 1 but left my ORPort off. This caused my Tor to make all sorts of weird decisions about what it would contact, what it would fetch, etc. After a while my Tor became useless because it didn't have enough descriptors to make a circuit, and it didn't care to get any more.
We fixed the Vidalia bug (I think), but if a user sets their config this way they will end up sad. We should explore why this is, and tighten up the checks inside Tor.
[Automatically added by flyspray2trac: Operating System: All]