Opened 6 years ago

Closed 6 years ago

#11043 closed task (implemented)

Improve the "You should enable Extended ORPort" log message.

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-bridge tor-pt
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by asn)

As can be seen in
https://lists.torproject.org/pipermail/tor-relays/2014-February/003908.html
people get confused about the new "You should enable Extended ORPort" log message.

This is kind of related to #10957 , but in this ticket we should figure out a better log message for the short term.

We currently log:

We are a bridge with a pluggable transport
proxy but the Extended ORPort is disabled. The Extended ORPort helps Tor
communicate with the pluggable transport proxy. Please enable it using
the ExtORPort torrc option.

we should at least mention that users can simply put ExtORPort auto in their torrc to fix this issue. And maybe we should include an online link to further documentation about ExtORPort.

Child Tickets

Change History (8)

comment:1 Changed 6 years ago by asn

Milestone: Tor: 0.2.5.x-final

comment:2 Changed 6 years ago by asn

Description: modified (diff)

comment:3 Changed 6 years ago by asn

How about this new message:

We use pluggable transports but the Extended ORPort is disabled. Tor
and your pluggable transport proxy communicate with each other via the
Extended ORPort so it is suggested you enable it: it will also allow
your Bridge to collect statistics about its clients that use pluggable
transports.  Use the ExtORPort torrc option to enable it (e.g. set
'ExtORPort auto').

It's not a great improvement but at least it explains how to enable the Extended ORPort.

If we want to do it better, we could make an informative page about Extended ORPort somewhere around https://www.torproject.org/docs/pluggable-transports , mention the URL in the log message and point people there. You think it's worth it?

comment:4 Changed 6 years ago by nickm

Something like that seems fine; patch welcome.

comment:5 Changed 6 years ago by asn

Status: newneeds_review

Please see branch bug11043 in https://git.torproject.org/user/asn/tor.git.

BTW, I noticed that this log message happens before we drop privileges, which means that it doesn't appear in logfiles. Do you think we should move the log message after we drop privileges and start writing to the logfile? (I wonder which function I should use inside config.c for this)

comment:6 Changed 6 years ago by nickm

looks ok but needs a changes file.

To do it later, you could move it into options_act().

comment:7 Changed 6 years ago by asn

OK. Please see branch bug11043_take2 at https://git.torproject.org/user/asn/tor.git.

I was also considering bumping up the log severity to warn, but I decided against it.

comment:8 Changed 6 years ago by nickm

Resolution: implemented
Status: needs_reviewclosed

squashed and merged; thanks!

Note: See TracTickets for help on using tickets.