Re: [qubes-users] Re: why Whonix and not Tails or the anon-vm?

[qubenix]

john:
> On 05/17/18 06:25, awokd wrote:
>> On Thu, May 17, 2018 3:46 pm,
>> josefh.maier-revL73yDgGBWk0Htik3J/w...@public.gmane.org wrote:
>>> Hello Forum
>>>
>>> why was Whonix and not Tails selected for thes anon-vm of QubesOS?
>>> Thank's for your feedback!
>>
>> Don't know the exact discussion that led up to it, but I imagine it's due
>> to the flexibility Whonix-Gateway provides by permitting anything
>> attached
>> to it to get routed through Tor. It is still possible to run Tails under
>> Qubes, see https://www.qubes-os.org/doc/tails/.
>>
>>
> technically this is a whonix question, I would suggest  posting there :
> 
> https://forums.whonix.org/
> 
> or read their docs a bit 1st, then  patrick and crew  respond to most
> posts .
> 
I believe it started here:
https://blog.invisiblethings.org/2015/06/04/otf-funding-announcement.html.

-- 
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500

-- 
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/b48a06b0-49b0-e468-6c64-62e8564d6d9c%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [Qubes R4.0] USB Mouse Issue | AppVM External Monitor

[Troy]

Setup:
Software -- Qubes R4.0, Debian AppVM
Hardware -- External monitor connected by HDMI to laptop, USB mouse 

Issue:
Mouse works perfectly when application window is on laptop monitor [aligned 
with dom0 mouse pointer]. However, when the application windows is moved to the 
external monitor, the clicks inside the application window are either 
incredibly misaligned from the mouse pointer displayed by dom0 or do not 
register. The bar at the top of the application window [with the color that 
identifies the domain] works correctly in both the external and laptop monitor.

Have tried [but failed to resolve the issue]:
Dom0 terminal: "qvm-start-gui --notify-monitor-layout"
AppVM: xrandr output shows there are two monitors as expected

Has anyone encountered and resolved this issue?


Referenced Issues:
https://github.com/QubesOS/qubes-issues/issues/1599
https://github.com/QubesOS/qubes-issues/issues/3897
https://github.com/QubesOS/qubes-issues/issues/3253

-- 
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/d610bdb4-6cac-430a-94e2-cd37df4d7292%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: U2F on Gmail not working (using Chrome on Personal AppVM)

[Troy]

On Saturday, May 12, 2018 at 8:03:11 AM UTC-4, qube...@gmail.com wrote:
> Hello there, I was wondering if there is a workaround to make this work.
> I have a Yubikey with U2F, which has the dual purpose of being a normal 
> Yubikey as well as being able to do U2F when the webbrowser requests it.
> 
> I am on the latest stable Qubes 4.0.
> This is so far what I have been doing:
> 
> 1) I go to gmail.com and enter my user and password.
> 2) I plug the yubikey to the laptop, sys-usb recognizes it
> 3) I "attach" the usb to "personal" from the sys-usb
> 
> And nothing happens, the yubikey is not blinking, the light stays steadily on.
> It doesn't react in any way by touching on it, it neither generating yubikeys 
> nor the u2f.
> 
> Does anyone have a solution to this?
> Regards

Hello, I was able to successfully log into gmail using google chrome on an 
Debian AppVM on Qubes R4.0

Questions for your own issue:
1. What template are you using for your AppVM?
2. Have you tried to install the qubes-usb-proxy tool on the template for your 
AppVM?
3. Have you tried the command-line qvm-usb attach [VMName] [USB ID]? Did it 
return any errors? You can list the USB IDs by entering "qvm-usb" into dom0 
terminal.

Documentation: https://www.qubes-os.org/doc/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/b55df1b2-df54-490e-9122-aa76a2254f5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Any way to attach a USB drive to a VM by label?

[Qubes Guy]

