[qubes-users] LPT port passthrough supported?
Hello qubes-users list, after running Qubes OS on a notebook for some time by now, using it on a desktop PC has been on my list for quite a while. At this point, I would like to thank you for developing and maintaining this operating system, which is the most secure one I ever seen (including proprietary ones ;-) ). Thank you very much! However, there is a rather old LPT printer (HP LaserJet 6L) connected to the machine, which is still working very well. On the other hand, passthrough of this device does not seem to be possible as it does not show up as a distinct device, e.g. like USB peripherals would do. Is LPT passthtough supported by Qubes OS? If so, how do I do this? As far as I am concerned, there is no documentation on this - correct me if that is wrong. Best regards, Charles Allen -- 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/2f75f44a-2bef-b0e0-f6dc-cc2d859e5835%40skyline.link38.eu.
Re: [qubes-users] Recovering data from unbootable Qubes install
‐‐‐ Original Message ‐‐‐ On Saturday, November 9, 2019 4:54 PM, Claudia wrote: > 'Zeko' via qubes-users: > > > Hello > > I managed to screw up my Qubes install and it fails at boot, resetting > > every time. However, that happens after the partition gets mounted and I > > screwed it up without having my /boot partition (a USB pendrive, since I > > multiboot) mounted, so I expect I'll be able to mount the Qubes encrypted > > partition somehow based on the data on the boot pendrive and the disk > > password. > > I've tried simply unlocking the partition with a Linux recovery live CD by > > inputting the disk password as the LUKS passphrase but I get the reply: "No > > key available with this passphrase." > > What do I need to do on the /boot filesystem to get to the LUKS passphrase? > > I need these files :( > > Sent with ProtonMail Secure Email. > > Interesting. As a matter of fact I had to do this yesterday to reset my > user password. All I had to do was boot the Qubes installation CD, > switch to a shell, and unlock the dm-crypt container. It should be that > simple. I didn't have to mount /boot or anything like that. You should > be able to do it from any recovery CD, but have you tried doing it from > the Qubes installation media? Are you sure you're using the same > keyboard layout? Are you sure you're typing the passphrase correctly > (try `echo "mypassphrase" | cryptsetup open --key-file - /dev/sdX1 root`)? > Have you tried `cryptsetup --verbose`? Did you use any custom > cryptsetup options when you created the container? > > -- > > This free account was provided by VFEmail.net - report spam to > ab...@vfemail.net > > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/dbf3915a-6c92-d572-daa2-d370685b4ea2%40vfemail.net. Thanks Claudia, it was only the keyboard layout. Should've thought of that myself *facepalm* Do you know if there's a documented way to turn the /dev/dm-* volumes into something the Qubes backup/restore utility understands? I have over 100 VMs and I'd prefer not to open each one up and copy the contents manually Sent with ProtonMail 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2wmKkH9281_vJ05BXbwSJUoJT_wUXt5P2BlwZZCR-a0EhxNoVkK8qvEMcmJOtrriOubUeyPD8-Jha5WrnkqY4_RqVrRNXSnOhPLkV1CBGac%3D%40protonmail.com.
[qubes-users] Re: How to use curl in a template VM?
Thanks for the reply. I went the proxy route below, since it was simpler, but I appreciate the help. billo -- 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/586186bd-6312-4ed7-89a0-df1ef012729a%40googlegroups.com.
Re: [qubes-users] Re: How to use curl in a template VM?
The proxy worked fine. It's all good. Thanks! billo -- 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/02fbc4b4-b2e6-4573-92b9-dbf3d212c3d6%40googlegroups.com.
[qubes-users] Qubes in a networked multi-user environment
Is there anybody around here, who is running a single Qubes box in a muli-user scenario? My idea would be to add a separate network interface to the Qubes dom0, connected exclusively to a handful of remote desktop clients to allow to control the Qubes VMs remotely. This network would be obviously separated from everything else, especially from the Internet. There are no services or local applications running on those remote desktop clients, they are assumed to have wired periphery only and no accessible external ports. I am not overly concerned about a compromised remote access network or a remote desktop client. If that happens, the bad guys are in my house an the weapons of choice are probably of a more physical nature ;-) . Aside from that objection, is there another reason, why my intended scenario might be a bad idea? I hope I am not bringing up an FAQ, but my attempts to google that scenario failed so far. Regards, Charles -- 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/c5fdc8c7-d06e-496c-a38e-d1277498f38b%40googlegroups.com.
[qubes-users] Re: HCL - 20L8S2BS00
Ah also I did not attempt to test AEM but machine has TPM2.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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/56d76cc8-9891-4352-b398-da40d9aaa7fa%40googlegroups.com.
[qubes-users] HCL - 20L8S2BS00
Before Installation I used this guide to set up the bios settings (credit to D4hrm4) https://github.com/dh4rm4/A-Reasonably-Secure-Thinkpad/tree/master/src/bios_settings Had ACPI exception errors during install, and the installer gui froze many times but it installed just fine in the end. https://www.qubes-os.org/doc/installation-guide/ Updated debian and whonix right after installation according to the 4.0.1 warning above in the link During boot I had "failed to start load kernel modules" error, solved by simply updating dom0 with the gui updater. Suspend was not working while sys-usb was running. This has also been solved after updating dom0. Everything works flawlessly, youtube video with sound, all usb devices recognised. -- 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/CABWumELjrjoz5uzTYth8PmJbX-TcRchah3B8J3tYouZ%3DcU2jpw%40mail.gmail.com. Qubes-HCL-LENOVO-20L8S2BS00-2019-150311.yml Description: Binary data
Re: [qubes-users] Recovering data from unbootable Qubes install
'Zeko' via qubes-users: Hello I managed to screw up my Qubes install and it fails at boot, resetting every time. However, that happens after the partition gets mounted and I screwed it up without having my /boot partition (a USB pendrive, since I multiboot) mounted, so I expect I'll be able to mount the Qubes encrypted partition somehow based on the data on the boot pendrive and the disk password. I've tried simply unlocking the partition with a Linux recovery live CD by inputting the disk password as the LUKS passphrase but I get the reply: "No key available with this passphrase." What do I need to do on the /boot filesystem to get to the LUKS passphrase? I need these files :( Sent with [ProtonMail](https://protonmail.com) Secure Email. Interesting. As a matter of fact I had to do this yesterday to reset my user password. All I had to do was boot the Qubes installation CD, switch to a shell, and unlock the dm-crypt container. It should be that simple. I didn't have to mount /boot or anything like that. You should be able to do it from any recovery CD, but have you tried doing it from the Qubes installation media? Are you sure you're using the same keyboard layout? Are you sure you're typing the passphrase correctly (try `echo "mypassphrase" | cryptsetup open --key-file - /dev/sdX1 root`)? Have you tried `cryptsetup --verbose`? Did you use any custom cryptsetup options when you created the container? - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dbf3915a-6c92-d572-daa2-d370685b4ea2%40vfemail.net.
[qubes-users] Re: 4.0.2-rc2 ISO hangs before graphical installer starts [solved]
Claudia: Claudia: The last message on the console is always "[OK] Started Monitoring of LVM2 mirrors, snapshots, etc. using dmeventd or progress polling" at which point it just hangs. The cursor doesn't blink, and pressing enter doesn't do anything. Some keys cause it to beep, though, and it does respond to ctrl-alt-delete by rebooting after a few seconds, but the screen remains completely frozen during that time. So it feels like it's running normally except the screen is frozen. 4.0.1 installer worked fine on the same machine. Any ideas on how to debug something like this? Okay, so oddly enough I was able to get past this by pressing ctrl-alt-f1 repeatedly during dom0 init (systemd), **before** it freezes. At that point I could see the anaconda shell, followed by the graphical installer. The installation went fine, but now I'm experiencing the same problem when booting the installed OS. It hangs at "Starting Show Plymouth Boot Screen... Starting dracut initqueue hook...", just before it should prompt for the disk password. I was able to get to the console-based (not graphical) disk password prompt a few times by pressing random keys, but I can't make it work reliably (or I don't know what I did exactly). Once again, it responds to ctrl-alt-delete but the screen is frozen. In both cases (installer and installed), it seems to freeze within a few lines of "Starting Show Plymouth Boot Screen". So I have a feeling it's being caused when Plymouth tries to switch into graphical mode. Any ideas would be helpful. Is there any way to make it boot in text mode up until lightdm? Note, I'm using AMD Vega graphics, there is no dGPU, and neither of these problems were present on 4.0.1, even under kernel 4.19. Okay, so I was able to disable plymouth by removing "rhgb quiet" from the kernel command line. Now, the last thing on the console before it freezes is "fb: switching to amdgpudrmfb from EFI VGA". I looked it up, and this message has something to do with amdgpu. Adding "nomodeset" to the kernel command line fixed it. It gives me the text-based disk passphrase prompt, and eventually lightdm starts. It seems to run fine after that, but I don't know if running with nomodeset is really a good solution or not. I still consider it a bug, because 1) amdgpu should work properly and not have to be disabled, and it worked in previous releases, and 2) AMD users should not have to debug the boot process and modify kernel parameters right out of the box. Thoughts? - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9bf2a74f-d810-1eda-e2ef-3ba0424ccc87%40vfemail.net.
[qubes-users] Qubes 4.0.2-rc2 Updating tor-browser Whonix-ws-15-dvm
Hi, I am trying to update the torbrowser in the Whonix-ws-15-dvm, but cant seem to get it updated. Thought the torbrowser in the disposablevm could be updated by running the "Tor browser Downloader" in the "Template : Whonix-ws-15" .. The torbrowser in the template is updated correctly, only its not passed to the DVM.. What am i doing wrong ..? Thanks in advance .. -- 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/4e9dc55a-7ff5-4954-9298-6af3b0cec7b5%40googlegroups.com.
