Opened 6 years ago

Closed 12 months ago

Last modified 12 months ago

#6773 closed enhancement (duplicate)

DirServer lines should take more than one "orport="

Reported by: ln5 Owned by:
Priority: Medium Milestone: Tor: 0.2.8.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, tor-dirauth, good-idea easy
Cc: Actual Points: 0
Parent ID: Points: 2
Reviewer: Sponsor:

Description

In order for clients and relays to be able to contact an authority
server over IPv6 we should expand the DirServer line to accept more
than one OR port.

Do we prefer "orport=ADDR0,ADDR1,..." or "orport=ADDR0 orport=ADDR1 ..."?
Or perhaps something completely different?

Note that an ADDR will be IP-ADDRESS ":" PORT-NUMBER rather than
todays PORT-NUMBER..

We need to

  • add field(s) to trusted_dir_server_t
  • fix the parsing in parse_dir_server_line(), probably by calling tor_addr_port_lookup().

We also need #6772 (Fall back to alternative OR port if the current
fails) to be implemented for this to be useful, f.ex. in
directory_post_to_dirservers().

Child Tickets

Change History (20)

comment:1 Changed 6 years ago by nickm

I prefer having multiple orport= entries. So "orport=ADDR0 orport=ADDR1 ..." seems fine.

I'd like to keep the current behavior of allowing PORT-NUMBER on its own to work too, so that existing test network configurations don't break.

comment:2 in reply to:  1 Changed 6 years ago by ln5

Replying to nickm:

I'd like to keep the current behavior of allowing PORT-NUMBER on its own to work too, so that existing test network configurations don't break.

Oh, I _meant_ to say [IP-ADDRESS ":"] PORT-NUMBER. Thanks.

comment:3 Changed 6 years ago by nickm

Keywords: tor-auth added

comment:4 Changed 6 years ago by nickm

Component: Tor Directory AuthorityTor

comment:5 Changed 6 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

Bumping to 0.2.5, along with other remaining noncritical enhancements.

comment:6 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:7 Changed 3 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.8.x-final

comment:8 Changed 3 years ago by nickm

Points: small

comment:9 Changed 3 years ago by teor

Parent ID: #6027
Severity: Normal

comment:10 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

It is impossible that we will fix all 226 currently open 028 tickets before 028 releases. Time to move some out. This is my second pass through the "new" and tickets, looking for things to move to 0.2.9.

comment:11 Changed 3 years ago by isabela

Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

tickets market to be removed from milestone 029

comment:12 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:13 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:14 Changed 18 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:15 Changed 18 months ago by dgoulet

Keywords: tor-dirauth added; tor-auth removed

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

comment:16 Changed 18 months ago by nickm

Keywords: good-idea easy added
Points: small2

comment:17 Changed 12 months ago by aruna1234

Hey! I am a beginner! Can I work on this?

comment:18 Changed 12 months ago by ln5

This wouldn't hurt, but also wouldn't help much until #6772 is implemented i think.

comment:19 Changed 12 months ago by teor

Actual Points: 0
Milestone: Tor: unspecifiedTor: 0.2.8.x-final
Resolution: duplicate
Status: newclosed

Hi aruna1234,

Thanks for being keen to help out with Tor!
It turns out that we already implemented this a few years ago when we gave authorities and fallback directories an "ipv6=" field in #17327.
But we never closed this ticket. Oops!

If you want to work on a similar intro ticket, try #24338.

(And I don't think we'll ever want more than one IPv4 or IPv6 address.)

comment:20 Changed 12 months ago by aruna1234

Okay! thanks for the prompt reply!

Note: See TracTickets for help on using tickets.