Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#5216 closed enhancement (wontfix)

Create new exit policy flag for encrypted-only traffic

Reported by: yawnbox Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I run an Exit node but am not flagged as an Exit node.

ExitPolicy accept *:119 # accept nntp as well as default exit policy
ExitPolicy accept *:22 # ssh
ExitPolicy accept *:443 # https (HTTP via TLS)
ExitPolicy accept *:465 # smtps (SMTP over SSL)
ExitPolicy accept *:993 # imaps (IMAP over SSL)
ExitPolicy accept *:994 # ircs (IRC over SSL)
ExitPolicy accept *:995 # pop3s (POP3 over SSL)
ExitPolicy reject *:* # no exits allowed

I'd like to have the spec changed/added for recognition of encrypted-only exit nodes.

Child Tickets

Change History (4)

comment:1 Changed 9 years ago by Sebastian

Resolution: wontfix
Status: newclosed

Not having the Exit flag is fine in your case, it is there only for load balancing reasons. You're still used and recognized as an exit node, and thanks for running it, too!

Nevertheless, this is a wontfix because adding a new flag doesn't really make sense as flags are for internal use of Tor. Maybe you'd instead want this to be fixed in torstatus or so, so that exit nodes without the flag get marked as exits?

comment:2 Changed 9 years ago by rransom

Component: - Select a componentTor Relay

comment:3 Changed 8 years ago by nickm

Keywords: tor-relay added

comment:4 Changed 8 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.