-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
by comparing different methodologies of "parsing" myfamily data I
stumbled upon differences between onionoo and compass.
After manual review I assume there is a bug in onionoo (or onionoo has
a different opinion on what families actually are)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/15 17:48, Nick Mathewson wrote:
> On Mon, Jun 1, 2015 at 3:27 AM, Karsten Loesing
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> Hi Nick,
>>
>> On 31/05/15 16:21, Nick Mathewson wrote:
>>> On Sat, May 30, 2015 at 5:16 PM, K
On Mon, Jun 1, 2015 at 3:27 AM, Karsten Loesing wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Nick,
>
> On 31/05/15 16:21, Nick Mathewson wrote:
>> On Sat, May 30, 2015 at 5:16 PM, Karsten Loesing
>> wrote:
>>> So, I think a "fingerprint-ed25519" line would be useful. It
>>> wo
Karsten Loesing writes:
> Hi asn, hi weasel,
>
> could it be that the recently added GuardFraction stuff broke
> something that led to removing the "bandwidth-weights" line?
>
> All the best,
> Karsten
>
It does seem like this is the case. I filed a bug here:
https://trac.torproject.org/projects
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi asn, hi weasel,
could it be that the recently added GuardFraction stuff broke
something that led to removing the "bandwidth-weights" line?
All the best,
Karsten
$ grep -c bandwidth-weights 2015-05-31-*
2015-05-31-00-00-00-consensus:1
2015-05-31-
On Mon, 01 Jun 2015 07:43:50 +
Georg Koppen wrote:
> > My question is, what causes Tor Browser to set the SOCKS username to
> > "--unknown--" and what the behavior should be in that case if:
>
> Ideally, "--unknown--" would only be used for requests originating
> from privileged browser code
Yawning Angel:
[snip]
> My question is, what causes Tor Browser to set the SOCKS username to
> "--unknown--" and what the behavior should be in that case if:
Ideally, "--unknown--" would only be used for requests originating from
privileged browser code and not belonging to a website/resource a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
On 31/05/15 16:21, Nick Mathewson wrote:
> On Sat, May 30, 2015 at 5:16 PM, Karsten Loesing
> wrote:
>> So, I think a "fingerprint-ed25519" line would be useful. It
>> would make the bridge descriptor sanitizing process much easier.
>> It w
