Alot of this is posted on the reddit.com/r/qubes board, there are alot of problems with 3.2, both security + function.
1. Dom0 is exposed to Sata connected drives. This is evident when running qubes on a usb connected drive going into dom0 file manager, the sata drive is automatically mounted and exposed to dom0. Part of Tails security is to require auth and manual mounting of locally connected drives, if this is not necessary for some reason users are owed an explanation. 2. Attaching USB controller to a usbVM (running qubes on a sata connected disk), renders all vm's unable to start, even after controller is detatched. Short-term remedy is to detatch and reboot. My entire equipment hierarchy is intel, recent hardware, compatibility should not be an issue. 3. Installing a printer produces an authentication window when attempting to add a printer. The documentation doesnt provide what those login details are, attempting to use ones user login credentials is denied. Also there are some minor issues that should be addressed: 4. Two [Dom0 monitor configuration] windows pop up everytime a VM is started. 5. VM manager signals that dom0/templates require updates even when it reports there are no updates in the update window. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9d268a2a0904c318fa75471cb37db4a1.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
