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
  • #33728

Closed (moved)
(moved)
Open
Created 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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking