Include sizeof(void *) in your extrainfo.

From #16535 (moved), 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.

added 028-triage component::core tor/tor easy extrainfo lorax metrics points::small priority::medium resolution::wontfix severity::normal status::closed tor-core type::enhancement version::tor unspecified labels

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.8.x-final

Trac:
Keywords: N/A deleted, 028-triage added

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).

Trac:
Sponsor: N/A to N/A

Trac:
Points: N/A to small
Keywords: 028-triage deleted, 028-triage easy added

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 ???.

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

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?

Trac:
Severity: N/A to Normal
Reviewer: N/A to N/A

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".

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

Trac:
Status: new to closed
Resolution: N/A to wontfix

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Milestone deleted

Trac:
Milestone: Tor: 0.3.??? to N/A

closed

moved to tpo/core/tor#16846 (closed)