Opened 4 years ago

Closed 3 years ago

Last modified 3 years ago

#16846 closed enhancement (wontfix)

Include sizeof(void *) in your extrainfo.

Reported by: yawning Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Normal Keywords: tor-core, extrainfo, metrics, lorax, 028-triage easy
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

From #16535, it appears that it would be useful to get an idea of how much x86 vs x86_64 we have as part of the tor network. If we don't also include CPU architecture information, it would be good to have that as well if we can do it safely.

Child Tickets

Change History (10)

comment:1 Changed 4 years ago by nickm

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

comment:2 Changed 4 years ago by nickm

Keywords: 028-triage added

comment:3 Changed 4 years ago by mikeperry

FWIW, this seems OK to gather in aggregate, but I am a bit nervous about exposing specific platform details in individual extra-info since that will aid in targeted attacks. For example, ASLR is significantly weaker on 32 bit systems. Similarly, the attacker will know that things like ASAN could not have been used to build the Tor binary on a 32 bit system (and so has much less risk of an 0day being captured by a 32 bit relay operator).

comment:4 Changed 4 years ago by nickm

Keywords: easy added
Points: small

comment:5 Changed 4 years ago by nickm

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

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

comment:6 Changed 3 years ago by arma

Severity: Normal

I wonder what are some ways to gather this info in aggregate?

Maybe the privex style approach? That sure would be overkill for just this.

But maybe we have a big pile of things that we wanted to learn in aggregate, making the effort worthwhile?

Do we actually have other things, or should we close this ticket as won't-ever-do, or should we leave it open in case the world is different in a few years?

comment:7 Changed 3 years ago by yawning

The original reason for wanting this, isn't so valid anymore.

It'd still be nice to know what sort of microarchitecture people tend to run relays on, so further hardware specific optimization efforts can be targeted, but that's more of a stat than "is it a 64 bit architecture".

comment:8 Changed 3 years ago by nickm

Resolution: wontfix
Status: newclosed

ok; closing as wontfix then. Please reopen if I misunderstand.

comment:9 Changed 3 years ago by teor

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

Milestone renamed

comment:10 Changed 3 years ago by nickm

Milestone: Tor: 0.3.???

Milestone deleted

Note: See TracTickets for help on using tickets.