On Thursday, May 17, 2018 at 8:57:09 PM UTC-4, Qubes Guy wrote:
> I've successfully used qvm-block (in Dom0) to attach USB drives to different 
> VMs (persistently), but I've noticed that Qubes (or Linux) sometimes gives 
> them to different devices over time. In other words, on Monday, my 
> BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to /dev/sdj when 
> I boot up on Wednesday. This is throwing off my VeraCrypt / FreeFileSync 
> backup routine. (Another way of saying this is if I say "qvm-block attach 
> MyVM sys-usb:sda --persistent" when one of the three drives I use for MyVM is 
> currently attached to that, this will fail if Qubes moves that drive to a 
> different device-name (during boot) that isn't one of the three I previously 
> attached (when I go to start up that VM).
> 
> I thought about persistently attaching all 10 of my USB drives to the VM 
> (some HDs, some flash, one SSD - I never use all of them at once - don't 
> ask!) because that would certainly fix this problem, but I get the following 
> error when I try to start the VM: "ERROR: Start failed: XML error: target 
> 'xvdi' duplicated for disk sources '/dev/sdc' and '/dev/sde', see 
> /var/log/libvirt/libxl/libxl-driver.log for details".
> 
> Note that I did all the persistent attachment commands while the VM was not 
> running. If I detach all those, start the VM, do the persistent attachments, 
> shut down the VM and then restart it, I get an error along the lines of 
> "qrexec process failed to respond in 60 seconds".
> 
> So, I guess I'm asking if there's a way to just persistently attach 2 or 3 
> external USB drives and have them consistently available on the same device 
> names when I start the VM so VeraCrypt doesn't balk?  (VeraCrypt ultimately 
> doesn't care what device a drive is attached to (it could be sda - sdj on my 
> system) because it shows the attached drive as "/media/user/BIG_TOSHIBA, but 
> if a drive isn't where it's supposed to be, that'll fail.
> 
> In case you're curious, the error messages in 
> /var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you 
> want me to post it, I can.
> 
> Any help you guys can give me would be greatly appreciated! Thanks...

By the way, I'm running version 4.0 of Qubes on a fairly recent laptop with 8GB 
of 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/592ec7f7-d1c5-4bf6-871a-3863fec8ff0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Any way to attach a USB drive to a VM by label?

[Qubes Guy]

I've successfully used qvm-block (in Dom0) to attach USB drives to different 
VMs (persistently), but I've noticed that Qubes (or Linux) sometimes gives them 
to different devices over time. In other words, on Monday, my BIG_TOSHIBA drive 
will be on /dev/sda, but it'll be assigned to /dev/sdj when I boot up on 
Wednesday. This is throwing off my VeraCrypt / FreeFileSync backup routine. 
(Another way of saying this is if I say "qvm-block attach MyVM sys-usb:sda 
--persistent" when one of the three drives I use for MyVM is currently attached 
to that, this will fail if Qubes moves that drive to a different device-name 
(during boot) that isn't one of the three I previously attached (when I go to 
start up that VM).

I thought about persistently attaching all 10 of my USB drives to the VM (some 
HDs, some flash, one SSD - I never use all of them at once - don't ask!) 
because that would certainly fix this problem, but I get the following error 
when I try to start the VM: "ERROR: Start failed: XML error: target 'xvdi' 
duplicated for disk sources '/dev/sdc' and '/dev/sde', see 
/var/log/libvirt/libxl/libxl-driver.log for details".

Note that I did all the persistent attachment commands while the VM was not 
running. If I detach all those, start the VM, do the persistent attachments, 
shut down the VM and then restart it, I get an error along the lines of "qrexec 
process failed to respond in 60 seconds".

So, I guess I'm asking if there's a way to just persistently attach 2 or 3 
external USB drives and have them consistently available on the same device 
names when I start the VM so VeraCrypt doesn't balk?  (VeraCrypt ultimately 
doesn't care what device a drive is attached to (it could be sda - sdj on my 
system) because it shows the attached drive as "/media/user/BIG_TOSHIBA, but if 
a drive isn't where it's supposed to be, that'll fail.

In case you're curious, the error messages in 
/var/log/libvirt/libxl/libxl-driver.log are meaningless to me, but if you want 
me to post it, I can.

Any help you guys can give me would be greatly appreciated! 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/f0434929-c5e2-446e-8835-045f7203906b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Any way to attach a USB drive to a PVH by label?

[Qubes Guy]

I've successfully used qvm-block (in Dom0) to attach USB drives to different 
VMs (even persistently), but I've noticed that Qubes (or Linux?) sometimes 
gives them to different devices over time. In other words, on Monday, my 
BIG_TOSHIBA drive will be on /dev/sda, but it'll be assigned to /dev/sdj when I 
boot up on Wednesday. This is throwing off my VeraCrypt / FreeFileSync backup 
routine. Is there a way to make this stick?

-- 
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/f09ce2f0-cce3-4099-ad10-09a57bd046eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - System76 Lemur8

[Scott Henry]

(I think this failed sending before, retrying. Pardon if
duplicate)

Everything works that I have tried -- USB keyboard& mouse,
external NFS mount, VPN, additional volumes, others. I can
successfully use VPN in some domains and no VPN in others at
the same time.

In order for networking to work, you need to do the following
steps as early as possible in the install/configure phase. This
laptop model still has the shared bus with the ethernet card.

1. blacklist the driver in both dom0 and sys-net:
1a: echo "blacklist rtsx_pci" | sudo
tee /etc/modprobe.d/blacklist.conf 1b: qvm-prefs -s sys-net
kernelopts "nopat iommu=soft swiotlb=8192
modprobe.blacklist=rtsx_pci" 2. Map the offending port into
sys-net also: 2a: qvm-device attach sys-net dom0:02_00.0

