I see that 4.0rc2 is due out in a little over a week. Does anyone know if
there'll be an upgrade path from rc1 to rc2, or if complete re-install will
be preferred? I'm trying to decide how invested I should get in my current
4.0rc1 setup.
Thanks,
Sean
--
You received this message because yo
On Thu, Aug 24, 2017 at 4:28 PM
wrote:
>
> Issue 1: Copying files from dom0 seems to be broken.
>
> qvm-copy-to-vm hangs and never completes. sending a SIGINT results in
> error message popup: qfile-unpacker: Fatal error: Child process exited
> abnormally(error type: File exists). Python trace
I spent a while fighting with this myself with the same dock. Turns out
the dock adds USB and ethernet support via PCI hot adding some new PCI
devices. The Qubes kernel has also disabled PCI hot add disabled in order
to block some attack vectors.
Everything on the dock should work if you turn on
If you set it up as:
AppVM -> TorVM -> VpnVM -> NetVM
The VPN VM will use the Net VM to talk to the VPN server
The Tor VM will use the VPN VM to talk to the next Tor node, then to your
website
With this, the website will see you coming from a Tor exit node.
AppVM -> VpnVM -> TorVM -> NetVM
Wit
On Mon, Aug 14, 2017 at 6:53 AM Sean Dilda wrote:
> On Mon, Aug 14, 2017 at 6:23 AM ora...@riseup.net
> wrote:
>
>
>> for me fresh install on x230 using legacy boot and there is no grub, so
>> how make the iommu=no-igfx edit?
>>
>
> I had to make the same
On Mon, Aug 14, 2017 at 6:23 AM ora...@riseup.net wrote:
> for me fresh install on x230 using legacy boot and there is no grub, so
> how make the iommu=no-igfx edit?
>
I had to make the same edit.. however, I did see the grub screen for a few
seconds until it started the boot, and rebooted the
I'm playing around with Qubes 4.0rc1 and I noticed that the IPs that are
getting assigned internally to my AppVMs are possible conflicts for me.
Does anyone know what IP ranges are used internally? And how do we
configure which ranges it can use?
Thanks!
--
You received this message because yo
