>> I'm not sure I understand what you mean by brute-forcing in this case
>> since I would not suggest any deterministic algorithm (like a hash) that
>> takes an ASname and a timestamp and produces a string but just a
>> AS number -> random id
>> mapping, stored for a day or an hour and deleted afte
> On 15 Dec. 2016, at 06:01, nusenu wrote:
>
>> How could we avoid an adversary brute-forcing all the possible ASs and
>> days/hours?
>
> I'm not sure I understand what you mean by brute-forcing in this case
> since I would not suggest any deterministic algorithm (like a hash) that
> takes an A
Dear CollecTor devs,
> https://collector.torproject.org/#bridge-descriptors
>> 5. Replace contact information: If there is contact information in a
>> descriptor, the contact line is changed to somebody.
would you be willing to change this to allow 1:1 mapping (one way but
not a hash) from the ac
>> another raw idea:
>>
>> - would the bridge auth be willing to publish a randomly generated AS
>> identifier (regenerated daily) that allows new bridges added on the same
>> day to be grouped by that identifier without directly disclosing the AS
>> itself.
>
> Bridges don't necessarily contact t
On Wed, Dec 14, 2016 at 10:09:00AM +, nusenu wrote:
> in the context of [1] I'm wondering if it makes sense to add bridge
> support to ornetradar.
>
> If there is any value to automatically detect multiple new bridges:
>
> - Do bridges publish ContactInfo in their descriptor? If not: Why not?
Roger Dingledine:
> On Sat, Dec 10, 2016 at 08:52:47PM +, Yawning Angel wrote:
>> I tagged sandboxed-tor-browser 0.0.2 (0.0.1 is also tagged, but it has
>> a few issues), so this is the obligatory release announcement.
>>
>> Official binaries should be available sometime next week, so I strongl
> On 14 Dec. 2016, at 21:09, nusenu wrote:
>
> another raw idea:
>
> - would the bridge auth be willing to publish a randomly generated AS
> identifier (regenerated daily) that allows new bridges added on the same
> day to be grouped by that identifier without directly disclosing the AS
> itsel
Hi,
in the context of [1] I'm wondering if it makes sense to add bridge
support to ornetradar.
If there is any value to automatically detect multiple new bridges:
- Do bridges publish ContactInfo in their descriptor? If not: Why not?
(it shouldn't disclose their bridge location)
another raw ide
