> On 24 Jul 2018, at 12:20, arisbe wrote:
>
> The other issue is why these two bridges don't show up on Tor Metrics.
>
> Hamlet and Othello
>
Tor metrics just published an explanation of how they get their statistics:
https://metrics.torproject.org/reproducible-metrics.html
Perhaps your bridg
The other issue is why these two bridges don't show up on Tor
Metrics.
Hamlet and Othello
On 7/23/2018 1:02 AM, nusenu wrote:
arisbe:
On 7/22/2018 11:59 PM, nusenu wrote:
arisbe:
Two
Hey All,
As an FYI, I'm temorarily shutting down the non-exit HardenedBSD-based
relay I run at home (3CA2B91F2F2720202DD845E0E4C827E720CF5430) due to
an upcoming extensive shoulder surgery my wife is having. I need to
cut costs as she will be out of work for a year.
My plan is to re-enable it onc
On 2018-07-23 16:03, Cristian Consonni wrote:
```
[notice] Registered server transport 'obfs4' at '[::]:46396'
```
Remember the random port associated to your bridge needs to be open for
incoming connections. You can find it from the logs: it's 46396 in this
example.
---
I can assume that usin
If you were required to hand over your relay keys be sure to switch over to
new ones to avoid future traffic from being affected by MITMs.
On Mon, Jul 23, 2018 at 12:26 PM IPfail (Tor Admin)
wrote:
> Vasilis,
>
> It turned out to be a pretty "non-event". The jurisdiction was a
> relatively small
Vasilis,
It turned out to be a pretty "non-event". The jurisdiction was a relatively
small one on the east coast of the US. The staff of the prosecutor's office
were all very professional and pleasant to work with. Phoul coordinated the
production of a letter from the Tor Project in record time
Hi IPfail,
"IPfail (Tor Admin)":
> The one I received seemed very reasonable in language and scope, and came
> with contact information for someone with a title that implied that they work
> specifically on "cyber crimes". I am currently anticipating that this will be
> a non-event.
>
> Eithe
Hi,
Form the instructions to install obsf4:
https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxy
---
```
ExtORPort auto
```
[...]
```
[notice] Registered server transport 'obfs4' at '[::]:46396'
```
Remember the random port associated to your bridge needs to be open
>> generally speaking:
>> - please don't run bridges and exits at the same time
>
> Ok, that's news (I have not read this advice anywhere else)
it would allow end-to-end correlation and we had this before on this
list, I'll ask Moritz about his bridges again
>> - don't add MyFamily lines to yo
On 22/07/2018 18:57, nusenu wrote:
>> I am running a couple of relay nodes and now I would like to set a
>> bridge relay. The `torrc` file says the following:
>> ---
>> ## Uncomment this if you run more than one Tor relay, and add the identity
>> ## key fingerprint of each Tor relay you control, ev
arisbe:
>
>
> On 7/22/2018 11:59 PM, nusenu wrote:
>>
>> arisbe:
>>> Two of my bridges (not all) show the same response:
>>>
>>> hamlet@v3460:~$ tor --version
>>> Tor version 0.3.3.9 (git-ca1a436fa8e53a32).
>>> hamlet@v3460:~$
>>>
>>> Thanks for looking at this discrepancy.
>> is NYX showing th
On 7/22/2018 11:59 PM, nusenu wrote:
arisbe:
Two of my bridges (not all) show the same response:
hamlet@v3460:~$ tor --version
Tor version 0.3.3.9 (git-ca1a436fa8e53a32).
hamlet@v3460:~$
Thanks for looking at this discrepancy.
arisbe:
> Two of my bridges (not all) show the same response:
>
> hamlet@v3460:~$ tor --version
> Tor version 0.3.3.9 (git-ca1a436fa8e53a32).
> hamlet@v3460:~$
>
> Thanks for looking at this discrepancy.
is NYX showing the same version?
if not: did you restart tor after upgrading?
--
https://
13 matches
Mail list logo
