[tor-bugs] #5376 [Tor Relay]: The ExitPolicyRejectPrivate option seems to be ignored

[Tor Bug Tracker & Wiki]

#5376: The ExitPolicyRejectPrivate option seems to be ignored
-----------------------+----------------------------------------------------
 Reporter:  kevin      |          Owner:                    
     Type:  defect     |         Status:  new               
 Priority:  normal     |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:                    
 Keywords:             |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by kevin):

 Indeed, you are correct. The clients are connecting to the live directory
 authorities, seemingly still having trouble with the TestingTorNetwork
 option (and maybe the DirServer option, too?). Here's an example client
 configuration, following the workaround directions of
 [https://trac.torproject.org/projects/tor/ticket/5373 Ticket 5373]. The
 torrc config file passed via the command line with --defaults-torrc:

 {{{
 SafeLogging 0
 ReachableAddresses 10.0.0.0/8
 ReachableORAddresses 10.0.0.0/8
 TestingTorNetwork 1
 ControlPort 5100
 DirServer router1 v3ident=2742779FAA4C08DD1A400AAA4F8CBA5317C1CC8C
 orport=6001 !10.0.0.1:20001 2A7A C69C EEE2 5573 899F A598 0752 898E 777F
 6107
 DirServer router2 v3ident=F43C5503929B0E4A1A93026C6810CD9C3C9FC95E
 orport=6002 !10.0.0.2:20002 B5D9 0AE9 DF3C 8F3B FFFB FE67 883A 1F38 A3FF
 4E22
 DirServer router3 v3ident=AA4DA69D8655E48BA271F561C9AFF81F5E31779A
 orport=6003 !10.0.0.3:20003 7DEA F408 F641 A82E 1FF9 4EB1 EE0E 250E EFF5
 A433
 DirServer router4 v3ident=665CE5F47C7212954EDC1A80E65123E7CA5572DE
 orport=6004 !10.0.0.4:20004 4475 A1B8 B4C4 7BBA BFBA 4699 1FA5 DE23 190D
 DA08
 DirServer router5 v3ident=DADB8F236660FFD1C15C08215A2EEA5EE8ADCA70
 orport=6005 !10.0.0.5:20005 96A3 866E 916C D73B C928 5BB5 83FF 5F05 E40F
 1649
 }}}
 And here's the socks configuration option passed via the -f command-line
 option:

 {{{
 SocksPort 10.0.0.21:2000
 }}}
 To answer your question about the relay descriptors, here's an example
 descriptor:

 {{{
 @downloaded-at 2012-03-13 12:30:56
 @source "10.0.0.1"
 router router6 10.0.0.6 6006 0 0
 platform Tor 0.2.3.12-alpha-dev on Linux x86_64
 opt protocols Link 1 2 Circuit 1
 published 2012-03-13 12:25:50
 opt fingerprint 0335 C2CD D890 F6ED 9F58 A30B 1DA7 037C D850 C40A
 uptime 0
 bandwidth 2314240 2314240 2314240
 opt extra-info-digest B3E5EA28602B608D4D8BDBF7350D551AC9403D21
 onion-key
 -----BEGIN RSA PUBLIC KEY-----
 MIGJAoGBALL33lYV6ChTPT4Qf7CbW9xERjNYJQJ1p3MQIf5utvh60VHPYdvdWXLD
 A+pDahJ3dPIY0F6k/iI/gGn0kzAQQZl0bALUjSUldu2UjW2OOzRfwpY4NmuLFXGj
 VLhgp3ifspnf0Ih/dw7NJNwLEl6OJtg0i/v90879nKbYOgG91s9lAgMBAAE=
 -----END RSA PUBLIC KEY-----
 signing-key
 -----BEGIN RSA PUBLIC KEY-----
 MIGJAoGBAOwAhTH2RMNFICgKQTAPcICDny1eUfnxCIz6sq4JglYQeHPJyc4spcvi
 bm1kijQAHEBluU+kwuv8eeDf4nZFDuS4RxOT7Jx69oB6LJxrr6arIWviqWVaK7ms
 LXjAmP2nogfTA+z0yTlh4tYJWGAFDJRF67ERURixweqStaWeDlizAgMBAAE=
 -----END RSA PUBLIC KEY-----
 opt hidden-service-dir
 accept *:*
 router-signature
 -----BEGIN SIGNATURE-----
 bW39N6sb1VzZfchs1nyONDehp0k+/7buUbaMQ3UvaOUETUv7D0dv/bth81Up01ni
 GV6H4yxhI/8sqNRir/4PQdU7BCBx5+T/n0S/7PfeAy/DKTjeIcCJ/dxVl0Bjx4M6
 RIefjhpMKtBhnuPqyFGpzc9I/YLrXbgbDcusPNNKOZI=
 -----END SIGNATURE-----
 }}}
 And a microdescriptor:

 {{{
 @last-listed 2012-03-13 12:30:56
 onion-key
 -----BEGIN RSA PUBLIC KEY-----
 MIGJAoGBALL33lYV6ChTPT4Qf7CbW9xERjNYJQJ1p3MQIf5utvh60VHPYdvdWXLD
 A+pDahJ3dPIY0F6k/iI/gGn0kzAQQZl0bALUjSUldu2UjW2OOzRfwpY4NmuLFXGj
 VLhgp3ifspnf0Ih/dw7NJNwLEl6OJtg0i/v90879nKbYOgG91s9lAgMBAAE=
 -----END RSA PUBLIC KEY-----
 p accept 1-65535
 }}}

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5376#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online