Now my sys-net can use the ethernet and the wifi just fine.

Even though the rtsx device is in sys-net, you still cannot
un-blacklist it.

-- scott henry

-- 
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/20180517144913.1b5dd4e5%40skuld.tenchiki.net.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-System76-Lemur-20180506-195249.cpio.gz
Description: application/gzip


Qubes-HCL-System76-Lemur-20180506-195249.yml
Description: application/yaml

[qubes-users] Putting /boot on a USB thumb drive

['Zeko' via qubes-users]

Hello guys

I'm thinking of ways to multiboot Qubes 4 safely on my laptop. Would it be 
possible to install the /boot partition on a thumb drive while having the / 
encrypted filesystem on an internal drive partition? This should not require 
Anti-Evil Maid, right?

Also if this works, will I have to keep the thumb drive plugged in while Qubes 
is running? It's a little awkward on a laptop.

Thanks for answers

-- 
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/7PxcCKHVpk3XNd8sNsKAneb0zztmSToy0jkyqI5wzLA6ooBLYCc-RNEl60Jwc2vdOd8ooa_rQhUH9JJ-4IAzapy6lXACbPFfrDUxwzMSBc0%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: In new Fed28 template I am getting fedora-27 updates sigh

[john]

On 05/17/18 09:13, john wrote:

In new Fed28 template I am getting fedora-27  updates  sigh

I now have persistent green arrows in Fed26 template and the Fed28 just 
created from the cloned Fed26 , but sadly I am seeing the Fed27 updates 
in what is supposed to be Fed28 ...


Must I go and make a Fed27 template before  going to Fed28 ,  I'm confused,

or which repos  would I check and/or update  to fix this if possible?

ya, disregard, somehow I went to 27 not 28 , maybe that is  why  the 
last trial going from 26-28 "worked" ,  maybe I'll just now clone 27 to 28



but I still don't get why the  Fed26 arrows and ..27 arrows in VM 
manager 4.0  persist 


--
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/005a4f9e-c3b8-8d3a-2362-0f17dd395c25%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] In new Fed28 template I am getting fedora-27 updates sigh

[john]

In new Fed28 template I am getting fedora-27  updates  sigh

I now have persistent green arrows in Fed26 template and the Fed28 just 
created from the cloned Fed26 , but sadly I am seeing the Fed27 updates 
in what is supposed to be Fed28 ...


Must I go and make a Fed27 template before  going to Fed28 ,  I'm confused,

or which repos  would I check and/or update  to fix this if possible?

--
john 

--
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/7ca59ef9-e5dd-a24d-3cd4-3178fd7e2861%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: install fedora 28

[john]

On 05/17/18 06:13, Roy Bernat wrote:

I tries to install fedora 28 by upgrade 26 but at the end i am getting lot of 
errors.

is there any option to download clean fedora-28 / 27 ?

Thanks
Roy


why not try
https://www.qubes-os.org/doc/templates/fedora/
$ sudo qubes-dom0-update qubes-template-fedora-28  see if it works

if not no harm no foul,  I don't think

--
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/27143a75-49c0-9b05-55ab-28d4b67f9af3%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: why Whonix and not Tails or the anon-vm?

[john]

On 05/17/18 06:25, awokd wrote:

On Thu, May 17, 2018 3:46 pm, 
josefh.maier-revL73yDgGBWk0Htik3J/w...@public.gmane.org wrote:

Hello Forum

why was Whonix and not Tails selected for thes anon-vm of QubesOS?
Thank's for your feedback!


Don't know the exact discussion that led up to it, but I imagine it's due
to the flexibility Whonix-Gateway provides by permitting anything attached
to it to get routed through Tor. It is still possible to run Tails under
Qubes, see https://www.qubes-os.org/doc/tails/.



technically this is a whonix question, I would suggest  posting there :

https://forums.whonix.org/

or read their docs a bit 1st, then  patrick and crew  respond to most 
posts .


--
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/500111d0-4a68-fbec-e025-dcca878dd863%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Restore backup in different storage pool

[donoban]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

I want to restore a backed VM in a new pool. I don't see any option on
qvm-backup-restore for specify it.

Is there any way for do it or do I have to restore and then move it?

