> Imagine that an .onion site is compromised. This could be by the owner who
> wishes to expose visitors or by the police who want to target the
> clientele.
> How would it
> be possible for a visitor to be in danger?
Other posts covered technical code exploits.
Other risks are trust changes...
On 12/06/2018 01:51 PM, Nathaniel Suchy wrote:
> If an onion site is compromised, you can serve the user malicious content and
> with a Tor Browser Vulnerability can harm it's users.
>
> If your private key is compromised, your only recourse is to go create a new
> onion address.
>
> We don't
If an onion site is compromised, you can serve the user malicious content and
with a Tor Browser Vulnerability can harm it's users.
If your private key is compromised, your only recourse is to go create a new
onion address.
We don't know what vulnerabilities exist in the current version of Tor
Imagine that an .onion site is compromised. This could be by the owner who
wishes to expose visitors or by the police who want to target the
clientele.
(I remember, in the later case, reading something on Deep Dot Web about
when the FBI took over a CP site and installed malware).
The goal is to
