-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great. Thanks.
Adam Langley wrote:
> Looks like I should do a quick write up:
>
> One caveat, I'm running Android 1.1 PLAT-RC16, which is an unreleased
> testing version. However, I don't believe that anything pertinent has
> changed.
>
> 1) Setup y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Adam,
I would like the binaries and build instructions. I have a G1 development phone
(T-Mobile).
Thanks.
Alex Donnini
Adam Langley wrote:
> Just for lark, more than anything else, I built Tor on Android and
> have it running on a (release) HTC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have you thought about contacting
www.eff.org
Nicky van Etten wrote:
> The MPAA still has to prove you realy have the content which they claim
> you downloaded stored on your computer or any other storage device afaik.
>
>
>
> On Sat, Dec 13, 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lots of words to say that you do not want the system analyzed by outsiders.
Arrakis wrote:
> Robert,
>
>> At first glance your statement above could be taken to suggest that Onyx
>> provides provably better anonymity than Tor. A second reading sugge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
0.2.1.7 in relay node configuration has been running apparently normally for the
last 30 hours.
The only message (recurring) in the log is:
Dec 05 07:45:26.964 [Notice] We stalled too much while trying to write 179 bytes
to address [scrubbed]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I installed tor-0.2.1.7-alpha-dev-win32.exe, deleted torrc from the Vidalia
Application Data directory, and started Vidalia.
So far, so good, Tor is configured to run as a relay node (nessuno), and seems
to be running normally. The logs appear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I replaced the current ttorrc with the one labeled "old". Tor still cannot run
as a relay node but the error messages have changed. Here they are:
Dec 03 12:05:09.746 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental
software. Do not rely on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the response. I understand. Below, you will find the copy of the
Vidalia generated torrc.
The problem is occurring on a system running MS Windows XP SP2.
Note that prior to the upgrade from 0.2.0.31 to 0.2.1.7 I had no problems. The
proble
resolve the problem described below, and I need help in order to do that.
Any help would be greatly appreciated.
thanks.
Alex Donnini
Alessandro Donnini wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> I just upgraded to versions
>
> 0.1.10 of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I just upgraded to versions
0.1.10 of Vidalia
and
0.2.1.7 of Tor
Vidalia is able to run Tor as a client without any problems.
However, when I try to configure and run it as a relay node Vidalia is not able
to run Tor and reports the warnings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I sincerely hope you will be compensated. It would be a sign that Finnish
authorities, unlike those in most parts of the world recognize when they make a
mistake, and accept responsibility for their actions.
M wrote:
> Hi all!
>
> As I informed this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know. My statement below is wrong.
Juliusz Chroboczek wrote:
>> True, I did take that into account. I could be mistaken but I think the main
>> problem lies with the proxy software. I think that Polipo and, especially,
>> Privoxy are pretty resource
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks. I was already aware of this. Please refer to my other response.
Marco Bonetti wrote:
> covered in the FAQ:
> https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#GoogleSpyware
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Ming
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Right, that was my point too. I ma under the impression that there has been a
change.
[EMAIL PROTECTED] wrote:
> On Fri, Oct 24, 2008 at 08:32:23AM -0400, [EMAIL PROTECTED] wrote 1.1K bytes
> in 41 lines about:
> : For the past month or so, I have be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
FYI.
For the past month or so, I have been unable to consistently run web searches
via Google using a "Tor-enabled" browser".
Every time I try to use Google, the response to a search is a page asking me to
enter a character sequence (I guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
True, I did take that into account. I could be mistaken but I think the main
problem lies with the proxy software. I think that Polipo and, especially,
Privoxy are pretty resource intensive, and affect performance more than Tor
itself. But, this is jus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have been using tor for about four months.
Tor release - 0.2.0.30 running on an MS Windows XP SP2 system.
Browser
-
1) Sea Monkey (Mozilla)
with Polipo 1.0.4
2) MS IE6
with Privoxy 3.0.8
Using either browser, performance has been
[EMAIL PROTECTED] wrote:
On Sun, Aug 10, 2008 at 08:22:03AM -0400, [EMAIL PROTECTED] wrote 0.9K bytes in
37 lines about:
: Vidalia is configured to send Tor traffic via proxy (127.0.0.1 via port
: 8118)
did you configure privoxy, on port 8118, to forward to tor?
https://www.torproject.org/do
Hello,
I am having a problem in making Tor work. Below, you will find a
description of the problem together with background information.
System installation information
MS Windows XP SP2
Firefox 3.01 + SwitchProxy add-on
Vidalia 0.1.5
Tor 0.2.0.30(r15956)
Qt 4.4.0
Privoxy 3.0.8
JonDo client
19 matches
Mail list logo
