-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Dear all,
The Tor Manual [1], as of today, says that ORListenAddress option is deprecated and that same behaviour can be achieved by specifying the listening address within the ORPort option.
Although using ORPort to specify listening address works as expected whit tor, it causes arm to crash, see ticket #9269 [2].
You guys know how much relay operators rely on arm to check on their babies, and having tor operate on a specific IP address may not be such an uncommon practice.
I don't know how both tor and arm projects coordinate their efforts, if they do, so the big question is :
Can users expect support for ORListenAddress at least untill ticket #9269 is closed ?
That would be nice
[1] https://www.torproject.org/docs/tor-manual.html.en [2] https://trac.torproject.org/projects/tor/ticket/9269
- -- Frédéric CORNU http://wardsback.org
On Thu, Jan 22, 2015 at 1:12 AM, Frédéric CORNU fcornu@wardsback.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Dear all,
The Tor Manual [1], as of today, says that ORListenAddress option is deprecated and that same behaviour can be achieved by specifying the listening address within the ORPort option.
Although using ORPort to specify listening address works as expected whit tor, it causes arm to crash, see ticket #9269 [2].
You guys know how much relay operators rely on arm to check on their babies, and having tor operate on a specific IP address may not be such an uncommon practice.
I don't know how both tor and arm projects coordinate their efforts, if they do, so the big question is :
Can users expect support for ORListenAddress at least untill ticket #9269 is closed ?
I'm not planning to remove ORListenAddress any time soon. Maybe in 0.2.7 or 0.2.8, I guess.
-
Frédéric CORNU -
Nick Mathewson