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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed
Open
Opened Jun 03, 2011 by Roger Dingledine@arma

exit policy checkbox 80 should imply checkbox 443

Right now you can choose whether to exit to port 80 and whether to exit to port 443.

I originally suggested this separation so you could check the 443 box without checking the 80 box.

It turns out that if you check the 80 box without checking the 443 box, Mike will set the badexit flag for your relay.

Option 1: if you click the 80 box, the 443 box gets clicked automatically.

Option 2: change the meaning of the 80 box so it means "80, 443", and change the text "secure web browsing" to "only secure web browsing".

Option 3: Remove the option to allow 443 without allowing 80. That is, make it just one checkbox, called 'web browsing', and get rid of the 443 box entirely.

I like option 1 best so far. But the actual rules might get messy, like, if you try to unclick the 443 box, should it mysteriously not work, or should it auto unclick the 80 box too? Probably the latter, but yuck. So maybe that argues for option 3.

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