#15015: tor --verify-config should not bind to ports -------------------------------------------------+------------------------- Reporter: cypherpunks | Owner: Type: defect | Status: | assigned Priority: Medium | Milestone: Tor: | 0.3.??? Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-relay, 027-triaged-1-out, intro | Actual Points: Parent ID: | Points: small Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by teor): Hmm, there are two different use cases here: 1) I am not running a relay, and I'm about to start one, and I want to know if it will work, 2) I am running a relay, and I'm about to change the config, and I want to know if it will work We can bind to ports in case 1), but not case 2). I think we should add a new option `--parse-config` that just does an options_verify(). Of course, the risk is that it will succeed, and then when it gets to options_act(), it will fail because it suddenly finds out it can't do what it wanted to do. But for `--verify-config`, the risk is that it will fail unnecessarily, because it could do the things if only it were the existing tor process. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15015#comment:13> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs