Re: [qubes-users] Switch of DMA altogether..?
OK. This is getting confusing. So you are now saying that you can't do a DMA attack over the web..? If I had one computer connected to another via Ethernet crossover, could one computer infect the other via DMA by sending the DMA attack over the crossover cable..? Or can a computer only launch a DMA attack on itself? -- 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/6a7e0a00-72a4-4939-804b-0687e08bad4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Switch of DMA altogether..?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 07, 2016 at 01:31:56PM -0700, neilhard...@gmail.com wrote: > Another question... > > Are DMA attacks on Ethernet are even plausible? > > WiFi seems much more vulnerable than Ethernet, due to more complexity. I think there is misunderstanding here about "DMA attack". It have nothing to do with breaking to the system from the outside. It is only about spreading from _already compromised VM_ to other parts of the system. Any DMA-capable device can be used for this, regardless of its complexity. Using VT-d effectively block such attacks. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJX+ApMAAoJENuP0xzK19cskZwH/inLEGvBCKqCa6eigQwVJeVT ILXrTt4oBMlfB3KMPjNwKmxjNkDWZ1yDVx7G9WUQZD/aJRwkmD23NyW5cTFf4mvZ pfTRrH8iz3Ass+++y3m1ttDxcn09KHBNYEa+qY+rkjj9cbLv9hygKk0xphsnUAtD HZjKAWEl/FiDB1wyGRYhfdUaSOKInngYXd2y1+UyYsnG0OYPmnDoDVZRgRedxNxr mdop0Ah0I1shFitbKzw+tyVdmpBJnfJIIbRYa/NSeXFGs8tk/gnQ0pnkscNtWLuf DZ5eiV2P7jLaMQ7G0Izei2hqcy7C/PPg57gaIV8yAHG37ybJsY8FJ8SejkW/CbE= =VwqX -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/20161007204917.GL15776%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - HP EliteBook 8560w
Qubes-HCL-Hewlett_Packard-HP_EliteBook_8560w-20161007-224417.cpio.gz Description: GNU Zip compressed data --- layout: 'hcl' type: 'notebook' hvm: 'yes' iommu: 'no' slat: 'yes' tpm: '' brand: | Hewlett-Packard model: | HP EliteBook 8560w bios: | 68SVD Ver. F.50 cpu: | Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz cpu-short: | FIXME chipset: | Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) chipset-short: | FIXME gpu: | NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation 82579LM Gigabit Network Connection (rev 04) Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) memory: | 16334 scsi: | SAMSUNG MZ7PC256 Rev: 5H1Q DVDRAM GT50N Rev: MP00 versions: - works: 'FIXME:yes|no|partial' qubes: | R3.2 xen: | 4.6.1 kernel: | 4.4.14-11 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK --- -- 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/2939a677d17c32afc6e0c5e390138175%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Switch of DMA altogether..?
Another question... Are DMA attacks on Ethernet are even plausible? WiFi seems much more vulnerable than Ethernet, due to more complexity. -- 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/999d2ee0-f6aa-4617-80de-9264d87be87e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot start qubes-guid!
The first thing that I have done On 10/7/2016 at 7:53 PM, "Andrew David Wong" wrote:On 2016-10-07 04:12, illix...@hushmail.com wrote: > Hello > I was updating my whonix-ws but maybe it was reboot and I closed it. > Now I can't start more it and shows up this message > > "Error starting vm: cannot start qubes-guid!" > > Reading some post I run this command > > qvm-run whonix-ws --nogui --pass-io -u root "journalctl -xb | grep -i > -E "error|fail|qubes-gui" > > The result is: > > .host kernel: Could not initialize VPMU for cpu 0, error -95 > .host kernel: dmi: Firmware registration failed. > .host systemd[1]: Failed to insert module 'kdbus" : Function not > implemented > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host kernel: Error: Driver 'pcspkr' is already registered > aborting.. > > Any help is appreciated > Have you tried restarting the host? -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -- 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/20161007200601.C07CFE072B%40smtp.hushmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Switch of DMA altogether..?
" The original cards, the NE1000 (8-bit ISA; announced as "E-Net adapter" in February 1987 for 495 USD) and NE2000 (16-bit ISA), and the corresponding use of limited 8-bit and later 16-bit DMA in the NE2000 " That seems to say that DMA is in fact used in the NE2000. By the way, will these cards support modern Ethernet cables, like cat5e...? Do they support Ethernet crossover? 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/a4eb75f1-3a78-48f5-addf-063e014f79fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] mounting a qemu-img'd file error?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 07, 2016 at 11:30:58AM -0700, gaikokujinkyofu...@gmail.com wrote: > On Thursday, October 6, 2016 at 11:11:47 PM UTC-4, Marek Marczykowski-Górecki > wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On Mon, Oct 03, 2016 at 06:51:39PM -0700, gaikokujinkyofu...@gmail.com > > wrote: > > > I converted a vdi file over to a raw file which seemed to go fine but > > > mounting it is not going so well. mount seems to be having problems with > > > the file sys. I have tried auto but no luck, I tried manually specifying > > > but no luck. It was whonix so I assumed it was ext3 or 4 (or 2, tried em > > > all) but no luck. > > > I have tried specifying offset points (2480 here) and just "loop" etc... > > > nada > > > > > > fdisk -l tells me: > > > Disk whonix.raw: 4 GiB, 4294967296 bytes, 8388608 sectors > > > Units: sectors of 1 * 512 = 512 bytes > > > Sector size (logical/physical): 512 bytes / 512 bytes > > > I/O size (minimum/optimal): 512 bytes / 512 bytes > > > Disklabel type: dos > > > Disk identifier: 0x3d6b07dc > > > > > > Device Boot Start End Sectors Size Id Type > > > whonix.raw1 2048 8388607 8386560 4G 83 Linux > > > > > > thoughts? > > > > Try `losetup -P /dev/loop0 whonix.raw`, then mount /dev/loop0p1. > > > > Assuming I got it right I am still getting filesystem errors (or "can't find > in fstab), here is what I have tried: > > [user@untrusted MV]$ sudo losetup -P /dev/loop0 whonix.raw > [user@untrusted MV]$ mount /dev/loop0p1 > mount: can't find /dev/loop0p1 in /etc/fstab > [user@untrusted MV]$ sudo mount -t auto /dev/loop0p1 ~/whonix/ > mount: wrong fs type, bad option, bad superblock on /dev/loop0p1, >missing codepage or helper program, or other error > >In some cases useful info is found in syslog - try >dmesg | tail or so. > [user@untrusted MV]$ sudo mount /dev/loop0p1 ~/whonix/ > mount: wrong fs type, bad option, bad superblock on /dev/loop0p1, >missing codepage or helper program, or other error > >In some cases useful info is found in syslog - try >dmesg | tail or so. > [user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 ~/whonix/ > mount: can't find /home/user/whonix/ in /etc/fstab > [user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 whonix.raw ~/whonix/ > mount: /dev/loop1 is write-protected, mounting read-only > mount: wrong fs type, bad option, bad superblock on /dev/loop1, >missing codepage or helper program, or other error > >In some cases useful info is found in syslog - try >dmesg | tail or so. Have you followed this suggestion: dmesg | tail Maybe this filesystem is really broken? - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJX9/NuAAoJENuP0xzK19cs9S0H/j+lhoUjPFu7plLipSnHmZ1b U4nuO5DMEANLX8sKeC4zPQlatpyObqUSeseCcuKDeP/xcFymtYPbZIVaxuGHjvBa 1Aa6Z3A2A3i9P7p8efMZWB3qHlDtapxUDURcwuYsakYyKjAy+16g+BD7rSyEX7zx tHV/zYO8BRq9arB3TNGbwDaz0+HMyQ0mjemyKlk3OCNm+VMAo5JQyeMPv6xP0o8E fibOlZd9YTH2UBYrgVFarsapJYOypb6UxjRQCZGuARbuWCV3NoURD2IbNp6QRcWZ VkYDgcCMsuChOhiiO91vGrZCe7A5kn83LirzZ9Fd0HOynyUde8SSSEuW597SQQA= =d3fr -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/20161007191143.GL7105%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Switch of DMA altogether..?
Am 07.10.2016 um 20:40 schrieb neilhard...@gmail.com: > On Friday, 7 October 2016 19:37:50 UTC+1, Achim Patzner wrote: >> I think I’ve still got a bunch of NE2000 and early RealTekNICs somewhere in >> the cellar – how much do you want to offer? > > Are you saying that these devices are non-DMA…? Let me wiki that for you. There you go: https://en.wikipedia.org/wiki/NE2000 By the way, your “.” key seems to be broken. Achim -- 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/DADFC01C-FDE8-4A05-9FBE-210AEC121A6F%40noses.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Installing Windows 7 freeze Qubes dom0
Everytime i try to install windows 7 my qubes gui (dom0) freeze while win7 installing. Also listen to music in another vm is impossible. I have a fast i5 cpu and 24gb ram. Windows HVM with 8 GB ram and 4vcores. I installed qubes 3.2 on ssd. So how i can prevent that? Is it qubes creates the "hdd" file for win7 ? It seems the installation freez all other also the mouse for 5-10seconds this every 1-2 Minutes. -- 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/nt8r9h%24j2h%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Switch of DMA altogether..?
On Friday, 7 October 2016 19:37:50 UTC+1, Achim Patzner wrote: > I think I’ve still got a bunch of NE2000 and early RealTekNICs somewhere in > the cellar – how much do you want to offer? Are you saying that these devices are non-DMA...? -- 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/e30f1d83-efa0-468d-a1a0-6032f70d7f0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Switch of DMA altogether..?
Am 07.10.2016 um 16:57 schrieb neilhard...@gmail.com: > > Presumably through the CPU. I think I’ve still got a bunch of NE2000 and early RealTekNICs somewhere in the cellar – how much do you want to offer? > So I see no reason you couldn’t get Ethernet + WiFi chips without DMA. I do; those doing IO with CPU IO transfers have died out in the beginning of the 100 MBit age. > But certainly, I think there are devices out there without DMA. I think you > just need to search the market for a Ethernet/WiFi that supports non-DMA. Please post the result of your research – if possible including the sustainable bandwidth with these devices. Achim -- 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/ACA86453-9322-4C46-AABE-64AA72421A89%40noses.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Switch of DMA altogether..?
So are you saying that VT-D does not actually depend on Xen...? With a Xen bug, couldn't a hacked WiFi device just break out of sys-net..? Or not..? -- 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/0e9712cf-5c52-41d4-92bd-7a5853add4c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] mounting a qemu-img'd file error?
On Thursday, October 6, 2016 at 11:11:47 PM UTC-4, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, Oct 03, 2016 at 06:51:39PM -0700, gaikokujinkyofu...@gmail.com wrote: > > I converted a vdi file over to a raw file which seemed to go fine but > > mounting it is not going so well. mount seems to be having problems with > > the file sys. I have tried auto but no luck, I tried manually specifying > > but no luck. It was whonix so I assumed it was ext3 or 4 (or 2, tried em > > all) but no luck. > > I have tried specifying offset points (2480 here) and just "loop" etc... > > nada > > > > fdisk -l tells me: > > Disk whonix.raw: 4 GiB, 4294967296 bytes, 8388608 sectors > > Units: sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 512 bytes > > I/O size (minimum/optimal): 512 bytes / 512 bytes > > Disklabel type: dos > > Disk identifier: 0x3d6b07dc > > > > Device Boot Start End Sectors Size Id Type > > whonix.raw1 2048 8388607 8386560 4G 83 Linux > > > > thoughts? > > Try `losetup -P /dev/loop0 whonix.raw`, then mount /dev/loop0p1. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJX9xJiAAoJENuP0xzK19csoNMH/jUcyBOwKFmyHsYVaEt/3TrX > HU48pwq0WOTrwNwvtFl0WQW0PTH44vMrwoBlhYRsqlZ+S6PqBJXPukdnlyx2T6V4 > imZU1DgymFCBMNvkdlq1tFDEU8nt0JjkS7USL3Vfc0pyS+WXwSobHIJaS7mIbWzL > XYr0mECzsVhVE1WH4QXcZO9J3v68tRPKmFKTj7jpThsFDgvRx5868Bj7URw1CqUZ > uhAEmTd33ka3mgvHi3+ityC10AQ8/DhMt+MgSpfwH231L2apuPXkVAQ3TegafboW > 0YmRxP3n0r6HalYmH0Gdr160avkkM7qXmHgJO5IaaIGheAcnLC+PUC4xkRkHM0U= > =ANsq > -END PGP SIGNATURE- Assuming I got it right I am still getting filesystem errors (or "can't find in fstab), here is what I have tried: [user@untrusted MV]$ sudo losetup -P /dev/loop0 whonix.raw [user@untrusted MV]$ mount /dev/loop0p1 mount: can't find /dev/loop0p1 in /etc/fstab [user@untrusted MV]$ sudo mount -t auto /dev/loop0p1 ~/whonix/ mount: wrong fs type, bad option, bad superblock on /dev/loop0p1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. [user@untrusted MV]$ sudo mount /dev/loop0p1 ~/whonix/ mount: wrong fs type, bad option, bad superblock on /dev/loop0p1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. [user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 ~/whonix/ mount: can't find /home/user/whonix/ in /etc/fstab [user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 whonix.raw ~/whonix/ mount: /dev/loop1 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. -- 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/a6b1ed94-aef3-47d5-b7dd-1909215b9ad5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Switch of DMA altogether..?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 07, 2016 at 07:57:35AM -0700, neilhard...@gmail.com wrote: > Presumably through the CPU. > > We know this option exists for hard drives for a facts. > > So I see no reason you couldn't get Ethernet + WiFi chips without DMA. > > Not all devices support switching off DMA, so I can see why Qubes decided to > use VT-D + Xen instead. > > But certainly, I think there are devices out there without DMA. I think you > just need to search the market for a Ethernet/WiFi that supports non-DMA. I don't think any modern network adapter support non-DMA mode, with decent performance (if at all). Using CPU for just transferring the data is horrible waste of resources (few hundreds of instructions for 1KB). Regarding Xen and VT-d - Xen responsibility is only to setup allowed memory areas for given device. Actual enforcement is done by the hardware. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJX9+agAAoJENuP0xzK19cspTcH/2vRRR+gkaBXw0yf04BXSkA/ ooAGvCEV/If/gVXs0LiLyGLoBw/SC6HSEFu9WUEiXUnTrmY41M/H4WCDx5oXAOwP /cO0Wa0anq9QG5AkxEaJvySI043wQiBi0ZIBLxSMNGRbqi+jxr09Fvf/E31sBClh t0duS2RCJK4v1AiWh6SrGYUrWh4ijGxMwlHjyUPT/931aCLb9YRp8Hszg19lQ95i JituYaAVmQNZ+Rh8VMOKhgdViLLIYAHuswTQt/wKfsjxx79nPbOGRfyEVgYofJ7I mv6doHzzWfds5hnR1WkPxiLI67yk0AJ7QD6zpvvuGYPEpWIVvSHOjGW4JauIP7M= =NTct -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/20161007181706.GI15776%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot start qubes-guid!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-07 04:12, illix...@hushmail.com wrote: > Hello > I was updating my whonix-ws but maybe it was reboot and I closed it. > Now I can't start more it and shows up this message > > "Error starting vm: cannot start qubes-guid!" > > Reading some post I run this command > > qvm-run whonix-ws --nogui --pass-io -u root "journalctl -xb | grep -i > -E "error|fail|qubes-gui" > > The result is: > > .host kernel: Could not initialize VPMU for cpu 0, error -95 > .host kernel: dmi: Firmware registration failed. > .host systemd[1]: Failed to insert module 'kdbus" : Function not > implemented > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> > /var/run/brltty/usbfs: No such device > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl > /sys/fs/fuse/connections' failed with exit code 32 > .host kernel: Error: Driver 'pcspkr' is already registered > aborting.. > > Any help is appreciated > Have you tried restarting the host? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJX9+EkAAoJENtN07w5UDAwp/kP/Aj8FrTBE0JYaUBlG1ZbrUHK 0brEawqgxv/LWSbkruKM1eSPYJ6LD3Ii5mbu19mS15w7VlZKVQRCHaNQgc9gnUBs MQCP7zH/2tYD0FsGd4J+zyTYe7R+AAiKW4FCx+/QkUYQL6H5zCCAz/ZoIbLtHv/y 1EF8MbAL80GtDboL/qxYnv2qzefZ//zuQcIm0LpjBSQPxXUduJYczjusVQT2fz5X Ei0o4XnGhvZ9GWIBv/gNccChiu6Ocsx/Ur8GvZSfGLUMJl5NYVQNmc5jKxcf8KYw +3JFN1EUqN6guambVTQ4q2vulU2EqrmS0Z0Si8UBGTbXTOYXub1MK8yvRV1xBP0O wLN75ZH23dqYK4g4CBJ4+oJ7gbNQFuly1Rog7k1Xbir2eCG2+pfgxWreBaxjwi9C QtredkE/gN4TWVl3uB1XT4hrBQ4Woo+4WFMJzfJlOBoE7Y5gsAbWApkf+dLs5Gyh ez/As/kKWvSdtozaD0gZi2hX0ImCRxg3pQBaUGgwstrywcOv4enBTpiLRwTy/YD9 hwVhY6HMCfgvSAfyHh4PHINVDIt2BgiWKwqh7PHIxsFSGJWqoirZ4gn8d5yzG2iC CNUVTzbwJK7H+3l+dSwL7u7IZvlyzDfrBdE/ozzEnc4Gly3viLv1udIHhnhPE39h ciBg9gu43Nmj8NI/N7ND =fBkn -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/7b67fcb1-4f48-6c64-eab6-cbc2aaf5565b%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali screen problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-07 10:50, Andrew David Wong wrote: > On 2016-10-07 00:37, petor...@gmail.com wrote: >> I was wondering if anyone else is experiencing problems with installing Kali >> on a HVM in Qubes. When I boot the fresh installed Kali HVM i see the logon >> screen fine, but after that I see the top op the screen in the lower 10% of >> the window > > > Did you follow the instructions here? > > https://www.qubes-os.org/doc/pentesting/kali/ > > Some other users have also reported problems with installing Kali HVMs, but I > don't recall your specific issue being reported yet. Added: > > https://github.com/QubesOS/qubes-issues/issues/1981#issuecomment-252317236 > > Oh, I see now that you also found the other thread by NewbieG. So, it looks like it may be the same issue. For anyone else, this is the thread: https://groups.google.com/d/topic/qubes-users/u7COjQTy1_I/discussion Already added to qubes-issue #1981: https://github.com/QubesOS/qubes-issues/issues/1981#issuecomment-236744342 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJX9+D+AAoJENtN07w5UDAwcYQP/3ymgaM+Tde6VtlZ8NdjuXv5 dDJZsexClndxz4G21WhLRJh8tupjTzjgVSwJi42ZucJJupzrUfmdN9QCoYtmQmYX LhUSnTNBOuo2Whp3fsNB2Sc62Gz0duBaoLfCGThiuZuEF5oyUjhDKvHKeIZ6MlXs Az3diGcqfiPPz3aIkgIZndO8IgKCHx0OnV+OVmnaakLlYv1/LF8ulLrX1/JqZlrB tPE9JYcswa9rUW8lwjmOJbmrOyvP8R2zCSjluTCPx23SfSpqlYePm/C5i4N3J8rJ 8BkA12AU0OuXv/7maPr+ieDnKcVrAcSJpfXcTuZMSv382b7c6AI4lBLa6zJKsBK+ gEr5oJ/NI85Qtuz2QfiDFKRPgy7/oAOc+xQCuPH2EaVzLOwpxX0Lm9si5e0syPVv SLxLTqBjjHFLfTfi5l4MkwpRwGr/nuWRlv7yF2ulEu0MpafM87PCJUY52KzHEb5V ID1v3KuOJVtpV5Q21OlHQTgoPeXNgxvmK703U+zRQplx2t4sPOAX6YY4eUQAsEEu f5DH6tqaADPsQp7WL85HuSaC6rchY0XBZvycxKBG36pNfkaTidmmc/7hRdZ2m8im U8EfmkhyOGvF3BtlEpiz91/foSztJ/ngERgiEyEyWOkZpm6L+q1O1eHiFYkXML34 0upiQU2WBD4S4J83Ipsl =pcMs -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/71339801-3fbf-f9cd-4232-22ec516bad40%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kali screen problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-07 00:37, petor...@gmail.com wrote: > I was wondering if anyone else is experiencing problems with installing Kali > on a HVM in Qubes. When I boot the fresh installed Kali HVM i see the logon > screen fine, but after that I see the top op the screen in the lower 10% of > the window > Did you follow the instructions here? https://www.qubes-os.org/doc/pentesting/kali/ Some other users have also reported problems with installing Kali HVMs, but I don't recall your specific issue being reported yet. Added: https://github.com/QubesOS/qubes-issues/issues/1981#issuecomment-252317236 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJX9+BWAAoJENtN07w5UDAwDFQP/0ikwP2L1UUI8a214Ry9RwFW WQ7lsWxELbw6eLbosx8FGLRqdhae/zeHcv/VYsztCvxwRJ9/DUizn7apE5jk5tKU 1zsDgBaE3T4nhli1sBU7EvSA5KDzBGeI7H/RiONusyOLz9gC/vRE1XxjPlOXLqCX O3EdZfjmqHMlQYHTJYS6BPcxHB+YJtt9AeopPsJff5acqkHkuMIep5r7y/IX7jad 445xZMX3yWVyRsTy+QS4RFj8pWJzrC8PdxQXR05+siIVyDfW2ca+s1lCEdeEBetg Z/CwzXJUzcFmEkTH2HuIMWZJMuLvdWLq+OyJnbSmxGM9N9DAV85ZhP76c5tWQzBz GRYQ+KVp9t2iY+ZRJQSp0sS46ETd5sJ+g1XQ9vImiKVvgwMMn5T0FKRtLtQjkO5V S+KJGtC+7DS7oyC+vni1ZGjK6iOdaI0gjoSZr8ARInsigqL6waL9n3Cx4k4IV4pQ Ox8cymBV4EONknZ9cJQUFErnmPOVbBkvZXvEbUOEkQJTQKmDF0tZasnkEcrqHfhh ePyGBEZBYmQNtEn2M/nH4QHx/0IgSDnswyoy7YOz1y2Vtjf9T7Er4Pthvdkwh3h1 WlLhYmlgQ6yOZr6py317a8EfanxyH6jkTAQ60rT2jr5ChWgEv9XSGNMO8fT8M7xU JSv5lPqZvlN4nDaGBKAn =FRMX -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/dd3e1478-9f03-7ef8-61a5-42edb4d16464%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How do i get installed software to persist?
On Fri, Oct 7, 2016 at 12:45 PM, wrote: > Using 'sudo aptitude update' > 'sudo aptitude install libreoffice' > > in whonix-ws template terminal, libreoffice does not show up in whonix-ws > vm's when started afterwards. Installing libreoffice directly into vm's > works but does not persist between reboots. Is this qubes normal behavior? > How do i install libreoffice so that it persists? > > Have you shut down your template before starting the dependent applVMs? Best Fran > -- > 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/4010c38dc1452b2eeadd4e74448b56bb.webmail%40localhost. > 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/CAPzH-qAEtcJVCBpbT%3DxcPz0dt2fwosV0jQU2DKJTSpbQ2CM5%2Bg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How do i get installed software to persist?
Using 'sudo aptitude update' 'sudo aptitude install libreoffice' in whonix-ws template terminal, libreoffice does not show up in whonix-ws vm's when started afterwards. Installing libreoffice directly into vm's works but does not persist between reboots. Is this qubes normal behavior? How do i install libreoffice so that it persists? -- 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/4010c38dc1452b2eeadd4e74448b56bb.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Switch of DMA altogether..?
Presumably through the CPU. We know this option exists for hard drives for a facts. So I see no reason you couldn't get Ethernet + WiFi chips without DMA. Not all devices support switching off DMA, so I can see why Qubes decided to use VT-D + Xen instead. But certainly, I think there are devices out there without DMA. I think you just need to search the market for a Ethernet/WiFi that supports non-DMA. -- 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/1dfba313-0f8f-4ddd-83fe-1e61c684ccd2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Switch of DMA altogether..?
W dniu piątek, 7 października 2016 13:14:41 UTC+2 użytkownik neilh...@gmail.com napisał: > Qubes uses VT-D and a Net VM to attempt to isolate buggy WiFi adapters from > the rest of the Qubes system. > > But this isolation still depends on Xen not having bugs... And we know that > Xen has bugs, and will likely continue to have more going forward. > > So, instead of VT-D, why not just switch off DMA altogether..? > > In Debian, you can edit "/etc/hdparms.conf", and do stuff like this: > > /dev/hdc { > dma = on > } > > Why not just do this for WiFi and Ethernet chips in Qubes, and thus, not have > to rely on Xen for isolation? How exactly are PCIe devices going to communicate with the rest of the system without DMA? -- 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/a0cd153b-2644-47ac-b62a-4cbc532c92de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Switch of DMA altogether..?
Qubes uses VT-D and a Net VM to attempt to isolate buggy WiFi adapters from the rest of the Qubes system. But this isolation still depends on Xen not having bugs... And we know that Xen has bugs, and will likely continue to have more going forward. So, instead of VT-D, why not just switch off DMA altogether..? In Debian, you can edit "/etc/hdparms.conf", and do stuff like this: /dev/hdc { dma = on } Why not just do this for WiFi and Ethernet chips in Qubes, and thus, not have to rely on Xen for isolation? -- 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/7da00a1d-df99-46fd-8f22-efb638d4f463%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot start qubes-guid!
Hello I was updating my whonix-ws but maybe it was reboot and I closed it. Now I can't start more it and shows up this message "Error starting vm: cannot start qubes-guid!" Reading some post I run this command qvm-run whonix-ws --nogui --pass-io -u root "journalctl -xb | grep -i -E "error|fail|qubes-gui" The result is: .host kernel: Could not initialize VPMU for cpu 0, error -95 .host kernel: dmi: Firmware registration failed. .host systemd[1]: Failed to insert module 'kdbus" : Function not implemented .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host brltty[204]: file system mount error: usbfs[brltty-usbfs] -> /var/run/brltty/usbfs: No such device .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32 .host systemd-udevd[317]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32 .host kernel: Error: Driver 'pcspkr' is already registered aborting.. Any help is appreciated -- 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/20161007111253.2011DE06AE%40smtp.hushmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Unable to get right X display for kali on HVM
Had the same issue on my Dell. Both the xfce and lxde editions work fine though. -- 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/yW-j3jHlWQ3L_RTfuMEy2xEEIavDrHHrp55jgl4u5FqpRFECwo2OARRvLdasCZgxvsnVj0a-qEcVBJuI-Go1LfLP6tyd5chXFp5m9cdQb0w%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Major problems with 3.2, devs must address
Am 07.10.2016 um 06:44 schrieb boromirsbe...@sigaint.org: > Ok my concern mostly is because its my windows disk and i dont trust it, If you're not using a dedicated machine for Qubes instead of booting multiple operating systems with definitely lower security standards anyway I don't see your problems at all as this is only a minor problem in that kind of environment. The same applies to Tails – it's generally a good idea to stop trusting a machine that has been running something like Windows if your security requirements prompt you to consider attacks coming from the firmware of a possibly compromised SATA device. > > This is not specific to my printer, i used it fine in Tails, the OS > asked > > me in tails for a login/pass to install a printer, this is not printer > > specific, i dont even have to have a printer connected in qubes for this > > to happen. Part two of the answer before: This is probably a CUPS-related problem; as soon as you're dealing with the CUPS server itself (instead of the tools that modify the CUPS configuration files) you'll be running into this. Either keep your fingers off the web interface, editing the configuration files with an editor or (ironically using the same editor) modify the authentication requirements of the configuration files appropriately for the web interface to permit you to use it (keep in mind that "user" does not have a password so you'll have to do quite some cleaning). > In tails i would set an admin password prior to logging in and then > use that to add printers, in qubes it asks for this but does not > accept my user account login info. because the account on the virtual machine is not the login account of dom0 Always keep in: Qubes is not Tails. Not by far. Achim -- 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/0a13d5f0-bbf0-a96b-b757-16841376c5ef%40noses.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unable to get right X display for kali on HVM
I have the same issue on a Lenovo T440s -- 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/985b7d49-2b18-42b1-ae87-94533da34a28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Kali screen problems
I was wondering if anyone else is experiencing problems with installing Kali on a HVM in Qubes. When I boot the fresh installed Kali HVM i see the logon screen fine, but after that I see the top op the screen in the lower 10% of the 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/2cfc8134-6621-4297-823a-9e996cf16ba8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.