Regards.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlr9vR0ACgkQFBMQ2OPt
CKVlTBAAvyJH6qtVEeeenW1dA2n1tNkTbKmfDhiyGLT2E514P4RMVfCjnExZdvbq
4emkqD4c/1CdMk3VCdeg88WubT6MWFJ5pCf7rn9og6UAMPPAQZwyy9E1qIuDaoaI
A6dX/BU4dNt2LNtC5L/8tCLTxdmpZS8tgSAUm4fmbEh63UqwQ9tq2KlrM5tONe1C
hQQzEFCA11Ae2/WUfwkh7IZ7zb1UcJwvNrc3sYKE2WNGRyidFU/HUx0+Sqq/qrlu
t3eeAQTUDjjLcZ8e51XgsqEy0RjwgnGrrwAsri8xxtuYtsEdWJ9+8Qwih3MX8FP0
l1W0zI6LyQHT4fKU9z3MdDRhfsKGcIvxxuR+UaJStyQ89r+tanPdRw5qzmkUQuC+
jyx3AqOKiZ9xBF3RQ9whxCgnxKDPFB7asi8v91vEoCjHar2XJNdekXM+IfOc3U8M
e0mbHvh5dR6egywXR9PoQ99jP1ewwssggOdEBgbr4x9StIUczFRmL7Dz0AA7EV6E
C9AJruloTY7XRa6GSjSHCEMo0QjTolrgA93uBCiEsv1xReu1XMUGse+C+KoEYnYI
6Qk0Sw827f706nmLzFrV+vmreXJ2O6XAq1HB/KnjwnLFBhkuksB9PsspHNqpgGe9
9RKsZD+TqoMi33df6tGpaXAE4oDQGYpaRpyDTx5HUW+ximjltsU=
=uQ/q
-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/75549ba6-aadb-59be-e54f-9feb509e0ec7%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Networking freezing and impossible to restore without reboot

[Chris Laprise]

On 05/15/2018 08:01 PM, 'Evastar' via qubes-users wrote:


And 2th question:

Do you know how to restore all connections after proxyvm reboot. Yes, it's not 
possible to reboot it from qubes manager, but I can reboot it with terminal. 
Then, maybe, some simple steps exists to reconnect all AppVMs? This would help 
me a lot. It's my simpler to reboot only proxyVM vs all vms.


The way I'm familiar with involves re-setting the netvm of each 
downstream VM after the proxyVM has rebooted.


One way you could achieve this is with my 'findpref' script in dom0:
https://github.com/tasket/Qubes-scripts

$ findpref -p netvm sys-vpn sys-vpn


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
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/83fd76cc-1714-3b7f-3b7b-62f06116e909%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No boot after dom0 security repo update on may 15

[ponyboy]

>> My machine directly boots into BIOS screen if my Asus Zenbook UX303 after 
>> updating Qubes 4.0 dom0, security repo enabled. I don't remember the error 
>> messages (s.th. with keys).
>> So I boot from rescue USB Stick. Have to choose (3), going directly to 
>> shell. —
>> And here I'm stuck, since many, many hours. No really helpful, _accurate_ 
>> instructions for medium talented users found. ;)
>> How to replace dom0? Or restore boot files?>> I've got a pretty fresh 
>> complete backup on external USB drive, but don't want to install everything 
>> anew.
>
>
>
>
>  I think I'm on the right way.
>
>
>
>
>   1) Booting from USB installer/rescue stick
>
>   2) 'Rescue' mode
>
>   3) Number (1), waiting _patiently_ for decryption
>
>   4) Following
>
>   > https://www.qubes-os.org/doc/uefi-troubleshooting 
> > ,
>
>   section 'Installation finished but “Qubes” boot
>
>   option is missing and xen.cfg is empty'
>
>
>
>
>   Let's see ...
>




 Yay!




  Deleted new kernel entries, changed default in

  xen.cfg to older kernel.




  Uff.

-- 
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/LCj14XH--3-0%40keemail.me.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Networking freezing and impossible to restore without reboot

[Chris Laprise]

On 05/15/2018 07:51 PM, 'Evastar' via qubes-users wrote:




If the vif interfaces are going down, that suggests a bug either in


Today it happens again and now I open terminal at ethervpn and write "route". 
It freeze, not totally freeze, but it print line by line output of this command and every 
line took ~10 seconds to print. Maybe it's because I use imported ethervpn from 3.2. 
backup? Something happens :(


Try adding '-n' option to route so it won't try to look up names for 
each IP address.





tun and tap interfaces look similar in the sense that they're all


I don't know how to check this.


This can only be checked in the ethervpn code. You may wish to report 
the behavior to the ethervpn people.




And other question. You are advanced user and you must know.

I'm trying to use this script to get correct gatewayIP to setup routes.

IP="$(ip addr | grep 'vpn_vpn' -A0 | tail -n1 | awk '{print $2}' | cut -f1 
-d'/')"

(vpn_vpn is "dhclient vpn_vpn" )

"ip addr" print output: 192.168.30.10/24, this command give me 192.168.30.10, 
but I need to find somehow and add to variable 192.168.30.1 then I want to use it with 
this command:
ip route add default via $IP

So sure, I don't know why it's report .10/24 and not .1/24

Maybe you know where/how to get correct IP? My regular setup works with 
hard-coded 192.168.30.1, but I want to parse it on the fly.


Normally I would use 'hostname -I' to find the VM's IP address.



Thanks





