Opened 2 years ago

Closed 18 months ago

#23412 closed defect (fixed)

Do bandwidth authorities reset history when the relay fingerprint changes?

Reported by: Dbryrtfbcbhgf Owned by:
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Normal Keywords: bwauth, security-low
Cc: Actual Points:
Parent ID: #13630 Points: 2
Reviewer: Sponsor:

Description

I deleted all the private keys from my relay and created a new one, within the day of the new one running it’s middle probability jumped up to around what the other relay had after a week of running. Is this a bug?

My relay.
https://atlas.torproject.org/#details/CD8F43AE828C7F9A8B32C6DC9B5D7DABB4D27A97

Child Tickets

Attachments (2)

new relay.png (35.5 KB) - added by Dbryrtfbcbhgf 2 years ago.
old relay.png (44.0 KB) - added by Dbryrtfbcbhgf 2 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 2 years ago by cypherpunks

If that was under the same IP I assume this is normal, no?

comment:2 Changed 2 years ago by Dbryrtfbcbhgf

It is using the same ip. If a attacker would compromise the relay and the keys are revoked, would the attacker be able to create a new relay and get in the same position as the old relay?

comment:3 in reply to:  2 Changed 2 years ago by teor

Component: Core Tor/TorCore Tor/Torflow
Keywords: bwauth security-low added
Owner: set to aagbsn
Points: 2
Summary: I deleted all the private keys from my relay and created a new oneDo bandwidth authorities reset history when the relay fingerprint changes?

Replying to Dbryrtfbcbhgf:

It is using the same ip. If a attacker would compromise the relay and the keys are revoked, would the attacker be able to create a new relay and get in the same position as the old relay?

The new relay doesn't have the Stable or HSDir flags yet. So it won't be used much for a week or so.

The bandwidth authorities measure fingerprints, not IP addresses. So they should reset the usage when the fingerprint changes. (I'm not sure if they reset it when the IP changes.)

We will test this to make sure.

comment:4 Changed 2 years ago by Dbryrtfbcbhgf

Replying to teor:

Replying to Dbryrtfbcbhgf:

It is using the same ip. If a attacker would compromise the relay and the keys are revoked, would the attacker be able to create a new relay and get in the same position as the old relay?

The new relay doesn't have the Stable or HSDir flags yet. So it won't be used much for a week or so.

The bandwidth authorities measure fingerprints, not IP addresses. So they should reset the usage when the fingerprint changes. (I'm not sure if they reset it when the IP changes.)

We will test this to make sure.

My old relay: ​https://atlas.torproject.org/#details/39F5044735BFA39FD959BB0A1161CC3E51225377
My new relay: ​​https://atlas.torproject.org/#details/CD8F43AE828C7F9A8B32C6DC9B5D7DABB4D27A97
I attached photos showing the graphs of my old and new relay, showing that the new relay picks up where the old relay left off "when it comes to middle probability."

Last edited 2 years ago by Dbryrtfbcbhgf (previous) (diff)

Changed 2 years ago by Dbryrtfbcbhgf

Attachment: new relay.png added

Changed 2 years ago by Dbryrtfbcbhgf

Attachment: old relay.png added

comment:5 Changed 2 years ago by teor

Parent ID: #13630

We won't fix this in torflow.

comment:6 Changed 2 years ago by teor

Priorities and Severities in torflow are meaningless, setting them all to Medium/Normal.

comment:7 Changed 2 years ago by teor

Owner: aagbsn deleted
Status: newassigned

aagbsn was the default owner, unassigning

comment:8 Changed 22 months ago by teor

Status: assignednew

Mark all tickets that are assigned to nobody as "new".

comment:9 Changed 18 months ago by teor

Resolution: fixed
Status: newclosed

We are unlikely to do tests like this on torflow.

Note: See TracTickets for help on using tickets.