[qubes-users] BACKUP IMPORTANT VMS Q4
Hello, im using qubes os 4, i updated all the VMs + updated dom0 When i turned on my pc, Qubes os didnt get recognized at boot menu, i have tried a lot of things and now im tired, i just want to backup my vms and i will make a fresh install. I have saw a lot of tutorials but im not that familiar with disk partitions, logical volumes etc. Can someone please tell me step by step how to backup the important vms? I have tried mounting the drive to a live system but i cant mount it, i always get this issue: mount: /mnt: unknown filesystem type 'LVM2_member'. Encrypted partition with all vm data: /dev/sda I cloned the disk in case something goes wrong. Hope you can help 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/48604034-a64c-4f6a-b9b2-5a2091b0b044%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: [qubes-devel] ANN: Fast incremental backups project
Dec 21, 2018, 1:39 PM by tas...@posteo.net: > On 12/20/2018 09:40 PM, Marek Marczykowski-Górecki wrote: > > As for borg, I'm not sure a heavy emphasis on deduplication is appropriate > for many PC applications. Its a resource drain that leads to complex archive > formats on the back end. And my initial testing suggests the dedup efficacy > is oversold: Sparsebak can sometimes produce smaller multi-generation > archives even without dedup. > The borg default chunk size does not dedup Qubes volumes well. You get much better dedup with a smaller chunk size, for example `borg create --chunker-params=11,24,16,4095 ...` Borg's dedup makes it simpler to think about. The repository is a pool of chunks and each backup is like a set of pointers to chunks. When a chunk is no longer referenced by any backup, it is deleted from the repo. -- 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/LUInzpb--3-1%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Well color me impressed (4.0.1-rc2 install on laptop and desktop)
On Friday, December 21, 2018 at 3:39:25 PM UTC-8, unman wrote: > On Thu, Dec 20, 2018 at 09:20:11PM -0800, John Smiley wrote: > > On Thursday, December 20, 2018 at 9:11:34 PM UTC-8, John Smiley wrote: > > > I've been having head-banging issues with 4.0 and 4.0.1-rc1 ever since I > > > became a fledgling Qubes user a few weeks ago. I never did get Qubes > > > working well with Whonix 14 on the desktop. > > > > > > When 4.0.1-rc2 came out the other day, I made a new bootable USB stick > > > with it and replaced Ubuntu on my Thinkpad T480 with it. It booted and > > > installed without a hitch. Perfect first use impression (minus a point > > > for nagging about template updates that aren't there). > > > > > > Then I decided to do a reinstall (for the N thousanth time) on my > > > X299-based desktop. 4.0.1-rc2 fired right up. No problems whatsoever. > > > It works like I expected 4.0 and 4.0.1-rc1 to work. > > > > > > Then for the really impressive part. I have a Caldigit TS3 Plus that I > > > like to use to move all of the wire mess to it and have a single > > > Thunderbolt3 wire running from it to the T480. It provides lots of > > > things but I use it for power to my laptop (replacing the brick), > > > Ethernet, Displayport for a second monitor, and USB 3.1. After the > > > 4.0.1-rc2 install went so well, I decided to plug that bad boy in and > > > watch Qubes fall to the ground writhing in agony. > > > > > > My expectations were not met. 4.0.1-rc2 handled it like a champ. I had > > > to do some minor fiddling with the display settings to get the second > > > monitor working via DP and after a bit of hunting around, I discovered > > > that all I had to do to get Ethernet working was to add the new Ethernet > > > controller it saw to sys-net. Shutdown the Whonix GW and sys-firewall, > > > reboot sys-net, restart sys-firewall and the Whonix GW, plug in my > > > Ethernet cable and voila. It works! > > > > > > Now the first question that comes to mind is, how much security did I > > > throw out the window when I plugged that Thunderbolt 3 hub in? > > > > Oh and one more thing. Everything installed with default settings. No > > fiddling with kernelopts to get the Debian-9 template to boot on the X299 > > desktop by setting noxsave. > > > > Very pleased all the testing you did on rc1 paid off. ;-) > Now you need to do the same on rc2. Somewhat disappointed that you > haven't yet found a bug or two. "Somewhat disappointed that you haven't yet found a bug or two." Well, I did mention that the template update system was nagging about updates that don't exist. That's one! You could consider the manual fiddling required to get the devices on the Thunderbolt 3 hub working a bug (or two if you count per device), so that's two and maybe three. I'll have plenty of time to poke at it over the holiday week. I'm sure I'll find some more. I've got a lot of reading and setup to do to make this into a usable replacement for a regular use environment. Once I get through the hardening tips, password management and use of Yubikey for various things like LUKS, user authentication and setting up we-based 2FA are top of my list. Thank you again for your help and patience. -- 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/529ed42b-995c-4826-ba47-845f94ffead6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot get PHPStorm to work under VM in Qubes OS
Hello All I have just started using Qubes OS and so far love it, I thought it would be a lot harder to get setup. However, although many apps are easy to install such as FileZilla and LibreOffice. I am trying to install PhpStorm via the JetBrains toolbox. I have installed JetBrains Toolbox in the Fedora-26 template, and installed PHPStorm with it. Both applications now show up in the application menu list, I have assigned just PHPStorm to the "Work" Qube. When I launch nothing happens, I can launch from the Fedora template, but not from any of the the other Qubes. I have tried adding the Toolbox to the VM and setting up custom shortcuts but still no luck. As anyone else had this issue and can you share any pointed to get Jetbrains software installed. I will look forward to your reply -- 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/aac0c5d3-3bfe-4da1-9673-e378fac35c35%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Well color me impressed (4.0.1-rc2 install on laptop and desktop)
On Friday, December 21, 2018 at 3:39:25 PM UTC-8, unman wrote: > On Thu, Dec 20, 2018 at 09:20:11PM -0800, John Smiley wrote: > > On Thursday, December 20, 2018 at 9:11:34 PM UTC-8, John Smiley wrote: > > > I've been having head-banging issues with 4.0 and 4.0.1-rc1 ever since I > > > became a fledgling Qubes user a few weeks ago. I never did get Qubes > > > working well with Whonix 14 on the desktop. > > > > > > When 4.0.1-rc2 came out the other day, I made a new bootable USB stick > > > with it and replaced Ubuntu on my Thinkpad T480 with it. It booted and > > > installed without a hitch. Perfect first use impression (minus a point > > > for nagging about template updates that aren't there). > > > > > > Then I decided to do a reinstall (for the N thousanth time) on my > > > X299-based desktop. 4.0.1-rc2 fired right up. No problems whatsoever. > > > It works like I expected 4.0 and 4.0.1-rc1 to work. > > > > > > Then for the really impressive part. I have a Caldigit TS3 Plus that I > > > like to use to move all of the wire mess to it and have a single > > > Thunderbolt3 wire running from it to the T480. It provides lots of > > > things but I use it for power to my laptop (replacing the brick), > > > Ethernet, Displayport for a second monitor, and USB 3.1. After the > > > 4.0.1-rc2 install went so well, I decided to plug that bad boy in and > > > watch Qubes fall to the ground writhing in agony. > > > > > > My expectations were not met. 4.0.1-rc2 handled it like a champ. I had > > > to do some minor fiddling with the display settings to get the second > > > monitor working via DP and after a bit of hunting around, I discovered > > > that all I had to do to get Ethernet working was to add the new Ethernet > > > controller it saw to sys-net. Shutdown the Whonix GW and sys-firewall, > > > reboot sys-net, restart sys-firewall and the Whonix GW, plug in my > > > Ethernet cable and voila. It works! > > > > > > Now the first question that comes to mind is, how much security did I > > > throw out the window when I plugged that Thunderbolt 3 hub in? > > > > Oh and one more thing. Everything installed with default settings. No > > fiddling with kernelopts to get the Debian-9 template to boot on the X299 > > desktop by setting noxsave. > > > > Very pleased all the testing you did on rc1 paid off. ;-) > Now you need to do the same on rc2. Somewhat disappointed that you > haven't yet found a bug or two. Haven't had time to do much more than install it yet. At least it's up. The bugs I was hitting before were all related to installing / upgrading. A partial answer to my question about how much security is diminished when using Thunderbolt comes from the Whonix doc on hardware hardening. https://www.whonix.org/wiki/System_Hardening_Checklist#Anonymous_Blogging.2C_Posting.2C_Chat.2C_Email_and_File_Sharing "Disable or remove problematic devices like ExpressCard, PCMCIA, FireWire or Thunderbolt which may allow attackers with physical access to read RAM." -- 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/df56dbe7-6b7b-483f-9d4d-d1653227d610%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Well color me impressed (4.0.1-rc2 install on laptop and desktop)
On Thu, Dec 20, 2018 at 09:20:11PM -0800, John Smiley wrote: > On Thursday, December 20, 2018 at 9:11:34 PM UTC-8, John Smiley wrote: > > I've been having head-banging issues with 4.0 and 4.0.1-rc1 ever since I > > became a fledgling Qubes user a few weeks ago. I never did get Qubes > > working well with Whonix 14 on the desktop. > > > > When 4.0.1-rc2 came out the other day, I made a new bootable USB stick with > > it and replaced Ubuntu on my Thinkpad T480 with it. It booted and > > installed without a hitch. Perfect first use impression (minus a point for > > nagging about template updates that aren't there). > > > > Then I decided to do a reinstall (for the N thousanth time) on my > > X299-based desktop. 4.0.1-rc2 fired right up. No problems whatsoever. It > > works like I expected 4.0 and 4.0.1-rc1 to work. > > > > Then for the really impressive part. I have a Caldigit TS3 Plus that I > > like to use to move all of the wire mess to it and have a single > > Thunderbolt3 wire running from it to the T480. It provides lots of things > > but I use it for power to my laptop (replacing the brick), Ethernet, > > Displayport for a second monitor, and USB 3.1. After the 4.0.1-rc2 install > > went so well, I decided to plug that bad boy in and watch Qubes fall to the > > ground writhing in agony. > > > > My expectations were not met. 4.0.1-rc2 handled it like a champ. I had to > > do some minor fiddling with the display settings to get the second monitor > > working via DP and after a bit of hunting around, I discovered that all I > > had to do to get Ethernet working was to add the new Ethernet controller it > > saw to sys-net. Shutdown the Whonix GW and sys-firewall, reboot sys-net, > > restart sys-firewall and the Whonix GW, plug in my Ethernet cable and > > voila. It works! > > > > Now the first question that comes to mind is, how much security did I throw > > out the window when I plugged that Thunderbolt 3 hub in? > > Oh and one more thing. Everything installed with default settings. No > fiddling with kernelopts to get the Debian-9 template to boot on the X299 > desktop by setting noxsave. > Very pleased all the testing you did on rc1 paid off. ;-) Now you need to do the same on rc2. Somewhat disappointed that you haven't yet found a bug or two. -- 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/20181221233920.uqalykdn4wjwxllr%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] screen brightness
I run Q4 on a dell notebook.The "screen brightness" key-combination leans qubes to show a screen brightness icon, but I cannot change brightness at all.Is this maybe a setting somewhere? Especially in evening hours this is really a pain in the eye ... Bernhard -- 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/bfbf8444-93b5-f7f1-c2a5-8df336503ec6%40web.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] dom0 "critical error"? and maybe separate broken dependencies on fedora 28 error
Just got this error from dom0, thought I should post it?
I am running 4.0 with fed28 and fed28 minimal, I also got some fedora
update errors which I will post below this:
line: 'Got empty response from qubesd. See journalctl in dom0 for '
func: _parse_qubesd_response
line no.: 81
file: /usr/lib/python3.5/site-packages/qubesadmin/base.py
line: '''
func: qubesd_call
line no.: 514
file: /usr/lib/python3.5/site-packages/qubesadmin/app.py
line: payload_stream)
func: qubesd_call
line no.: 68
file: /usr/lib/python3.5/site-packages/qubesadmin/base.py
line: self.vm.name, 'admin.vm.feature.Get', item).decode('utf-8')
func: __getitem__
line no.: 55
file: /usr/lib/python3.5/site-packages/qubesadmin/features.py
line: return self[item]
func: get
line no.: 74
file: /usr/lib/python3.5/site-packages/qubesadmin/features.py
line: self.internal = self.vm.features.get('internal', False)
func: update
line no.: 340
file: /usr/lib/python3.5/site-packages/qubesmanager/table_widgets.py
line: self.info_widget.update_vm_state()
func: update
line no.: 146
file: /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py
line: # It needs to store threads until they finish
func: on_halted
line no.: 467
file: /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py
line: callback(*params)
func: signal_fired
line no.: 15
file: /usr/lib/python3.5/site-packages/pydbus/proxy_signal.py
line: callback = (lambda con, sender, object, iface, signal, params:
signal_fired(sender, object, iface, signal, params.unpack())) if
signal_fired is not None else lambda *args: None
func:
line no.: 52
file: /usr/lib/python3.5/site-packages/pydbus/subscription.py
===
I tried running update/upgrade and got:
[user@fedora-28 ~]$ sudo dnf update && sudo dnf upgrade
Last metadata expiration check: 0:00:00 ago on Fri 21 Dec 2018 04:55:39
PM EST.
Dependencies resolved.
Problem 1: cannot install the best update candidate for package
hplip-3.18.6-7.fc28.x86_64
- nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-3.18.6-11.fc28.x86_64
Problem 2: cannot install the best update candidate for package
hplip-libs-3.18.6-7.fc28.x86_64
- nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-libs-3.18.6-11.fc28.x86_64
Problem 3: cannot install the best update candidate for package
libsane-hpaio-3.18.6-7.fc28.x86_64
- nothing provides libnetsnmp.so.35()(64bit) needed by
libsane-hpaio-3.18.6-11.fc28.x86_64
Problem 4: package hplip-libs-3.18.6-7.fc28.x86_64 requires
hplip-common(x86-64) = 3.18.6-7.fc28, but none of the providers can be
installed
- cannot install both hplip-common-3.18.6-11.fc28.x86_64 and
hplip-common-3.18.6-7.fc28.x86_64
- problem with installed package hplip-libs-3.18.6-7.fc28.x86_64
- cannot install the best update candidate for package
hplip-common-3.18.6-7.fc28.x86_64
- nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-libs-3.18.6-11.fc28.x86_64
==
Package Arch Version
Repository Size
==
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
hplip-commonx86_64 3.18.6-11.fc28
updates 110 k
Skipping packages with broken dependencies:
hplip x86_64 3.18.6-11.fc28
updates16 M
hplip-libs x86_64 3.18.6-11.fc28
updates 204 k
libsane-hpaio x86_64 3.18.6-11.fc28
updates 127 k
Transaction Summary
==
Skip 4 Packages
Nothing to do.
Complete!
Last metadata expiration check: 0:00:04 ago on Fri 21 Dec 2018 04:55:39
PM EST.
Dependencies resolved.
Problem 1: cannot install the best update candidate for package
hplip-3.18.6-7.fc28.x86_64
- nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-3.18.6-11.fc28.x86_64
Problem 2: cannot install the best update candidate for package
hplip-libs-3.18.6-7.fc28.x86_64
- nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-libs-3.18.6-11.fc28.x86_64
Problem 3: cannot install the best update candidate for package
libsane-hpaio-3.18.6-7.fc28.x86_64
- nothing provides libnetsnmp.so.35()(64bit) needed by
libsane-hpaio-3.18.6-11.fc28.x86_64
Problem 4: package hplip-libs-3.18.6-7.fc28.x86_64 requires
hplip-common(x86-64) = 3.18.6-7.fc28, but none of the providers can be
installed
- cannot install both hplip-common-3.18.6-11.fc28.x86_64 and
hplip-common-3.18.6-7.fc28.x86_64
- proble
Re: [qubes-users] 2FA AEM (anti-evil-maid) fails: "All key slots full"
Dear Patrik, thanks for your kind mail and your thoughtful explanation. Your instructions worked properly. Cheers qubeslover Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Wednesday, December 19, 2018 12:35 PM, Patrik Hagara wrote: > On 12/17/18 2:38 PM, 'qubeslover' via qubes-users wrote: > > > Hi, > > I am trying to configure 2FA AEM (usb stick + TOTP) on my computer. I've > > done several attempts and I've probably messed up with something somewhere. > > Now when I run: > > "anti-evil-maid-install -m /dev/sdb1" > > > > - A new ext4 filesystem is created on my usb stick. > > - I get and verify my QR code. > > - I enter the passphrase for the new LUKS key file. > > > > but I get this output in dom0: > > "anti-evil-maid-install: Adding key file to new key slot for /dev/sda2 > > (UUID XXX) > > All key slots full" > > Can somebody help me with this, please? As mentioned above, I've done > > many attempts to configure AEM without success. However, I've never seen > > this output earlier. > > Every LUKS-encrypted block device is limited to 8 key slots total (pass > phrases and key files). > > You check to see the used/free key slot count using the following > command in dom0: > > $ sudo cryptsetup luksDump /dev/sda2 > > Replace /dev/sda2 with the actual encrypted dom0 root partition, if > you're not sure which one that is (again in dom0): > > $ sudo lsblk > > The partition you're looking for should be listed near the top, with its > "TYPE" being "part" and it will be immediately followed by a TYPE=crypt > block device the name of which will start with "luks-". > > To free up LUKS key slots, use the luksKillSlot command (it will prompt > you to enter any remaining pass phrase, to make sure you won't lock > yourself out): > > $ sudo cryptsetup luksKillSlot /dev/sda2 7 > > where /dev/sda2 is the partition from previous step and 7 is the last > LUKS key slot (they go from 0 to 7, for a total of 8; key slot #0 will > be the pass phrase you set during Qubes installation). If you haven't > provisioned any additional pass phrases or key files, you can safely > kill slots 1 through 7 (leaving just the slot #0). > > Cheers, > Patrik > > > Thanks in advance for your kind attention. > > -- > > 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 > > mailto:qubes-users+unsubscr...@googlegroups.com. > > To post to this group, send email to qubes-users@googlegroups.com > > mailto:qubes-users@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/qubes-users/4gx8cl3gdGrdkuAW8YmANM_F2IUA1r74q6NpFkl3a5fQU_5WuFRe9y_bJKu0yCOGFUvkjbqfVfkjVsN-JaiGEM31WYof4wfvAL7He88T2gQ%3D%40protonmail.com > > https://groups.google.com/d/msgid/qubes-users/4gx8cl3gdGrdkuAW8YmANM_F2IUA1r74q6NpFkl3a5fQU_5WuFRe9y_bJKu0yCOGFUvkjbqfVfkjVsN-JaiGEM31WYof4wfvAL7He88T2gQ%3D%40protonmail.com?utm_medium=email&utm_source=footer. > > For more options, visit https://groups.google.com/d/optout. -- 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/XOndrX0pF_lFMlPoetTeWYo0ZXAaOonlgyvyu31LDthJWaQySYhl0gHWlrd29Fo--8WWVTHvbZFTx566L4zNf6ffPFMQWFMRzZxB5lvDZ-E%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: updating CentOS-7 templates
Le jeudi 20 décembre 2018 16:22:00 UTC+1, Tseng Wynn a écrit : > So does anyone reported this issue to qubes-issues? Yes (https://github.com/QubesOS/qubes-issues/issues/4646). I'm on 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 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/8eaac72e-7e86-499d-90f8-a0e1ba1f6170%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] /usr/lib/qubes/qubes-download-dom0-updates.sh No such file or directory !!!
I followed step by step the whonix uninstall procedure, and have set sys-firewall as UpdateVM. Then I tried to test the update procedure via qubes-dom0-update - and get the above error. I feel that I am close to brick my qubes right now and need really some help. Could someone email me the script? Can I download it manually? Solved. Simply don't use fedora-minimal but a full-fedora distrib as template for sys-firewall when using it as UpdateVM to uninstall / reinstall Whonix. -- 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/758c2894-7d0c-6b45-8410-bbe757ff9c72%40web.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: default-mgmt-dvm no longer hidden
On Thursday, December 20, 2018 at 11:49:27 AM UTC-5, edt...@gmail.com wrote: > I ran updates for dom0 this morning, I noticed that after the updates, the > default-mgmt-dvm is no longer hidden. It is still marked internal, but not > hidden. Is this the desired outcome of the latest dom0 updates? > > Ed It's intentional, see https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-045-2018.txt -- 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/b159ee58-c138-4689-b56d-cd01914a8bbd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-Vpn-support not connected. Please help me.
четверг, 20 декабря 2018 г., 22:42:58 UTC+3 пользователь Chris Laprise написал: > On 12/20/2018 02:11 PM, menoldst...@gmail.com wrote: > > Dec 20 20:49:08 VPN1 qubes-vpn-setup[2085]: Thu Dec 20 20:49:08 2018 > > RESOLVE: Cannot resolve host address: fi.privateinternetaccess.com:1198 > > (Name or service not known) > > That's the problem. > > Did you test the connection as suggested in Step 2, before running install? > > Also, what is the difference between the old style and the new style men? > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Problem solved. Now there is another problem. Windows VM works fine through sys-firewall and sys-net. Any created upvm does not work through sys-net and sys-firewall. Any created upvm works only through a sys-whonix. sys-whonix works through sys-firewall. Suppose I create a new apm and execute a command in the terminal: sudo git clone https://github.com/tasket/qubes-vpn-support.git/ After that, the terminal writes to me: unable to acess 'https://github.com/tasket/qubes-vpn-support.git/': unable to resolve host: github.com If I switch the connection to sys-whonix, then everything will work. Friends, you can help me solve this problem. And forgive me for my bad english. Thank! -- 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/087bb6e4-dce9-4003-8bd9-8271df8e7f5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-Vpn-support not connected. Please help me.
четверг, 20 декабря 2018 г., 22:42:58 UTC+3 пользователь Chris Laprise написал: > On 12/20/2018 02:11 PM, menoldst...@gmail.com wrote: > > Dec 20 20:49:08 VPN1 qubes-vpn-setup[2085]: Thu Dec 20 20:49:08 2018 > > RESOLVE: Cannot resolve host address: fi.privateinternetaccess.com:1198 > > (Name or service not known) > > That's the problem. > > Did you test the connection as suggested in Step 2, before running install? > > Also, what is the difference between the old style and the new style men? > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Problem solved. Now there is another problem. Windows VM works fine through sys-firewall and sys-net. Any created upvm does not work through system-no and system-firewall. Any created upvm works only through a system unix. sis-junix works through sys-firewall. Suppose I create a new apm and execute a command in the terminal: sudo git clone https://github.com/tasket/qubes-vpn-support.git/ After that, the terminal writes to me: unable to acess 'https://github.com/tasket/qubes-vpn-support.git/': unable to resolve host: github.com If I switch the connection to system hunix, then everything will work. Friends, you can help me solve this problem. And forgive me for my bad english. Thank! -- 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/1387ef45-3212-41dd-9dd2-06ccc62cdc4d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-Vpn-support not connected. Please help me.
четверг, 20 декабря 2018 г., 22:42:58 UTC+3 пользователь Chris Laprise написал: > On 12/20/2018 02:11 PM, menoldst...@gmail.com wrote: > > Dec 20 20:49:08 VPN1 qubes-vpn-setup[2085]: Thu Dec 20 20:49:08 2018 > > RESOLVE: Cannot resolve host address: fi.privateinternetaccess.com:1198 > > (Name or service not known) > > That's the problem. > > Did you test the connection as suggested in Step 2, before running install? > > Also, what is the difference between the old style and the new style men? > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Problem solved. Now there is another problem. Windows VM works fine through system firewall and system no. Any created upvm does not work through sys-net and sys-firewall. Any created upvm works only through a sys-whonix. sys-whonix works through sys-firewall. Suppose I create a new apm and execute a command in the terminal: sudo git clone https://github.com/tasket/qubes-vpn-support.git/ After that, the terminal writes to me: unable to acess 'https://github.com/tasket/qubes-vpn-support.git/': unable to resolve host: github.com If I switch the connection to sys-whonix, then everything will work. Friends, you can help me solve this problem. And forgive me for my bad english. Thank! -- 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/f129b8d2-fcfa-4a1f-a99f-81311f776ee8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Failed to synchronize cache for repo 'updates' in fedora-28 template
On Monday, November 26, 2018 at 2:05:30 PM UTC-8, pixel fairy wrote: > $ sudo dnf -y update > Error: Failed to synchronize cache for repo 'fedora-cisco-openh264' > > tried disabling fedora-cisco-openh264 and got > > Error: Failed to synchronize cache for repo 'updates' > > same error on the distro template, which only has updates applied, and my > clone of it, which i use. fedora templates use sys-net. i made a sys-ethernet which i was using instead, so the proxy could not connect. the debian based templates didnt have this limitation. -- 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/97fc321a-0f60-4f6a-b784-e78c51624958%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] delete old whonix-13
On 12/21/18 10:36 AM, haaber wrote: I have slat-installed whonix-14 along with the old whonix-13. At least the W14-GW does work, so I want to delete old W13-GW. But I can't. qvm-remove says "it is in use by: " and then an empty list. That is buggy. the Qubes-Settings delet-function fails as well. How delete this template? Bernhard check that: - the template isn't installed by an rpm (`qvm-prefs whonix-13 installed_by_rpm`). If it is, `qvm-remove` will exit with the cryptic "It is in use by: " error. You'll have do remove the vm with `dnf`. - none of your vms use whonix-13 as a template (`qvm-prefs vmname template` for each of your non-standalone VMs) ; Chris' excellent findpref tool [1] is a time saver for such tasks, otherwise check the prefs manuall for each VM (or write a bash loop over the output of `qvm-ls --raw-list --all --exclude dom0`). - whonix-13 isn't defined as a general settings in `qubes-prefs` [1] https://raw.githubusercontent.com/tasket/Qubes-scripts/master/findpref -- 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/6fa1f9af-423b-8b0d-19c9-72d7e5eed9db%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] /usr/lib/qubes/qubes-download-dom0-updates.sh No such file or directory !!!
I followed step by step the whonix uninstall procedure, and have set sys-firewall as UpdateVM. Then I tried to test the update procedure via qubes-dom0-update - and get the above error. I feel that I am close to brick my qubes right now and need really some help. Could someone email me the script? Can I download it manually? Thank you, Bernhard -- 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/0bb3d309-2754-32d5-9ee2-114dfcbf426f%40web.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] delete old whonix-13
I have slat-installed whonix-14 along with the old whonix-13. At least the W14-GW does work, so I want to delete old W13-GW. But I can't. qvm-remove says "it is in use by: " and then an empty list. That is buggy. the Qubes-Settings delet-function fails as well. How delete this template? Bernhard -- 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/a9309b56-ae91-3ec2-47f3-6bbe6848df7f%40web.de. For more options, visit https://groups.google.com/d/optout.
