Hi wonderful relay operators. It's GSoC season again, where students
can be funded to make open source projects like Tor even better!
Nyx (previously known as arm [1]) has been my main focus this last
year and is inching ever closer to release. For those unfamiliar with
it, Nyx is an ncurses monit
Hi,
One of the directory authoritites (maatuska) is submitting new consensus
documents to a public append-only verifiable log, similar to what
Certificate Transparency uses.
If you think this is exciting and want to help out with this experiment,
consider setting up a monitor and start looking fo
Hi,
Some time ago, like 1,5 years, this list received a proposal for how to
build Tor Consensus Transparency. I got some good feedback and then i
got busy with other things.
Here's an updated version with feedback incorporated, change in
wordings, more of an actual specification, some changes in
On 2/16/16 12:20, George Kadianakis wrote:
> The
> very latest prop259 basically forgets the unreachable guard status as soon as
> the algorithm terminates. I wonder if we actually want this. Hopefully
> guardsim
> has a simulation scenario that will illustrate whether that's a good idea or
> not.
>
> Does differentiating traffic into multiple timing classes make traffic timing
> analysis easier?
> (For example, while high-latency traffic is better protected from
> fingerprinting, low-latency traffic is easier to identify and fingerprint.)
The opposite should be the case, as the delayin
