tetrahedra via qubes-users:
> On Fri, Sep 27, 2019 at 01:37:06PM +, Claudia wrote:
>> Isolating apps in the same VM is a different issue, but you're saying
>> traffic from different VMs is appearing to come from the same address?
>>
>> Hmm, that definitely should not be happening. VM isolation
On Mon, Sep 30, 2019 at 04:15:26PM +, Claudia wrote:
To make sure IsolateClientAddr is working (as opposed to
IsolateSOCKSAuth), you can run
curl.anondist-orig https://check.torproject.org
in two different whonix-ws VMs at the same time, and make sure they
output different addresses. You
tetrahedra via qubes-users:
On Mon, Sep 30, 2019 at 08:05:44AM +, Claudia wrote:
Glad to hear it's working. I guess I should have asked at the
beginning... What brought you to the conclusion they were using the
same circuits? I assumed you were using check.torproject.org or
another "what
On Mon, Sep 30, 2019 at 08:05:44AM +, Claudia wrote:
Glad to hear it's working. I guess I should have asked at the
beginning... What brought you to the conclusion they were using the
same circuits? I assumed you were using check.torproject.org or
another "what is my IP" site, but if
tetrahedra via qubes-users:
On Sun, Sep 29, 2019 at 02:42:29PM +, Claudia wrote:
You can try viewing your active tor settings in Nyx (preinstalled in
Whonix) rather than from torrc directly. Just in case some setting is
being overridden or something like that. See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
tetrahedra:
> Naturally I want Alice to appear to be using a different IP address than
> Bob, else the two identities are linked.
>
> Right now it appears this is not necessarily the case -- the network
> traffic of AppVMs A and B may end up using
On Sun, Sep 29, 2019 at 02:42:29PM +, Claudia wrote:
You can try viewing your active tor settings in Nyx (preinstalled in
Whonix) rather than from torrc directly. Just in case some setting is
being overridden or something like that. See
https://www.whonix.org/wiki/Tor_Controller and
tetrahedra via qubes-users:
On Fri, Sep 27, 2019 at 01:37:06PM +, Claudia wrote:
Isolating apps in the same VM is a different issue, but you're saying
traffic from different VMs is appearing to come from the same address?
Hmm, that definitely should not be happening. VM isolation is
On Fri, Sep 27, 2019 at 01:37:06PM +, Claudia wrote:
Isolating apps in the same VM is a different issue, but you're saying
traffic from different VMs is appearing to come from the same address?
Hmm, that definitely should not be happening. VM isolation is enabled
out of the box. Different
tetrahedra via qubes-users:
On Sun, Sep 22, 2019 at 02:51:00PM +, 'awokd' via qubes-users wrote:
tetrahedra via qubes-users:
Is there any way to automatically do stream isolation on a per-VM basis?
Right now it appears this is not necessarily the case -- the network
traffic of AppVMs A
On Sun, Sep 22, 2019 at 02:51:00PM +, 'awokd' via qubes-users wrote:
tetrahedra via qubes-users:
Is there any way to automatically do stream isolation on a per-VM basis?
Right now it appears this is not necessarily the case -- the network
traffic of AppVMs A and B may end up using the
tetrahedra via qubes-users:
> Is there any way to automatically do stream isolation on a per-VM basis?
> Right now it appears this is not necessarily the case -- the network
> traffic of AppVMs A and B may end up using the same Tor circuits (and
> exit nodes).
>
> Is there a way to set this up?
Is there any way to automatically do stream isolation on a per-VM basis?
For example:
I start AppVM "A", with networking via Whonix, and interact with the
internet as "Alice"
I start AppVM "B", with networking via Whonix, and interact with the
internet as "Bob"
Naturally I want Alice to
13 matches
Mail list logo
