Opened 8 years ago

Closed 7 years ago

#7344 closed defect (fixed)

All PrivacyRepublic exits should have BadExit flag set

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Keywords: tor-auth
Cc: phw Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

All the PrivacyRepublic exits below have a very suspicious exit policy. As of the most recent cached-consensus, the following exits below only allow ports 80 and 110. These should be treated as rogue exits and given the BadExit flag.

5.135.54.66,PrivacyRepublic14
94.23.70.173,PrivacyRepublic02
5.135.54.6,PrivacyRepublic06
5.135.54.8,PrivacyRepublic08
5.135.54.11,PrivacyRepublic11
5.135.54.4,PrivacyRepublic04
94.23.73.182,PrivacyRepublic01
5.135.54.10,PrivacyRepublic10
5.135.54.9,PrivacyRepublic09
5.135.54.65,PrivacyRepublic13
94.23.68.252,PrivacyRepublic03
5.135.54.7,PrivacyRepublic07
5.135.54.64,PrivacyRepublic12
5.135.54.5,PrivacyRepublic05

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by nickm

Component: - Select a componentTor
Keywords: tor-auth added

Tenatively assigning a component. But I think that after emailing them, they set their policies more sensibly. Is this still happening?

comment:2 Changed 7 years ago by nickm

Milestone: Tor: unspecified

comment:3 Changed 7 years ago by cypherpunks

Exit policies here look better now.

p accept 80,443,6667,6697

For all the PrivacyRepublic exits.

comment:4 Changed 7 years ago by arma

Cc: phw added
Resolution: fixed
Status: newclosed

Ok, closing. And cc'ing phw since he's studying this topic.

Note: See TracTickets for help on using tickets.