[qubes-users] Re: dom0: no space left on device / Qubes partition size?
hey , i need your help with qubes and installing partition on the usb to save files.. do you do it on the windows while you download Qubes in the terminal or once your first running qubes ? On Wednesday, February 17, 2016 at 9:44:03 AM UTC-6 dbo...@gmail.com wrote: > Dear all, > Some help needed - yet! > I got to the point of resizing my /dev/sdb4 partition, which contains the > LUKS partition, to fill the avalable size. Following the archlinux tutorial > mentioned in above post, I tried too use pvresize, but pvresize /dev/sdb4 > as well as pvresize /dev/mapper/luks... annoounce it is resized but no > effective resizing is taking place . vgdisplay still gives 0 PE. > > tnks > > -- 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/b2553c09-cbca-4031-bc6c-46421b1c101cn%40googlegroups.com.
[qubes-users] Re: off topic - invite codes to 'riseup'
On Thursday, April 4, 2019 at 3:19:10 PM UTC-3, robsonsil...@gmail.com wrote: > Me to. If anyone has a rise up invite I will be thankful in advance. > > :) can some one send me a invite to riseUp too? thank you -- 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/d843e0d1-08b8-40e2-a855-9e04dd979167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide on installing Qubes and Coreboot with encrypted boot on thinkpads
On 2018-04-06 09:22, 799 wrote: As mentioned I have also drafted a how-to to setup Coreboot on a X230, including building the pi, flashrom and extracting Blobs. My how-to is located in the Qubes Community docs. While I need to fill in some small gaps how to put the hardware parts together, all the other stuff is covered including extracting Blobs and vga.rom. The how-to is located here: https://github.com/Qubes-Community/Contents/blob/master/docs/coreboot/x230.md The coreboot config I have used is here: https://github.com/Qubes-Community/Contents/blob/master/docs/coreboot/x230-configfile Good guide, thank you. I'm looking forward in better understanding Heads (http://osresearch.net/) and maybe adding some notes on it. Currently i do not have a Github account set up, so i will not be able to make a pull request adding my guide. If anyone can do it would be much appreciated, otherwise i'll probably do it given some time. I am interested in getting the best out of both worlds (Coreboot + Qubes). It seems that your approach (using GRUB) offers some benefits vs. using SeaBIOS as the boot partition can so be encrypted. Are there issues going this way? For example breaking the future upgrade ability ? It seems to me that if I run Coreboot with grub + encrypted boot, there is no need to run anti evil maid, as the boot partition can't be messed with. Is this correct? Currently i have hardcoded the kernel version in the grub config inside the ROM. This is an ugly temporary solution as obviously even if i upgrade i'll continue to boot the old kernel by default. My idea is to modify the update script to always add/update a symlink to the newest kernel and use that naming in Grub but i have yet to look into it. As for the AEM, i guess that if you are satisfied with your Grub config you could set the lock bits in coreboot and flash the rom as read only. Also preventing the boot of external device should be a good idea. However as far as I can understand, while this is better than the standard it doesn't really provide a valid chain of trust. There are still additional measures that can be taken like signing your kernel and using the TPM, see https://trmm.net/Heads for more deatils. -- 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/66f21da272ab23d0dd5373e3969c7463%40anche.no. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide on installing Qubes and Coreboot with encrypted boot on thinkpads
On 2018-04-05 19:38, 799 wrote: Nice how-to, I'm currently writing something similar for my X230. Would you mind adding your howto to the Qubes Community doc repository, which we've established to work on howtos and docs until they're easy to be migrated to the official Qubes Docs. If you agree, I can also add your notes there, mentioning you as the original author. Hello, no problem as I said it is copyleft. Where's the Qubes Community repository? I'd like to use grub as payload but without using encrypted boot as I am afraid to damage my production Qubes environment and loosing time fixing it. What do I need to do, if I would like to just use Grub and leave my boot untouched? As far as I understand the benefit of having Grub as payload is to be able to encrypt /boot. Does this mean than include that it makes no sense to run Grub instead of SeaBIOS without having boot encrypted? [799] The advantage of using SeaBIOS is that it should be able to launch the Grub on the original /boot partition which means that Grub config will be updated with system updates and that boot options can be changed without the need to re-flash. Also probably SeaBIOS do have more low level configuration options similar to a vendor BIOS. Honestly the process of encrypting /boot went far smoother than I expected, it actually worked on the first try (even though I did a full dd backup copy of the whole disk before and kept also a Grub entry to boot the old way). All included it took less than a day for the transition. The other benefit apart from encrypting /boot is a faster boot process i'd say and maybe a little more security: don't know if it's possible for SeaBIOS (probably yes) but i configured Grub to ask for a user and password for every non standard option in the menu (ex: modifying an entry or using the command line), this way it should be very difficult to boot an external media. -- 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/92530580be3e308d0477f777c4895b03%40anche.no. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide on installing Qubes and Coreboot with encrypted boot on thinkpads
On 2018-03-28 12:14, G wrote:
You're right. So the no ME no TPM rule probably apply only when using
the stock bios. I just noticed coreboot recently pushed a commit
fixing a problem in TPM activation
https://github.com/coreboot/coreboot/commit/676887d2e2e474f70a8ebb1b6065f71e4e81001d
maybe that's the issue with my x220. I'm rebuilding my rom to check if
something changes with that commit, i'll give an update soon.
Giulio
I just flahed the latest commit: still no luck. By checking the source
code I think that the init_tpm() function is actually being called:
From file coreboot/src/northbridge/intel/sandybridge/romstage.c:
120 if (IS_ENABLED(CONFIG_LPC_TPM)) {
121 init_tpm(s3resume);
122 }
From my config:
CONFIG_LPC_TPM=y
CONFIG_NORTHBRIDGE_INTEL_SANDYBRIDGE=y
I think i'll try opening an issue in coreboot about this.
--
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/ef7fef774ffe5d7df56fdc0daa33a4c3%40anche.no.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide on installing Qubes and Coreboot with encrypted boot on thinkpads
On 2018-03-28 11:42, 'awokd' via qubes-users wrote: On Wed, March 28, 2018 8:13 am, G wrote: I looked into adding a secondary TPM, maybe in the ExpressCard slot but it looks like no such piece of hardware exist. Or maybe there's a way to use the integrated TPM without the Intel ME but i don't have the skills to research in that direction. It looks like they are cleaning ME and still using the TPM? http://osresearch.net/Installing-Heads You're right. So the no ME no TPM rule probably apply only when using the stock bios. I just noticed coreboot recently pushed a commit fixing a problem in TPM activation https://github.com/coreboot/coreboot/commit/676887d2e2e474f70a8ebb1b6065f71e4e81001d maybe that's the issue with my x220. I'm rebuilding my rom to check if something changes with that commit, i'll give an update soon. Giulio -- 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/d8676aecdf0d84210818138c892c8508%40anche.no. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide on installing Qubes and Coreboot with encrypted boot on thinkpads
On 2018-03-27 22:17, awokd wrote: PS Have you seen Heads? http://osresearch.net/ Nope i didn't know it. By the overview it looks like a very good idea but i have yet to understand all the details. Still the problem is that currently one has to choose between keeping the Intel ME active or have a working TPM. I tried starting a discussion on the tradeoffs of both https://groups.google.com/forum/#!topic/qubes-users/JEEaDRZpnpA and as other users pointed out, while it stills depend on your threat model, the Intel ME pose a potential remote threat while the TPM should help notice a physical attack (given coreboot is flashed with write protection). I looked into adding a secondary TPM, maybe in the ExpressCard slot but it looks like no such piece of hardware exist. Or maybe there's a way to use the integrated TPM without the Intel ME but i don't have the skills to research in that direction. -- 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/c346292aa1c1a38b6a92abbe79e7facc%40anche.no. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Guide on installing Qubes and Coreboot with encrypted boot on thinkpads
On 2018-03-27 18:10, G wrote: Hello, since it took a while for me to sum up all piece and a lot of trial and error to get the whole setup working i took some notes to help other who want to try something similar. Please note that everything written there is public domain (so copy-edit-whatever). https://git.lsd.cat/g/thinkad-coreboot-qubes I did it today in a hurry so any feedback, modification or contribution is welcome. Giulio There's a typo in the url: should be https://git.lsd.cat/g/thinkpad-coreboot-qubes -- 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/d9c690caf8abd16540d5d99e905fdff2%40anche.no. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Guide on installing Qubes and Coreboot with encrypted boot on thinkpads
Hello, since it took a while for me to sum up all piece and a lot of trial and error to get the whole setup working i took some notes to help other who want to try something similar. Please note that everything written there is public domain (so copy-edit-whatever). https://git.lsd.cat/g/thinkad-coreboot-qubes I did it today in a hurry so any feedback, modification or contribution is welcome. Giulio -- 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/b86e10cc71df1700ed87b110a142a131%40anche.no. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Failed to start Qubes DB agent after upgrade fedora 24 to 25 (r3.2)
On Wednesday, 10 January 2018 18:13:37 UTC+1, Pawel G wrote: > I upgraded dom0 from fedora-24 to fedora-25 on Qubes r3.2. > > After reboot, I can login, GUI starts, I'm able to open dom0 Terminal window > etc. but Qubes Manager is not running, I can't start VMs: > > "Failed to execute child process "qvm-run" (No such file or directory)." > > > "journaltcl | grep Fail" shows: > > "Failed to start Qubes DB agent", and > "Failed to start Virtualzation daemon". > > I tried to restart qubesd (not sure if it's related), but it says that: > > "Failed to restart qubesd.service: Unit qubesd.service failed to load: No > such file or directory". > > I can't find any related thread to my problem (here and issues on github). > > Any help would be highly appreciated as I'm smart but unfortunately not too > bright. I have no idea how to diagnose this problem and how to make my Qubes > works again. > > Thanks! > > Pawel I found out some more information regarding qubes-db-dom0.service failure: symlink /var/run/qub es/qubesdb.sock: No such file or directory FATAL: server socket initialization failed qubes-db-dom0.service: Main process exited, code=exited, status=1/FAILURE Failed to start Qubes DB agent. -- 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/0b6eb3c6-d4d6-4ebc-8a3d-072e3b0ea717%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Failed to start Qubes DB agent after upgrade fedora 24 to 25 (r3.2)
On Thursday, 11 January 2018 21:12:22 UTC+1, awokd wrote: > If you back up the VMs first, you can reinstall then restore the VMs. In > 3.2, go to Qubes VM Manager, then System menu, and choose Backup. Best if > you can do this to an external drive so the backups don't get wiped by > mistake on the install! Is this the only way? No recovery mode? :) Qubes VM Manager is not running unfortunetly, so no go for 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 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/58a39e1a-a74a-4e28-8a5d-69555f49f884%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Failed to start Qubes DB agent after upgrade fedora 24 to 25 (r3.2)
On Wednesday, 10 January 2018 23:30:42 UTC+1, awokd wrote: > On Wed, January 10, 2018 5:13 pm, Pawel G wrote: > > I upgraded dom0 from fedora-24 to fedora-25 on Qubes r3.2. > > Well there's the problem! :) Ordinarily, you should not upgrade dom0. Sorry for misunderstanding, I figured out what I did analysing my bash_history file (as I was sure that I haven't experimenting, just followed docummentation): I upgraded dom0 (following "Installing and using Windows-based AppVMs" doc): sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-windows-tools and not long after that I upgraded all my VMs from f-24 to f-25. I use my laptop for a few weeks puting it into hibernation mode. After restart - you know the story. I haven't found anything in bash_history what would damage qubes, aside from those updates. Is it possible to reinstall base system and have my VMs and data not earased (like from ISO installer)? 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/a0da733b-02cf-4605-84d8-c26993fcf5f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Failed to start Qubes DB agent after upgrade fedora 24 to 25 (r3.2)
I upgraded dom0 from fedora-24 to fedora-25 on Qubes r3.2. After reboot, I can login, GUI starts, I'm able to open dom0 Terminal window etc. but Qubes Manager is not running, I can't start VMs: "Failed to execute child process "qvm-run" (No such file or directory)." "journaltcl | grep Fail" shows: "Failed to start Qubes DB agent", and "Failed to start Virtualzation daemon". I tried to restart qubesd (not sure if it's related), but it says that: "Failed to restart qubesd.service: Unit qubesd.service failed to load: No such file or directory". I can't find any related thread to my problem (here and issues on github). Any help would be highly appreciated as I'm smart but unfortunately not too bright. I have no idea how to diagnose this problem and how to make my Qubes works again. Thanks! Pawel -- 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/3a0c8967-7bef-49e7-971a-ef767dc294b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes on iMac 27" late 2009
Dear, I've an iMac 27 late 2009 (2,66 GHz Intel Core i5). When I tried to install Qubes OS 4.0 rc2, I get following message: "Unsupported Hardware Detected This hardware lack features required by Qubes OS Missing features: HVM/VT-x/AMD-V, IOMMU/VT-d/AMD-Vi, HAP/SLAT/EPT/RVI, Interrupt remapping" Is it possible to solve this issue by activating something? Or do I have to buy a new computer? Thank you for your help. -- 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/20171119170124.DC7704E003D%40mta-1.openmailbox.og. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Boot Problem
On Saturday, April 22, 2017 at 8:28:35 PM UTC-7, Andrew Morgan wrote: > On 04/22/2017 03:21 PM, > craig.g.jes...@gmail.com wrote: > > On Wednesday, April 19, 2017 at 1:35:06 PM UTC-7, > > craig.g...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: > >> I am having at boot problem with my Qubes OS 3.2. When I boot up I enter > >> the disk password and the boot process continues until it gets to the > >> line... > >> > >> A start job is running for Qubes NetVM startup (32s / no limit) > >> > >> And it hangs. The HDD turns off and the computer will stay here never > >> booting or shutting down until you force it to turn off. Anyone have an > >> idea of what is going on and how to fix it? > >> > >> Thank you, > >> > >> Craig > > > > Thank you for your information. Using your directions I have managed to > > get into my Qubes system. I disabled qubes-netvm.service and my system > > will now shutdown and startup without any kernel command line options. Of > > course this means I have no network connections to anything. If I enable > > the qubes-netvm.service and start sys-net the Qubes OS freezes up and I > > have to power cycle the laptop. How do I fix the qubes-netvm.service? It > > seems to be causing the problem but what do I check next? > > > > Thank you, > > > > Craig Jesson > > > > When I was having issues with my NetVM, I backed off all my AppVMs and > templates (sans the NetVM) to an external drive, reinstalled QubesOS, > generated a new sys-net and sys-firewall, then restored all my AppVMs > back again. Fixed all my issues. > > May be a good last resort if you're not sure what's the issue with the > NetVM. > > Andrew First I want to thank Manual Amador and Andrew Morgan for your help. Using Manual's advice I was able to get into my frozen laptop. I then used Andrew's advice to backup all of my vm's except for sys-net and sys-firewall. Then I reinstalled Qubes OS v. 3.2. I have figured out what went wrong. Qubes on my laptop started freezing after a recent update. The update replaced qubes-netvm.service with a new qubes-netvm.service. This overwrote changes I made to qubes-netvm.service to make my Broadcom NetXtreme BCM5761 Gigabit Ethernet PCIe and BCM4313 802.11bgn Wireless Network Adapter work. Unfortunately I did not backup the qubes-netvm.service to document the changes I made. So I am trying to remember what I did to get these cards working. But everything I have tried has not worked. I did the "Assigning Devices" work around listed here https://www.qubes-os.org/doc/assigning-devices/ and This does not seem to matter on the BCM5761 Ethernet card. But it does seem necessary for the wireless card. Right now I have the wireless card disabled in the BIOS figuring that I will get each card working one at a time. So the Ethernet card shows up and I have it assigned to the sys-net vm but it will not get an IP address. I have live booted the laptop with Knoppix and I can get an IP address and use the Internet so I know the Ethernet card, the cable, and the residential gateway are all working fine so it has to be some kind of configuration problem in Qubes. Here is my Qubes HCL Report... --- layout: 'hcl' type: 'laptop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' brand: | Dell Inc. model: | Latitude E5520 bios: | A14 cpu: | Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz cpu-short: | FIXME chipset: | Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) chipset-short: | FIXME gpu: | Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10) memory: | 8089 scsi: | ST9500423AS Rev: DEM1 DVD+-RW GT60NRev: A102 versions: - works: 'FIXME:yes|no|partial' qubes: | R3.2 xen: | 4.6.1 kernel: | 4.4.14-11 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK --- Here is my Qubes-pre-netvm.service [Unit] Description=Netvm fixup Before=qubes-netvm.service [Service] ExecStart=/bin/sh -c echo ':09:00.0 > /sys/bus/pci/drivers/pciback/permissive' Type=oneshot RemainAfterExit=yes [Install] WantedBy=multi-user.target Anybody have a clue as how to make my network cards work? Thank you, Craig Jesson -- 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/d10f7c65-fe73-4b6e-ada8-ce9bd2cff29b%40googlegroups.com. For more options, visit
[qubes-users] Boot Problem
I am having at boot problem with my Qubes OS 3.2. When I boot up I enter the disk password and the boot process continues until it gets to the line... A start job is running for Qubes NetVM startup (32s / no limit) And it hangs. The HDD turns off and the computer will stay here never booting or shutting down until you force it to turn off. Anyone have an idea of what is going on and how to fix it? Thank you, Craig -- 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/f530a772-54a7-4783-8db8-746916bfa834%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
