Re: [qubes-users] pen testing / port forwarding guide?
On 2020-07-14 17:54, 'J.M. Porup' via qubes-users wrote: > Has anyone written a guide to setting up a Kali vm in Qubes for > pen testing? I created a template based on the Debian template as described here: https://www.qubes-os.org/doc/pentesting/kali/#kali-linux-templatevm-from-a-debian-template---1 > The alternatives seem to be 1) create a HVM with direct access > to hardware--no sys-net or firewall-vm--or 2) purchase a > dedicated laptop for this use case. > > Any suggestions? Try a USB network adapter and attach it to your pentesting VM. Unfortunately, not all devices work, check https://github.com/QubesOS/qubes-issues/issues/3778 for a list of tested adapters. If nothing helps: Shut down your network VM and attach your network device directly to your Kali VM. For switching to and fro, you can create a script in dom0. Stefan. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f37ae429-6f44-cd44-62fa-d28b27fca19c%40ploing.de.
Re: [qubes-users] How does dropbox know that I‘m using qubes?
On 6/18/19 12:39 PM, cycle via qubes-users wrote: > recently I logged in into dropbox with a browser from my qubes box and > had to confirm my login. Afterwards I got a mail saying that there was > an login attempt from: > > *Desktop-Client Linux 4.14.116-1.pvops.qubes.x86_64 > > *How can I avoid that this information is send to servers? Is it part of > the http header? My guess: You have the Dropbox sync client installed. "4.14.116-1.pvops.qubes.x86_64" is part of the kernel id - you can see it for yourself using "uname -a". Stefan. -- 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/c56ebc8c-1e7e-61f2-f03b-516a7394ebbe%40ploing.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Some VMs on an external disk (unavailable at boot)
On 2/4/19 5:59 PM, Stuart Perkins wrote: > I do not know the official stance or method, but I symbolically link from the > standard appVM location to my other drive where I have the larger appVM's. > Mine is always available so I don't know if Qubes would boot if it weren't, > but it is a thought...obviously the drive would need to be available to start > the appVM's located thereon. This is what I did on Qubes 3.2. On Qubes 4.0, I used the new thin pool provisioning, so the symlink trick doesn't work anymore... Stefan. -- 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/b38db73c-1ab3-25a5-042b-5f4b3441ee7f%40ploing.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Some VMs on an external disk (unavailable at boot)
Hi, I'd like to have some VMs on a secondary disk. I successfully followed the guidelines from https://www.qubes-os.org/doc/secondary-storage/ Troubles arise when the disk is not available at boot time. I'm working on some mount/unmount scripts which adds/removes the storage pools. But it seems that this is not enough: Upon reboot (with the pool from the secondary disk removed), the qubesd terminates with an exception, causing the whole Qubes installation not to boot properly. First, I added some try-catch in qubes/app.py (line 905) so the qubesd starts even if some VMs cause errors. Perhaps this would be a general nice behaviour? After re-adding the pool, all VMs from the secondary disk pointed to the primary pool. Manually editing the /var/lib/qubes/qubes.xml fixed the issue, so I now have a working system again. My question: Is there a procedure to properly handle such a second disk (unavailable at boot time)? Stefan. -- 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/54e37a4d-7a38-12f7-7333-83e24506a258%40ploing.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: HCL - Dell XPS 15 9560
On 08/02/2017 02:16 PM, Eric wrote: > Have you been able to get AEM working? Haven't tried. > And, how is your battery life? Never used a stopwatch ;-) A little less than 4 hrs, I guess. > It sounds like the Killer AC chip is working ok, since it's just a rebranded > Atheros chipset, other than the standby issue - can you confirm? WLAN ist working fine, and since the last kernel updates the problems seem to have gone almost completely away. I'm fully rebooting the laptop perhaps every 2 weeks, and most of the time due to a kernel update (or running out of battery). Stefan. -- 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/b955a946-be17-87c3-f4f4-607a4849a157%40ploing.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: HCL - Dell XPS 15 9560
On 02/20/2017 06:18 PM, Alchemist wrote: > Were you able to disable the Nvidia in BIOS? I didn't try to. Is there a BIOS option? If so, I missed it. Stefan. -- 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/b9d33c6e-f3a7-a2b9-417a-f7bae340d1e2%40ploing.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HCL - Dell XPS 15 9560
On 02/20/2017 12:35 PM, Mike Keehan wrote: > I too have a new XPS-15 9560, but I can't install Qubes. The laptop > boots the installer into terminal mode - the graphics installer does > not come up at all. > > Did you have to do anything special to get the graphical installer > running? Hmm, obviously I've been lucky - I just put the Qubes 3.2 ISO on a USB stick, booted it, and everything worked fine. I remember making one modification in the BIOS settings: I set the HD mode to AHCI (default was set to RAID), I thought something more standard-esqe might be of advantage ;-) Stefan. -- 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/ce165624-d598-9ed8-a714-b20ab0681ed5%40ploing.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Dell XPS 15 9560
Hi, installed Qubes 3.2 on my new laptop. After some initial problems, it seems to be working great! After installing from the ISO image, the graphics driver was working fine (at least I remember it this way), only suspend to RAM crashed the machine. I updated all packages (fedora template and dom0), and after a reboot, X used the framebuffer driver and did not detect the Intel graphics chip :-( Both problems were solved by enabling the qubes-dom0-unstable repo and updating the dom0 kernel to the version provided there. Intel VGA and Suspend to RAM are working fine now. The nvidia chip (GTX 1050) is not supported by the nouveau driver, and I didn't go through the pain (not to speak of the security concerns) of manually installing the latest proprietary driver from nVidia on dom0. Suspend to RAM seems to have some problem with the WLAN driver, though. After some suspend cycles, WLAN won't come up again. I put the driver ath10k_pci to the suspend-module-blacklist, I think this did the trick. Stefan. -- 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/17e3e668-78f7-b6eb-114b-44dc6711c8e6%40ploing.de. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-XPS_15_9560-20170220-090349.yml Description: application/yaml
