On 2/9/20, Razer <g...@riseup.net> wrote:
>> users noticed “unknown Javascript” hidden in websites running on
> ...
> The article answers the question.

Pick a random case, then go back *before* the users were
exploited with some silly browser "NIT" or whatever else.

The question in some of the cases is not what was done to the
servers and users *after* the servers were cracked remotely over
tor or whatever other overlay network, or similarly done *after* being
physically found... that's obviously going to be some silly exploit.

Question how exactly the servers are being physically found in
the *first place*. Look for cases where the servers were mysteriously
just "found", with rest of timeline unfolding after that secret or
questionable moment. Tor and other networks are sold as being
able to protect from such network "finds".

It would be a big project to find, collate, research, and
report on those cases... some fame awaits whatever
group can bring them into more light, or even generate
some numerical statistics on the different types of cases,
exploits, questions remaining, etc.

Though in the end, with all the known public research exploits
proof of concept (traffic / protocol / sybil analysis and attacks)
against tor and other networks, it's safe to assume some of the
mystery cases do in fact use such network exploits (and even
some non public ones) and are being parallel constructed
against the prohibitions some jurisdictions have against
such illegal secret trickery.

>> even those using it for legal purposes such as visiting Tor Mail

And until those public research exploits are addressed
with fixes, and better designs in new networks, even things
like free speech mail comms and boring political blogs that
offend some King will continue to be taken down by said Kings.

Or until Kings trickery is embarrasingly exposed via reporting.

Or both.


Here's more on this case...

https://old.reddit.com/search?q=freedom+hosting
https://old.reddit.com/r/TOR/comments/2b8oq3/please_read_if_you_usedepend_on_tor_never_before/

Reply via email to