tor-0.1.2.18 build issues with zlib
hi torizens... 1 - how can i tell tor to compile and use the zlib in /usr/local ? there are two zlib versions on the system. the older supports legacy apps. there doesn't seem to be a --with-zlib-dir option to do this. 2 - i get a gzip test error as below. i've checked the bugtracker for both, no entries. ideas? thx. # installed in /usr openssl-0.9.7d zlib-1.1.4 # installed in /usr/local libevent-1.3e openssl-0.9.8g zlib-1.2.3 # host pentiumII, freebsd 4.11-STABLE [really RELENG_4 as of a week ago] # build info ports/packages are not used, all from original sources. configure options: --prefix, --mandir configure, make, make install output is completely clean as usual, no problems. tor itself runs fine, no problems. just ignore the torrc and socket stuff below. # build output - zlib related cf.std: checking zlib.h usability... yes cf.std: checking zlib.h presence... yes cf.std: checking for zlib.h... yes mk.std: gcc -g -O2 -Wall -g -O2 -L/usr/local/lib -o tor objs ../common/libor.a ../common/libor-crypto.a -lz -lssl -lcrypto -levent -lssl -lcrypto mk.std: gcc -g -O2 -Wall -g -O2 -L/usr/local/lib -o test objs ../common/libor.a ../common/libor-crypto.a -lz -lssl -lcrypto -levent -lssl -lcrypto # ldd tor01218/tor-0.1.2.18/src/or/tor: libz.so = /usr/lib/libz.so (0x28105000) libssl.so.0.9.8 = /usr/local/lib/libssl.so.0.9.8 (0x28112000) libcrypto.so.0.9.8 = /usr/local/lib/libcrypto.so.0.9.8 (0x2814d000) libevent-1.3e.so.1 = /usr/local/lib/libevent-1.3e.so.1 (0x2827a000) libc.so.4 = /usr/lib/libc.so.4 (0x2828e000) tor01218/tor-0.1.2.18/src/or/test: libz.so = /usr/lib/libz.so (0x28119000) libssl.so.0.9.8 = /usr/local/lib/libssl.so.0.9.8 (0x28126000) libcrypto.so.0.9.8 = /usr/local/lib/libcrypto.so.0.9.8 (0x28161000) libevent-1.3e.so.1 = /usr/local/lib/libevent-1.3e.so.1 (0x2828e000) libc.so.4 = /usr/lib/libc.so.4 (0x282a2000) # exec - works fine, this is just a test ./tor01218/tor-0.1.2.18/src/or/tor [notice] Tor v0.1.2.18. This is experimental software. Do not rely on it for strong anonymity. [notice] Configuration file /usr/local/tor01218/etc/tor/torrc not present, using reasonable defaults. [notice] Initialized libevent version 1.3e using method kqueue. Good. [notice] Opening Socks listener on 127.0.0.1:9050 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running? [warn] Failed to parse/validate config: Failed to bind one of the listener ports. [err] Reading config failed--see warnings above. # exec - excess .'s trimmed ./tor01218/tor-0.1.2.18/src/or/test Running Tor unit tests on FreeBSD i386 == Buffers = ... == Crypto == ... = Util . File test.c: line 1136 (test_gzip): assertion failed: (!tor_gzip_compress(buf2, len1, buf1, strlen(buf1)+1, GZIP_METHOD)) ... = Onion Skins = ... = Directory Formats === ... = Policies === ... = Rendezvous functionality ... __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: tor-0.1.2.18 build issues with zlib
more info. src/or/test PASSES under the conditions below. /usr/local happens to be a managed symlink farm, in case you're wondering about zlib123. still don't know how to resolve this during build without LD_LIBRARY_PATH though. ## ktrace accesses during build # configure 84749 cpp0 NAMI /usr/local/include/zlib.h 84765 cpp0 NAMI /usr/local/include/zlib.h # make 87693 cpp0 NAMI zlib.h 87693 cpp0 NAMI ../../zlib.h 87693 cpp0 NAMI /usr/local/include/zlib.h 88263 ld NAMI /usr/local/lib/libz.so 88292 ld NAMI /usr/local/lib/libz.so # ldconfig -r | egrep 'libz' 41:-lz.2 = /usr/lib/libz.so.2 200:-lz.1 = /usr/local/lib/libz.so.1 ldconfig -r | egrep 'ssl|crypto' 52:-lcrypto.3 = /usr/lib/libcrypto.so.3 53:-lssl.3 = /usr/lib/libssl.so.3 ldconfig -r | egrep 'event' 115:-levent-1.3e.1 = /usr/local/lib/libevent-1.3e.so.1 ### setting preference to library path ## ldd /usr/local/bin/tor /usr/local/bin/tor: libz.so = /usr/lib/libz.so (0x28105000) libssl.so.0.9.8 = /usr/local/lib/libssl.so.0.9.8 (0x28112000) libcrypto.so.0.9.8 = /usr/local/lib/libcrypto.so.0.9.8 (0x2814d000) libevent-1.3e.so.1 = /usr/local/lib/libevent-1.3e.so.1 (0x2827a000) libc.so.4 = /usr/lib/libc.so.4 (0x2828e000) ## LD_LIBRARY_PATH=/usr/local/lib ldd /usr/local/bin/tor /usr/local/bin/tor: libz.so = /usr/local/zlib123/lib/libz.so (0x28105000) libssl.so.0.9.8 = /usr/local/lib/libssl.so.0.9.8 (0x28117000) libcrypto.so.0.9.8 = /usr/local/lib/libcrypto.so.0.9.8 (0x28152000) libevent-1.3e.so.1 = /usr/local/lib/libevent-1.3e.so.1 (0x2827f000) libc.so.4 = /usr/lib/libc.so.4 (0x28293000) ## LD_LIBRARY_PATH=/usr/local/lib ldd src/or/test src/or/test: libz.so = /usr/local/zlib123/lib/libz.so (0x28119000) libssl.so.0.9.8 = /usr/local/lib/libssl.so.0.9.8 (0x2812b000) libcrypto.so.0.9.8 = /usr/local/lib/libcrypto.so.0.9.8 (0x28166000) libevent-1.3e.so.1 = /usr/local/lib/libevent-1.3e.so.1 (0x28293000) libc.so.4 = /usr/lib/libc.so.4 (0x282a7000) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: no traffic?
On 11/3/07, Udo van den Heuvel [EMAIL PROTECTED] wrote: Udo van den Heuvel wrote: Alexander W. Janssen wrote: no peaks. Why is the traffic like it is? No idea. Did you ever update/restart your Tor-server? Could you share your MRTG-grahps with us? http://pindarots.xs4all.nl/mrtg/tor.html Any insights after seeing the graphs? Not really, no. Have you ever updated/restarted the Tor-software? Alex. -- I am tired of all this sort of thing called science here... We have spent millions in that sort of thing for the last few years, and it is time it should be stopped. -- Simon Cameron, U.S. Senator, on the Smithsonian Institution, 1901. .
Re: GETINFO desc/all-recent output from 0.2.0.9 differ from 0.2.0.7
On 11/1/07, Olaf Selke [EMAIL PROTECTED] wrote: hi folks, the control port command GETINFO desc/all-recent provides only 355 routers on v0.2.0.9-alpha. 2199 items are returned as expected after downgrading to v0.2.0.7-alpha. Since my 0.2.0.9 bandwidth graph looked sane, I don't suppose a general problem with v0.2.0.9. Output of both versions can be found here: http://torstatus.blutmagie.de/GETINFO-desc-all-recent-ouput-0.2.0.7.txt http://torstatus.blutmagie.de/GETINFO-desc-all-recent-ouput-0.2.0.9.txt I didn't check v0.2.0.8-alpha. Is there a known bug regarding this issue? A couple of tor network status sites rely on GETINFO desc/all-recent control port output. regards, Olaf Hello, This has occurred with my installation of Tor as well (v0.2.0.9-alpha), however for the network status as opposed to the descriptors. I restarted Tor (stopping and starting, not a HUP), and it seemed to correct the problems. Kasimir -- Kasimir Gabert
New PortableTor
PortableTor is a rebundled version of the Vidalia-Privoxy bundle that comes out on the torproject.org website. This project was created in order to allow the end user full functionality, optimal disk space, and easy adaptation of portable applications with the Tor network. It can run on a flash drive, a desktop, external drive, iPod, and if modified, even on a solid medium, such as a CD. A new version of PortableTor has been released (and is released every stable update.) based on 0.1.2.18a-0.0.4 Vidalia and Privoxy bundle. There's been a few changes in this version that are significant on the PortableTor end: * Reformatted directory structure to the PortableApps Format. This means breaking down all directories into categories based on what they are, instead of what bundles they were in. All config files are in one place, all programs in one place, and all documentation in one place. * Thanks to the fix in bug 499, AvoidDiskWrites 1 doesn't leave a remnant behind in the temporary files anymore. * Made Tor start automatically by default. I assume if someone opens PortableTor, they want to join the network. If you're interested in getting PortableTor, head over to http://portabletor.sf.net . There you will find the main project goals, download links, recommended additions and usages, as well as support forums and discussion topics. Criticism and feedback are welcome on the Sourceforge forums! Any direct questions can be made to Silivrenion at [EMAIL PROTECTED] . Future developments: There's some work being done on making the launcher smarter to be able to regenerate missing sections of the package. Also using the PortableTor gateway on solid storage devices by default, e.g. giving a friend a PortableTor/PortableFirefox CD for a stocking stuffer. Kudos, Silivrenion Steve Morley [EMAIL PROTECTED]