--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
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/3e0ad9e2-eecd-2141-2594-8014ba53a03b%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No boot after dom0 security repo update on may 15

[ponyboy]

> My machine directly boots into BIOS screen if my Asus Zenbook UX303 after 
> updating Qubes 4.0 dom0, security repo enabled. I don't remember the error 
> messages (s.th. with keys).
> So I boot from rescue USB Stick. Have to choose (3), going directly to shell. 
> —
> And here I'm stuck, since many, many hours. No really helpful, _accurate_ 
> instructions for medium talented users found. ;)
> How to replace dom0? Or restore boot files?> I've got a pretty fresh complete 
> backup on external USB drive, but don't want to install everything anew.




 I think I'm on the right way.




  1) Booting from USB installer/rescue stick

  2) 'Rescue' mode

  3) Number (1), waiting _patiently_ for decryption

  4) Following

  https://www.qubes-os.org/doc/uefi-troubleshooting 
,

  section 'Installation finished but “Qubes” boot

  option is missing and xen.cfg is empty'




  Let's see ...

-- 
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/LCixRHU--3-0%40keemail.me.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] why Whonix and not Tails or the anon-vm?

[awokd]

On Thu, May 17, 2018 3:46 pm, josefh.ma...@hushmail.com wrote:
> Hello Forum
>
> why was Whonix and not Tails selected for thes anon-vm of QubesOS?
> Thank's for your feedback!

Don't know the exact discussion that led up to it, but I imagine it's due
to the flexibility Whonix-Gateway provides by permitting anything attached
to it to get routed through Tor. It is still possible to run Tails under
Qubes, see https://www.qubes-os.org/doc/tails/.


-- 
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/151b334cb309405dc2e494d3f701d070%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Lenovo G505S Coreboot

[Ivan Ivanov]

These microcodes from platomav are not new enough to have spectre v2
fixed at them! We are in the process of requesting an updated
microcodes from AMD, and there is already some progress: we have been
offered the updated microcodes with spectre V2 fix under the NDA.
However, most likely this NDA requirement is only because of the Ryzen
microcodes and maybe the microcodes for the other CPUs with built-in
PSP Platform Secure Processor. We have asked AMD to offer us a smaller
set of the microcodes (for the older CPUs only) which will be possible
to obtain without signing the NDA, and we are currently waiting for
reply. It does not make sense to ask the NDA for the microcodes of
CPUs that are ~5 years old, also, the older microcodes could be found
as publicly shared at e.g. linux-firmware.git and nobody sent a DMCA
takedown regarding them , so most likely it means that both 15h and
16h microcodes, as well as some other older ones, should be possible
to obtain without any NDAs. We will keep you updated

Best regards,
Ivan Ivanov

2018-05-16 5:50 GMT+03:00 awokd :
> On Sat, May 12, 2018 7:58 pm, matthewwbradl...@gmail.com wrote:
>> On Saturday, May 12, 2018 at 3:38:31 PM UTC-4, mattheww...@gmail.com
>
>>> Does anybody know where I can find an up-to-date copy of the microcode
>>> for this laptop? The latest microcode images I've been able to find
>>> *anywhere* are
>>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd-ucode
>>> which according to the logs date back to 2016 and therefore can't
>>> possibly contain spectre mitigations for an A10-5750M CPU.
>>>
>>> Supposedly AMD has/will release mitigating microcode for family 15h but
>>> I don't think AMD has an equivalent to:
>>> https://downloadcenter.intel.com/download/27776/Linux-Processor-Microcode-Data-File
>>>
>>> Does AMD even announce when they release microcode for a particular
>>> family/CPU? Ideally they'd have a list of CPU->microcode.tar.gz but one
>>> can only dream I guess...
>>>
>>> The next step of course will be figuring out how to build coreboot to
>>> load the microcode image, but, one step at a time.
>>
>> EDIT:
>> https://web.archive.org/web/20160726141516/http://www.amd64.org:80/microcode.html
>> doesn't seem to have been up since 2016
>
> See below. There seems to be a way to do it if you edit the patch file
> directly into microcode_amd_fam15h.bin (but we might be getting off-topic
> for Qubes here).
>
> https://www.mail-archive.com/coreboot@coreboot.org/msg51496.html
>
>
>
>
>
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "qubes-users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/qubes-users/WEppbuqRpfY/unsubscribe.
> To unsubscribe from this group and all its topics, 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/ae712ae15304863b9cb47190d8db7f13%40elude.in.
> 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/CAAaskFBLbjznJZSOmexVGSKFCRMuE1fiHemCbitap9ZEvPEJ_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Insert/Inject keyboard hits to a Qube from Dom0

[799]

Hello Jo

 schrieb am Do., 17. Mai 2018, 15:22:

