[qubes-users] Re: slightly off-topic: self-resetting OS idea
You may want to take a look at Fedora's Silverblue immutable desktop operating system. I had problems installing the latest version but conceptually the OS in time will be a good alternative to Qubes which I use as my daily driver. -- 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/80448924-78cc-42c4-9ec2-c21fbed1d181%40googlegroups.com.
[qubes-users] Re: slightly off-topic: self-resetting OS idea
On Monday, August 26, 2019 at 1:24:48 AM UTC-7, panina wrote: > > Hi! > > This is not strictly Qubes-OS related, rather inspired by Qubes. > > I've been struggling with some parts of Qubes usage. Most of the time, > it is overkill for me, and putting some strain on my computer. The > bugginess is also quite annoying, whenever I just need to do some > everyday work. > I've been thinking I'd like some form of dual-boot solution, or possibly > a Live USB that could be used. > Most of the time I work with ssh and webapps, so the only persistent > data I need to work will fit on a smartcard. > > My thought is to have an installation that mounts most of the root > partition as readonly, and uses ramdisks wherever the system wants to > write (e.g /var/log). I'm also thinking it should be possible to get a > fingerprint or somesuch of the root partition, and use my TPM2 to check > this. > > The system should also have a possibility to update itself, that I can > choose to do in environments that I feel is safe. > > I am wondering if anyone knows of an OS that works like this? Or if > anyone knows of tools that might accomplish parts of this? > > <3 > /panina > > -- 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/5d08f05c-8cbc-4c74-89c2-eeb160079e15%40googlegroups.com.
Re: [qubes-users] Unable to install usb-keyboard in 4.0
I have a sys-net qube which was created during the installation. I get the same error when I try to create a USB qube: sudo qubesctl state.sls qvm.sys-usb -- 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/19e38533-e88f-4c38-be18-d349fef3b894%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Unable to install usb-keyboard in 4.0
Hello, I am trying to add a usb keyboard in 4.0. I am following the "How to use a USB Keyboard" in the Qubes documentation. When I run the "sudo qubesctl state.sls qvm.usb-keyboard" in dom0, I get the following error: ID: sys-net-usb Function: qvm.prefs Name: sys-net Result: False Comment: The following requisites were not found: require: sls: qvm.sys-net Changes: 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 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/c13cfdd7-eced-4ad6-8f6b-e90aaa1c4c6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora-29 Template Updates Kernel Question
On Friday, February 1, 2019 at 10:54:21 AM UTC-8, Chris Laprise wrote: > On 2/1/19 1:14 PM, scoobyscra...@gmail.com wrote: > > Hi All, > > > > I updated my Fedora-29 template today and I noticed that it installed > > vmlinux-4.20.5-200.fc29.x86_64. After a reboot, the fedora-29 template > > says 4.14.74-1.pvops.qubes.x86_64 which is the same as dom0. > > > > I am new to Qubes so I do not understand why the fedora-29 updated the > > kernel to 4.20 but did not boot to that kernel but instead stayed at 4.14 > > like dom0. > > > > tia > > > > By default the VM kernel is supplied by dom0 at start time and the > template kernel is ignored. This is normal and allows the VMs to operate > in PVH mode which is optimal for Qubes. > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 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/188ce967-0cd6-4be6-8636-a1fc8ce17d49%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Fedora-29 Template Updates Kernel Question
Hi All, I updated my Fedora-29 template today and I noticed that it installed vmlinux-4.20.5-200.fc29.x86_64. After a reboot, the fedora-29 template says 4.14.74-1.pvops.qubes.x86_64 which is the same as dom0. I am new to Qubes so I do not understand why the fedora-29 updated the kernel to 4.20 but did not boot to that kernel but instead stayed at 4.14 like dom0. tia -- 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/ba01bf31-b83c-4b8d-a43c-7d8ee95ff0a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using Untangle as Qubes firewall
On Tuesday, January 22, 2019 at 5:20:17 PM UTC-8, unman wrote: > On Tue, Jan 22, 2019 at 11:32:22AM -0800, scoobyscra...@gmail.com wrote: > > Hello, > > > > I am new to Qubes running on 4.0. I would like to test the Untangle > > firewall and have it run in place of sys-firewall and still use the default > > sys-net. > > > > I created the Untangle firewall as a HVM VM but it only shows one > > interface. How do I add the virtual interface? What else am I missing? > > > > TIA > > > > You should be able to set the HVM as netvm for another qube and the vif > will be set. Try it. In the untangle-firewall HVM, I added sys-net in the Networking field. I have a disposable qube which has the untangle-firewall in the Networking field. When I start the disposable qube, I do see that the untangle-firewall qube added a vif interface but it has no ip address and is down and the untangle firewall does not recognize the vif interface in its configuration gui. -- 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/fa21f110-4b40-4e22-9c44-7790c002e06e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Using Untangle as Qubes firewall
Hello, I am new to Qubes running on 4.0. I would like to test the Untangle firewall and have it run in place of sys-firewall and still use the default sys-net. I created the Untangle firewall as a HVM VM but it only shows one interface. How do I add the virtual interface? What else am I missing? TIA -- 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/69212633-9ebd-469d-96e7-e5b3f4be9e34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1
On Friday, January 11, 2019 at 10:35:11 AM UTC-8, John S.Recdep wrote: > On 1/11/19 8:08 AM, > scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: > > Hello, > > > > I am a new user to Qubes and I like it very much. > > > > I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 > > templates. Below are the errors for both: > > > > Fedora-29: > > > > Fedora Modular 29 - x86_64 > > Error: Failed to synchronize cache for repo 'fedora-modular' > > Done. > > > > Debian-9 (snippet): > > > > Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release > > 500 Unable to connect > > Err:6 https://deb.debian.org/debian stretch Release > > Received HTTP code 500 from proxy after CONNECT > > Err:7 https://deb.debian.org/debian-security stretch/updates Release > > Received HTTP code 500 from proxy after CONNECT > > Err:8 https://deb.debian.org/debian jessie-backports Release > > Received HTTP code 500 from proxy after CONNECT > > E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian-security stretch/updates > > Release' does no longer have a Release file. > > E: The repository 'https://deb.debian.org/debian jessie-backports Release' > > does no longer have a Release file. > > > > TIA > > > > try doing it via a terminal in the templates > > $sudo dnf update > > $sudo apt-get update > sudo apt-get dist-upgrade > > fwiw for myself, the qubes manager fails or is so slow I only use it to > make appvms or change/add applications lately > > > so I guess this is a new install of yours? This was a new install of 4.0.1. I got the same errors when I terminal into the debian-9 and fedora-29 templates. Here is the errors I got from the debian-9 update: Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox y over Qubes RPC (127.0.0.1:59084). Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox y over Qubes RPC (127.0.0.1:59086). Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1: 8082-127.0.0.1:59082.service: Main process exited, code=exited, status=1/FAILURE Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1: 8082-127.0.0.1:59082.service: Unit entered failed state. Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1: 8082-127.0.0.1:59082.service: Failed with result 'exit-code'. Here is the errors I get from fedora-29: 2019-01-13T17:34:39Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failoverm ethod" does not exist 2019-01-13T17:34:39Z DEBUG repo: downloading from remote: fedora-modular 2019-01-13T17:34:39Z DEBUG error: Curl error (56): Failure when receiving data f rom the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular- 29=x86_64 [Received HTTP code 500 from proxy after CONNECT] (https://mirror s.fedoraproject.org/metalink?repo=fedora-modular-29=x86_64). 2019-01-13T17:34:39Z DEBUG Cannot download 'https://mirrors.fedoraproject.org/me talink?repo=fedora-modular-29=x86_64': Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.f edoraproject.org/metalink?repo=fedora-modular-29=x86_64 [Received HTTP code 500 from proxy after CONNECT]. 2019-01-13T17:34:39Z DDEBUG Cleaning up. 2019-01-13T17:34:39Z SUBDEBUG Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/dnf/repo.py", line 566, in load ret = self._repo.load() File "/usr/lib64/python3.7/site-packages/libdnf/repo.py", line 503, in load return _repo.Repo_load(self) RuntimeError: Failed to synchronize cache for repo 'fedora-modular' TIA -- 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/a37d9151-8464-403b-a01b-d8d93a3c7d5c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1
On Friday, January 11, 2019 at 10:35:11 AM UTC-8, John S.Recdep wrote: > On 1/11/19 8:08 AM, > scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: > > Hello, > > > > I am a new user to Qubes and I like it very much. > > > > I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 > > templates. Below are the errors for both: > > > > Fedora-29: > > > > Fedora Modular 29 - x86_64 > > Error: Failed to synchronize cache for repo 'fedora-modular' > > Done. > > > > Debian-9 (snippet): > > > > Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release > > 500 Unable to connect > > Err:6 https://deb.debian.org/debian stretch Release > > Received HTTP code 500 from proxy after CONNECT > > Err:7 https://deb.debian.org/debian-security stretch/updates Release > > Received HTTP code 500 from proxy after CONNECT > > Err:8 https://deb.debian.org/debian jessie-backports Release > > Received HTTP code 500 from proxy after CONNECT > > E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian-security stretch/updates > > Release' does no longer have a Release file. > > E: The repository 'https://deb.debian.org/debian jessie-backports Release' > > does no longer have a Release file. > > > > TIA > > > > try doing it via a terminal in the templates > > $sudo dnf update > > $sudo apt-get update > sudo apt-get dist-upgrade > > fwiw for myself, the qubes manager fails or is so slow I only use it to > make appvms or change/add applications lately > > > so I guess this is a new install of yours? This was a new install of 4.0.1. I got the same errors when I terminal into the debian-9 and fedora-29 templates using your commands. -- 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/a3ea9cdf-2e51-44fc-bf46-d4ef2514025a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot Update Fedora-29 and Debian-9 on 4.0.1
Hello, I am a new user to Qubes and I like it very much. I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 templates. Below are the errors for both: Fedora-29: Fedora Modular 29 - x86_64 Error: Failed to synchronize cache for repo 'fedora-modular' Done. Debian-9 (snippet): Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release 500 Unable to connect Err:6 https://deb.debian.org/debian stretch Release Received HTTP code 500 from proxy after CONNECT Err:7 https://deb.debian.org/debian-security stretch/updates Release Received HTTP code 500 from proxy after CONNECT Err:8 https://deb.debian.org/debian jessie-backports Release Received HTTP code 500 from proxy after CONNECT E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no longer have a Release file. E: The repository 'https://deb.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'https://deb.debian.org/debian-security stretch/updates Release' does no longer have a Release file. E: The repository 'https://deb.debian.org/debian jessie-backports Release' does no longer have a Release file. TIA -- 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/aab39672-5e5e-403e-a5e5-969153f67b92%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
