On Sat, Jun 30, 2018 at 5:22 PM, nusenu nusenu-lists@riseup.net wrote:

tor's man page for OutboundBindAddress* options say:

...

IPv6 addresses should be wrapped in square brackets

since it does not throw an error without square brackets: does it make any difference?

Previously I forgot the square brackets when generating torrc files with relayor and I would like to document the impact of my bug (if there is any).

I posting somewhere about normalizing IPv6 address format, it might have listed the RFC, for which the man page and code was probably inconsistant. Similar to how fingerprints are a mess.

On 1 Jul 2018, at 07:22, nusenu nusenu-lists@riseup.net wrote:

Hi,

tor's man page for OutboundBindAddress* options say:

...

IPv6 addresses should be wrapped in square brackets

since it does not throw an error without square brackets: does it make any difference?

When an option only takes an IP address, it does not make a difference. (As long as the underlying code uses tor_addr_parse().)

When an option takes an IP address and port, the brackets are required to separate the port from the IPv6 address. That's why we say that all IPv6 addresses should have square brackets.

Previously I forgot the square brackets when generating torrc files with relayor and I would like to document the impact of my bug (if there is any).

No impact, but you should use square brackets for consistency.

T