> Am Donnerstag, 17. Mai 2018 07:28:19 UTC+2 schrieb [ 799 ]:
> > (...)
> > my solution to run more complicated command in an AppVM:
> >
> > 1) "build" a script in dom0
> > 2) qvm-copy the script to the AppVM
> > 3) use qvm-run from dom0 to launch the script
> > 4) remove the script from the AppVM
> >
> > if you need I can look for an example in my script-collection.
>
> Yes please - I would appreciate. That might help me out.
>


An example can be found in my qvm-screenshot-to-clipboard-script.
It takes a screenshot from dom0 and copy it to the clipboard of an appvm

In the script I am setting up a simple "helper file" from dom0 which gets
moved to the AppVM and then executed there.

If you have further questions do not hesitate to contact me.


https://github.com/one7two99/my-qubes/blob/master/home/bin/qvm-screenshot-to-clipboard.sh

- - - 8< - - -

#!/bin/bash
# qvm-screenshot-to-clipboard
# Creates a dom0 screenshot and copy it to the Clipboard of an AppVM

# Define Variables
MyAppVM=$1
MyScreenshot=qvm-screenshot-to-clipboard.png

# Take screenshot in dom0 by selecting an area and adding border+shadow
gnome-screenshot --area --include-border --border-effect=shadow
--file=/tmp/$MyScreenshot

# Copy screenhot to AppVM
qvm-move-to-vm $MyAppVM /tmp/$MyScreenshot

# Create a helper-Script in the AppVM to copy screenshot file to clipboard
echo "xclip -selection clipboard -l 1 -t image/png
/home/user/QubesIncoming/dom0/$MyScreenshot" > /tmp/file2clipboard.sh
chmod +x /tmp/file2clipboard.sh
qvm-move-to-vm $MyAppVM /tmp/file2clipboard.sh

# Send notification for 5sec when Screenshot has been pasted into (!) AppVM
notify-send --urgency low --icon image --expire-time=5000
"qvm-screenshot-to-clipboard" "Screenshot available in $MyAppVM's clipboard"

# Run the helper script in the AppVM
qvm-run $MyAppVM /home/user/QubesIncoming/dom0/file2clipboard.sh

### The last command will remain active until the pasting has been done in
the AppVM

# Send notification for 5sec after Screenshot has been pasted from (!) AppVM
notify-send --urgency low --icon image --expire-time=5000
"qvm-screenshot-to-clipboard" "Screenshot pasted from $MyAppVM's clipboard"

# Remove helper script and screenshot file in AppVM
qvm-run $MyAppVM "rm -f /home/user/QubesIncoming/dom0/file2clipboard.sh
/home/user/QubesIncoming/dom0/$MyScreenshot"
 Desktop version

-- 
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/CAJ3yz2tOj%2BeLoS_4d7fbxA0iOK7rRM6Svt8V1G2XL%3D5JHAjOUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] install fedora 28

[Roy Bernat]

I tries to install fedora 28 by upgrade 26 but at the end i am getting lot of 
errors. 

is there any option to download clean fedora-28 / 27 ?

Thanks 
Roy 

-- 
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/14d5a384-b399-42ae-ae85-42cdb6ac73c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] why Whonix and not Tails or the anon-vm?

[josefh . maier]

Hello Forum

why was Whonix and not Tails selected for thes anon-vm of QubesOS?
Thank's for your feedback!
Joe

-- 
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/20180517154639.5017E60137%40smtp.hushmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Lenovo T480 freezes after resume on suspend

[maurice]

" I needed to remove the assignement of one of the USB controllers from sys-usb 
"
What do you mean by that? Are you unloading a kernel module before suspending 
or the PCI controller? Which module is this?
The sys-usb still freezes on resume, so for the time being I have to manually 
kill and start the vm again.
Which drivers or USB assignments do you remove from your

May 8, 2018 7:51 PM, maur...@disroot.org (mailto:maur...@disroot.org) wrote:
I'm also experiencing the same issue.
Whenever my laptop resumes after have being suspended, the sys-usb is frozen 
and all USB devices attached to it fail to work. I have to kill the appvm and 
start it again. This only affects the sys-usb though, the sys-net is working 
fine during the resume.
The issue that describes this problem - 
https://github.com/QubesOS/qubes-issues/issues/3142  
(https://github.com/QubesOS/qubes-issues/issues/3142) - was closed but the 
problem still persists.

Any idea how can we resolve this?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/70a23c3eec37524a2bfcffd686d44a7b%40disroot.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] sys-usb needs more than default RAM to mount LUKS encrypted backup volume

[awokd]

On Thu, May 17, 2018 12:51 pm, Bernhard wrote:
>
>> You shouldn't mount encrypted drives on sys-usb. Use qvm-block to attach
>> the partition to a different VM, then mount it there.
>>
> This is a good question, I think. Since we distrust sys-usb I agree that
> we should not do the cryptsetup operations in sys-usb. But if you
> distrust the attached device as well (might be safer, right?), one might
> attach the luks-partition (resp. file) first to an intermediate (even
> temp !) VM, luksOpen it in there and re-attach the generated /dev/mapper
> volumes to the destination VM. That way sys-usb is blind to cryptsetup
> and the destination-vm is maximally protected from usb-based attacks.
> Overkill?

I think it's a bit overkill for partition based LUKS volumes, using
qvm-block already gets you protection against usb attacks. File based ones
might benefit from the additional step, but not sure how much.

-- 
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/7c5f55f67ffe69de3b7aa40fe7dd3c9b%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Insert/Inject keyboard hits to a Qube from Dom0

[cr33dc0d3r]

Am Donnerstag, 17. Mai 2018 07:28:19 UTC+2 schrieb [ 799 ]:
> On 05/13 04:40, cr33dc0d3r wrote:
> 
> > what i try to accomplish is a process executed on dom0 that downloads an 
> > data package from the server onto AppVM1 - then forward it over to another 
> > AppVM - then execute (read) it. Currently i have scripted the transfer 
> > between dom1 and 2 and the download from the server with a script inside 
> > dom1. However, i want to try to initiate & control the download from dom0 
> > that the script does not have to be placed in the AppVM.
> > 
> > - it would be ok to enter login data from dom0 (that login information 
> > would be stored on dom0)
> > - in that case i will always connect to the same ftp server
> > - i will always execute the same ftp command differ by data-name:
> >   - like: ftp get /path/to/fileX.txt
> > - would not need to be that flexible - here what i have got for dom1:
> > #--#
> > #!/bin/bash
> > 
> > HOST='x.x.x.x'
> > USER='AppVM1'
> > PASSWD=''
> > 
> > FILE=$1
> > ftp -n -v $HOST < > ascii
> > user $USER $ PASSWD
> > prompt
> > ls
> > lcd /path/to/
> > get $FILE
> > bye
> > EOT
> > #--#
> > 
> > This can be just 'triggered' by dom0 using qvm-run.
> 
> my solution to run more complicated command in an AppVM:
> 
> 1) "build" a script in dom0
> 2) qvm-copy the script to the AppVM
> 3) use qvm-run from dom0 to launch the script
> 4) remove the script from the AppVM
> 
> if you need I can look for an example in my script-collection.

Yes please - I would appreciate. That might help me out.

Thanks,
Jonny
> 
> [799]

-- 
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/cbdfce3b-4ccb-4a60-bb2e-d094df8cf993%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Librem 13v2: Qubes 4.0 stuck at loading the desktop

[platschi]

https://share.riseup.net/#9tAE4-t7G8clcYXQxGQQVA

sys-net not working properly with older kernel though :/

-- 
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/f1d0e2ef-26e0-4c82-b023-027e206a8f73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] sys-usb needs more than default RAM to mount LUKS encrypted backup volume

[Bernhard]

You shouldn't mount encrypted drives on sys-usb. Use qvm-block to attach
the partition to a different VM, then mount it there.

This is a good question, I think. Since we distrust sys-usb I agree that 
we should not do the cryptsetup operations in sys-usb. But if you 
distrust the attached device as well (might be safer, right?), one might 
attach the luks-partition (resp. file) first to an intermediate (even 
temp !) VM, luksOpen it in there and re-attach the generated /dev/mapper 
volumes to the destination VM. That way sys-usb is blind to cryptsetup 
and the destination-vm is maximally protected from usb-based attacks. 
Overkill?


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/205543a3-89e6-5a55-f607-f48a6dd73d35%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Librem 13v2: Qubes 4.0 stuck at loading the desktop

[platschi]

Same issue here. Might have o do with the latest dom0 updates. Getting a kernel 
panic. 

When booting, in grub menu choose "advanced options" and try to boot with an 
older kernel. Then it should boot. 4.14.18-1 works fine here, 4.14.35-1 breaks 
everything.

Screenshot following

-- 
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/2c369bb6-c607-4f10-887c-be4003846561%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4 and Disk Trim

[qubes-os]

awokd:

Thanks for the clarification!

--
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/6b84b4cd-ecad-911b-528a-7c46053e5108%40go-bailey.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Librem 13v2: Qubes 4.0 stuck at loading the desktop

[awokd]

On Thu, May 17, 2018 12:17 pm, Thibaut Demmerlé wrote:
> Hello!
> Until now everything worked with Qubes 4.0 on my Librem 13v2 (with
> coreboot
> updated).
> Now, when I boot I can still enter the encryption password, but when it
> comes to the user password, Qubes don’t load the desktop anymore and go
> back to the user password...

Caps lock is off, right? See if you can switch to terminal at that point
with ctrl-alt-F2. Try the other function keys if that doesn't work. Then,
check log files in /var/log to try to figure out why it won't let you
login.

> I feel desperate because I would really like to see my data again and some
> help to do it...
> Would you be willing to show me what I could enter in “rescue a Qubes
> system”?

Sounds like your data is still intact. It's possible to recover it
manually, but it's an involved process so try to fix your current
installation first.

-- 
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/afce25a6548159228507c4da0e46bba3%40elude.in.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Librem 13v2: Qubes 4.0 stuck at loading the desktop

[Thibaut Demmerlé]

Hello!
Until now everything worked with Qubes 4.0 on my Librem 13v2 (with coreboot
updated).
Now, when I boot I can still enter the encryption password, but when it
comes to the user password, Qubes don’t load the desktop anymore and go
back to the user password...

I feel desperate because I would really like to see my data again and some
help to do it...
Would you be willing to show me what I could enter in “rescue a Qubes
system”?

-- 
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/CAC0kDA1xf_t4jcr8ZEFrRx%2B2LNnKC-zJu4%3DUzV6vzwTT4MePzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4 and Disk Trim

[awokd]

On Wed, May 16, 2018 10:08 pm, qubes...@go-bailey.com wrote:
> For a default install of Qubes 4, is there anything else that needs to
> be done in regards to disk trims/discards for SSDs?
>
> The docs page at:
>
> https://www.qubes-os.org/doc/disk-trim/
>
> mentions setting up a systemd timer or a cron job.
>
> The timer appears to already be set to run by default in Qubes 4.
>
> The section labeled LUKS also mentions that if LUKS is enabled in dom0
> that discards won't get passed down.
>
> Step 5 mentions to run fstrim -av and notes that you should see a /
> followed by the number of bytes trimmed. On a default install, running
> it shows the bytes trimmed which suggests that the command is working.

Yes, that may not be a valid test to indicate discards getting passed down
to the drive. I think it's showing trim is working on the LVM thin volume
for dom0, but to get them passed all the way through you need to edit
lvm.conf and that crypttab option.

> Not sure if the docs aren't quite up-to-date for the defaults for the
> release version of 4.0. So was curious if anything else needed to be
> done for a default install to make sure trimming is working and getting
> passed down the chain.

Not sure how to word it better in the document, please submit a PR if you
have suggestions!

-- 
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/4a5d041cab5814c1bd4f85f53aa2b86f%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Desperately want Qubes, but can't install on Asus Sabertooth x79

[awokd]

On Wed, May 16, 2018 7:35 pm, Mindus Amitiel Debsin wrote:


> So I have a couple questions now as to whether or not I can use Qubes as a
> primary OS:
>
> 1) Is it true that only Windows 7 can be installed as a qube?

I think a couple have managed to get Win10 installed, but 7 is better
supported by the qubes windows tools.

> 2) I have a brand new GTX 1080 TI graphics card on the way: will there be
> any driver support on qubes for this, or will I suffer dramatically
> reduced performance?

To use the card for Qubes, you might have to follow
https://www.qubes-os.org/doc/install-nvidia-driver/.

> 3) Will Steam and it's games work on a Windows 7 qubes VM?

Here you are talking about pass-through. Nvidia cards in general won't
work for this. Haven't seen any recent reports of successfully passing
through a video card to Win7 in Qubes R4.0, but that doesn't mean it's
impossible. Will have a better chance of success with a GTX580 or earlier
AMD video 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/1918d3225595da028fcbe9fc4556126c%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] sys-usb needs more than default RAM to mount LUKS encrypted backup volume

[awokd]

On Thu, May 17, 2018 6:03 am, Alex wrote:
> Hi all,
>
> In migrating multiple systems to Qubes 4.0 I noticed that sys-usb was
> unable to mount the LUKS encrypted hard drive that contained my Qubes
> backup. Looking into the logs I realised the process was getting killed by
> oom-killer, which is invoked when the system has ran out of memory.
>
> Increasing the default allocated memory of sys-usb from 300MB to 500MB
> solved this issue.
>
> @devs: I would recommend fixing this default value out of the box.

You shouldn't mount encrypted drives on sys-usb. Use qvm-block to attach
the partition to a different VM, then mount it there.

-- 
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/959a8721615d9fba77ea9d255e1f6b02%40elude.in.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] sys-usb needs more than default RAM to mount LUKS encrypted backup volume

[Alex]

Hi all,

In migrating multiple systems to Qubes 4.0 I noticed that sys-usb was unable to 
mount the LUKS encrypted hard drive that contained my Qubes backup. Looking 
into the logs I realised the process was getting killed by oom-killer, which is 
invoked when the system has ran out of memory. 

Increasing the default allocated memory of sys-usb from 300MB to 500MB solved 
this issue. 

@devs: I would recommend fixing this default value out of the box.

Many thanks,

Alex 

-- 
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/D479E84C-D41F-45D3-942A-BCAE825E96AD%40gmail.com.
For more options, visit https://groups.google.com/d/optout.