Re: Problems with irc because of tor?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 scar @ 11/23/2008 11:45 PM: > Praedor Atrebates @ 11/20/2008 01:08 PM: >> [snip] >> Why does running tor suddenly cause me to be unable to connect to freenode? >> I >> am NOT running a torified irc client. > > if you have tor configured as an exit node on the same IP address, then > that is probably why. freenode is probably just looking at the list of > exit nodes and acting accordingly. > >> Also, where's the address 127.0.0.1 >> coming from? Why is my REAL IP address now invisible (apparently) and tor >> causing sites to think I am trying to use the localhost IP? > > i think that IP is generated by the freenode server. they could have > configured their server to just say that IP address when they ban any > address... > > oops, sorry about that. i thought no one had replied to you since *ahem* some people's clients break threading ;) looking further through the unread mails, i see that wasn't the case. hopefully my reply wasn't completely useless -BEGIN PGP SIGNATURE- iD8DBQFJKk7aXhfCJNu98qARCAZHAKD4YqrEXRZOcWaliVMX5uPc9FkT9QCg1FOC B1CjvF+25MVYTXHfY49/QwI= =zOws -END PGP SIGNATURE-
Re: Problems with irc because of tor?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Praedor Atrebates @ 11/20/2008 01:08 PM: > [snip] > Why does running tor suddenly cause me to be unable to connect to freenode? > I > am NOT running a torified irc client. if you have tor configured as an exit node on the same IP address, then that is probably why. freenode is probably just looking at the list of exit nodes and acting accordingly. > Also, where's the address 127.0.0.1 > coming from? Why is my REAL IP address now invisible (apparently) and tor > causing sites to think I am trying to use the localhost IP? i think that IP is generated by the freenode server. they could have configured their server to just say that IP address when they ban any address... -BEGIN PGP SIGNATURE- iD8DBQFJKk2CXhfCJNu98qARCDKRAKDwxetf4IVrLagnSFwxW5Gh91ZjowCeLDA2 Fk2ks2Hl3PZZq4HGgYpnKnw= =hEbF -END PGP SIGNATURE-
Re: Tor 0.2.1.6-alpha is out
On Sat, Oct 18, 2008 at 01:15:48PM +, otto otto wrote: > I get the following error when trying to build tor-0.2.1.6-alpha on Sun > Solaris 10x86. > (I did compile and run tor-0.2.0.31 without any issue before.) > Any help is appreciated. [snip] > gcc -DHAVE_CONFIG_H -I. -I../.. -I../common -I/opt/csw/include > -I/usr/local/ssl/include -D__DARWIN_UNIX03 -DIPHONE -Wall -g -O2 -MT > compat.o -MD -MP -MF .deps/compat.Tpo -c -o compat.o compat.c > compat.c: In function `tor_lockfile_lock': > compat.c:509: warning: implicit declaration of function `flock' > compat.c:509: error: `LOCK_EX' undeclared (first use in this function) > compat.c:509: error: (Each undeclared identifier is reported only once > compat.c:509: error: for each function it appears in.) > compat.c:509: error: `LOCK_NB' undeclared (first use in this function) > compat.c: In function `tor_lockfile_unlock': > compat.c:538: error: `LOCK_UN' undeclared (first use in this function) Is this compile error still present for 0.2.1.7-alpha? If so, can you open a flyspray entry (https://bugs.torproject.org/) so we don't lose track of it? While I'm at it, why do you have "-D__DARWIN_UNIX03 -DIPHONE" as part of your commandline? Did you run ./configure with --enable-iphone? Thanks, --Roger
Re: Tor 0.2.1.7-alpha is out
Roger Dingledine <[EMAIL PROTECTED]> wrote: > Changes in version 0.2.1.7-alpha - 2008-11-08 > o Minor bugfixes: > - Minor fix in the warning messages when you're having problems > bootstrapping; also, be more forgiving of bootstrap problems when > we're still making incremental progress on a given bootstrap phase. I'm not sure if it's related to this change, but bootstrapping no longer works for me on FreeBSD 8.0-CURRENT: Nov 23 18:59:08.931 [notice] Tor 0.2.1.7-alpha-dev (r17366) opening log file. Nov 23 18:59:08.945 [notice] Parsing GEOIP file. Nov 23 18:59:10.160 [notice] This version of Tor (0.2.1.7-alpha-dev) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.1.2.17,0.1.2.18,0.1.2.19,0.2.0.26-rc,0.2.0.27-rc,0.2.0.28-rc,0.2.0.29-rc,0.2.0.30,0.2.0.31,0.2.0.32,0.2.1.1-alpha,0.2.1.2-alpha,0.2.1.4-alpha,0.2.1.5-alpha,0.2.1.6-alpha,0.2.1.7-alpha Nov 23 18:59:11.347 [notice] Bootstrapped 45%: Asking for relay descriptors. Nov 23 18:59:11.347 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1259 usable descriptors. Nov 23 18:59:12.163 [notice] Bootstrapped 50%: Loading relay descriptors. Nov 23 18:59:12.741 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1259 usable descriptors. [repeated 31 times] Nov 23 18:59:28.774 [warn] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Tor gave up on the connection; TIMEOUT; count 10; recommendation warn) Nov 23 18:59:28.805 [warn] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Tor gave up on the connection; TIMEOUT; count 11; recommendation warn) Nov 23 18:59:28.810 [warn] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (DONE; DONE; count 12; recommendation warn) Nov 23 18:59:28.810 [warn] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (DONE; DONE; count 13; recommendation warn) Nov 23 18:59:28.872 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1259 usable descriptors. [Seems to loop endlessly here] I have a complete debug log if any Tor developer is interested. Does the following indicate that Tor is trying to use invalid sockets? Nov 23 15:05:14.034 [debug] relay_lookup_conn(): found conn for stream 17393. Nov 23 15:05:14.035 [debug] circuit_receive_relay_cell(): Sending to origin. Nov 23 15:05:14.035 [debug] connection_edge_process_relay_cell(): Now seen 343 relay cells here. Nov 23 15:05:14.035 [debug] connection_edge_process_relay_cell(): circ deliver_window now 992. Nov 23 15:05:14.035 [debug] connection_or_process_cells_from_inbuf(): 28: starting, inbuf_datalen 496 (0 pending in tls object). Nov 23 15:05:14.035 [debug] conn_write_callback(): socket 19 wants to write. Nov 23 15:05:14.035 [debug] flush_chunk_tls(): flushed 512 bytes, 0 ready to flush, 0 remain. Nov 23 15:05:14.035 [debug] connection_handle_write(): After TLS write of 512: 0 read, 586 written Nov 23 15:05:14.035 [debug] connection_or_flush_from_first_active_circuit(): Made a circuit inactive. Nov 23 15:05:14.035 [debug] conn_read_callback(): socket 28 wants to read. Nov 23 15:05:14.036 [debug] connection_read_to_buf(): 28: starting, inbuf_datalen 496 (0 pending in tls object). at_most 16384. Nov 23 15:05:14.036 [debug] tor_tls_read(): read returned r=-1, err=-2 Nov 23 15:05:14.036 [debug] connection_read_to_buf(): After TLS read of 0: 1440 read, 0 written Nov 23 15:05:14.036 [debug] connection_or_process_cells_from_inbuf(): 28: starting, inbuf_datalen 496 (0 pending in tls object). Nov 23 15:05:14.036 [debug] conn_write_callback(): socket 19 wants to write. Nov 23 15:05:14.036 [debug] flush_chunk_tls(): flushed 512 bytes, 0 ready to flush, 0 remain. Nov 23 15:05:14.036 [debug] connection_handle_write(): After TLS write of 512: 0 read, 586 written Nov 23 15:05:14.036 [debug] conn_read_callback(): socket -1 wants to read. Nov 23 15:05:14.036 [debug] connection_dir_process_inbuf(): Got data, not eof. Leaving on inbuf. Nov 23 15:05:14.045 [debug] conn_read_callback(): socket 21 wants to read. Nov 23 15:05:14.045 [debug] connection_read_to_buf(): 21: starting, inbuf_datalen 0 (0 pending in tls object). at_most 16384. Nov 23 15:05:14.046 [debug] connection_read_to_buf(): After TLS read of 4080: 1258 read, 0 written Nov 23 15:05:14.046 [debug] connection_or_process_cells_from_inbuf(): 21: starting, inbuf_datalen 4080 (0 pending in tls object). According to the debug log, tor_tls_read() returns -1 all the time: [EMAIL PROTECTED] ~ $grep -c "tor_tls_read(): read returned r=-1, err=-2" test/tor/debug.log 757 [EMAIL PROTECTED] ~ $grep "tor_tls_read(): read" test/tor/debug.log | grep -v -c "r=-1" 0 Tor 0.2.1.6-alpha bootstraps without problems: Nov 23 19:38:00.572 [notice] Tor 0.2.1.6-alpha (r17011) opening log file. Nov 23 19:38:00.584 [notice] Parsing GEOIP file. Nov 23 19:3
article about Tor in german language
Hi is anyone able to write an article about Tor in german language? https://www.opensourcepress.de/fileadmin/osp/pdf/Stasi2.0.pdf summary needs to be send till end of the month and article needs to be finished end of January Take you chance.. Regards
RE: tor-0.2.0.32 doesn't compile on Solaris?
Sorry, it was my fault, after removing "--enable-gcc-warnings" from my config command it compiled. otto From: [EMAIL PROTECTED] To: or-talk@freehaven.net Subject: tor-0.2.0.32 doesn't compile on Solaris? Date: Sun, 23 Nov 2008 08:53:40 + I did run tor-0.2.0.31 on Solaris but when trying to compile tor-0.2.0.32 I'm getting compile errors. Any help is appreciated. Thanks. Otto ... ... gcc -DHAVE_CONFIG_H -I. -I../..-I../common -I/opt/csw/include -I/usr/local/ssl/include -D__DARWIN_UNIX03 -DIPHONE -Wall -g -O2 -W -Wfloat-equal -Wundef -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -Wredundant-decls -Wchar-subscripts -Wcomment -Wformat=2 -Wwrite-strings -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wbad-function-cast -Wswitch-enum -Werror -MT compat.o -MD -MP -MF .deps/compat.Tpo -c -o compat.o compat.c compat.c: In function `log_credential_status': compat.c:906: warning: unsigned int format, uid_t arg (arg 5) compat.c:906: warning: unsigned int format, uid_t arg (arg 6) compat.c:924: warning: unsigned int format, gid_t arg (arg 5) compat.c:924: warning: unsigned int format, gid_t arg (arg 6) *** Error code 1 make: Fatal error: Command failed for target `compat.o' Current working directory /usr/local/lib/tor-0.2.0.32/src/common *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='common or tools win32 config'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /usr/local/lib/tor-0.2.0.32/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc contrib'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /usr/local/lib/tor-0.2.0.32 *** Error code 1 make: Fatal error: Command failed for target `all' Zeigen Sie es Ihren Freunden! Erstellen Sie kostenlos Fotoalben und Diashows in Ihrem Space! _ MSN Toolbar: Alle Infos sehen, ohne die Website auf der Sie gerade sind zu verlassen. http://www.msn.de/toolbar
Re: DoS attack
Roger Dingledine schrieb: > On Wed, Oct 01, 2008 at 03:10:40PM +0200, Karsten N. wrote: >> the Tor node "gpfa" is for 10 hours target of a DoS attack. >> The attack is running on at the moment. > > Hi Karsten, > > How did this resolve? Hopefully it ended after a while? > > Thanks, > --Roger The DoS attack was over 7 hours later (was running 17 hours at all). There was a posting here: "Relax guys, and please verify the attack is over, a server went amok" (I can not find ist now :-[ ) The nick of my tor node was "gpfTOR1", sorry "gpfa" is the nick of the mixmaster on this server. Karsten N.
Re: DoS attack
On Sat, Nov 22, 2008 at 06:43:03PM -0500, Roger Dingledine wrote: > On Wed, Oct 01, 2008 at 03:10:40PM +0200, Karsten N. wrote: > > the Tor node "gpfa" is for 10 hours target of a DoS attack. > > The attack is running on at the moment. > > Hi Karsten, > > How did this resolve? Hopefully it ended after a while? > > Thanks, > --Roger Hi, due to the overlay in timing (parallel start of an 'attack' on my machine) I believe this to be the same issue. With standard *x tools (no intelligence sorcery or alike, for the paranoid) I managed to find the person in charge of the machine and called him up. He then basically 'pulled the plug' as the box proved to be inresponsive and apparently had gone out of control. Until failure there was a Tornode active. The box was killed on 1 Oct 2008 at around 16:00 (UST). Actually this is about the same time when the scroogle issue a bit earlier was solved, when, according to this post http://archives.seul.org/or/talk/Oct-2008/msg00014.html an attack on scroogle ceased, so I believe this all was the same issue. According to the person in charge the reason was a misconfigured or out of control machine. If the above is not related to Karstens post, my apologies for the noise. I do not remember who I talked to, and I do not own any logs, the person was surprised but friendly and almost immediately responded to solve the matter. Regards Hans >
Re: tor-0.2.0.32 doesn't compile on Solaris?
On Sun, Nov 23, 2008 at 12:53 AM, otto otto <[EMAIL PROTECTED]> wrote: > ... -D__DARWIN_UNIX03 -DIPHONE did you specify an architecture when invoking the configure script? the config.log would be helpful but should probably go in a flyspray report if needed. best regards,
tor-0.2.0.32 doesn't compile on Solaris?
I did run tor-0.2.0.31 on Solaris but when trying to compile tor-0.2.0.32 I'm getting compile errors. Any help is appreciated. Thanks. Otto ... ... gcc -DHAVE_CONFIG_H -I. -I../..-I../common -I/opt/csw/include -I/usr/local/ssl/include -D__DARWIN_UNIX03 -DIPHONE -Wall -g -O2 -W -Wfloat-equal -Wundef -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -Wredundant-decls -Wchar-subscripts -Wcomment -Wformat=2 -Wwrite-strings -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wbad-function-cast -Wswitch-enum -Werror -MT compat.o -MD -MP -MF .deps/compat.Tpo -c -o compat.o compat.c compat.c: In function `log_credential_status': compat.c:906: warning: unsigned int format, uid_t arg (arg 5) compat.c:906: warning: unsigned int format, uid_t arg (arg 6) compat.c:924: warning: unsigned int format, gid_t arg (arg 5) compat.c:924: warning: unsigned int format, gid_t arg (arg 6) *** Error code 1 make: Fatal error: Command failed for target `compat.o' Current working directory /usr/local/lib/tor-0.2.0.32/src/common *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='common or tools win32 config'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /usr/local/lib/tor-0.2.0.32/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc contrib'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /usr/local/lib/tor-0.2.0.32 *** Error code 1 make: Fatal error: Command failed for target `all' _ Messenger to go! Hol' Dir Messenger aufs Handy! http://windowslivemobile.msn.com/BrowserServiceMessenger.aspx?lang=DE-DE
