-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Are there also bundles for linux?
thanks,
tagnaq
-BEGIN PGP SIGNATURE-
iF4EAREKAAYFAk3VRJcACgkQyM26BSNOM7bWdQEAuq+NBUnbS+3ehgalMkFdu+K1
Dyd56AzFI+ZkTmgCS/oBAJ9ne8m/tGWhMsRxyPDInj81Z2O9MSgZOOjSb8/YuOro
=Vjnc
-END PGP SIGNATURE-
_
Hi,
I don't know if this is something we should be concerned about, but I
thought I'd bring it to your attention anyway.
Firefox 4 implements Content-Security-Policy:
https://wiki.mozilla.org/Security/CSP/Specification
It allows website owners to send a HTTP response header containing a
policy a
On Thu, 19 May 2011 14:13:31 +0200
Daniel Franganillo wrote:
> So, Why release an unpatched version?
Because 0.2.2.26 was already tagged in git.
--
Andrew
pgp 0x74ED336B
___
tor-talk mailing list
tor-talk@lists.torproject.org
https://lists.torproject
On Thu, 19 May 2011 11:51:34 +0200
Olaf Selke wrote:
> On 19.05.2011 08:54, Roger Dingledine wrote:
> >
> > o Major features:
> > - Set SO_REUSEADDR on all sockets, not just listeners. This should
> > help busy exit nodes avoid running out of useable ports just
> > because all
El 19/05/11 13:41, and...@torproject.org escribió:
On Thu, May 19, 2011 at 12:16:23PM +0200, dani...@dilmun.ls.fi.upm.es wrote 16K
bytes in 337 lines about:
: Maybe it's just a stupid question, but why there are two version
: from the 0.2.2 branch being released?
: Is 0.2.2.27 a patched version
On 19.05.2011 13:21, Eugen Leitl wrote:
>
> I can help with testing, just got IPv6 to work natively.
blutmagie exit node's operating system as well as torstatus.blutmagie.de
are IPv6 enabled, too.
regards Olaf
___
tor-talk mailing list
tor-talk@lists.t
On Thu, May 19, 2011 at 06:48:20AM -0400, cmeclax-sazri wrote:
> What's the plan for introducing ipv6 to Tor?
I can help with testing, just got IPv6 to work natively.
--
Eugen* Leitl http://leitl.org";>leitl http://leitl.org
__
ICBM: 48
On Thu, May 19, 2011 at 11:48 AM, cmeclax-sazri
wrote:
> What's the plan for introducing ipv6 to Tor?
Nick wrote a blog post explaining what's left to do before we an call
Tor fully IPv6-compliant:
https://blog.torproject.org/blog/ipv6-future-i-hear
--
Runa A. Sandvik
__
On Thu, May 19, 2011 at 12:16:23PM +0200, dani...@dilmun.ls.fi.upm.es wrote 16K
bytes in 337 lines about:
: Maybe it's just a stupid question, but why there are two version
: from the 0.2.2 branch being released?
: Is 0.2.2.27 a patched version of 0.2.2.26?
No, they are two different releases. Th
El 19/05/11 08:54, Roger Dingledine escribió:
Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
also introduces a new "socksport auto" approach that should make it
easier to run multiple Tors on the same system, and does a lot of
cleanup to get us closer to a release candidate.
What's the plan for introducing ipv6 to Tor?
cmeclax
___
tor-talk mailing list
tor-talk@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
On 19.05.2011 08:54, Roger Dingledine wrote:
>
> o Major features:
> - Set SO_REUSEADDR on all sockets, not just listeners. This should
> help busy exit nodes avoid running out of useable ports just
> because all the ports have been used in the near past. Resolves
> issue 2
Ignore that fortune cookie, was a misconfiguration on my part.
On Thu, May 19, 2011 at 11:39:32AM +0200, Eugen Leitl wrote:
>
> Jiggle my memory, when does this happen?
>
> Your server (xx.xx.xx.xx:9030) has not managed to confirm that its DirPort is
> reachable.
>
> This is running in a vser
Jiggle my memory, when does this happen?
Your server (xx.xx.xx.xx:9030) has not managed to confirm that its DirPort is
reachable.
This is running in a vserver guest.
--
Eugen* Leitl http://leitl.org";>leitl http://leitl.org
__
ICBM:
14 matches
Mail list logo
