Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33728

Closed (moved)
Open
Opened Mar 25, 2020 by Nick Mathewson@nickm🐙

Make tor-security@ non-schleuder; add tor-security-encrypted@

Tor-security gets huge amounts of spam, making it nigh unusable. Further, most of the people who send email there don't use the gpg key, thus rendering its encryption feature mostly pointless.

I'm proposing this solution:

  • Add a tor-security-encrypted@ list/alias. Give it the same key as tor-security@ used to have. Make it reject unencrypted email.
  • Update the documentation on the wiki to tell people to send tor-security mail to tor-security@, and if they think it's very sensitive to gpg encrypt it and send it to tor-security-encrypted@.
  • Remove schleuder from tor-security@.

I've talked about this with the other tor-security@ subscribers (arma and sysrqb) and they seem okay with it.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33728