Custom Query (26254 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (61 - 63 of 26254)

Ticket Resolution Summary Owner Reporter
#135 Fixed change Privoxy config file or not? nn
Description

http://tor.eff.org/cvs/tor/doc/tor-doc-osx.html states: "You do not need to configure Privoxy to use Tor. A custom Privoxy configuration for Tor has been installed as part of the installer package."

but http://tor.eff.org/cvs/tor/doc/tor-doc.html states: "Add the line forward-socks4a / localhost:9050 . (don't forget the dot) to privoxy's config file (you can just add it to the top)."

These two statements seem contradictory. Many potential Tor/Privoxy users would be unsure about whether to add the line or not. Also, many potential Tor/Privoxy users would not know where to find Privoxy's config file, which one to edit, or how to edit it.

[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]

#138 Won't fix tor's dynamically linked against openssl version not in OSX 10.2 jlkinsel
Description

Hey guys - After installing Tor/Privoxy on my OS X 10.2 box and configuring everything according to the docs, I kept on getting Privoxy's 503 error that a few people have mentioned on the net(I haven't seen this solution yet).

Turns out after doing a bit of digging, when tor starts up, it pretty much instantly dies since the dynamic linker cannot find the openssl version 0.9.7:

dyld: ./tor can't open library: /usr/lib/libssl.0.9.7.dylib (No such file or directory, errno = 2)

This post has two purposes:

  • Document the reason people are probably seeing the 503 error
  • Ask the Tor group if it's possible to release a version of tor that's statically linked against OpenSSL 0.9.7 for those do not have it installed.

Personally, this hopefully won't be an issue to me after I upgrade to 10.4 tonight (I had somebody verify that 10.3.9 has openssl-0.9.7) but I'm sure others would appreciate it.

John

[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]

#140 Fixed controller receives truncated INFOVALUE responses goodell
Description

The controller sometimes receives truncated INFOVALUE responses, as observed by requesting descriptors (i.e. desc/name/router). This happens because s.recv(length) apparently is not guaranteed to read the entire length. The result is what appears to the controller to be multiple messages, not in fragment form, such that the first one looks like an ordinary INFOVALUE message of incorrect length and the rest look like improperly formed messages with weird types.

[Automatically added by flyspray2trac: Operating System: All]

Note: See TracQuery for help on using queries.