#29863: Add disk space monitoring for snowflake infrastructure -----------------------------------+------------------------------ Reporter: cohosh | Owner: (none) Type: task | Status: needs_review Priority: Medium | Milestone: Component: Obfuscation/Snowflake | Version: Severity: Normal | Resolution: Keywords: snowflake | Actual Points: Parent ID: #30152 | Points: Reviewer: | Sponsor: Sponsor19 -----------------------------------+------------------------------
Comment (by anarcat): @cohosh do you mind dumping the result of `curl localhost:9100/metrics | grep '# HELP'` so that people can evaluate what metrics are currently available here and therefore judge the impact of a possible disclosure? my current opinion (yes, it changes! :)) is that we should not export metrics that are sensitive in the first place. this would alleviate the need for stronger (but also more complex) authentication systems on the monitoring servers which could then stay in the "semi-public" mode they have always been. the problem is we have a two-dimension matrix of servers right now, based on those parameters: * external/internal * private/public .. which would mean four monitoring servers. :p too complicated. let's drop that second part and stick with external/internal as a distinction. how does that sound? if we clear the exporters so that the stuff they generate is safe (a good idea anyways, given they lack authentication themselves, other than IP-level blocking), it seems that the private/public distinction isn't necessary anymore... -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29863#comment:21> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs