chutney reads the system torrc when generating the router key

This can easily be demonstrated by adding an invalid option to /etc/tor/torrc and then running chutney configure. This feels wrong, and will fail if you run a hidden service on the system-wide Tor instance.

added component::core tor/chutney owner::nickm priority::medium resolution::fixed severity::normal status::closed type::defect labels

Trac:
do_not_use_system_torrc.patch

The patch I've attached fixes the issue for me. I'm not sure if this is the ideal solution, but feel free to apply it if you think it is good enough.

The last patch had a little mistake: it removed net/.empty, which is wrong. Here's is a corrected version.

Trac:
Username: bertagaz

Trac:
Cc: N/A to teor

Trac:
Status: new to needs_review

This patch looks sensible to me, but I have yet to test it.

The patch does not apply cleanly and seems to contain bits from #18826 (moved).

Trac:
0001-Do-not-use-the-system-torrc-when-generating-router-k.patch

Corrected version of the patch.

Replying to cypherpunks:

The patch does not apply cleanly and seems to contain bits from #18826 (moved).

Sorry for that, should be fixed now!

Can confirm this does work on my system. I ran into this bug today. Thank you for the fix!

Thanks for the patch!

Merged to chutney master after testing using a make test-network-all with tor master.

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

closed

moved to tpo/core/chutney#18882 (closed)