new ip-address for tor.dizum.com (auth-dir)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Guys,

tor.dizum.com has changed it's IP address. As tor.dizum.com is a directory server, it's ip address is hardcoded in the source code.

Please update the ip.

OLD: 194.109.206.212
NEW: 45.66.33.45

You can verify and validate this change by either
1) retrieving the ip for tor.dizum.com.
2) contact alex, by email or by phone or on irc to verify this change.
3) you could read the announcement at the dir-auth list.

-----BEGIN PGP SIGNATURE-----
Version: BCPG v1.47

iGYEARECACYFAl1RuckfHEFsZXggZGUgSm9vZGUgPGFsZXhAaWRnYXJhLm5sPgAK
CRB4AD5zEX0r0DQsAJwN+/zRHTRgIiiXps8Lw0NieQgFpACgoz/YHdlt/X2YMQQL
bpY/OwGavRE=
=SFAn
-----END PGP SIGNATURE-----

changed milestone to %Tor: 0.2.9.x-final

added 029-backport 035-backport 040-backport 041-backport actualpoints::0.2 component::core tor/tor dir-auth ip milestone::Tor: 0.2.9.x-final nickm-merge points::0.2 priority::high resolution::implemented reviewer::teor severity::critical status::closed type::task labels

Trac:
tor-sig.txt

pgp signed text

Trac:
Description: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi Guys,

tor.dizum.com has changed it's IP address. As tor.dizum.com is a directory server, it's ip address is hardcoded in the source code.

Please update the ip.

OLD: 194.109.206.212 NEW: 45.66.33.45

You can verify and validate this change by either

1. retrieving the ip for tor.dizum.com.
2. contact alex, by email or by phone or on irc to verify this change.
3. you could read the announcement at the dir-auth list.

-----BEGIN PGP SIGNATURE----- Version: BCPG v1.47

iGYEARECACYFAl1RuckfHEFsZXggZGUgSm9vZGUgPGFsZXhAaWRnYXJhLm5sPgAK CRB4AD5zEX0r0DQsAJwN+/zRHTRgIiiXps8Lw0NieQgFpACgoz/YHdlt/X2YMQQL bpY/OwGavRE= =SFAn -----END PGP SIGNATURE-----

to

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Guys,

tor.dizum.com has changed it's IP address. As tor.dizum.com is a directory server, it's ip address is hardcoded in the source code.

Please update the ip.

OLD: 194.109.206.212
NEW: 45.66.33.45

You can verify and validate this change by either
1) retrieving the ip for tor.dizum.com.
2) contact alex, by email or by phone or on irc to verify this change.
3) you could read the announcement at the dir-auth list.

-----BEGIN PGP SIGNATURE-----
Version: BCPG v1.47

iGYEARECACYFAl1RuckfHEFsZXggZGUgSm9vZGUgPGFsZXhAaWRnYXJhLm5sPgAK
CRB4AD5zEX0r0DQsAJwN+/zRHTRgIiiXps8Lw0NieQgFpACgoz/YHdlt/X2YMQQL
bpY/OwGavRE=
=SFAn
-----END PGP SIGNATURE-----

Priority: Very High to High
Milestone: N/A to Tor: 0.4.2.x-final

We can confirm that the new IP is signed by dizum's relay and authority keys, because the consensus contains the new IP. (All 9 authorities have checked the signature on dizum's descriptor and vote, which both contain the new IP.)

dir-source dizum E8A9C45EDE6D711294FADF8E7951F4DE6CA56B58 45.66.33.45 45.66.33.45 80 443
contact 1024R/8D56913D Alex de Joode <adejoode@sabotage.org>
vote-digest 159D8D8D8174DE8F866A552D27A3CD809DDC062F
…
r dizum fqbq1v2DCDxTj0QDi7+gd1h911U GZmZtCLaPDQNxkhIFj8UcgTRAuA 2019-08-12 15:28:40 45.66.33.45 443 80
s Authority Fast Running Stable V2Dir Valid
v Tor 0.4.0.5
pr Cons=1-2 Desc=1-2 DirCache=1-2 HSDir=1-2 HSIntro=3-4 HSRend=1-2 Link=1-5 LinkAuth=1,3 Microdesc=1-2 Relay=1-2 Padding=1
w Bandwidth=20 Unmeasured=1
p reject 1-65535

Trac:
Type: defect to task
Keywords: ip dir-auth deleted, ip dir-auth 029-backport 035-backport 040-backport 041-backport added
Points: N/A to 0.2

armadev says: i think doing [a backport release] just for a new dizum ip address is borderline. since the old address will work for a long while yet (years, was alex's estimate)

Patch is here: ticket31406_042_01

I've signed the commit also with my key.

Trac:
Status: new to needs_review

Replying to teor:

armadev says: i think doing [a backport release] just for a new dizum ip address is borderline. since the old address will work for a long while yet (years, was alex's estimate)

We still need backport branches for the new IP address, even if we won't do releases straight away.

If you make an 0.2.9 branch, you can create test branches using the new "-t" option to git-merge-forward.sh: https://trac.torproject.org/projects/tor/ticket/31314#comment:5

It hasn't been merged yet, so you'll need to copy it from the PR.

Trac:
Status: needs_review to needs_revision

029 branch: ticket31406_029_01

It merges forward cleanly up to master.

Trac:
Status: needs_revision to needs_review

Trac:
Reviewer: N/A to asn
Keywords: ip dir-auth 029-backport 035-backport 040-backport 041-backport deleted, ip dir-auth 029-backport 035-backport 040-backport 041-backport nickm-merge added

There's no CI, but I'm going to assume it passes, because it's a simple IPv4 address change.

Let's merge it to 0.2.9 and later straight away.

Trac:
Status: needs_review to merge_ready
Reviewer: asn to teor

Merged to 0.2.9 and forward.

Trac:
Status: merge_ready to closed
Resolution: N/A to implemented

Fix backport release, or it will show up in my "missed backports" list.

Trac:
Actualpoints: N/A to 0.2
Milestone: Tor: 0.4.2.x-final to Tor: 0.2.9.x-final

closed

changed time estimate to 1h 36m

added 1h 36m of time spent