[qubes-users] Re: Partially off-topic: best OpenVPN-Set-up with Qubes 3.2, AirVPN and Turris Omnia router?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 rob_66: >> What do you think would produce the best balance between security >> and speed? >> >> 1. Running AirVPN's client 'Eddie' in sys-netVM. >> >> 2. Putting AirVPN's OpenVPN config into Turris Omnia 2 GB >> router. >> >> 3. Setting up a VPN gateway in Qubes as described in Qubes' >> docs. >> >> Hardware: Asus »Zenbook«, Intel i5-5200U, 2.20 GHz, 12 GB RAM. Chris Laprise: > Best overall approach is to download your service's openvpn config > files and continue with the doc instructions or the slightly > fancier setup here: > > https://github.com/tasket/Qubes-vpn-support > > The one at the link (my own project) configures the link as a > systemd service... gives you more control. The anti-leak measures > are the same. > > I haven't looked at 'Eddie' but usually these proprietary tools > assume you are configuring a traditional PC. OTOH, Qubes proxyVMs > are akin to _routers_ so protection features in Eddie et al might > not work. (Anyway it would go in a proxyVM, not sys-net.) There was > some discussion here I think about Mullvad and that service's > special tool, and ultimately it was better to download the config > files and use the Qubes-specific instructions. > > As for Turris Omnia router setup, it depends on how much you trust > the security of that router -- generally, openvpn is safer in Qubes > than in router hardware (even the 'impressive' ones). Hello again. Even as a medium talented/experienced Qubes and Linux user I managed to run your »slightly fancier« setup successfully in less than an hour, following the instructions slowly, step by step. Speeds are impressive also, > 60 MBit/s (100 MBit max. according to the ISP) – I never reached this with my VPN before, neither with the »impressive« Turris Omnia. AirVPN's 'Eddie' client seems to work fine, too, but I'm not sure if the protection features are working correctly. Maybe more advanced users would get a grip on 'Eddies' numerous settings. Thank you so much, Chris! Best regards, rob -BEGIN PGP SIGNATURE- iQIwBAEBCgAaBQJZKrlRExxyb2JvdGljb0Bwb3N0ZW8uZXMACgkQxPzEC1AWVIXX OQ//UqX2moA7iIYJRC4+JqZotFtV/AyqLg6Iiw4w684y6paQRUTvR9T/NfBNSrv9 H7OrEndjGpMlzklRRlXmHEYnSsZyOHWc0dlPnrqfd/8uuaNDjqCNR2XhrjxSBTrs Szdn4StKqg8McKkAurli6r1mhQNT0hcyC5KU/mnu0tW2f3HNk4giK4Rv9zIQdjbi u8XfWxAlApgbYgMaTFNtUASBCJYVc8SFdTwRy1i+Jl24ga8B/uBmM0mZEXEZ5NOa OpF6PRbs89I8UiQE0PhtsrPuIupX+8BpZpOuNFbpXNc0gKJWIMOMtOYgbNZpouFu 7JlJe+UwuNS6EZbgKLqw7f6eQz0zGf3YMZHbx61TmAYRDzcJiKzwApZ6eHRr9WL5 wYKBTdSDdobC5VxsfDYOXN6HEc2DvRiajBPSpUgPPNDIfh1Qx+Yz308koYCBW5CS o8iRaH76q/bwQByHc/4QfLfAZqwTlgLmV9HsJb7pPe0LhUADh9HUL7Zae/VOygEz puIA97EUqn3GgyXuKANfT6mfMqZPtcQQSvfz/+dRjxMPJP+4xsJ6couYdEtPJCxj q0mTztLotME064ica9aECONRHERqQairezVgsy2wpPkqcSqZbYCMIAy4olkFGw7N 1/DL9B0BvA9j8/BqnMtwaBm6ZoeRJwVTCBAcDH7SYNaO83g= =Y/Xw -END PGP SIGNATURE- -- 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/d991e9f3-9435-8fe7-2853-9b6a97dc786e%40posteo.es. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot start Windows VMs any more
Hi List, from time to time I need my win7, WinXp etc Standalone-VMs. Everything was fine until just now (so maybe after the last dom0-Update) I cannot start any Windows Standalone HVM any more. I get "line: vm.name.thread_monoitor.error_msg), func: start_vm line no.: 1217 file /usr/lib64/python2.7/site-packages/qubesmanager/main.py -- line:self.start_vm(vm) func: action_resumevm_triggered line no.: 1195 file: /usre/lib64/python2.7)site-packages/qubesmanager/main.py " "Icon size: 128x128 domain dead Failed to connect to gui-agent " and "domain dead cannot connect to qrexec agent: No such process " Could anyone give a hint? gs -- 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/20170528172723.4be2a0e6%40posteo.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Min hardware requirement and boot options.
Qubes advise that a minimum storage of 32 GB is required on the USB drive. 1. Can it be installed with a 16 GB USB drive? I am new to Qubes, I have been using Tails for a few months booting in my HP notebook running Ubuntu 17.04 2. Is dual boot of both OS available and recommended for that matter? Thanks, John Sent with [ProtonMail](https://protonmail.com) Secure Email. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/wDni0WVmIQmh2JoC2Ii78yPJZrDeD-zRE0DN7TFFwtcLG790U-bS7y3tCo7x3CDE0YXSkL3FZqCcH-TEJZTvcTCmwKwW8PHvMN4jnWQ-3Hg%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Can't go pasts the grub menu
ok finally succeeded if anyone still has this problem, I booted in legacy mode it then went through all the install and it worked. -- 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/10145e6a-9701-474d-9d5f-9108c8467518%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
Thanks, my wifi in the debian9 template should work now, ill gonna verify it in 2 hours.Is there a particular reason fedora is the default template for sys-net? Wy is the Macchanger method in the documentaion the way you should use to change the maccadress? It looks a lot easyer to me just to update Networkmanager in fedora and use this Methode? also, can someone please tell me whats the terminal Command for locking the screen? i want to make a shortcut with the Windows-button for quickly locking the screen. greetings -- 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/b9b54e21-ca91-4b79-835c-ce3f3b3c1c6d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can "see" but not access secondary storage?
Thanx for that. Strange thing now. I tried looking at it with fdisk as suggested, though xvdi is no longer there? Can't figure out why, anyway, when I go to attach/detach block devices I now see: md126p5 md126 They are both also accessible via fdisk but what is bugging me is that I have these two disks setup via hardware RAID? shouldn't they show up as one disk? Since I don't have any data on these disks I tried partitioning one so now I have this when I print the part table: Disk /dev/md126: 1.8 TiB, 2000381018112 bytes, 3906994176 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x89e5c39e Device Boot StartEndSectors Size Id Type /dev/md126p1 16065 3907024064 3907008000 1.8T f W95 Ext'd (LBA) /dev/md126p5 16128 3907024064 3907007937 1.8T 83 Linux I appologise as this is perhaps getting into non-qubes territory but help would be apprecaited (as the uplimate goal is making this RAID1 setup available to some of my larger appVMs and local backups). Thanks in advance (again!) On Fri, May 19, 2017 at 5:58 PM, Unman wrote: > On Fri, May 19, 2017 at 03:07:40PM -0400, Gaiko Kyofusho wrote: > > On Thu, May 18, 2017 at 3:10 PM, Unman > wrote: > > > > > On Mon, May 15, 2017 at 11:17:57PM -0400, Gaiko Kyofusho wrote: > > > > I managed (with help from qubes-users) to setup secondary storage on > > > > another computer but I am having trouble with my current computer. > > > > > > > > It (they) are two drives setup with hardware raid, I partd/formated > > > (ext4) > > > > them as one raid drive which seemd to go ok. Qubes "sees" it, > actually it > > > > saw both drives for awhile but now only sees one (don't know what I > did > > > > there) but now when I try to attach it, it qubes vm manager shows it > > > > attached but it doesn't seem to be accessible from things like > nautilus? > > > I > > > > assume I just need to partition/setup as lvm/encrupt or something > like > > > that > > > > but am unsure how to go about it correctly? I'd be happy to post some > > > logs > > > > or something but am not sure where to go to get them? > > > > > > When you attach the drive to a qube, open a terminal in the qube and > > > run dmesg. Look at the contents of /dev/ and see what xvd* devices are > > > there. If you have attached the whole drive you would expect to see > > > /dev/xvdi, and associated partitions. > > > > > > You haven't said what template you are using, but it is possible that > > > you will have to manually mount the device/partition. > > > > > > unman > > > > > Thanks for the reply. I am not sure I 100% follow you (noobness). Other > > devices do show up, here is what I got: > > > > [user@personal ~]$ cd /dev/ > > [user@personal dev]$ ls xvd* > > xvda xvdb xvdc xvdc1 xvdc2 xvdd xvdi > > > > Do you mean like xvdi1 xvdi2 etc? > > > > As for template, sorry about that, I have tried both the fedora-24 and > > debian-9 templates (the above is output from a fed appvm) > > > > I generally got mounting partitions but that does lead me to two > questions: > > #1 I assume I need to see more than just xvdi? (like partition numbers > like > > i do for xvdc?) > > #2 would I have to manually mount it on each appvm everytime I want to > use > > it? (perhaps not a huge deal as I eventually want to have it permantly > used > > by 2-3appvms and no others so I assume that would involve some fstab > > tinkering?) > > I dont know if you attached the drive or a partition - if just the > latter then you would only expect to see xvdi - Try mounting that and > see what happens. > Alternatively run fdisk or cfdisk /dev/xvdi and see what is reported. > > You can mount these during qube startup from /rw/config/rc.local or > alternatively use bind-dirs to have a per-qube fstab. (Check the docs on > bind-dirs) > > unman > -- 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/CAGpWZxPm1PUmtW%2B5o5-bD6phNZKE-%2BnBtXGp2%3DQ7E-iw1zDF4g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Can't rename appvm?
Ah oops, I didn't see that. Thank you very much for pointing it out (and adding my post to the issues thread). On Tue, May 23, 2017 at 2:31 AM, Jean-Philippe Ouellet wrote: > On Sun, May 21, 2017 at 4:41 PM, Gaiko > wrote: > > On Friday, May 19, 2017 at 9:35:26 PM UTC-4, cooloutac wrote: > >> On Friday, May 19, 2017 at 2:48:03 PM UTC-4, Gaiko wrote: > >> > I tried to rename my anon-whonix appvm through the qubes-manager, > right click, vm settings, name & label. This worked fine for other appvms > but this time it didn't seem to change the name. Strangely it did change > the private storage to 0mb and now when I try to change the mem to > something else I get: > >> > > >> > > >> > > >> > ERROR: Basic tab: > >> > [Errno 2] No such file or directory: '/var/lib/qubes/appvms/anon- > whonix/private.img' > >> > > >> > > >> > > >> > > >> > Or to change the vm name (which still shows up as "anon-whonix") I > get: > >> > > >> > > >> > > >> > ERROR: Basic tab: > >> > [Errno 2] No such file or directory > >> > > >> > > >> > I looked in /var/lib/qubes/appvms/ and the anon-whonix-renamed dir is > there as I think it should be but the qubes manager doesn't seem to know > this. I tried restarting qubes (simple reboot) and that didn't work. So I > am now not quite sure where to go from here? > >> > > >> > > >> > Thoughts? Thx. > >> I was able to change mine. Pretty strange. Check smartctl in dom0. > do a memory check overnight? > >> > >> If I was your I would just backup any data delete the vm and create a > new one or delete and restore from older. cause its suspect. > > > > Thanks. I ended up deleting it and then making a new one, not ideal > though. In the future how would I have packed it up? Could I have just > copied the private.img to a new anon-whonix appvm and overwritten the old > one? > > Known issue [1], not yet fixed. > > [1]: https://github.com/QubesOS/qubes-issues/issues/2054 > -- 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/CAGpWZxN8XOXDi%2B4xRZEDPPaSZL2G-XzUb3hpYe3pmDSe%3D5tUMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
On 05/28/2017 10:43 AM, Finsh wrote: > Wy is the Macchanger method in the documentaion the way you should use to > change the maccadress? > It looks a lot easyer to me just to update Networkmanager in fedora and use > this Methode? Because the version of NetworkManager that supports randomizing the MAC address properly doesn't appear until Fedora 25. So the other method is the only way to do it on older Fedora templates (and on Debian 8 as well). -- 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/ogf0d5%24vtk%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can "see" but not access secondary storage?
On Friday, May 19, 2017 at 5:59:01 PM UTC-4, Unman wrote: > On Fri, May 19, 2017 at 03:07:40PM -0400, Gaiko Kyofusho wrote: > > On Thu, May 18, 2017 at 3:10 PM, Unman wrote: > > > > > On Mon, May 15, 2017 at 11:17:57PM -0400, Gaiko Kyofusho wrote: > > > > I managed (with help from qubes-users) to setup secondary storage on > > > > another computer but I am having trouble with my current computer. > > > > > > > > It (they) are two drives setup with hardware raid, I partd/formated > > > (ext4) > > > > them as one raid drive which seemd to go ok. Qubes "sees" it, actually > > > > it > > > > saw both drives for awhile but now only sees one (don't know what I did > > > > there) but now when I try to attach it, it qubes vm manager shows it > > > > attached but it doesn't seem to be accessible from things like nautilus? > > > I > > > > assume I just need to partition/setup as lvm/encrupt or something like > > > that > > > > but am unsure how to go about it correctly? I'd be happy to post some > > > logs > > > > or something but am not sure where to go to get them? > > > > > > When you attach the drive to a qube, open a terminal in the qube and > > > run dmesg. Look at the contents of /dev/ and see what xvd* devices are > > > there. If you have attached the whole drive you would expect to see > > > /dev/xvdi, and associated partitions. > > > > > > You haven't said what template you are using, but it is possible that > > > you will have to manually mount the device/partition. > > > > > > unman > > > > > Thanks for the reply. I am not sure I 100% follow you (noobness). Other > > devices do show up, here is what I got: > > > > [user@personal ~]$ cd /dev/ > > [user@personal dev]$ ls xvd* > > xvda xvdb xvdc xvdc1 xvdc2 xvdd xvdi > > > > Do you mean like xvdi1 xvdi2 etc? > > > > As for template, sorry about that, I have tried both the fedora-24 and > > debian-9 templates (the above is output from a fed appvm) > > > > I generally got mounting partitions but that does lead me to two questions: > > #1 I assume I need to see more than just xvdi? (like partition numbers like > > i do for xvdc?) > > #2 would I have to manually mount it on each appvm everytime I want to use > > it? (perhaps not a huge deal as I eventually want to have it permantly used > > by 2-3appvms and no others so I assume that would involve some fstab > > tinkering?) > > I dont know if you attached the drive or a partition - if just the > latter then you would only expect to see xvdi - Try mounting that and > see what happens. > Alternatively run fdisk or cfdisk /dev/xvdi and see what is reported. > > You can mount these during qube startup from /rw/config/rc.local or > alternatively use bind-dirs to have a per-qube fstab. (Check the docs on > bind-dirs) > > unman Thanks for that. I am barely sure what I am doing at the moment but think I am making progress. So as I think you mentioned i think I was looking at or messing with separate partitions so I tried to access the device and start over, that is sudo fdisk /dev/md126 I deleted the two partitions then created a new one and it shows up as md126p1 and automatically with "Linux filesystem" as the type. I thought that I should then format it: sudo mkfs.ext4 /dev/md126p1 but it told me: /dev/md126p1 contains a crypto_LUKS file system How is that? I mean good i guess, except I didn't setup a crypto_LUKS fs or is that default? I tried to access it via a VM and it now shows up in nautilus and asked me for a pw (like an encrypted dev i guess) except... I don't know the pw? I tried a pw, it wasn't right, then the dev disapeared from nautilus, i tried detaching/reattaching it, still didn't show up in nautilus. I am stumped? (though hope I am getting close) -- 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/5ac622ad-cbe2-4b2d-a7d1-948b1be08638%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Maccchanger, debian9 template, Screensave
On 05/28/2017 01:12 PM, Reg Tiangha wrote: On 05/28/2017 10:43 AM, Finsh wrote: Wy is the Macchanger method in the documentaion the way you should use to change the maccadress? It looks a lot easyer to me just to update Networkmanager in fedora and use this Methode? Because the version of NetworkManager that supports randomizing the MAC address properly doesn't appear until Fedora 25. So the other method is the only way to do it on older Fedora templates (and on Debian 8 as well). Since Finsh is already using Debian 9, which has the newer NM, I think that method should be used. The macchanger scripts are unreliable. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/43460633-ba6c-f902-c305-6be784c75dd9%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
thanks, that makes sense. can anybody explain to me how to update the Networkmanager in Fedora-24? dnf --showduplicates list NetworkManager only shows older versions... greetings. -- 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/2efec0f5-7c90-4309-a521-3e75b49bbe78%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
On 05/28/2017 12:19 PM, Finsh wrote: > thanks, that makes sense. can anybody explain to me how to update the > Networkmanager in Fedora-24? > > dnf --showduplicates list NetworkManager only shows older versions... > > > greetings. > Again, the version of Network Manager that properly randomizes MAC addresses doesn't appear until Fedora 25. If you really want to get it on Fedora 24, you'll need to compile it yourself. But depending on what libraries are included in Fedora 24, it might not be possible without upgrading the libraries too (it may or may not be the case, but that is certainly the case with Debian 8). -- 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/ogf6gt%244g9%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
oh ok, thanks.well, that is very unfortunate.so i will have to use the debian-9 template for sys-net. an other question, how do i remove templates ? i tried to remove fedora-23, but it still visible at the applicationsmenu. command: $ sudo yum remove qubes-template-fedora-23 -- 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/8a991bed-5263-4b00-b4fd-fda927337891%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
On 05/28/2017 01:14 PM, Finsh wrote: > oh ok, thanks.well, that is very unfortunate.so i will have to use the > debian-9 template for sys-net. Well, that's not exactly true. You could take that fedora-24 (or fedora-24-minimal) template, clone it, and then upgrade the clone to Fedora 25. [user@dom0 ~]$ qvm-clone fedora-24 fedora-25 [user@dom0 ~]$ truncate -s 5GB /var/tmp/template-upgrade-cache.img [user@dom0 ~]$ qvm-run -a fedora-25 gnome-terminal [user@dom0 ~]$ qvm-block -A fedora-25 dom0:/var/tmp/template-upgrade-cache.img [user@fedora-25 ~]$ sudo mkfs.ext4 /dev/xvdi [user@fedora-25 ~]$ sudo mount /dev/xvdi /mnt/removable [user@fedora-25 ~]$ sudo dnf clean all [user@fedora-25 ~]$ sudo dnf --releasever=25 --setopt=cachedir=/mnt/removable distro-sync (Shut down TemplateVM by any normal means.) [user@dom0 ~]$ rm /var/tmp/template-upgrade-cache.img [user@dom0 ~]$ qvm-trim-template fedora-25 Assuming Network Manager is already installed in that fedora-24 template, it should get upgraded to version 1.4.0 after the whole template gets upgraded to Fedora 25. Be warned that there maybe be some graphical bugs still present with some applications due to the switch to Wayland, which is why I think there's no official Qubes Fedora 25 template even though there's already an official FC25 Qubes repository. But for something as sys-net, it should work fine; I had that running on my laptop for a while before I switched my sys-net to Debian 9. -- 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/ogfa8h%243qd%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
On 05/28/2017 02:00 PM, Reg Tiangha wrote: > On 05/28/2017 01:14 PM, Finsh wrote: >> oh ok, thanks.well, that is very unfortunate.so i will have to use the >> debian-9 template for sys-net. > > Well, that's not exactly true. You could take that fedora-24 (or > fedora-24-minimal) template, clone it, and then upgrade the clone to > Fedora 25. > > [user@dom0 ~]$ qvm-clone fedora-24 fedora-25 > [user@dom0 ~]$ truncate -s 5GB /var/tmp/template-upgrade-cache.img > [user@dom0 ~]$ qvm-run -a fedora-25 gnome-terminal > [user@dom0 ~]$ qvm-block -A fedora-25 > dom0:/var/tmp/template-upgrade-cache.img > [user@fedora-25 ~]$ sudo mkfs.ext4 /dev/xvdi > [user@fedora-25 ~]$ sudo mount /dev/xvdi /mnt/removable > [user@fedora-25 ~]$ sudo dnf clean all > [user@fedora-25 ~]$ sudo dnf --releasever=25 > --setopt=cachedir=/mnt/removable distro-sync > > (Shut down TemplateVM by any normal means.) > > [user@dom0 ~]$ rm /var/tmp/template-upgrade-cache.img > [user@dom0 ~]$ qvm-trim-template fedora-25 > > > Assuming Network Manager is already installed in that fedora-24 > template, it should get upgraded to version 1.4.0 after the whole > template gets upgraded to Fedora 25. Be warned that there maybe be some > graphical bugs still present with some applications due to the switch to > Wayland, which is why I think there's no official Qubes Fedora 25 > template even though there's already an official FC25 Qubes repository. > But for something as sys-net, it should work fine; I had that running on > my laptop for a while before I switched my sys-net to Debian 9. > > Ugh. Word-wrap screwed up the commands. Let me try again: In dom0: [user@dom0 ~]$ qvm-clone fedora-24 fedora-25 [user@dom0 ~]$ truncate -s 5GB /var/tmp/template-upgrade-cache.img [user@dom0 ~]$ qvm-run -a fedora-25 gnome-terminal [user@dom0 ~]$ qvm-block -A fedora-25 dom0:/var/tmp/template-upgrade-cache.img (all one line) Then open a terminal on the fedora-25 template and run: [user@fedora-25 ~]$ sudo mkfs.ext4 /dev/xvdi [user@fedora-25 ~]$ sudo mount /dev/xvdi /mnt/removable [user@fedora-25 ~]$ sudo dnf clean all [user@fedora-25 ~]$ sudo dnf --releasever=25 --setopt=cachedir=/mnt/removable distro-sync (all one line) Shut down TemplateVM by any normal means. Then in dom0: [user@dom0 ~]$ rm /var/tmp/template-upgrade-cache.img [user@dom0 ~]$ qvm-trim-template fedora-25 -- 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/ogfaej%243qd%242%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
thanks, ive already made a fed25 template(not tested so far) I followed the instructiosn on the documentation site, what are the differences to your methode? -- 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/82908830-048d-48da-ba46-b961cb700612%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
On 05/28/2017 02:20 PM, Finsh wrote: > thanks, ive already made a fed25 template(not tested so far) I followed the > instructiosn on the documentation site, what are the differences to your > methode? > If your fedora-25 template already works properly, then there's no difference. I copy/pasted mine from the Qubes website and changed it to work going from fc24 to fc25 instead of fc23 to fc24. -- 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/ogfbu3%246sr%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Maccchanger, debian9 template, Screensave
thanks. anybody about the question how to completly remove templates? its kinda unnerving to still see debian8 , fedora23 etc in the menu... -- 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/e61e3730-306f-44e4-9d9c-d6b2dd5be4f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Accessing Android phone photos
On Fri, 12 May 2017 00:05:42 +0200 "'PR' via qubes-users" wrote: > Hello Alex, > > On 05/11/2017 11:41 PM, Alex wrote: > > /I'm connecting my Android phone over USB to my Qubes 3.2 host > > and... nothing happens. I'm using a Fedora 24 template and a USB > > Qube. I've read the issues on github relating to this but have not > > found a simple set of instructions for accessing my phone's files > > over MTP. What are the steps? / > > I have never attached my Android phone to Qubes before, but tried so > a few minutes ago and could access it without any problems: > > 1) attach phone via USB > > 2) on the phone, switch from "Charging only" to "USB Data tranfser > (MTP)" > > 3) Launch a dom0 Terminal, you should see your phone after entering: > [user@dom0 ~]$ qvm-usb > ... > sys-usb:3-3 04xx:88xx Android_Androidxxx > ... > > 4) mount your phone via sys-usb to your AppVM (I've choosen my > untrusted AppVM in this case): > [user@dom0 ~]$ qvm-usb -a untrusted sys-usb:3-3 > > 5) Open a File Explorer in this AppVM > [user@dom0 ~]$ qvm-run untrusted nautilus > > 6) you should see your phone as an additional device beneath the > Trash-Icon. If not, unmount and remount the phone once: > [user@dom0 ~]$ qvm-usb -d sys-usb:3-3 > [user@dom0 ~]$ qvm-usb -a untrusted sys-usb:3-3 > > > Good luck > > - P > Can attaching an android phone be accomplished without having a usb-vm? When I try the above method substituting my devices and dom0 instead of sys-usb, I get this error: qubes-usb-proxy not installed in the VM qubes-usb-proxy is installed in the destination VM, but I don't have a sys-usb. 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/C0DD71FA-7929-45DD-AA3B-D0271A676690%40mail.bitmessage.ch. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Lenovo T470 - x startup failed
I'm attempting to install on my new T470: i7-7600U Intel HD Graphics 620 500GB HDD Starting the installer, I get this error: X startup failed, falling back to text mode I'm assuming there is some graphics card issue, but I can't find any reports of people working to solve installer problems with the Intel 620. It seems to be just issues after installation. I tried to install in text mode, but I got an error when autoparting the disk (something to do with LUKS key) which seems to be universal and not to have a solution. I took the recommended steps for installing on a Lenovo with UEFI. Any suggestions on the next step for troubleshooting? -- 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/14c385fe-9510-4f41-a042-520390c7eb46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: PFSense
On Wednesday, 24 May 2017 19:15:35 UTC+10, Connor Page wrote: > Drew, as I've said my wifi card is not supported . Perhaps, yours isn't > either. I need to test something that pfsense can talk to. > all I changed in VM config was to do with virtual interfaces. those are > correctly recognised as xn0 and xn1. It is not a wifi card. It's a generic NIC. I have a Realtek and a Broadcom. They both do the same thing. I have not even tried using my TP-Link WiFi card. -- 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/5f6889c0-985d-4fb6-ad09-2c538b09e623%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Lenovo T470 - x startup failed
On Sunday, May 28, 2017 at 9:12:44 PM UTC-4, wordsw...@gmail.com wrote: > I'm attempting to install on my new T470: > > i7-7600U > Intel HD Graphics 620 > 500GB HDD > > Starting the installer, I get this error: > > X startup failed, falling back to text mode > > I'm assuming there is some graphics card issue, but I can't find any reports > of people working to solve installer problems with the Intel 620. It seems to > be just issues after installation. > > I tried to install in text mode, but I got an error when autoparting the disk > (something to do with LUKS key) which seems to be universal and not to have a > solution. > > I took the recommended steps for installing on a Lenovo with UEFI. > > Any suggestions on the next step for troubleshooting? so you mean it installs fine but then doesn't boot into desktop gui? doublecheck bios settings and disable any other gpu. Try to change kernel options from grub to add nomodeset. see if anything diff happens. -- 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/4d5f7290-be23-4081-bec0-f313028a7ff2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Lenovo T470 - x startup failed
On Sunday, May 28, 2017 at 10:41:00 PM UTC-4, cooloutac wrote: > On Sunday, May 28, 2017 at 9:12:44 PM UTC-4, wordsw...@gmail.com wrote: > > I'm attempting to install on my new T470: > > > > i7-7600U > > Intel HD Graphics 620 > > 500GB HDD > > > > Starting the installer, I get this error: > > > > X startup failed, falling back to text mode > > > > I'm assuming there is some graphics card issue, but I can't find any > > reports of people working to solve installer problems with the Intel 620. > > It seems to be just issues after installation. > > > > I tried to install in text mode, but I got an error when autoparting the > > disk (something to do with LUKS key) which seems to be universal and not to > > have a solution. > > > > I took the recommended steps for installing on a Lenovo with UEFI. > > > > Any suggestions on the next step for troubleshooting? > > so you mean it installs fine but then doesn't boot into desktop gui? > > doublecheck bios settings and disable any other gpu. > > Try to change kernel options from grub to add nomodeset. see if anything diff > happens. enable testing repo and install latest kernel. -- 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/c418c52b-03a7-417e-a046-247066b3d92c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Accessing Android phone photos
On Sunday, May 28, 2017 at 5:49:29 PM UTC-4, haw...@bitmessage.ch wrote: > On Fri, 12 May 2017 00:05:42 +0200 > "'PR' via qubes-users" wrote: > > > Hello Alex, > > > > On 05/11/2017 11:41 PM, Alex wrote: > > > /I'm connecting my Android phone over USB to my Qubes 3.2 host > > > and... nothing happens. I'm using a Fedora 24 template and a USB > > > Qube. I've read the issues on github relating to this but have not > > > found a simple set of instructions for accessing my phone's files > > > over MTP. What are the steps? / > > > > I have never attached my Android phone to Qubes before, but tried so > > a few minutes ago and could access it without any problems: > > > > 1) attach phone via USB > > > > 2) on the phone, switch from "Charging only" to "USB Data tranfser > > (MTP)" > > > > 3) Launch a dom0 Terminal, you should see your phone after entering: > > [user@dom0 ~]$ qvm-usb > > ... > > sys-usb:3-3 04xx:88xx Android_Androidxxx > > ... > > > > 4) mount your phone via sys-usb to your AppVM (I've choosen my > > untrusted AppVM in this case): > > [user@dom0 ~]$ qvm-usb -a untrusted sys-usb:3-3 > > > > 5) Open a File Explorer in this AppVM > > [user@dom0 ~]$ qvm-run untrusted nautilus > > > > 6) you should see your phone as an additional device beneath the > > Trash-Icon. If not, unmount and remount the phone once: > > [user@dom0 ~]$ qvm-usb -d sys-usb:3-3 > > [user@dom0 ~]$ qvm-usb -a untrusted sys-usb:3-3 > > > > > > Good luck > > > > - P > > > > > Can attaching an android phone be accomplished without having a usb-vm? > > When I try the above method substituting my devices and dom0 instead > of sys-usb, I get this error: > > qubes-usb-proxy not installed in the VM > > qubes-usb-proxy is installed in the destination VM, but I don't have a > sys-usb. > > Thanks! I don't know I do it the same way as described above. -- 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/677de5f3-93c4-4f06-ad76-37c32995ec68%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Problem with Microphone of the Headset
On Wednesday, May 24, 2017 at 6:44:04 PM UTC-4, Ángel wrote: > Really basic hints, but often those end up being the hardest to realize. > > > > attaching audio input to the VM i'm listening music in does nothing. > > Did you enable audio input for this VM? > (Right-click the VM on qubes-manager and choose "Enable audio input", or > press the mic button on the toolbar.) > > > > if i go to the audio mixer, i can see the mic acting. > > at the configuration is "analog stereo duplex" > > at the recording is "internal audio analog stereo" and it reacts on mic > > action on every VM. > > The audio mixer shows on every VM but, is the recording level at a > suitable for the VM you are recording from? > Note that by default it's at 0% (Silence) > > Hope that helps > > Cheers yes check audio mixer for the vm name, also check alsamixer from a dom0 terminal and unmute everything. -- 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/431d8701-d6d4-495e-88c1-66035fdf822b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: error starting VM : invalid argument: network device with mac 00:16:00:00:00:00 already exists when starting sys-whonix
On Wednesday, May 24, 2017 at 1:35:50 AM UTC-4, yreb-qusw wrote: > I should add this is intermittent, and I detect no loss of function, so > maybe I just close my eyes, and let it go ? just delete them and make new ones. its what great about qubes, you don't have to bother trying to figure it out. lol -- 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/2ed050dd-e1aa-4941-993f-237e47721cdc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Lenovo T470 - x startup failed
On Sunday, May 28, 2017 at 10:41:33 PM UTC-4, cooloutac wrote: > On Sunday, May 28, 2017 at 10:41:00 PM UTC-4, cooloutac wrote: > > On Sunday, May 28, 2017 at 9:12:44 PM UTC-4, wordsw...@gmail.com wrote: > > > I'm attempting to install on my new T470: > > > > > > i7-7600U > > > Intel HD Graphics 620 > > > 500GB HDD > > > > > > Starting the installer, I get this error: > > > > > > X startup failed, falling back to text mode > > > > > > I'm assuming there is some graphics card issue, but I can't find any > > > reports of people working to solve installer problems with the Intel 620. > > > It seems to be just issues after installation. > > > > > > I tried to install in text mode, but I got an error when autoparting the > > > disk (something to do with LUKS key) which seems to be universal and not > > > to have a solution. > > > > > > I took the recommended steps for installing on a Lenovo with UEFI. > > > > > > Any suggestions on the next step for troubleshooting? > > > > so you mean it installs fine but then doesn't boot into desktop gui? > > > > doublecheck bios settings and disable any other gpu. > > > > Try to change kernel options from grub to add nomodeset. see if anything > > diff happens. > > enable testing repo and install latest kernel. No, the problem occurs during install. Are these steps I can take on the installer, or only once install is complete? -- 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/fb5fc09f-60c1-421b-a1ce-420a7fb6467c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Lenovo T470 - x startup failed
On 05/28/2017 08:12 PM, wordswithn...@gmail.com wrote: I'm attempting to install on my new T470: i7-7600U Intel HD Graphics 620 500GB HDD Starting the installer, I get this error: X startup failed, falling back to text mode I'm assuming there is some graphics card issue, but I can't find any reports of people working to solve installer problems with the Intel 620. It seems to be just issues after installation. I tried to install in text mode, but I got an error when autoparting the disk (something to do with LUKS key) which seems to be universal and not to have a solution. I took the recommended steps for installing on a Lenovo with UEFI. Any suggestions on the next step for troubleshooting? https://groups.google.com/forum/#!msg/qubes-users/Eq2zZU5yXEs/qs94AX1uAAAJ -- 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/bfbea86f-36ea-6541-5341-49a1fb822f58%40zoho.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Accessing Android phone photos
The qubes-usb-proxy is needed in both VMs (in this case, you would have to install in dom0). Well, it might work in dom0, but I am not sure if it is the intended usage. What's your reason for not using sys-usb? Do you use some USB device that needs to be connected directly to dom0? Regards, Vít Šesták 'v6ak' -- 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/175b5fdc-b356-4025-a93f-aa667bb21dec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
