Re: [qubes-users] What happened to "paranoid mode"?
I wasn’t aware of these options. Thanks for pointing out. I will certainly try them out. I agree with all your points about backup being practical and usable. The password is the weak link here’ as everywhere’ just like private keys. Perhaps something like YubiKey plus KeePass can solve this problem. Or someone may have a better suggestion. I had once tried setting up YubiKey on Qubes, but there was some problem. I will get around to solve them as YubiKey is known to work with Qubes. I made the mistake of trying it out on MacOS Catalina, but all hell broke lose. I do use it on Windows, Google etc. Regards, Anil > On 04-Jan-2020, at 4:41 PM, dhorf-hfref.4a288...@hashmail.org wrote: > > On Sat, Jan 04, 2020 at 03:56:49PM +0530, Anil Eklavya wrote: >> A better way to backup and restore will make Qubes much more usable, >> preferably at some point using something like rsync, as they have >> already been considering. This is one crucial feature that makes it >> difficult for common users to use this OS as a default. > > idgi, why dont these people use whatever backup solution they prefer? > > i have been using "borgbackup" to make automated, hourly, incremental > backups of my qubes machines since qubes3, even did the move > from qubes3 to qubes4 by "reinstall, restore" or use "backup on machine > x, restore on machine y" to move appvms or even templates around. > > "restic" looks to have a very similar featureset and i heard good things > about it, might have used it if i had found it before borg. > > in comparison, "qubes-backup" is about as useful as considering "tar" > to be the actual default backup solution of a plain linux. > dont get me wrong, i am not uninstalling tar or qubes-backup, but > i cant remember the last time i was desperate enough to actualy > use either for a backup. > > three important points wrt backups in the real world: > - backups have to be automated + background, or they wont happen. > - backups have to be incremental, or they wont happen frequently. > - and unless you have a restore process you are familiar with and > use at least sometimes ... > ... you dont have a (real) backup you should rely on. > > -- 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/9FA0DE1A-7AD3-45C2-965D-CD3DD9758271%40gmail.com.
Re: [qubes-users] What happened to "paranoid mode"?
A better way to backup and restore will make Qubes much more usable, preferably at some point using something like rsync, as they have already been considering. This is one crucial feature that makes it difficult for common users to use this OS as a default. > On 04-Jan-2020, at 3:08 PM, 'awokd' via qubes-users > wrote: > > tetrahedra via qubes-users: >> From back in the 3.2 era: >> >> https://www.qubes-os.org/news/2017/04/26/qubes-compromise-recovery/ >> $ qvm-backup-restore --paranoid-mode >> >> On my 4.0 install this option does not appear. Is it no longer >> considered necessary? >> > Looks like it is coming back: > https://github.com/QubesOS/qubes-issues/issues/5310. > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > > -- > 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/8255dbcc-7e09-eb18-cce3-17aa54dcfa82%40danwin1210.me. -- 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/8AC436C7-D3C0-435C-9AF2-A9DB6D3441BA%40gmail.com.
Re: [qubes-users] Re: Recommended laptop?
Thanks for putting all this information in one place. I was earlier looking to buy Insurgio Privacy Beast, but it was not clear whether it could be shipped to India. I then ordered Librem 13. Is there any comparison available between these two, based on privacy and security considerations? Regards, Anil Kumar Singh > On 01-Jan-2020, at 2:15 AM, Thierry Laurion wrote: > > > >> On Wed, Dec 25, 2019 at 6:03 PM wrote: >> Insurgo is providing a service. >> >> If one can do the steps themselves, that’s fine. >> >> If I were advising a somewhat less technical journalist or a potentially >> targeted human-rights worker or politically targeted activist who just >> wanted to get stuff done and had the resources, I’d point them to Insurgo. >> >> Brendan >> >> -- >> 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/7a7741f2-6b80-40be-a5a0-0f56b658f9fc%40googlegroups.com. > > > Hello there, Thierry Laurion from Insurgo Open Technologies. > > Thanks Brendan. > > I feel the need to clarify things a bit once in a while. This reply is one of > those. This QubesOS community is large, and even if replies were done on > Reddit and other posts here in the past, the same questions arises with the > same scattered answers. Here is a combination of those answers. > Insurgo made grant applications so that actual best trustworthy unmaintained > hardware becomes mainstreamed under coreboot, and added under Heads (extend > Heads measured boot support of latest coreboot VBOOT+measured boot on > Sandy/Ivy bridge xx30 and xx20 platforms: t530, t430, x220. Thanks to > obtained NlNet grant for Accessible Security project). > Insurgo is attempting to gather developers, device manufacturers > (RaptorEngineering) and funders around Power9-Power10 hardware based X86 > alternative platform (PPC64le QubesOS platform support which has a bounty > offer already but needs commited developers). Let's remember that their > Blackbird/Talos II platforms recently got RYF certification. > The last x86 platform having met RYF criteria is the X200, thanks to the > Libreboot project, which removed Intel ME. > Since then, the x86 platforms have blobs we have to accept/deal with to make > it trustworthier: > Sandy Bridge/Ivy bridge : EC firmware, Intel ME BUP ROMP modules. Coreboot > doesnt rely on FSP blobs for initialization. ME is actually neutered (no > kernel nor syslibs as opposed to newer platforms, just BUP and ROMP) and > deactivated (AltMeDisable bit, not HAP bit). > More recent hardware requires ME with its kernel and syslibs binary blobs > present, while ME is asked to be deactivated through HAP bit, requires Intel > FSP and other binary blobs for hardware initialization. > Insurgo works to bridge the gap to broader QubesOS accessibility, so that > users in need of remote support can have secured remote administration from > trusted third parties (new revenue? AccessNow? Other third parties?) over > hidden tor onion service from additional GUI (NlNet grant for Accessible > Security project). > Insurgo tries its best to support Heads community through GitHub opened > issues while promoting collaboration. > Insurgo tries its best to mainstream CI build systems to produce reproducible > builds artifacts (this is broken for months and is still not resolved). > Insurgo tries to raise awareness of researchers and developers on the current > state of "Open Source Firmware" (currently requiring FSP, ME or > equivalent,not having completely neutered Intel ME while claiming it is > deactivated, while system libraries and kernel is still there but latent...) > This implies going to conferences, doing talks, confronting the status quo, > researching, developing so we have alternatives in the futurewhile also > doing the required clerical work. > Insurgo made QubesOS preinstallable for the first time on the PrivacyBeast > X230, thanks to its reownership wizard which takes care of GPG key > generation, internal ROM reflashing, TPM ownership and sealing of > measurements, signing boot configuration, while enforcing diceware > passphrases in the provisioning phase. The goal is to generalize it to other > platforms. Ideally through collaboration... > Insurgo made the PrivacyBeast X230 certified by QubesOS, with a lot of work > done on Heads that is unfortunately not upstreamed yet. Will go back at this, > while branch is available through Gitlab and GitHub. > Insurgo collaborates with other parties to make needed work to have fwupd > (firmware upgrades), available inside of QubesOS, including Heads firmware, > thanks to NlNet Privacy and Trust grant, once again. > Insurgo tries to push verified boot to measure also the LVM
Re: [qubes-users] Anyone tried Qubes on HP Paviliion x360 14cd
The mail got sent halfway mistakenly. I installed the rc2 version on HP Pavillion x360. It only got installed in legacy mode. Doesn’t boot in UEFI or with secure boot. Also I have moved network-manager to sys-net. I can attach the USB-ethernet adapter to sys-net, but I am not sure how to get ethernet working in sys-net after that. I tried the method given in documentation about PCI devices, but it says sys-usb doesn’t expose the device (which readlink says is for ethernet). Regards, Anil > On 19-Nov-2019, at 9:58 PM, Anil Eklavya wrote: > > I installed the rc2 version on HP Pavillion x360. It only got installed in > legacy mode. Doesn’t boot in UEFI or with secure boot. > > Also I have moved network-manager to sys-net. I can attach the USB-ethernet > adapter to sys-net, but > > 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4FB27F9D-B45F-4E23-A714-D72C61701708%40gmail.com.
Re: [qubes-users] Anyone tried Qubes on HP Paviliion x360 14cd
I installed the rc2 version on HP Pavillion x360. It only got installed in legacy mode. Doesn’t boot in UEFI or with secure boot. Also I have moved network-manager to sys-net. I can attach the USB-ethernet adapter to sys-net, but Regards, Anil > On 20-Oct-2019, at 4:06 AM, Anil Eklavya wrote: > > I tried again and it did get installed. I have just installed it and so far > it’s working fine. > > There was probably a mistake in the dd command. > > Right now I am using the stable version, as this model or anything similar > was not listed in the HCL list. I have separate sys-usb and sys-net. > > It would have been good if Coreboot or Heads Linux was available for this > model. > > Can you point me to directions to change the whole disk passphrase. I had > done it earlier, but I seem to have forgotten the exact way. Mainly, I am not > sure whether I have to use cryptsetup on the disk device or the boot > partition device. I have not played around with command line encryption much. > > Regards, > > Anil > >> On 17-Oct-2019, at 11:21 PM, awokd wrote: >> >> Anil Eklavya: >>> I am trying to install Qubes on HP Pavillion x360 14 inch (cd0056TX). I >>> have tried both in UEFI mode and legacy boot mode. It either doesn’t >>> recognise the bootable drive (says not bootable drive), or it stops at one >>> point during booting from the installation pen drive and just stops at one >>> point and doesn’t proceed further, no matter how long I wait. >>> >>> Has anyone tried on this model and can anyone any hint as to what could be >>> the problem. >>> >>> I tried both with MBR and GPT for the pen drive. I had searched for the >>> line at which stopping, but did not find any solution that works. >> >> Make sure to use dd mode to create the install pen drive. Try UEFI >> first, and refer to https://www.qubes-os.org/doc/uefi-troubleshooting/ >> if you still have trouble. If that doesn't help, update here! >> >> -- >> - don't top post >> Mailing list etiquette: >> - trim quoted reply to only relevant portions >> - when possible, copy and paste text instead of screenshots -- 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/C519E4ED-8DB1-434B-8F93-861E449803CE%40gmail.com.
Re: [qubes-users] Anyone tried Qubes on HP Paviliion x360 14cd
I tried again and it did get installed. I have just installed it and so far it’s working fine. There was probably a mistake in the dd command. Right now I am using the stable version, as this model or anything similar was not listed in the HCL list. I have separate sys-usb and sys-net. It would have been good if Coreboot or Heads Linux was available for this model. Can you point me to directions to change the whole disk passphrase. I had done it earlier, but I seem to have forgotten the exact way. Mainly, I am not sure whether I have to use cryptsetup on the disk device or the boot partition device. I have not played around with command line encryption much. Regards, Anil > On 17-Oct-2019, at 11:21 PM, awokd wrote: > > Anil Eklavya: >> I am trying to install Qubes on HP Pavillion x360 14 inch (cd0056TX). I have >> tried both in UEFI mode and legacy boot mode. It either doesn’t recognise >> the bootable drive (says not bootable drive), or it stops at one point >> during booting from the installation pen drive and just stops at one point >> and doesn’t proceed further, no matter how long I wait. >> >> Has anyone tried on this model and can anyone any hint as to what could be >> the problem. >> >> I tried both with MBR and GPT for the pen drive. I had searched for the line >> at which stopping, but did not find any solution that works. > > Make sure to use dd mode to create the install pen drive. Try UEFI > first, and refer to https://www.qubes-os.org/doc/uefi-troubleshooting/ > if you still have trouble. If that doesn't help, update here! > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots -- 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/6DE89F6B-2E96-4C88-86BE-C65B3F8DDFA2%40gmail.com.
[qubes-users] Anyone tried Qubes on HP Paviliion x360 14cd
I am trying to install Qubes on HP Pavillion x360 14 inch (cd0056TX). I have tried both in UEFI mode and legacy boot mode. It either doesn’t recognise the bootable drive (says not bootable drive), or it stops at one point during booting from the installation pen drive and just stops at one point and doesn’t proceed further, no matter how long I wait. Has anyone tried on this model and can anyone any hint as to what could be the problem. I tried both with MBR and GPT for the pen drive. I had searched for the line at which stopping, but did not find any solution that works. Regards, Anil -- 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/3CF456FC-7064-4215-9E6B-70885A814114%40gmail.com.
Re: [qubes-users] Re: Unsure about network device attachment to VMs
> Dropping Qubes mailing list since it's not a Qubes issue any more. > Recommend calling Dell again and telling them the above paragraph. > Sounds like a hardware problem with the laptop to me. Get them to > replace it. I understand it no longer seems to be directly a Qubes issue, but I am updating because it may indirectly be of interest to Qubes users and developers. I will be contacting Dell on Monday. They are unlikely to replace it, but if they think it’s a hardware issue, they may repair it. Right after my last post, during the last attempt, there was a notification from Quick Heal about a suspicious file. I tried today when I booted up the laptop again, it worked without any problem for several hours. I updated all the drivers and checked that the Windows updates were up to date. Everything went well. Finally when I started to proceed with changing login options, it froze again. And then it started freezing repeatedly. The part which may be relevant to the Qubes community is about the fact that today it started freezing when I restarted the NordVPN app, which I had to disable earlier, because the network just won’t work properly. Earlier also I think the problems started after I logged in to NordVPN. But again, it may be a problem specific to NordVPN. About two years ago, I had subscribed to IPVanish and I had to give up using it with a few weeks as it just won’t get connected to the Internet. Years earlier, when the Tor Project was relatively new and I tried to use it, it also just won’t connect to the Internet. However, later on it started working. Still, my problems on laptops might have something to do with the use of Tor or VPNs. In the university where I work, the users who use a VPN have their internet access disabled. Since Qubes and Tor are about privacy and that is what I have been arguing for for years openly, even in official settings, I think the problems might have something to do with trying to maintain privacy online. Besides laptop, there are other reasons why I think this may be one of the causes. I mention it here so that Qubes users and developers may be aware of this possibility, in case they are not (I think many already are). -- 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/3C705D48-2CAB-43DD-ABD0-A3FD3B06E2B7%40gmail.com.
Re: [qubes-users] Re: Unsure about network device attachment to VMs
> So, I am not sure whether it is a problem related to Qubes, or the graphics > card or with BIOS. My hunch is still that it is with BIOS, unless the > hardware itself is compromised. At this point (that is since I reinstalled Windows 10), I have don’t have any Qubes on my system, but the laptop is still freezing. -- 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/A96651C8-4F47-4F89-AB52-1A3650B49A13%40gmail.com.
Re: [qubes-users] Re: Unsure about network device attachment to VMs
>> Your system intermittently freezing sounds like it could be >> https://github.com/QubesOS/qubes-issues/issues/5272 too. > > It does seem like it, but one difference is that this time I haven’t even > updated dom0 yet. I have not connected to internet at all, as I was first > trying to connect through ethernet. Since at that time USB-C seemed to be the problem, I decided it was not possible to use Qubes with Dell XPS 9370. So I reintalled Windows 10. Before that I updated the latest BIOS driver from pen drive. Everything went well till the installation was finished and Windows activated and some other applications installed. I was trying to update drivers and Windows, when the system started freezing in the same way: after a flicker. At one point I must have rebooted at least 20 times within 1 hour or so. I finally decided to call Dell Customer Service, as the laptop is still under warranty. After several attempts (as the calls also sort of froze in the middle of my telling what was wrong), I was able to get through to someone at Dell India. There was a long session that involved running diagnostics at bootup, then checking that the graphics driver was installed or not. The graphics driver had to be downloaded and installed. Strangely, the system didn’t freeze once during the more than one hour session with the Dell representative. Since it seemed to be working well, I thought the problem was related to graphics driver. Several online forums also mentioned Dell XPS 9370 freezes due to graphics card driver problem, but in my case freeze often happens even during the bootup, before the OS starts. Still, I updated the drivers suggested by Dell Update tool and also updated Windows. All seem to be going well when the freezing started again. This time it was even worse. It once froze during typing the boot password, which I have had setup for several months now. There were many freezes and restarts, but one was particularly strange. The system restarted automatically in the middle of my typing the boot password (I had typed only part of the password) and then it rebooted without asking me for boot password. On this occasion, every key press was accompanied by a flicker. I was able to reboot again several times (the boot password is not deleted, as the system is asking for it, but it flickers at every key press while typing the boot password). I did Dell bootup diagnostics again and it said everything was fine. Still, the system is freezing so frequently now that it is again practically unusable. So, I am not sure whether it is a problem related to Qubes, or the graphics card or with BIOS. My hunch is still that it is with BIOS, unless the hardware itself is compromised. -- 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/AA91ACCB-E3B9-4683-ABF8-BCA94E4AA920%40gmail.com.
Re: [qubes-users] Re: Unsure about network device attachment to VMs
> Your system intermittently freezing sounds like it could be > https://github.com/QubesOS/qubes-issues/issues/5272 too. It does seem like it, but one difference is that this time I haven’t even updated dom0 yet. I have not connected to internet at all, as I was first trying to connect through ethernet. -- 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/F8B6DD60-035A-48BC-BA65-25073AB0D3CE%40gmail.com.
Re: [qubes-users] Re: Unsure about network device attachment to VMs
> In dom0, do qvm-pci. Check the USED BY column to make sure the > appropriate devices are in the appropriate qubes. > I tried that. There is no PCI device used by a VM, except wireless adapter (sys-net) and USB controller (sys-usb). > Next, ISTR others saying USB-C devices are twitchy in Qubes. Try > powering everything off, then attaching the Realtek to the hub, hub to > laptop, and only then powering on the laptop. I did that. The device apparently gets attached to sys-net, but it is still not listed by lsusb in sys-net and network still doesn’t connect by ethernet. There may be a problem with USB-C devices in Qubes. (I don’t really know what you mean exactly by doing ISTR to other: ISTR seems to stand for It Stands To Reason. Do I have to send a separate mail at some other forum?). I haven’t tried Qubes so far on any other laptop without using USB-C ports. Is it normal to sometimes get GUI textbox for device passphrase and sometimes command line prompt? -- 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/52734941-1D56-446E-9EF4-B56DFC406497%40gmail.com.
Re: [qubes-users] Re: Unsure about network device attachment to VMs
>> >> The freezing might have been caused by the PCI device changes you made. >> Try to undo them, so your USB controllers (only) are in sys-usb, and >> wifi controller (only) is in sys-net. >> >> Then, verify the Realtek is listed in dom0 under qvm-usb. You _may_ then >> be able to map it to sys-net with qvm-usb a sys-net [Realtek]. >> > > I will try that out. But how will I undo the changes when the changes (actually only one attempt) did not succeed? -- 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/A4B506BD-91FA-41F2-B71C-9029125597CD%40gmail.com.
Re: [qubes-users] Re: Unsure about network device attachment to VMs
> On 15-Sep-2019, at 5:32 PM, awokd wrote: > > Anil Eklavya: >>> Can you diagram what you are trying to do? E.g. I think it's: >>> >>> Ethernet---Realtek---USB3 hub---sys-usb---sys-net(for networking) ? > I am simply trying to connect the ethernet adapter to sys-net, instead of > having network directly in sys-usb (which seems to be against the design of > Qubes, I think). I tried with qvm-sub, but it didn’t work, so I tried with > qvm-pci, but that also doesn’t work (it is not even supposed to, I think, if > the adapter is listed as a USB device). > > So, yes, the above diagram is basically correct, except that it is USB 3.1 > (type C) hub. The laptop has no ethernet port. > > About freezing, it also coincided with upgrading to a larger nvme drive from > a different company. That is why I had asked earlier if the drive can cause > the freezing, or perhaps the firmware in the drive is not reliable. Should I > go back to previous drive and see it freezing still happens. I don’t know > exactly what is happening, but given the fact that I have been using > computers of various kinds with different OS’s since 1994 as a power user (at > least), my instinctive response is that it is something malicious. At what > level it is occurring, that I don’t know. > > This is a costly laptop (with costly upgrades) and I can’t afford to buy > another laptop right now and to dispose of this one. I would like to try to > make it work if it can be made to work with Qubes. > > It was working (without freezing) earlier, but with legacy boot and with a > different drive, but I am not sure if it was compromised even then. More > importantly, it was working with sys-usb and sys-net combined. > > As an aside, the pen drive (HP class 10) I had use earlier after upgrading to > this larger nvme to update the BIOS, got bricked apparently for no reason, > without being attached to anything else. I noticed that only when I tried to > use it again for updating the BIOS again. >> I am simply trying to connect the ethernet adapter to sys-net, instead of >> having network directly in sys-usb (which seems to be against the design of >> Qubes, I think). I tried with qvm-sub, but it didn’t work, so I tried with >> qvm-pci, but that also doesn’t work (it is not even supposed to, I think, if >> the adapter is listed as a USB device). >> >> So, yes, the above diagram is basically correct, except that it is USB 3.1 >> (type C) hub. The laptop has no ethernet port. > > The freezing might have been caused by the PCI device changes you made. > Try to undo them, so your USB controllers (only) are in sys-usb, and > wifi controller (only) is in sys-net. > > Then, verify the Realtek is listed in dom0 under qvm-usb. You _may_ then > be able to map it to sys-net with qvm-usb a sys-net [Realtek]. > I will try that out. >> About freezing, it also coincided with upgrading to a larger nvme drive from >> a different company. That is why I had asked earlier if the drive can cause >> the freezing, or perhaps the firmware in the drive is not reliable. Should I >> go back to previous drive and see it freezing still happens. I don’t know >> exactly what is happening, but given the fact that I have been using >> computers of various kinds with different OS’s since 1994 as a power user >> (at least), my instinctive response is that it is something malicious. At >> what level it is occurring, that I don’t know. > > You shouldn't have to go back to the previous drive. > > PS Did you mean to drop the list from your reply? No, I just replied in the mail client and forgot to include to list mail id. I have added the missing part in the quote above for reference. -- 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/47B17116-21E9-4A24-BC53-AE719F39F149%40gmail.com.
[qubes-users] Re: Unsure about network device attachment to VMs
On 15-Sep-2019, at 4:31 PM, Anil Eklavya wrote: > The system froze again after I attached the ethernet usb device through > qvm-usb, even though network did not connect and the adapter was not listed > in sys-net by lsusb. > > On rebooting, it froze twice while typing the disk passphrase. Third time it > froze while typing the user passphrase. Each time the freezing occurs with a > flash of the screen, the kind that occurs when we take a screenshot. > > Also, I don’t know whether it is relevant here, but I get the error “Failed > to start load kernel modules” while booting up, just am mentioned on a Qubes > github forum. I should have mentioned that this time I have installed with UEFI, not with legacy mode. Also, on this installation, I get a command line prompt for typing the disk passphrase and not the GUI textbox. Before that, there is a lot of what seems to be Xen related output (things that happen while booting up). These were not visible earlier when things were working fine. Even the last time, the system started freezing after this change occurred: the visible Xen output. I don’t know whether it is relevant, but ever since it started happening, the arbitrary freezing also started occurring. I should emphasize that freezing is total. It doesn’t go away after any length of time. I simply have to physically restart the laptop. -- 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/AD2C51DB-BBBF-4735-855D-BE0795FD85AC%40gmail.com.
[qubes-users] Re: Unsure about network device attachment to VMs
> I have already tried attaching with qvm-usb as the Realtek adapter is listed > by this command. It apparently gets attached with sys-net, but lsusb in > sys-net doesn’t show it. Ifconfig also doesn’t list it. The system froze again after I attached the ethernet usb device through qvm-usb, even though network did not connect and the adapter was not listed in sys-net by lsusb. On rebooting, it froze twice while typing the disk passphrase. Third time it froze while typing the user passphrase. Each time the freezing occurs with a flash of the screen, the kind that occurs when we take a screenshot. Also, I don’t know whether it is relevant here, but I get the error “Failed to start load kernel modules” while booting up, just am mentioned on a Qubes github forum. Regards, Anil -- 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/36CA9258-EEEA-4DA4-9A86-437E82653F24%40gmail.com.
[qubes-users] Re: Unsure about network device attachment to VMs
> On 15-Sep-2019, at 3:36 PM, Anil Eklavya wrote: > Following the documentation USB and PCI devices, I tried the following: > > - lsusb in sys-usb to list USB devices > > The ethernet device is listed as Bus 003 Device 002, but there is another > device as Bus 003 Device 001 (Linux Foundation root hub) > > - I then used the readlink for usb3 > > This gave the BDF as 00:06.0 > > - From dom0 terminal, I then tried: > > qvm-pci attach sys-net sys-usb:00:06.0 —persistent > > I get an error message saying sys-usb doesn’t expose the device 00:06.0 I have already tried attaching with qvm-usb as the Realtek adapter is listed by this command. It apparently gets attached with sys-net, but lsusb in sys-net doesn’t show it. Ifconfig also doesn’t list it. -- 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/FD7F0099-7996-426B-931D-B68F18476092%40gmail.com.
[qubes-users] Re: Unsure about network device attachment to VMs
> On 14-Sep-2019, at 11:21 PM, Anil Eklavya wrote: > > The ethernet link is down in sys-net. I tried using ip and ifconfig and ifup > commands to bring it up, but it is still down. On finally giving for now and > pulling out the ethernet adapter, the system froze completely again, like it > was doing before I reinstalled. Following the documentation USB and PCI devices, I tried the following: - lsusb in sys-usb to list USB devices The ethernet device is listed as Bus 003 Device 002, but there is another device as Bus 003 Device 001 (Linux Foundation root hub) - I then used the readlink for usb3 This gave the BDF as 00:06.0 - From dom0 terminal, I then tried: qvm-pci attach sys-net sys-usb:00:06.0 —persistent I get an error message saying sys-usb doesn’t expose the device 00:06.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/2BAAA2E4-557E-4568-AE8D-B8BFF96976F9%40gmail.com.
[qubes-users] Re: Unsure about network device attachment to VMs
The ethernet link is down in sys-net. I tried using ip and ifconfig and ifup commands to bring it up, but it is still down. On finally giving for now and pulling out the ethernet adapter, the system froze completely again, like it was doing before I reinstalled. Regards, Anil -- 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/89BE667B-79B1-49FA-B09F-D239D06B4D72%40gmail.com.
[qubes-users] Re: Unsure about network device attachment to VMs
> Can someone help with this problem, right now just for getting my Qubes > installation started, keeping ethernet and other USB devices separate, and > with VPN installed somewhere. Detailed documentation can come later. Right now, I have the wireless device connected to sys-net, but I am trying to get ethernet through sys-usb. On installation, the list of services in sys-usb included network-manager, which was causing ethernet based networking to be connected directly in sys-usb and that was being used in sys-net (as far as I can understand). Now I have removed network-manager service from sys-usb and put it in sys-net. I then manually attach the LAN device to sys-net. However, this doesn’t seem to allow me to connect to network through ethernet. Running lsusb doesn’t show the LAN device in sys-net even after attaching. I am missing something basic here, it seems. When I try to create an ethernet connection in sys-net, there is no ethernet device to be connected to. Regards, Anil -- 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/945C39B4-2A71-46B3-ABC5-7EC995468980%40gmail.com.
[qubes-users] Unsure about network device attachment to VMs
I am reinstalling Qubes, but I am not sure how to which devices to attach to sys-usb and which to sys-net. Earlier the network devices were directly attached to sys-usb and sys-usb was providing the network. This is the setting my new install started with. I am trying to avoid getting network directly from sys-usb. There seems to be some trivial thing that I am missing. For context, my laptop (Dell XPS 13 9370) has two thunderbolt USB-C ports and one normal USB-C port. It is the third port which is practically the only port I can use as things are setup, since it seems to be unadvisable to attach thunderbolt devices to Qubes. So I mostly use a USB-C hub, which has the ethernet port as well other ports. The laptop is not in the HCL list, but it seems to work fine with some issues. The documentation for Qubes is pretty good, but one problem is that it is better for those who either have no technical knowledge or have deep technical knowledge of how Linux and OS work, along with networking. I fall somewhere in the middle, so both kinds of advised are not very useful. I think, given that the online threats come from network, there should be a more detailed, technically middle-grounded documentation for setting up network on Qubes, including where should VPN go (various options and their pros and cons). Can someone help with this problem, right now just for getting my Qubes installation started, keeping ethernet and other USB devices separate, and with VPN installed somewhere. Detailed documentation can come later. Regards, Anil -- 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/D9D6B664-465E-4C2A-A8B9-A25D52628917%40gmail.com.
[qubes-users] What does Qubes backup save?
Can someone clarify exactly what all does Qubes Backup save and restore? To me this is important because I am fairly sure my Qubes installation has been compromised, if not at dom0, then certainly for some VMs, including sys-net (which includes sys-usb). Most probable reason is Evil Maid Attack as I found one screw on my laptop missing, which was earlier there. I know this attack could be accomplished even without opening the laptop up, but someone might have tampered with the laptop and may also have used the USB. In such a case, if I backup and restore to a new installation, will the VMs still be compromised because they will be restored completely, or will they be fresh in the sense that only my data will be restored, along with a few basics like the specification of VM? Will it be preferable to use something like rsync for taking separate backups of the data on VMs? -- 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/e92546ea-ad65-4eb3-9963-cd66a8976c87%40googlegroups.com.
