Re: [qubes-users] Safely use USB keyboard and untrusted USB devices with only 1 USB controller?
[2017-05-23 15:18] Vít Šesták: > So, I've created DVM-like sys-usb and it the first working version was easier > than I thought. Just make /var/lib/qubes/servicevms/sys-usb/private.img an > empty file. I have renamed the original file and performed "touch > private.img". > > VM sys-usb then still boots and works as USB input proxy. It does not run X11 > apps until I create+chown /home/user and perform systemctl restart > qubes-gui-agent.service, but it does not matter so much. Thanks for the tip! I did it and hope it's working. But now sometimes I need to "replug" mouse or/and keyboard after boot for them to work... -- 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/149977468708.5204.3258625358229903159%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: kali failing to start as a HVM (bootable iso)
[2017-07-06 17:18] Unman: > Can you check the command line? > In the thread it is incorrect and i want to make sure that you havent > been misled. > The correct format would be something like: > qvm-start --cdrom=:/home/user/kali.iso Sure. This didn't work: $ qvm-start hvm --cdrom=media:/home/user/a.iso Then I copied the ISO to dom0 and this worked: $ qvm-start hvm --cdrom=/home/user/a.iso -- 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/149937311226.6232.15817870788107264063%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: kali failing to start as a HVM (bootable iso)
I just copied the debian ISO to dom0 and it booted (installing at this very moment, let's see if works). So it can't boot the ISO from inside another VM... No idea why... And yes, I checked the path many times, even moved and renamed to a short path (/home/user/a.iso) and set permissions to 777. [2017-07-06 12:20] Andres MRM: > [2017-07-06 11:33] Unman: > > > You can see packkage information from QubesManager - About - Qubes OS - > > Version Information. > > xen_version: 4.6.5 > Linux 4.4.38-11.pvops.qubes.x86_64 > > Installed Packages: > > i3-settings-qubes.x86_64 > 1.2-1.fc23 > kernel-qubes-vm.x86_64 > 1000:4.4.62-12.pvops.qubes > kernel-qubes-vm.x86_64 > 1000:4.4.67-12.pvops.qubes > kernel-qubes-vm.x86_64 > 1000:4.4.67-13.pvops.qubes > qubes-anaconda-addon.noarch > 3.2.3-1.fc23 > qubes-artwork.noarch > 3.2.0-2.fc23 > qubes-core-dom0.x86_64 > 3.2.14-1.fc23 > qubes-core-dom0-doc.noarch > 3.2.14-1 > qubes-core-dom0-linux.x86_64 > 3.2.13-1.fc23 > qubes-core-dom0-linux-kernel-install.x86_64 > qubes-db.x86_64 > 3.2.3-1.fc23 > qubes-db-dom0.x86_64 > 3.2.3-1.fc23 > qubes-db-libs.x86_64 > 3.2.3-1.fc23 > qubes-gpg-split-dom0.x86_64 > 2.0.24-1.fc23 > qubes-gui-dom0.x86_64 > 3.2.11-1.fc23 > qubes-img-converter-dom0.x86_64 > 1.2.3-1.fc23 > qubes-input-proxy.x86_64 > 1.0.8-1.fc23 > qubes-libvchan-xen.x86_64 > 3.2.1-1.fc23 > qubes-manager.x86_64 > 3.2.11-1.fc23 > qubes-menus.noarch > 2.0-1 > qubes-mgmt-salt.noarch > 3.2.5-1.fc23 > qubes-mgmt-salt-admin-tools.noarch > 3.2.5-1.fc23 > qubes-mgmt-salt-base.noarch > 3.2.2-1.fc23 > qubes-mgmt-salt-base-config.noarch > 3.2.2-1.fc23 > qubes-mgmt-salt-base-overrides.noarch > qubes-mgmt-salt-base-overrides-libs.noarch > qubes-mgmt-salt-base-topd.noarch > 3.2.1-1.fc23 > qubes-mgmt-salt-config.noarch > 3.2.5-1.fc23 > qubes-mgmt-salt-dom0.noarch > 3.2.5-1.fc23 > qubes-mgmt-salt-dom0-qvm.noarch > 3.2.1-1.fc23 > qubes-mgmt-salt-dom0-update.noarch > 3.2.0-1.fc23 > qubes-mgmt-salt-dom0-virtual-machines.noarch > qubes-pdf-converter-dom0.x86_64 > 2.1.2-1.fc23 > qubes-release.noarch > 3.2-0.26 > qubes-release-notes.noarch > 3.2-0.26 > qubes-template-archlinux.noarch > 3.0.6-201611130159 > qubes-template-debian-8.noarch > 3.0.6-201608090120 > qubes-template-fedora-23.noarch > 3.0.6-201608081228 > qubes-template-whonix-gw.noarch > 3.0.6-201608050041 > qubes-template-whonix-ws.noarch > 3.0.6-201608050146 > qubes-usb-proxy-dom0.noarch > 1.0.5-1.fc23 > qubes-utils.x86_64 > 3.2.4-1.fc23 > qubes-utils-libs.x86_64 > 3.2.4-1.fc23 > xfce4-settings-qubes.x86_64
Re: [qubes-users] Re: kali failing to start as a HVM (bootable iso)
[2017-07-06 11:33] Unman: > You can see packkage information from QubesManager - About - Qubes OS - > Version Information. xen_version: 4.6.5 Linux 4.4.38-11.pvops.qubes.x86_64 Installed Packages: i3-settings-qubes.x86_64 1.2-1.fc23 kernel-qubes-vm.x86_64 1000:4.4.62-12.pvops.qubes kernel-qubes-vm.x86_64 1000:4.4.67-12.pvops.qubes kernel-qubes-vm.x86_64 1000:4.4.67-13.pvops.qubes qubes-anaconda-addon.noarch 3.2.3-1.fc23 qubes-artwork.noarch 3.2.0-2.fc23 qubes-core-dom0.x86_64 3.2.14-1.fc23 qubes-core-dom0-doc.noarch 3.2.14-1 qubes-core-dom0-linux.x86_64 3.2.13-1.fc23 qubes-core-dom0-linux-kernel-install.x86_64 qubes-db.x86_64 3.2.3-1.fc23 qubes-db-dom0.x86_64 3.2.3-1.fc23 qubes-db-libs.x86_64 3.2.3-1.fc23 qubes-gpg-split-dom0.x86_64 2.0.24-1.fc23 qubes-gui-dom0.x86_64 3.2.11-1.fc23 qubes-img-converter-dom0.x86_64 1.2.3-1.fc23 qubes-input-proxy.x86_64 1.0.8-1.fc23 qubes-libvchan-xen.x86_64 3.2.1-1.fc23 qubes-manager.x86_64 3.2.11-1.fc23 qubes-menus.noarch 2.0-1 qubes-mgmt-salt.noarch 3.2.5-1.fc23 qubes-mgmt-salt-admin-tools.noarch 3.2.5-1.fc23 qubes-mgmt-salt-base.noarch 3.2.2-1.fc23 qubes-mgmt-salt-base-config.noarch 3.2.2-1.fc23 qubes-mgmt-salt-base-overrides.noarch qubes-mgmt-salt-base-overrides-libs.noarch qubes-mgmt-salt-base-topd.noarch 3.2.1-1.fc23 qubes-mgmt-salt-config.noarch 3.2.5-1.fc23 qubes-mgmt-salt-dom0.noarch 3.2.5-1.fc23 qubes-mgmt-salt-dom0-qvm.noarch 3.2.1-1.fc23 qubes-mgmt-salt-dom0-update.noarch 3.2.0-1.fc23 qubes-mgmt-salt-dom0-virtual-machines.noarch qubes-pdf-converter-dom0.x86_64 2.1.2-1.fc23 qubes-release.noarch 3.2-0.26 qubes-release-notes.noarch 3.2-0.26 qubes-template-archlinux.noarch 3.0.6-201611130159 qubes-template-debian-8.noarch 3.0.6-201608090120 qubes-template-fedora-23.noarch 3.0.6-201608081228 qubes-template-whonix-gw.noarch 3.0.6-201608050041 qubes-template-whonix-ws.noarch 3.0.6-201608050146 qubes-usb-proxy-dom0.noarch 1.0.5-1.fc23 qubes-utils.x86_64 3.2.4-1.fc23 qubes-utils-libs.x86_64 3.2.4-1.fc23 xfce4-settings-qubes.x86_64 3.2.2-1.fc23 > Are you using standard repositories, or have yu enabled testing? Yes and no. -- 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/149935443037.7886.1054297749536477904%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: kali failing to start as a HVM (bootable iso)
[2017-07-05 19:30] Unman: > I see this error if there's a typo in the filename or permissions are > wrong. > Otherwise it works as expected - what versions of the Qubes packages are > you using? What are specs of your box? Plenty of RAM? Thanks for the reply! I noticed it gives the same error for filename typos, so I checked the path multiple times and even copied the file to /a.iso to make sure. The permissions of the images are "-rw-r--r--" owned by user. My RAM is 8GB, and the error seems to change when there isn't enough RAM (when many VMs are running), so I think this is not the case. Not sure about Qubes packages version, but I just did a qubes-dom0-update to test, and still same error. -- 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/149934383589.7886.10799018145966845381%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Safely use USB keyboard and untrusted USB devices with only 1 USB controller?
Thanks for the replies! [2017-03-27 22:13] cooloutac: > so I guess just take your chances with it on the usb qube. I do it with > mouse never seen anything weird happen. a wireless mouse too. although I > probably should put lock screen on I just realized I don't even have it on. I setup an USB qube. It's working well, for now. =) [2017-03-28 04:03] Vít Šesták: > DVM for sys-usb would be cool, but I don't think it is possible today. The > main challenge is probably to attach a PCI device to DVM. Well, maybe if you > clone/tune qfile-daemon-dvm or related files… After you attach the USB > controller to the DVM, you have essentially won; you will probably need just > to upload and run some script (for starting the input proxy) to the USBDVM. > Thos should be trivial, compared to attaching the USB device. Is there any difference between using a DVM as USB qube, or just recreating the USB qube when needed (e.g.: after using an untrusted pen drive)? Best 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/149070066109.1245.5774877112809671387%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Safely use USB keyboard and untrusted USB devices with only 1 USB controller?
[2017-03-26 21:14] cooloutac: > what about using the internal kb, no good? No... I'm using an ergonomic one. It wasn't cheap, it's very different from a common one and it took me months to get used to it. =P -- 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/149057415942.803.181230451023176868%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Safely use USB keyboard and untrusted USB devices with only 1 USB controller?
> ehci is for older usb protocol. xhci is for 3.0, maybe there is option in > bios to disable usb 3.0. then maybe it will have separate routed > controllers? Thats how it works on my desktop pc. otherwise all controllers > get routed through the xhci one. but then you will be giving up usb 3.0, > but maybe worth it not to have kb in sys-usb. Thanks, cooloutac! I checked my BIOS, but couldn't find an option to disable USB 3.0. =/ -- 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/149052994964.798.1907313827177849368%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Safely use USB keyboard and untrusted USB devices with only 1 USB controller?
[2017-03-22 18:52] cooloutac: > not sure but if its like my pc when using xhci (usb 3.0) everything goes > through thaT one controller. it look like you have ehci controller too but > not sure. What I do with one controller is use a usb to pci adapter for the > kb. For mouse you can use the qubes proxy, not as bad as also having kb in > usbvm. Thanks, cooloutac! What do you mean by "it look like you have ehci controller too"? What is it? Can it help me? Unfortunately my notebook has no PCI port... -- 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/149027169476.4535.10778284502551220775%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Safely use USB keyboard and untrusted USB devices with only 1 USB controller?
Thanks for the replies, Unman and Andrew. And sorry for not answering you before, Unman, but I only saw your message now. [2017-03-19 20:48] Unman: > Try 'lspci|grep USB' > Alternatively, look in QubesManager on the devices tab, and see how many > Controllers are there. # lspci|grep USB 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) In the devices tab of any VM I also can see these 3 controllers. But, by the output of the other commands, it seems all my external devices are connected to the first controller, no? (Bus 4 and 3, that have id 00:14.0) 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/149000620962.1073.4482443968028805728%40email. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Safely use USB keyboard and untrusted USB devices with only 1 USB controller?
Thanks for the reply, Andrew! [2017-03-19 19:13] Andrew David Wong: > That's up to you. The pros and cons are, I think, pretty clearly laid > out on the USB page. If you have specific questions that aren't > addressed there, please feel free to ask. That's what I feared... =/ I think I have no option, for I can only forward the smartphone to an "adb" qube if the USB controller is in a USB qube, right? (can't do that from dom0) Do the USB qube get reset every reboot (like a DVM)? That would reduce the threat, I think... And about the commands' outputs, any idea if they really mean only one USB controller? Thanks! -- 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/148997117881.900.6223634171823122302%40email. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: [Arch Linux + i3] High CPU usage after closing windows
[2017-03-19 18:04] : > Hi, guys. Can you help me with this error ? > > Curl: (22) The requested URL returned error: 404 non found Hi! Does the VM has internet connection? Can you ping something? If not, maybe you need to change settings (QubesManager) so it connects through a NetVM. Me: > Any ideas about where to place a "xmodmap ~/.Xmodmap"? I added a .desktop to .config/autostart/, but it's not really good. It required a "sleep 1" before "xmodmap ~/.Xmodmap" for it to work... -- 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/148997026899.900.13212364451618759185%40email. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Arch Linux + i3] High CPU usage after closing windows
Thanks for the fast reply, Olivier! But no, I don't think it's related. The problem seems indeed to be with zsh cofig, but it only showed up after VM reboot. Sorry for the confusion. It seems the command that was causing the problem was "xset r rate 200 45". (no reason for running it in a VM since it should be configured in dom0, right?) And, yes, I know such command shouldn't be placed in .zshrc, but .xinitrc is not being run at X startup... Any ideas about where to place a "xmodmap ~/.Xmodmap"? rc.local seems not to work for this (maybe it is run before X startup? Thanks! -- 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/148993515432.807.7757520650894350868%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Mount different folders on same partition to different AppVMs?
Thanks, Unman! It's an interesting idea! I'll see what fits better for my case. -- 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/148924980771.898.11742464822643325426%40utopos. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Archlinux Community Template Qubes OS 3.2
[2017-03-09 19:24] Franz: > For me IgnoreGroup has no effect, but IgnorePkg = xorg-server pulseaudio does > prevent the update of xorg-server and pulseaudio, but the same, after that I > get: > > warning: pulseaudio: ignoring package upgrade (9.0-1 => 10.0-2) > warning: xorg-server: ignoring package upgrade (1.18.4-1 => 1.19.2-1) > resolving dependencies... > looking for conflicting packages... > :: xf86-input-evdev and xorg-server are in conflict. Remove xorg-server? [y/N] > n > error: unresolvable package conflicts detected > error: failed to prepare transaction (conflicting dependencies) > :: xf86-input-evdev and xorg-server are in conflict (xorg-server<1.19.0) > > I have no idea how to handle that. Hi, Franz! I just kept adding the packages to IgnorePkg, until I added one to IgnorePkg and the two main ones to IgnoreGroup. Then it worked. That's why I thought the IgnoreGroup ignored the rest of them, but maybe I just added them all to IgnorePkg. 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/148910340817.869.12531924820380016881%40utopos. For more options, visit https://groups.google.com/d/optout.
