PublishServerDescriptor allows options 0 and 1 simultaneously

That doesn't make sense, and I think we should reject a config like that.

[Automatically added by flyspray2trac: Operating System: All]

changed milestone to %Tor: 0.2.2.x-final in legacy/trac

added component::core tor/tor in Legacy / Trac easy in Legacy / Trac milestone::Tor: 0.2.2.x-final in Legacy / Trac priority::low in Legacy / Trac resolution::fixed in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac version::0.2.1.19 in Legacy / Trac labels

Hm. My inclination would be to warn if 0 or 1 is given in a list that is not a one-element list. It is not reasonable for either one to appear except on its own.

Then we can change the warning to a "reject the configuration" in 0.2.3.x.

Trac:
Milestone: N/A to Tor: 0.2.2.x-final
Parent: N/A to N/A
Keywords: N/A deleted, easy added

Trac:
0001-Bug-1107-Complain-if-PublishServerDescriptor-receive.patch

Attached a tested patch. Please review carefully, since I'm still new to the codebase; thanks.

Trac:
0002-Bug-1107-Complain-if-PublishServerDescriptor-receive.patch

patch v2

Attached v2 of the patch. Changes:

• Fix a check-spaces warning due to 80-char line
• Explain when the bug was introduced in the changes file.

Looks good to me now; thanks!

Trac:
Description: That doesn't make sense, and I think we should reject a config like that.

[Automatically added by flyspray2trac: Operating System: All]

to

That doesn't make sense, and I think we should reject a config like that.

[Automatically added by flyspray2trac: Operating System: All]

Trac:
Status: new to needs_review

Looks fine; merging. [You could also have used smartlist_string_isin().]

Trac:
Status: needs_review to closed
Resolution: None to fixed

Trac:
Component: Tor Client to Tor

closed

moved from legacy/trac#1107 (moved)

added Bug First Contribution labels and removed 1 deleted label

removed 1 deleted label