Re: [qubes-users] Ubuntu Template
On Friday, June 30, 2017 at 6:59:25 AM UTC+8, Unman wrote: > On Wed, Jun 28, 2017 at 10:20:49PM -0700, Michael MENG wrote: > > Thank you so much for help, Unman, can you please give me step, i dont know > > how to export PATH, because i am very new in linux and qubes. > > > The PR has been merged, so you just need to 'git pull' and 'make > get-sources' before you try another build. yeah!!! Unman, Thank you so much, it's work, but do you know how to install libre office to template? and how to show unbuntu desktop? -- 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/809816bc-514e-4916-aad1-8d46654eca20%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 install problem: Encryption requested for LUKS device sda2 but no encryption key specified
This is similar to the issue I have as well. Cheers, Christian -- 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/3d5d89be-004b-4322-8fe9-f664de113a0d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] WWAN-Card not showing up in Fedora 24 based NetworkManager
Hello, while my WWAN-card (Sierra Wireless EM7345) was working under the default Fedora 23 template I have a problems to get it working under my fedora 24 templates (all based on the Qubes OS fedora-24-minimal template). Problem: the WWAN card is visible within my net-VM, but I can't see it under the Network Manager applet in the menu bar. Setup: WWAN-Card is passed to my sys-net VM via an usb-qube and visible in the net-VM: It seems that my WWAN-card is present in my sys-net, but even after setting up a connection in NetworkManager I can't see a WWAN entry in the applet of Network Manager like in Fedora23, where I then hit connect and done. In my template VM I have also installed ModemManagerwith: sudo dnf install ModemManager As suggested in other treads and sites I have run the following commands in my Net VM [user@my-sys-net ~]$ sudo systemctl start ModemManager [user@my-sys-net ~]$ sudo systemctl enable ModemManager I'm stuck, what am I missing? - PhR Some more details regading the WWAN card, attached to my net VM WWAN-card is present in the VM as USB-device: [user@my-sys-net ~]$ lsusb Bus 002 Device 007: ID 1199:a001 Sierra Wireless, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub All radios are enabled: [user@my-sys-net ~]$ nmcli g STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled [user@my-sys-net ~]$ nmcli r WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled A connection has also been created in Network Manager [user@my-sys-net ~]$ nmcli c NAMEUUID TYPEDEVICE Wired connection 1 f19dd69b-8f0c-3f36-aa29-bbd0370b7cd5 802-3-ethernet enp0s0 T-Mobile(Telekom) 29f32d95-ea6e-46a3-b754-b92283031aaf gsm -- Strangely my WWAN device is in status unmanaged [user@my-sys-net ~]$ nmcli d DEVICE TYPE STATE CONNECTION enp0s0 ethernet connected Wired connection 1 wlp0s1 wifi disconnected -- lo loopback unmanaged -- wwan0 wwan unmanaged -- My loaded kernel modules: [user@my-sys-net ~]$ nmcli g STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled [user@my-sys-net ~]$ nmcli n enabled [user@my-sys-net ~]$ nmcli e Error: Object 'e' is unknown, try 'nmcli help'. [user@my-sys-net ~]$ nmcli r WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled [user@my-sys-net ~]$ nmcli c NAMEUUID TYPEDEVICE Wired connection 1 f19dd69b-8f0c-3f36-aa29-bbd0370b7cd5 802-3-ethernet enp0s0 T-Mobile(Telekom) 29f32d95-ea6e-46a3-b754-b92283031aaf gsm -- [user@my-sys-net ~]$ nmcli d DEVICE TYPE STATE CONNECTION enp0s0 ethernet connected Wired connection 1 wlp0s1 wifi disconnected -- lo loopback unmanaged -- wwan0 wwan unmanaged -- -- 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/964c04a9-1919-b1bc-d0e5-1c9d353700da%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4 testing feedback
On Friday, July 7, 2017 at 7:55:01 PM UTC, PR wrote: > Hello, > > > As I'm reading the 2nd post about the Qubes OS v4 ... Where and how to become > a tester? > Looking under Qubes Downloads I couldn't find any information about an alpha > or beta version. > https://www.qubes-os.org/downloads/ > > > > Kind regards > > > - PhR > > Marek posted a pre-release built for testing. https://groups.google.com/forum/#!topic/qubes-devel/SYDnEdLBVu4 Regards -- 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/d3f7d23d-cdb5-4794-a579-93ec2de12255%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4 testing feedback
On Friday, July 7, 2017 at 7:55:01 PM UTC, PR wrote: > Hello, > > > As I'm reading the 2nd post about the Qubes OS v4 ... Where and how to become > a tester? > Looking under Qubes Downloads I couldn't find any information about an alpha > or beta version. > https://www.qubes-os.org/downloads/ > > > > Kind regards > > > - PhR > > > Am 07.07.2017 8:24 nachm. schrieb: > Sadly not working: > > 1) uefi known isue - I have to add /mapbs /noexitboot > > Then installer freezes at boot loader configuration process > > > > 2) libxl issue > > 2017-07-07 06:17:30.686+: libxl: > libxl_exec.c:226:libxl__xenstore_child_wait_deprecated: Device Model not ready > > 2017-07-07 06:17:30.687+: libxl: libxl_pci.c:991:qemu_pci_add_xenstore: > qemu refused to add device: :00:19.0,msitranslate=0,power_mgmt=0 > > 2017-07-07 06:17:30.687+: libxl: libxl_pci.c:1329:libxl__add_pcidevs: > libxl_device_pci_add failed: -3 > > 2017-07-07 06:17:30.687+: libxl: > libxl_create.c:1498:domcreate_attach_devices: unable to add pci devices > > 2017-07-07 06:17:31.475+: libxl: > libxl_exec.c:118:libxl_report_child_exitstatus: > /etc/xen/scripts/block-snapshot remove [6863] exited with error status 1 > > 2017-07-07 06:17:31.475+: libxl: > libxl_device.c:1225:device_hotplug_child_death_cb: script: Device > /dev/mapper/snapshot-fd04:13240061-fd04:13240044-fd04:13502187 does not exists > > 2017-07-07 06:23:05.349+: libxl: > libxl_exec.c:226:libxl__xenstore_child_wait_deprecated: Device Model not ready > > 2017-07-07 06:23:05.350+: libxl: libxl_pci.c:991:qemu_pci_add_xenstore: > qemu refused to add device: :00:19.0,msitranslate=0,power_mgmt=0 > > 2017-07-07 06:23:05.351+: libxl: libxl_pci.c:1329:libxl__add_pcidevs: > libxl_device_pci_add failed: -3 > > 2017-07-07 06:23:05.351+: libxl: > libxl_create.c:1498:domcreate_attach_devices: unable to add pci devices > > 2017-07-07 06:23:06.155+: libxl: > libxl_exec.c:118:libxl_report_child_exitstatus: > /etc/xen/scripts/block-snapshot remove [8131] exited with error status 1 > > 2017-07-07 06:23:06.156+: libxl: > libxl_device.c:1225:device_hotplug_child_death_cb: script: Device > /dev/mapper/snapshot-fd04:13240061-fd04:13240044-fd04:13502187 does not exists > > > > Tested on HP 8570w. Will try official release next. > > > > -- > > 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...@googlegroups.com. > > To post to this group, send email to qubes...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/f1d1987b-5279-4d20-a282-ae79f3683ee4%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. Marek posted a pre-release built for testing. https://groups.google.com/forum/#!topic/qubes-devel/SYDnEdLBVu4 Regards -- 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/563f728b-5088-4e01-8183-31259b2b10af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 install problem: Encryption requested for LUKS device sda2 but no encryption key specified
Confirmed. I'm having the same issue. -- 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/ba41803d-7957-47cd-a485-70274d6fbc6e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to kill Screensaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/03/2017 08:00 PM, evo wrote: > How can i kill this screensaver?? i deactivated it everywhere, but > it doesn't give a f... about my settings. > > it goes just over xscreensaver-command -exit > > but i must do it after every restart. > Disable it at Session and Startup -> Application Autostart - -- Regards -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJZX+63AAoJEGSin3PC/C0AlZkQAMW2XlenuVdwNnQrnlovkCdw PfNYwcbY580Sg+JTCxqGG2gI0WjvCDoDVFiW655dlS/1s2J6wrUWis8otesCNhmn UmSuc2DrAmyELp80yQofyDjiBYeMoKzl+H1PxHB35PFLnW5aEl9v8sMrjiJCvU+Z jk4uIeYr3pcaxgri6oTbe8+ElCNk5IYtJsFhFMkLzw8LIWXud3HceeXkMOWHS5Hv hMZuF3d272ivikp85yboFyYDMP+qNUEZpYRJr9RS6cdy3mN7KYc/QUbPesSj7+Ag gueoky+W6ro1RX7HyJDVMDztaugTIp9TL6YghiAVzglT76wy4KE6dHsRk6h+Jrxx zukZ1s2mKZSB6GmOwzSHOptaix3Ah3eG5q7ss4yI0u0TiD41i6PVsrc6BWsMnC2u 3oI8MAWQqrvk/9XNvMdLqzjRM9B8nN0vnbohfT+iLLKPD/Soc4QzqMgmij4Y/PqN MZxZkuxDap0a1I9UTGq2BhSk0r6unPXJ8EQF9dFUq/zcjuK2QEIVpU/SrIFvC5PP U7F+/cnCcbw9iC4fAjo2yvOgM4m4XmD1KG16Cq48XaPAXseUZDdSPo88KBPkeivz IxIGbh5OGgieGzhFThB8ToCbkMPSPGbdt5p3BFiAnadoHnFkJ2Kzs3YFFirpLik6 rMpQjOGKaATY72hXbEab =TUx2 -END PGP SIGNATURE- -- 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/c464fcb0-ce8d-c0cc-dabd-024855c74306%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4 testing feedback
Hello, As I'm reading the 2nd post about the Qubes OS v4 ... Where and how to become a tester? Looking under Qubes Downloads I couldn't find any information about an alpha or beta version. https://www.qubes-os.org/downloads/ Kind regards - PhR Am 07.07.2017 8:24 nachm. schrieb: > Sadly not working: > 1) uefi known isue - I have to add /mapbs /noexitboot > Then installer freezes at boot loader configuration process > > 2) libxl issue > 2017-07-07 06:17:30.686+: libxl: libxl_exec.c:226:libxl__ > xenstore_child_wait_deprecated: Device Model not ready > 2017-07-07 06:17:30.687+: libxl: libxl_pci.c:991:qemu_pci_add_xenstore: > qemu refused to add device: :00:19.0,msitranslate=0,power_mgmt=0 > 2017-07-07 06:17:30.687+: libxl: libxl_pci.c:1329:libxl__add_pcidevs: > libxl_device_pci_add failed: -3 > 2017-07-07 06:17:30.687+: libxl: > libxl_create.c:1498:domcreate_attach_devices: > unable to add pci devices > 2017-07-07 06:17:31.475+: libxl: > libxl_exec.c:118:libxl_report_child_exitstatus: > /etc/xen/scripts/block-snapshot remove [6863] exited with error status 1 > 2017-07-07 06:17:31.475+: libxl: > libxl_device.c:1225:device_hotplug_child_death_cb: > script: Device /dev/mapper/snapshot-fd04:13240061-fd04:13240044-fd04:13502187 > does not exists > 2017-07-07 06:23:05.349+: libxl: libxl_exec.c:226:libxl__ > xenstore_child_wait_deprecated: Device Model not ready > 2017-07-07 06:23:05.350+: libxl: libxl_pci.c:991:qemu_pci_add_xenstore: > qemu refused to add device: :00:19.0,msitranslate=0,power_mgmt=0 > 2017-07-07 06:23:05.351+: libxl: libxl_pci.c:1329:libxl__add_pcidevs: > libxl_device_pci_add failed: -3 > 2017-07-07 06:23:05.351+: libxl: > libxl_create.c:1498:domcreate_attach_devices: > unable to add pci devices > 2017-07-07 06:23:06.155+: libxl: > libxl_exec.c:118:libxl_report_child_exitstatus: > /etc/xen/scripts/block-snapshot remove [8131] exited with error status 1 > 2017-07-07 06:23:06.156+: libxl: > libxl_device.c:1225:device_hotplug_child_death_cb: > script: Device /dev/mapper/snapshot-fd04:13240061-fd04:13240044-fd04:13502187 > does not exists > > Tested on HP 8570w. Will try official release next. > > -- > 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/f1d1987b-5279-4d20-a282-ae79f3683ee4%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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/CAM8xnv%2BeJ0m4PzHxEnHX6JXz-fff6%3DZjCqgDqpaU4q7OadLs_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Changing default applications in dispvm template
Unman: > On Fri, Jul 07, 2017 at 01:49:54AM +, js...@riseup.net wrote: >> Hi everyone, >> >> I followed the instructions in the Qubes docs to create a dispvm >> template based on the whonix-ws template. I installed a few applications >> in the template (gedit, libreoffice, etc.) and I've been able to >> customize my dispvm by setting preferences in applications. >> >> I'm having trouble changing the default applications that files open in >> though. For example, whenever I open a plain text file in a dispvm, it >> opens in libreoffice. I want it to open in gedit instead. I'm having a >> similar issue with pdf and image files. >> >> I tried using update-alternatives in whonix-ws-dvm, but that didn't work >> for me (the only options for editors were non-gui editors like nano and >> vim). Changing the default application in the file manager (dolphin) in >> whonix-ws-dvm also doesn't work for me. >> >> I'm able to get around this by opening a terminal in a dispvm, then >> using the "copy to vm" feature to copy the text file to my new dispvm, >> then opening gedit in terminal, then opening the file from >> QubesIncoming, but this is a pain. >> >> Does anyone know how to change the default applications for dispvms? > > This has been covered a number of times on the list - it's a subset of > configuring the dispVMTemplate. If setting it in file manager doesnt > work then mimeopen should serve. > There was a thread "How to set file association in disposable VMs" 6 > months back - that should have everything you need. > > unman Thank you very much, the instructions in that other thread worked perfectly! I might have performed some unnecessary steps, but here's what I did: 1. Open dolphin in whonix-ws. 2. Set file association for all desired filetypes in dolphin. 3. Use mimeopen -d in whonix-ws terminal to set default for all filetypes. 4. Shut down whonix-ws. 5. qvm-run -a whonix-ws-dvm konsole in dom0 terminal to open terminal in whonix-ws-dvm. 6. Perform same steps as above (set file association in dolphin and with mimeopen -d). 7. touch /home/user/.qubes-dispvm-customized in whonix-ws-dvm terminal. 8. Shut down whonix-ws-dvm. 9. qvm-create-default-dvm whonix-ws in dom0 terminal. -- 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/27def6b9-b514-b1de-1ade-f146ea5b67fc%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4 testing feedback
Sadly not working: 1) uefi known isue - I have to add /mapbs /noexitboot Then installer freezes at boot loader configuration process 2) libxl issue 2017-07-07 06:17:30.686+: libxl: libxl_exec.c:226:libxl__xenstore_child_wait_deprecated: Device Model not ready 2017-07-07 06:17:30.687+: libxl: libxl_pci.c:991:qemu_pci_add_xenstore: qemu refused to add device: :00:19.0,msitranslate=0,power_mgmt=0 2017-07-07 06:17:30.687+: libxl: libxl_pci.c:1329:libxl__add_pcidevs: libxl_device_pci_add failed: -3 2017-07-07 06:17:30.687+: libxl: libxl_create.c:1498:domcreate_attach_devices: unable to add pci devices 2017-07-07 06:17:31.475+: libxl: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block-snapshot remove [6863] exited with error status 1 2017-07-07 06:17:31.475+: libxl: libxl_device.c:1225:device_hotplug_child_death_cb: script: Device /dev/mapper/snapshot-fd04:13240061-fd04:13240044-fd04:13502187 does not exists 2017-07-07 06:23:05.349+: libxl: libxl_exec.c:226:libxl__xenstore_child_wait_deprecated: Device Model not ready 2017-07-07 06:23:05.350+: libxl: libxl_pci.c:991:qemu_pci_add_xenstore: qemu refused to add device: :00:19.0,msitranslate=0,power_mgmt=0 2017-07-07 06:23:05.351+: libxl: libxl_pci.c:1329:libxl__add_pcidevs: libxl_device_pci_add failed: -3 2017-07-07 06:23:05.351+: libxl: libxl_create.c:1498:domcreate_attach_devices: unable to add pci devices 2017-07-07 06:23:06.155+: libxl: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block-snapshot remove [8131] exited with error status 1 2017-07-07 06:23:06.156+: libxl: libxl_device.c:1225:device_hotplug_child_death_cb: script: Device /dev/mapper/snapshot-fd04:13240061-fd04:13240044-fd04:13502187 does not exists Tested on HP 8570w. Will try official release next. -- 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/f1d1987b-5279-4d20-a282-ae79f3683ee4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 install problem: Encryption requested for LUKS device sda2 but no encryption key specified
Folks, I'm trying to install Qubes 3.2. It falls-back to the text mode and when choosing LVM I get: autopart failed Encryption requested for LUKS device sda2 but no encryption key specified for this device how do I specify the encryption key? -- 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/47b97399-d0c1-4420-b3a6-039c8bf4c0e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4 Fails to Boot With Coreboot
As recommended by Qubes, I have installed Coreboot on my X230 - which successfully runs Debian, Tails etc. I've tried to run Qubes 3.2 but although the Installer process works OK, Qubes refuses to boot [hangs]. From what I can gather, its a Zen issue that's preventing the boot. I had hoped the issue would be resolved in Qubes 4. However, I've been disappointed - I get exactly the same symptoms having downloaded the trial version from [https://ftp.qubes-os.org/~marmarek/Qubes-DVD-x86_64-20170706.iso](https://ftp.qubes-os.org/%7Emarmarek/Qubes-DVD-x86_64-20170706.iso) Is this an isolated example or is there a wider problem with Coreboot and Qubes? Sent with [ProtonMail](https://protonmail.com) Secure Email. -- 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/MGEZpVt6pYIaYOxOT7U0emGldUOgkz521w70eU6KKu_oqgrtrhNn6YMBoLabZmKIGBYpnoxU-7nRlIjC82QZf6VP4FIKzAYo_Bu017uqq4Q%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] QubesOS featured on Level1Techs Youtube channel
So, Level1Techs just made a video about QubesOS. Hopefully this will help attract more attention to the project. TYou can watch it here: https://www.youtube.com/watch?v=NTOsHtyS_5k -- 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/ed2ce0e4-18d2-48b9-bf57-8228b2bf31f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] high-level summary/introduction/explanation video of why one might want to use qubes (Level1Techs)
Part 1: https://www.youtube.com/watch?v=NTOsHtyS_5k -- 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/c1a06612-298f-4b13-a6be-a9369c85e63e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Win7 Template?
On Fri, Jul 07, 2017 at 06:42:02AM -0700, henrydoblin...@gmail.com wrote: > I have 2 use cases for Windows. > 1. Watch Netflix or Amazon etc. They reject the use of VPN and ask for > a lot of "information", which is basically ok for me. They don't have Linux support yet? That's just crazy... > 2. Banking. I have 2 banking applications that have multilevel > authentication one of which makes use of a usb token. Here I want a > usb-vm to connect these and only these usb devices. And I want a VPN > connection with a trusted server and on top of that a very restrictive > (IP-range based) Firewall. > > The two contradict. That's why I wanted a basic Windows installation > and from that two or more domains with specific configs. To answer your general question, that workflow is very much possible and officially documented (as you've already read in the docs). You will have to run a CLI command or two to create the initial template, but from there on it looks like you create them much the same way as any other template-based VM using the GUI tools. Hopefully someone else have more experience in using win7 in the normal TemplateVM sense and can share some notes. :-) > But your idea of cloning is interesting. It seems simple, but it's a > bit harddisk consuming ... Yeah, it's harddisk consuming and I have to upgrade each cloned VM manually... -- noor |_|O|_| |_|_|O| Noor Christensen |O|O|O| n...@fripost.org ~ 0x401DA1E0 -- 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/20170707144503.u3hr4xqfcpopr4do%40mail. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [qubes-users] After sys-usb installation and reboot can't type passphrase at boot (keyboard not attached)
It's really important that you take it steadily, and stay calm. At this stage I would ensure that I have all the data secure. Since you know how to decrypt your Qubes partition and mount it, you can take a backup of the data - the VMs are all in /var/lib/qubes - and the xml file you see there contains Qubes internal data. But the actual data can be secured by copying the appVM directories to an external drive. Do that and the feeling of panic will subside, because you know your data is safe. At that point you can do what you like - reinstall, or continue to try to solve the boot problem. I would have a cup of tea while the files are backing up - very soothing. -- 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/20170706202803.xu6rgj4ye7rjblyl%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout. Alright, good, thank you, I've done the backup of the whole /var/lib/qubes directory. Now that I'm more calm, I was thinking of doing the following to try to fix the boot problem: Since I have already deleted the sys-usb folder at /var/lib/qubes/servicevms/, I'm installing qubes OS in an external drive, and the thought behind it is to copy the relative boot folders and files of this working qubes OS, and paste in the internal HDD (with the broken boot/grub thing) in order to fix the boot. So basically the idea is to copy the currently working boot of the working qubes OS freshly installed in the external drive, and paste it in the broken qubes OS to fix it, and so be able to launch the OS again. NOW THE QUESTION IS, what folders and files should I copy? ANY IDEA? The alternative is to completely reinstall qubes, and replace the whole qubes folder (got from /var/lib/qubes) to import the old vms, but I would cringe a bit doing that since I had set up my qubes panels, mouse speed, general settings, etc. By the way Thank you a lot for the support shown till now, it really is super appreciated! - ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! -- 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/20170707110913.Horde.DyPTpMXjuMTEaIH0sh4t-al%40www.vfemail.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Win7 Template?
Hi Noor, thanx for the fast reply. > There is some information on this workflow in the official docs[0]. I read some of that but at times my understanding is limited. > Personally I just have one specific win7 HVM that I treat as the base > template, then make a clone from that one whenever I need a win7 VM. I am currently still using MacOS. But within the year I want to move to Qubes. I have 2 use cases for Windows. 1. Watch Netflix or Amazon etc. They reject the use of VPN and ask for a lot of "information", which is basically ok for me. 2. Banking. I have 2 banking applications that have multilevel authentication one of which makes use of a usb token. Here I want a usb-vm to connect these and only these usb devices. And I want a VPN connection with a trusted server and on top of that a very restrictive (IP-range based) Firewall. The two contradict. That's why I wanted a basic Windows installation and from that two or more domains with specific configs. But your idea of cloning is interesting. It seems simple, but it's a bit harddisk consuming ... Thanx, hen -- 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/0955cf7f-31b2-4507-bacd-7c0d77ed7da0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Win7 Template?
On Fri, Jul 07, 2017 at 03:15:00PM +0200, Noor Christensen wrote: > On Fri, Jul 07, 2017 at 05:57:42AM -0700, henrydoblin...@gmail.com wrote: > > is it possible to have a win7 Template VM in order to create > > disposable VMs from that? > > There is some information on this workflow in the official docs[0]. Whoops, here's the link[0]: https://www.qubes-os.org/doc/windows-appvms/#using-template-based-windows-appvms-qubes-r2-beta-3-and-later -- noor |_|O|_| |_|_|O| Noor Christensen |O|O|O| n...@fripost.org ~ 0x401DA1E0 -- 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/20170707134108.kpxb3rqtxzqvjux7%40mail. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
[qubes-users] Re: Best Desktop for Qubes
W dniu niedziela, 2 lipca 2017 19:28:26 UTC+2 użytkownik Zbigniew Łukasiak napisał: > A companion to the Best Laptop for Qubes thread :) > > Most of the HCL is filled with laptops - very few desktops are there, > especially on the high end. > > Currently I have a Dell Inspiron - works but 16GB RAM is max there > (and it is a non-ECC so most probably more than that does not make > much sense), and 16BG is not enough for me (browsers seem to eat > unbelievable amounts of RAM). > > Is there a recommended desktop system for Qubes with over 16GB RAM? > > -- > Zbigniew Lukasiak > http://brudnopis.blogspot.com/ > http://perlalchemy.blogspot.com/ Highly depends on the use case and budget. SO, a few questions first: - Does it have to be prebuilt or do You want to build it yourself? - Do you plan on using it for GPU-intensive tasks? - How much do you care about the looks/size/portability of your machine? - DO you already own some PC components? - What's your budget? -- 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/3ae88d60-6cb3-4bae-89a0-7fcb9a977807%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Win7 Template?
Hi, is it possible to have a win7 Template VM in order to create disposable VMs from that? hen -- 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/61ba8be0-49ee-4790-82eb-182840bee14d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes support for PS2 mouse / keyboard
W dniu piątek, 7 lipca 2017 01:11:51 UTC+2 użytkownik motech man napisał: > I just tried to switch my USB keyboard and USB mouse over to the PS2 inputs > with adapters but neither work. > > My question is does Qubes use installable modules for PS2 support? Is support > for PS2 compiled into the kernel or is it dynamic? > > It may be a hardware issue, but I just thought I'd ask here about the OS. > > I have only tried one keyboard and 1 mouse, the ones that came bundled with > the system. They are rather fancy gaming devices, both have LEDs for > decoration & backlighting. > > There doesn't seem to be any shortage of current to supply either device, all > look just as it plugged into a USB port. There is no signs however that Qubes > recognizes input from either. > > Was hoping for a simple conversion, but it doesn't look like that is likely. Qubes most definitely supports PS/2 keyboards as that's how I have mine hooked up. But in order for a simple passive adapter to work the keyboard itself must support PS/2 transmission mode (totally different from USB mode). Try using a native PS/2 keyboard or buy a mechanical keyboard as these not only support PS/2 transmission mode but also come with PS/2 adapters by default. -- 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/e240e3b2-dbc2-4d98-8428-0aa83ec0273a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Sys-net with a 2 port NIC, how to allow/block interfaces?
On Thu, Jul 06, 2017 at 07:22:51PM -0400, Essax wrote: > Hi Unman > Thanks ! Thats is exactly what I wanted to accomplish. Although I could use a > little clarification on a couple things. > > > You can examine the IP addresses allocated to the qubes using > > "qvm-ls -n". > > I ran this command and there are three ip addresses listed for most of the > qubes. Going from left to right---> I know the first one is the qube ip > address. The second ip address is only given to proxy-vms (What is this ip > for?) And the third ip address is the up stream gateway ip?? > > > Each firewall provides masquerade NAT to downstream qubes. This means > > that you can simply do the following: > > firewall-vm0 : eth0 - 10.137.10.10 > > firewall-vm1 : eth0 - 10.137.10.100 > > I'm sure you can guess my next question. Those two ip addresses would be the > actual ip of the qubes. (sorry I have to be sure : ) > Essax > Sent with [ProtonMail](https://protonmail.com) Secure Email. > > > Original Message > > Subject: Re: [qubes-users] Sys-net with a 2 port NIC, how to allow/block > > interfaces? > > Local Time: July 5, 2017 9:24 PM > > UTC Time: July 6, 2017 1:24 AM > > From: un...@thirdeyesecurity.org > > To: Essax> > Google groups Qubes-users > > On Wed, Jul 05, 2017 at 08:08:02PM -0400, "Essax" via qubes-users wrote: > >> I have laptop with a 2 port NIC. I would like to have 1 subset of appVMs > >> that are connected to sys-net to use the eth0 interface and the other > >> subset to use the eth1 interface. It is not possible to assign 1 port into > >> seperate sys-nets. I have tried that and only eth0 will function. Its also > >> my understanding that eth0 is the interface used between qubes. ( is this > >> wrong? ) If so would this prevent me from using iptables in firewall-vm1 > >> to block traffic to the eth0 interface. That would block traffic to > >> sys-net as well (I think). The only solution I have come up with would be > >> to go to dom0 GUI --> appvm1---> edit VM firewall rules ---> allow > >> networks except 172.16.1.1/24 . This would not block traffic to the eth0 > >> interface but it would prevent if from going any further than the > >> 172.16.1.1 pfsense interface. Then I could do the same for firewall-vm0 > >> and block it from the 192.168.1.1 pfsense interface. Is there a better way > >> to do this with iptables. > >> pfsense-192.168.1.1/24eth1firewall-vm1appvm1 > >> sys-net > >> pfsense-172.16.1.1/24--eth0firewall-vm0VPN/proxyvmappvm0 > >> > >> Thanks in advance > >> Essax > > I"m not sure what you mean by "eth0 is the interface used between > > qubes". Each qube is attached to its upstream proxy, its eth0 > > connecting to a vifX interface on the proxy. > > You can examine the IP addresses allocated to the qubes using > > "qvm-ls -n". > > On your proposal the downstream qubes would only be able to connect to > > the networks attached to eth0 and eth1. This may be what you want. If > > you want to connect to the net (or another network) via those connected > > networks, there is an alternative. > > Each firewall provides masquerade NAT to downstream qubes. This means > > that you can simply do the following: > > firewall-vm0 : eth0 - 10.137.10.10 > > firewall-vm1 : eth0 - 10.137.10.100 > > On sys-net- > > iptables -I FORWARD -o eth0 -j DROP > > iptables -I FORWARD -o eth1 -j DROP > > iptables -I FORWARD -s 10.137.10.100 -o eth1 -j ACCEPT > > iptables -I FORWARD -s 10.137.10.10 -o eth0 -j ACCEPT > > Those rules explicitly block and allow traffic. You could combine into > > one rule but this makes it clearer what is happening and will allow you > > to track counters as traffic flows. > > I think it"s neater than your proposal. > > You"ll also want to keep the rules allowing established traffic back > > though sys-net. > > You can put these rules in to rc.local, and qubes-firewall-user-script, > > as set out here: > > www.qubes-os.org/doc/firewall > > unman So if you look at the top of the output you will see some helpful headings. The first address is that of eth0. The second is the address used on vif interfaces to conenct downstream. The third is the address of the upstream netvm, (and so will match the 2nd IP address of THAT qube) In answer to your question, the IP adresses I have shown in example are those of eth0 (1st in qvm-ls -n output) - all traffic going through the firewall will appear on sys-net to derive from this address, unless you are doing something clever. So yes, on sys-net put rules acting on those IP addresses. Hope it's all clear now unman -- 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
Re: [qubes-users] Changing default applications in dispvm template
On Fri, Jul 07, 2017 at 01:49:54AM +, js...@riseup.net wrote: > Hi everyone, > > I followed the instructions in the Qubes docs to create a dispvm > template based on the whonix-ws template. I installed a few applications > in the template (gedit, libreoffice, etc.) and I've been able to > customize my dispvm by setting preferences in applications. > > I'm having trouble changing the default applications that files open in > though. For example, whenever I open a plain text file in a dispvm, it > opens in libreoffice. I want it to open in gedit instead. I'm having a > similar issue with pdf and image files. > > I tried using update-alternatives in whonix-ws-dvm, but that didn't work > for me (the only options for editors were non-gui editors like nano and > vim). Changing the default application in the file manager (dolphin) in > whonix-ws-dvm also doesn't work for me. > > I'm able to get around this by opening a terminal in a dispvm, then > using the "copy to vm" feature to copy the text file to my new dispvm, > then opening gedit in terminal, then opening the file from > QubesIncoming, but this is a pain. > > Does anyone know how to change the default applications for dispvms? This has been covered a number of times on the list - it's a subset of configuring the dispVMTemplate. If setting it in file manager doesnt work then mimeopen should serve. There was a thread "How to set file association in disposable VMs" 6 months back - that should have everything you need. unman -- 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/20170707114147.a55qp3bg4aoi2yps%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - System76 Galago Pro (galp2)
Installation: - X failed to start in the installer for both the normal graphical install and the basic graphics mode - The text based installed was too borked to use - Added `inst.vnc inst.vncpassword=testpwd` as described in the anaconda docs to the bootline to get anaconda to run the graphical install using a VNC server - I was then able to install Qubes via VNC from a separate system Initial run(s): - X failed to start - I mostly followed the steps laid out in https://groups.google.com/forum/#!topic/qubes-users/Ot2u03aUmnc , except ethernet wasn't working so I added the entire USB device to the "netvm" VM from it to use a USB ethernet adapter Ethernet: - doesn't work (even post system update) - Attempting to add the ethernet device to a vm results in libxl errors (the first time, e.g. "The kernel doesn't support reset from sysfs for PCI device ") - On a second run of the `qvm-pci -a` command, it "works" insofar as the VM sees the device and it shows up in `ifconfig -a` - The ethernet adapter is not actually usable in this state - Attempting to boot a VM with the ethernet device added prevents the VM from booting with errors Screen: - After installing updates to that X can actually run, it "works" - Since the screen is HiDPI, everything is tiny to the point of being painful to read - Fixing the `xfce settings -> appearance -> font -> dpi` setting only sort-of works for dom0 - The personal vm seems to get this fine, or at least Firefox and gnome-terminal running in it scales properly Speakers: - work! Headphone jack: - works! Microphone: - not sure, the mixer seems to show it working, but gnome-sound-recorder in the sys-usb vm hangs Suspend: - laptop eventually turns off, and then doesn't come back again Wireless: - works! HDMI: - works! Mini DisplayPort: - doesn't appear to work USB: - the 3.0 A ports appear to work - the C port doesn't appear to work Bluetooth: - seems to show up under USB - haven't tested it -Jeff -- 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/CAKsSGx9wDxxev5pMFaiQ-V_qqr33-7hHG3O14-_XjrqLfPPw_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Notebook-N130BU-20170707-040644.cpio.gz Description: GNU Zip compressed data Qubes-HCL-Notebook-N130BU-20170707-040644.yml Description: application/yaml
[qubes-users] AEM failure after upgrade
The AEM package was upgraded recently (probably because of this thread: https://groups.google.com/forum/#!topic/qubes-users/3ZkmS5v7E38), and after I installed the updated version, AEM stopped working completely. Now, it asks me for the AEM password. I type it in, and it doesn't display my secret message. Instead, it immediately asks me for the disk password, and while it boots the system, I see a message telling me: "PCR sanity check failed". I have tried to completely clear and reinstall AEM several times, but the same issue persists. This is the content of the journalctl log: Jul 07 16:25:36 dom0 systemd[1]: Starting Anti Evil Maid sealing... Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: tpm_z_srk: detecting whether SRK is password protected Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: Tspi_Key_CreateKey failed: 0x0001 - layer=tpm, code=0001 (1), Authentication failed Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: tpm_z_srk: yes, SRK is password protected; resetting dictionary attack lock... Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-17: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-18: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jul 07 16:25:39 dom0 anti-evil-maid-seal[1982]: PCR-19: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jul 07 16:25:39 dom0 systemd[1]: anti-evil-maid-seal.service: Main process exited, code=exited, status=1/FAILURE Any idea what the cause of this issue could be? Regards, Elias -- 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/36028d9f-fb42-4761-b605-ef69d219fb18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes support for PS2 mouse / keyboard
There are quite a lot of 'modern' HIDs that no longer support ps/2 via converter; google may be able to tell you whether your devices do. ps/2 should 'just work', unless you built and are running a kernel with support disabled. -- 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/9b28b9de-9463-4ce5-8b12-51a473ab0854%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.