Opened 4 years ago

Closed 3 years ago

Last modified 3 years ago

#17436 closed enhancement (duplicate)

Expose daily shared random value to the control port

Reported by: asn Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description (last modified by asn)

After we implement prop250, it would be great if we could export the shared random value of the day to the control port.

If we do this, hidden service applications can get it as well and use it for their own application-layer needs. Since the shared random value is global to the whole network, applications can use this in various ways.

For example, you can imagine using this as a sort of replay protection, where a packet needs to have the current random value of the day. Hence, attackers won't be able to replay packets the next day.

Or you could build warrant cannaries on hidden services.

There must be better applications that currently escape me.

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by asn

Description: modified (diff)

comment:2 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-final

comment:3 Changed 4 years ago by dgoulet

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final
Parent ID: #16943
Type: defectenhancement

Moving this one to 029. Also removing parent ID since this doesn't become tied to the feature being merged upstream.

First reason is we probably won't get this in the next month. Second, the more important one, is that we want the shared random to run in 028 without any subsystems nor (ideally) external project using it. This is a precautionary measure in case of bugs that could make the value go bananas or unreliable. So let's not provide an easy way to get the value just yet.

comment:4 Changed 4 years ago by nickm

Points: small

comment:5 Changed 4 years ago by isabela

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

tickets market to be removed from milestone 029

comment:6 Changed 3 years ago by teor

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

Milestone renamed

comment:7 Changed 3 years ago by dgoulet

Resolution: duplicate
Status: newclosed

Closing as a duplicate because of #19925 and for some reason that ticket won ;).

comment:8 Changed 3 years ago by nickm

Milestone: Tor: 0.3.???

Milestone deleted

Note: See TracTickets for help on using tickets.