safelogging should cover hidden service name and intro-points too
In log messages about a hidden service we operate, we don't replace the hidden service name with [scrubbed].
Historically, this was considered fine, because you have your hostname and private_key files on disk already.
But if the user puts his $datadir on encrypted storage, and the logs aren't on encrypted storage, then the logs could be the weak link.
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Roger Dingledine changed milestone to %Tor: unspecified in legacy/trac
changed milestone to %Tor: unspecified in legacy/trac
- Roger Dingledine added component::core tor/tor in Legacy / Trac intro in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac owner::rransom in Legacy / Trac points::5 in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::assigned in Legacy / Trac tor-hs in Legacy / Trac type::defect in Legacy / Trac labels
added component::core tor/tor in Legacy / Trac intro in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac owner::rransom in Legacy / Trac points::5 in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::assigned in Legacy / Trac tor-hs in Legacy / Trac type::defect in Legacy / Trac labels
- Author Reporter
Right now SafeLogging is a tristate -- 0, 1, or relay. "relay" is like 0 with respect to client messages but like 1 with respect to messages about other peoples' traffic.
I think messages about a hidden service you operate should count as client messages, whereas messages about somebody else's hidden service should count as relay messages. (We could make it a quadstate, but I don't think that's needed.)
Trac:
Status: new to assigned
Owner: N/A to rransomA hidden service's introduction points should also be scrubbed.
This task should wait at least until legacy/trac#3045 (moved) is done.
- Owner
Trac:
Milestone: Tor: 0.2.3.x-final to Tor: 0.2.4.x-final Trac:
Cc: N/A to StrangeCharm- Owner
Trac:
Keywords: N/A deleted, tor-hs added - Owner
Trac:
Component: Tor Hidden Services to Tor - Owner
Trac:
Milestone: Tor: 0.2.4.x-final to Tor: 0.2.5.x-final
Summary: safelogging should cover hidden service operation too to safelogging should cover hidden service name and intro-points too - Owner
Trac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.??? - Owner
Trac:
Sponsor: N/A to N/A
Severity: N/A to Normal
Reviewer: N/A to N/A
Points: N/A to medium - Owner
Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.
Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified - Owner
Remove an old triaging keyword.
Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added - Owner
Trac:
Keywords: tor-hs deleted, tor-hs intro added
Points: medium to 5 Trac:
Cc: StrangeCharm to N/A- Trac changed time estimate to 40h
changed time estimate to 40h
- Trac moved from legacy/trac#2743 (moved)
moved from legacy/trac#2743 (moved)
- Trac added First Contribution + 1 deleted label and removed 1 deleted label
added First Contribution + 1 deleted label and removed 1 deleted label
- Nick Mathewson removed Bug label
removed Bug label
- Owner
I'm un-assigning tickets that have seen no activity in 9 months.
- Nick Mathewson unassigned @rransom
unassigned @rransom
- Nick Mathewson removed milestone
removed milestone
- Gaba added Onion Services label and removed 1 deleted label
added Onion Services label and removed 1 deleted label