Where is vidalia config file?.MacOSX.
I compiled/installed vidalia-0.2.10 from sources but I cannot find the vidalia configuration file(on Linux vidalia.conf) so I can change some things not available from the vidalia GUI interface.
Vidalia and interactively changing Tor circuits.
When,in Vidalia,we click on one of the active circuits,does that action effectively change the current Tor circuit?If we are using one circuit,clicking (in Vidalia GUI interface) on another one,does this change Tor circuits to the one we clicked?
Firefox,FireFTP,FTP etc. downloads anonymity.
When we read the Tor FAQs related to anonymity of ftp tranfers there are several questions that come to mind: 1)Is the most recent Filezilla really secure/tested so we can trust the anonymity it provides through Tor?(something close to Firefox/Privoxy/Torbutton?) 2)Using Firefox 3.6.12 and FireFTP 1.0.9(most recent versions) downloading from Adobe(Flash Player,Adobe Reader,for example) I receive a warning that an external application is being launched -accept or reject-,is this app FireFTP?Is this warning coming from Torbutton?Does FireFTP 1.0.9 still leak DNS requests? 3)When it comes to ftp through Tor and reading the Tor FAQs it seems the better solution is 3proxy,however this software is not integrated on the major (any?)linux distributions and downloading directly it must be done from a russian website.The guys behind 3proxy can be really trustworthy but I do not feel specially comfortable using the software.
Avoid TLS renegotiating error on FreeBSD 8.0.Unable to link to parallel openssl libraries.
I built/installed openssl-0.9.8l on /usr/local/ssl/ ,the tor configure script when run recognize according the messages this openssl (I used the configure option --with-openssl-dir=/usr/local/ssl/lib,but in fact the resulting tor binary is linked to the system openssl libraries (verified with ldd) ,then the resulting TLS renegotiating error. How can I force tor to be linked to openssl on /usr/local/ssl/ instead of the system openssl? The option --with-openssl-dir=/usr/local/ssl/lib does not work.It seems to work according to configure messages,but in fact it is linked to the system openssl. *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
TLS renegotiating error.Link openssl libraries problem.
My first time using FreeBSD is with this 8.0-RELEASE,so I am quite new with it.Ionly have on my system pre-compiled binaries I installed with pkg_add.I havenever used the ports system,I have had the idea that it is something comparableto sources/binaries on Linux distros using the sources gives exactly the samebinaries(installs exactly on the same directories).Here,I used a method I haveused on Linux distros for some software (binaries linked with specific librarieson specific directories,not to system libraries),I got the pristine sources fromwww.openssl.org compiled and installed them,now I need to link them to the torbinary.If a straightforward method does exist I appreciate you post a link to it. Thanks.
TLS renegotiating error persists on FreeBSD 8.0 updated.
The well-known TLS renegotiating error which the tor-0.2.1.21 version was supposed to address persists on FreeBSD-8.0 updated as of today.The unstable version (0.2.2.6) same thing the error persists (On Linux and using tor-0.2.2.6 the error does not exist -I had this error only on Debian Testing and OpenSuSE)-.So,it seems to be a FreeBSD issue,more specifically after a recent FreeBSD update(when I no more could use tor).
Re: Firefox,Torbutton leaks real IP Address.
I can't reproduce the event of leakage the real IP address within the initial period of establishing the first circuit.I have tried with the same settings: Firefox,Torbutton,Privoxy but now Firefox waits the necessary period till establishement of the circuit,only then,the page www.showmyip.com etc. is displayed,with the IP address of the Tor exit node.So,I am considering the hypothesis that in the two times I noticed the leakage of the real IP address,was not my IP address,but the IP address of an exit node in my country (same flag) within the range of dynamic IP addresses of my DSL provider(and I wrongly thought it was mine).Anyway,now I tested with tor-0.2.0.32(compiled from source) and Iceweasel-3.0.4.(more recent versions).When I noticed the leakage(perhaps it was not) I verified that the torbutton was green and privoxy was setup(as always is).
Firefox,Torbutton leaks real IP Address.
The combination Firefox-3.0.3(in fact,Iceweasel-3.0.3),Torbutton-1.2.0 leaks my real IPaddress.This happens BETWEEN when I initiate Tor-0.2.0.31 with the bash command /usr/local/tor/bin/tor and the moment when Tor effectively establishes a connection-circuit.This can be 60 seconds or more,and if in between we connect to the Internet withFirefox-Torbutton the real IP address is used(even with torbutton running-green)I tested with www.showmyip.com and others.My fear is if the same could happen when Tor changes circuit by ten-ten minutes or so,when leaves the previous circuit to the next one.(what happens in the transition moments).I did not test that situation. Thanks.
Configure Filezilla 3.0.11 to use Tor.
The steps to configure Filezilla 3.x to use Tor in http://www.torproject.org Toryfing apps...seem not correct as I can't find under Settings... the Generic Proxy to point to 127.0.0.1port 9050.Only an ftp proxy appears under Settings...,which by the way should not beused,as is written there.Are there other ways to configure Filezilla 3.x,or is this something specific to this 3.0.11,and in other 3.x versions Generic Proxy appears under Settings...
Blocked by my ISP?-Solved.But Additional Question.
The communication between Privoxy and Tor was not set up correctly in the configuration files,it is OK now.Additionaly some things in the logs were due to entrynodes and exitnodes restrict options in my torrc.Anyway I downloaded and compiled the most recent Tor which is run now from /usr/local/ when I need,and not when the computer boots(the default in debian). http://check.torproject.org tells me that everything is OK. The question: can I use the FQDN or IP preferably, instead of nicknames,in torrc entrynodes,exclude nodes,exitnodes options?I have read something lately about the functioning of the Tor system, and it seems the directory servers/client initial dialog to determine the running nodes is protected by strong authentication,but when I access a listing of running nodes(by country,etc.) using https://stat.xenobite.eu(for example) with a webbrowser,how do I have assurance that the nicknames correspond to the real IP address? Does Tor check based on the strong authenticated listing received upon initial dialog with the directory servers the authenticity of the pairs nicknames/computers we could set up in exitnodes etc. of torrc? Thanks.
Blocked by my ISP?
Jun 15 16:22:23.376 [notice] Tor 0.1.2.17 opening log file. Jun 15 16:22:36.737 [notice] We now have enough directory information to build circuits. Jun 15 16:22:36.877 [warn] You specified a server magus by name, but this name is not registered, so it could be used by any server, not just the one you meant. To make sure you get the same server in the future, refer to it by key, as $FB4FEE3E590D85D328569E2A8CB1EFB32BAF626A. Jun 15 16:22:36.878 [warn] You specified a server no2spam by name, but this name is not registered, so it could be used by any server, not just the one you meant. To make sure you get the same server in the future, refer to it by key, as $EE0EFA289981DFC0966F9C46C1BC019008425A0B. Jun 15 16:22:36.879 [warn] You specified a server Samael by name, but this name is not registered, so it could be used by any server, not just the one you meant. To make sure you get the same server in the future, refer to it by key, as $76123553A021FF4EA4426B6B3688128FC8521C55. Jun 15 16:40:14.427 [warn] Received http status code 400 (Bad Request) from server '194.109.206.212:80' while fetching /tor/server/d/BAFD4D5D2E0D98ADE50B3AC116F69909100C805C+BB1E75B4C8215DF5F4F18F50879318EF711426C7+BCA7AFCA9D852E4C7BF94DE1ACDC3FF8AA491854+BD44604B5840117E78FE65667FD94220D623F01E+BE667C6ED0748DF529AB9A690B68EC589ECF8B6B+BEC4F949D3E50E8A8FBD several lines(30 or 40) like the above 2 lines!!! several lines like the above 2 lines.!!! several lines like the above 2 lines.!!! BFB3AD010E482696DF2C11B5DCB55+463B10A6923E9514C6B364078433C0CC16DACBA2+4732ED93C9A4D3F3C43F3476B5E9A5AEA91B20FD.z. I'll try again soon. Jun 15 16:40:50.287 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Jun 15 16:40:55.083 [warn] Received http status code 404 (Not found) from server '86.59.21.38:80' while fetching /tor/status/fp/38D4F5FCF7B1023228B895EA56EDE7D5CCDCAF32.z. I'll try again soon. I am not able to use the Tor Network,I use Debian Linux everything well-installed,but the logs are as above everytime,and not once I could use Tor. So I suspect that my ISP blocks Tor.Looking at the above logs can someone tell me what is the problem? Note:I use tor-button with firefox.torcheck.xenobite.eu always tells me tor not in place,the same using showmyip.com the IP is my ISP IP.Now in torrc I determine entrynodes and exitnodes verified previously if are running.
Blocked by my ISP?-part2
signed-directory published 2008-06-15 23:32:35 recommended-software 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.1.1-alpha router-status dir-signing-key -BEGIN RSA PUBLIC KEY- MIGJAoGBAMQgV2gXLbXgesWgeAsj8P1Uvm/zibrFXqwDq27lLKNgWGYGX2ax3LyT 3nzI1Y5oLs4kPKTsMM5ft9aokwf417lKoCRlZc9ptfRbgxDx90c9GtWVmkrmDvCK ae59TMoXIiGfZiwWT6KKq5Zm9/Fu2Il3B2vHGkKJYKixmiBJRKp/AgMBAAE= -END RSA PUBLIC KEY- directory-signature tor26 -BEGIN SIGNATURE- ncqJLN4ySE9d0ODHDKb7NDEpZtctXhlqj9I/kGBK7SR71BIqCc9EIspSuPaIR9AH KXaIWHEMOQrwtIzav5QOZp3mEeQGDdBgfBsRoWYiR2ahpd8Jqj8WYduzmqXNRQ1Z 2Fyd+yPRdNDerqLJ0W5uW9OX9LGMftOqCqSV+FB+J/A= -END SIGNATURE- This is what I get when I try to connect with my webbrowser to http://86.59.21.38/.An ancient client of my DSL ISP says in a newsgroup that right before he left this ISP was blocking proxy ports 80 and 8080 and maybe this is a reason for Tor not effective to other user that was complaining about it,and that he should use foxyproxy to avoid this issue. How do I know if my ISP is blocking Tor and is the configuration of foxyproxy a good idea,but the configuration of privoxy should not be sufficient?
