Chutney fails when Tor is built with --enable-nss

We should get chutney passing when Tor is built with --enable-nss. Currently, it fails for two reasons:

• tor-gencert is not built with NSS.
• If you use a copy of a working tor-gencert, some of the chutney tests fail.

changed milestone to %Tor: unspecified in legacy/trac

added 041-deferred-20190530 in Legacy / Trac CI in Legacy / Trac component::core tor/tor in Legacy / Trac ex-sponsor-19 in Legacy / Trac ex-sponsor19 in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tor-ci in Legacy / Trac type::defect in Legacy / Trac labels

Trac:
Keywords: N/A deleted, tor-ci added

Marking these tickets as deferred from 041.

Trac:
Keywords: N/A deleted, 041-deferred-20190530 added

Trac:
Milestone: Tor: 0.4.1.x-final to Tor: unspecified

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

Trac:
Keywords: N/A deleted, ex-sponsor-19 added

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

Trac:
Keywords: N/A deleted, ex-sponsor19 added
Sponsor: Sponsor19-can to N/A

Trac:
Parent: legacy/trac#29280 (moved) to N/A

moved from legacy/trac#29491 (moved)

added Bug label and removed 1 deleted label

added Deferred label and removed 1 deleted label

added NSS label

added 1 deleted label

removed milestone

added BugSmashFund label

added Technical Debt label and removed 1 deleted label

Not currently planned.

closed