Custom Query (24779 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (19 - 21 of 24779)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Ticket Resolution Summary Owner Reporter
#71 Implemented Warn when exit policy allows private:* nickm
Description

Too many people are telling us that the sky is falling because that Tor allows connections to private networks. This is, of course, because people aren't setting their exit policies to block them. Nevertheless, we should probably have Tor give a warning when you start a server and the exit policy allows x:* connections to a non-public address.

[Automatically added by flyspray2trac: Operating System: All]

#72 Implemented Open LDAP and LDAPS ports in the default policy shamrock
Description

Tor currently does not proxy the LDAP (389/tcp) and LDAPS (636/tcp) ports.

Feature Request: proxy the LDAP and LDAPS ports.

Background: LDAP(S) is the standard protocol to obtain recipients' cryptographic keys on the Internet. Any entity making an LDAP server available to the public does so to permit public dissemination of their users' directory information. The abuse potential of permitting these ports to be proxied is negligible, no higher than the abuse potential of permitting the proxying of http and inarguably lower than permitting the proxying of other ports already available via tor, such as ssh or IRC.

[Automatically added by flyspray2trac: Operating System: All]

#74 Fixed Servers bloat memory from spawned children arma
Description

When we fork, our children inherit the memory from the main Tor process, which can be 50MB or more. Since it's copy-on-write, no problem so far. But when the main Tor process changes the memory, or frees it, then it gets copied so the child has a clean copy.

So we end up using 50+MB per child. When we spawn a lot of dnsworkers, this becomes really bad.

[Automatically added by flyspray2trac: Operating System: All]

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note: See TracQuery for help on using queries.