On 10/30/20 5:55 PM, anonym wrote:
proc...@riseup.net:
On 10/29/20 3:18 PM, anonym wrote:
proc...@riseup.net:
On a related note, with restrict-stream-events set to true, I was
still able to access all stream events when testing with netcat in the
workstation VM. Initially it worked as inten
proc...@riseup.net:
On 10/29/20 3:18 PM, anonym wrote:
proc...@riseup.net:
On a related note, with restrict-stream-events set to true, I was still able to
access all stream events when testing with netcat in the workstation VM.
Initially it worked as intended and didn't pass this info, but du
On 10/29/20 3:18 PM, anonym wrote:
proc...@riseup.net:
Re-sending this in a human readable form:
Thanks!
A couple of months ago I was looking at locking down the amount of
info leaked to Tor Browser in case it is compromised - if/when stream
events access is enabled. my thought was to hav
proc...@riseup.net:
Re-sending this in a human readable form:
Thanks!
A couple of months ago I was looking at locking down the amount of info leaked
to Tor Browser in case it is compromised - if/when stream events access is
enabled. my thought was to have the cake and eat it too.
I guess
Re-sending this in a human readable form:
Hi, posting this mail for input.
A couple of months ago I was looking at locking down the amount of info
leaked to Tor Browser in case it is compromised - if/when stream events
access is enabled. my thought was to have the cake and eat it too.
stream
