Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #32827

Closed (moved)
(moved)
Open
Created Dec 20, 2019 by Roger Dingledine@arma

archive.tpo's rsync logs ip addresses (and it shouldn't)

archive.tpo runs an rsync service, which logs to /var/log/rsyncd/rsyncd-archive.log, which includes lines like

2019/12/20 15:33:05 [7497] connect from UNDETERMINED (128.112.16.131)
2019/12/20 15:33:06 [7497] rsync on dist-mirror/ from UNDETERMINED (128.112.16.131)

In our privacy-oriented web log format, we explicitly don't collect timestamp beyond 'which day', and we scrub IP addresses: #20928 (moved).

We should do something similar for our rsync log format.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking