[qubes-users] Global updates question

[Fabrizio Romano Genovese]

Hello all,

I'm trying to write a little script to globally update my qubes templates.
It should work more or less like this:

- It prepares a window layout for i3, so that all the opening terminals from 
the various templates will occupy the right place in a dedicated desktop;
- Then it launches the terminal in every template vm, feeding it a nice 'sudo 
dnf update'
- When the update is finished, one should have the chance to close the vm by 
pressing enter like it happens now on qubes manager.

I already implemented the first point (window layout) but I'm having problems 
at launching the terminals in the right way. I'm basically passing to the vm 
commands like 'xterm -e "sudo dnf update"', but what happens is that the 
terminal opens up, checks for updates and then closes without giving me the 
chance to say y/n. 

As I mentioned above, in qubes manager when one clicks on "update vm" a nice 
terminal window opens up, does everything it has to do and then asks you if you 
want to shutdown the vm or not by pressing enter or control+c, respectively, if 
I remember well.
Since I would really like to have a similar feature in my script, I am 
wondering if qubes-manager calls some script to behave like it does.

If this is the case, I could just call the same script once for every template 
and solve my problems without struggle.

Thanks for your Time,
Fab

-- 
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/bfd89968-9bb5-464c-a091-0f7f2e229ef1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Global updates question

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-02-16 18:20, Fabrizio Romano Genovese wrote:
> Hello all,
> 
> I'm trying to write a little script to globally update my qubes 
> templates. It should work more or less like this:
> 
> - It prepares a window layout for i3, so that all the opening 
> terminals from the various templates will occupy the right place
> in a dedicated desktop; - Then it launches the terminal in every 
> template vm, feeding it a nice 'sudo dnf update' - When the update 
> is finished, one should have the chance to close the vm by
> pressing enter like it happens now on qubes manager.
> 
> I already implemented the first point (window layout) but I'm 
> having problems at launching the terminals in the right way. I'm 
> basically passing to the vm commands like 'xterm -e "sudo dnf 
> update"', but what happens is that the terminal opens up, checks 
> for updates and then closes without giving me the chance to say 
> y/n.
> 
> As I mentioned above, in qubes manager when one clicks on "update 
> vm" a nice terminal window opens up, does everything it has to do 
> and then asks you if you want to shutdown the vm or not by
> pressing enter or control+c, respectively, if I remember well.
> Since I would really like to have a similar feature in my script, I
> am wondering if qubes-manager calls some script to behave like it
> does.
> 
> If this is the case, I could just call the same script once for 
> every template and solve my problems without struggle.
> 
> Thanks for your Time, Fab
> 

Have you considered not starting terminals in the TemplateVMs? By
using --pass-io and not starting the GUI of each TemplateVM, you can
save resources and hassle. Here's an example:

https://gist.github.com/andrewdavidwong/d0b109186de65835255d467ae103c289

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYpmTdAAoJENtN07w5UDAwIhkP/R81vgO979DTCObP/hKE2E5h
0m5ewGt3TH1Ing51Ueiws8PoYdNDyAkPogdXG4cQZX4a4kMzyzEjJ/zzEzddzoDQ
32uFSYzEq7el+eoKyS+OiYiniFlDy4RFAIsjDndkiC+ZPGbfEcvgrrzvm7Ggdcvt
cD+ZGJaoVOuoN6bRRqNkE73VAkSFoIG0LOeaK/keqJwZobQo28UdMYtvsGvONsDR
2vWjDO0jT1K0UEsp0eYuqWDN9B8Ihzw+dYDhSzbKrF3nMGPNXxjcE4edsVdmvL6m
LzCRisoi2k+C+w/AMFjHNjmxTUrx+Gw2/YoytWsXFrCXUIJSr5g/kWyoqVdKVCtx
hwOxVFQQdTDJFUl5vbb+9CvAjc6EXddASslyfXXC3iB1mEAy7ATHvSsMiIup/Lx9
mj2HUk3X6j8uxALo1/+31cqfegEYpuXRtYxRz8sRxFlo9AYDRRNGKgWIn9OJgxl8
6mZ/Cfj2qPDttKvPsYhtvUftiTALzy5g5wZLzQh6SEWCizwkR7dUxeX5k/XMWREg
9d4WgN2zQ3kTN2FtgNFhd37T/O5z4MZoXWMgcwGW3ZgygGNeO9g+t+OqAYypaHQZ
4I0iCIhZTaOC74x0o2yiGd6IKnWLHFXJj+igOKmRve1KE/x0e+EMgahcsKnY0dbM
OmaMAnd1i7oT+ngnDdSJ
=X6k5
-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/bebfe6ed-4e4f-b853-ce30-4e6d576f4de0%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes manager not showing changes, etc.

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Feb 16, 2017 at 03:49:00PM +, qubenix wrote:
> Since the upgrade to version 3.2.8-1.fc23 of qubes manager I've been
> having some issues.
> 
> 1. Changes made to existing VMs or newly created VMs do not show in the
> manager until I restart Qubes. Restarting only the manager does not help.

To really restart manager you need to right click on its icon and choose
"Exit" option, then start it again from menu. Just closing its window
doesn't really restart anything.

> 2. I have very often yellow state indicators while the VM is running.
> `qvm-ls` shows state as "Running" and everything works normal in the VM
> during yellow indicator. Restarting the VM usually fixes this issue.
> I've noticed that this happens more often when I have many VMs starting
> together, but not dependant on each other (to rule out race condition of
> two VMs trying to start same proxy vm for example).
> 
> It seems others were having these issues before the upgrade, and since I
> haven't noticed any complaints. My experience was the opposite. I had no
> issues previous to this upgrade.
> 
> Please let me know any other info/logs that may be helpful.

I guess it's about this issue:
https://github.com/QubesOS/qubes-issues/issues/2637

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYpmYvAAoJENuP0xzK19csKz4IAItiI5kB/cQy+Jjr4EM5c6CN
cXtuyrS/JXTAIyVcagE4pu1RMdWI/rmj+rJASHhj2ippeZt/BWxXjNKyfq645loD
BGtYaGmhYlFl7HZ3m0MT0B2i5JxF+k+UiEeZmPCouKirR8BK6jo92I1trTRjAjyE
u4k+FlaFrn1Fd/9cGyFkoPBufYH8OHqL5cJL+/ms0S23wsPXTjMcnODIGSKHzgAk
Dl12uf4KUFjHx9Pgj5AdNl84pc2XP97zgSLjSyqF18dVsBcqIUREyX8WUAqoSCKP
+/MgrkawtuE+gL9uh1fOeqmNSThDpuCXT4fD+kgtAKdtLs2+q+QE6jZR8DHgSGY=
=HaOk
-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/20170217025542.GE12171%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes not detecting Spidf audio out

[Nautilus Maximus]

On Thursday, 16 February 2017 23:10:25 UTC+10, Grzesiek Chodzicki  wrote:
> W dniu środa, 15 lutego 2017 04:31:54 UTC+1 użytkownik Nautilus Maximus 
> napisał:
> > Hi all,
> > I have qubes up and running, no real issues... well... except one. Qubes 
> > has detected my normal hardware audio out and my HDMI Audio out but it has 
> > not detected my Spidf out. This is a real deal breaker for me as I use an 
> > SMSL headphone amp with only one input "Spidf". My MB is a Ausrock 990 fx 
> > killer. All other linux distro's including fedora, ubuntu, Arch, Gentoo and 
> > puppy Linux can detect it. Is there any way to get this up and running Any 
> > tips and or advice would be appreciated.
> 
> What is the output of sudo lspci -vk|grep -iA 10 audio in dom0 terminal?

Well copying and pasting from dom doesn't work which is good and I don't really 
want to enable it. There was no mention of opticle spidf on the output. It 
mentioned my three hard drives, 770 grapthics card, usb controllers but nothing 
about my Spidf out. Is this a xen issue rather than a dom issue as dom is just 
a VM after all.

-- 
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/37f79457-37f2-4754-8f0a-83eb2b7b9b80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Global updates question

[Fabrizio Romano Genovese]

Well, I have considered it, yes, and it's true that launching many
terminals can be resource intensive. But it's also faster:  Using & I can
launch all the terminals at the same time, while cycling as in the script
you linked I should wait for the previous update process to finish.

Moreover, I confess that staring at the terminals for 5 mins every couple
of days relaxes me, so I like it better :)

Anyway I feel like I'm missing something, what I want to do doesn't look so
difficult and I'm not sure why it doesn't work!

Cheers,
Fab

On Fri, Feb 17, 2017 at 2:50 AM, Andrew David Wong  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2017-02-16 18:20, Fabrizio Romano Genovese wrote:
> > Hello all,
> >
> > I'm trying to write a little script to globally update my qubes
> > templates. It should work more or less like this:
> >
> > - It prepares a window layout for i3, so that all the opening
> > terminals from the various templates will occupy the right place
> > in a dedicated desktop; - Then it launches the terminal in every
> > template vm, feeding it a nice 'sudo dnf update' - When the update
> > is finished, one should have the chance to close the vm by
> > pressing enter like it happens now on qubes manager.
> >
> > I already implemented the first point (window layout) but I'm
> > having problems at launching the terminals in the right way. I'm
> > basically passing to the vm commands like 'xterm -e "sudo dnf
> > update"', but what happens is that the terminal opens up, checks
> > for updates and then closes without giving me the chance to say
> > y/n.
> >
> > As I mentioned above, in qubes manager when one clicks on "update
> > vm" a nice terminal window opens up, does everything it has to do
> > and then asks you if you want to shutdown the vm or not by
> > pressing enter or control+c, respectively, if I remember well.
> > Since I would really like to have a similar feature in my script, I
> > am wondering if qubes-manager calls some script to behave like it
> > does.
> >
> > If this is the case, I could just call the same script once for
> > every template and solve my problems without struggle.
> >
> > Thanks for your Time, Fab
> >
>
> Have you considered not starting terminals in the TemplateVMs? By
> using --pass-io and not starting the GUI of each TemplateVM, you can
> save resources and hassle. Here's an example:
>
> https://gist.github.com/andrewdavidwong/d0b109186de65835255d467ae103c289
>
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCgAGBQJYpmTdAAoJENtN07w5UDAwIhkP/R81vgO979DTCObP/hKE2E5h
> 0m5ewGt3TH1Ing51Ueiws8PoYdNDyAkPogdXG4cQZX4a4kMzyzEjJ/zzEzddzoDQ
> 32uFSYzEq7el+eoKyS+OiYiniFlDy4RFAIsjDndkiC+ZPGbfEcvgrrzvm7Ggdcvt
> cD+ZGJaoVOuoN6bRRqNkE73VAkSFoIG0LOeaK/keqJwZobQo28UdMYtvsGvONsDR
> 2vWjDO0jT1K0UEsp0eYuqWDN9B8Ihzw+dYDhSzbKrF3nMGPNXxjcE4edsVdmvL6m
> LzCRisoi2k+C+w/AMFjHNjmxTUrx+Gw2/YoytWsXFrCXUIJSr5g/kWyoqVdKVCtx
> hwOxVFQQdTDJFUl5vbb+9CvAjc6EXddASslyfXXC3iB1mEAy7ATHvSsMiIup/Lx9
> mj2HUk3X6j8uxALo1/+31cqfegEYpuXRtYxRz8sRxFlo9AYDRRNGKgWIn9OJgxl8
> 6mZ/Cfj2qPDttKvPsYhtvUftiTALzy5g5wZLzQh6SEWCizwkR7dUxeX5k/XMWREg
> 9d4WgN2zQ3kTN2FtgNFhd37T/O5z4MZoXWMgcwGW3ZgygGNeO9g+t+OqAYypaHQZ
> 4I0iCIhZTaOC74x0o2yiGd6IKnWLHFXJj+igOKmRve1KE/x0e+EMgahcsKnY0dbM
> OmaMAnd1i7oT+ngnDdSJ
> =X6k5
> -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/CAAZqLaPzjjwqchAfk3RXMBX6ff5yMdvW8cuKF3abTbEjYd053g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Global updates question

[Jean-Philippe Ouellet]

On Thu, Feb 16, 2017 at 10:51 PM, Fabrizio Romano Genovese
 wrote:
> Well, I have considered it, yes, and it's true that launching many terminals
> can be resource intensive. But it's also faster:  Using & I can launch all
> the terminals at the same time, while cycling as in the script you linked I
> should wait for the previous update process to finish.

Not if you just background the process, like:

for dom in templateA templateB ...; do
qvm-run -p -u root some-template 'dnf update' &
done

Anyway... the code you're looking for is here:
https://github.com/QubesOS/qubes-core-agent-linux/blob/master/qubes-rpc/qubes.InstallUpdatesGUI

-- 
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/CABQWM_DeDSNuuqvNN4NgAmLM21SnpPgmSR%3DccB03z--8R%2Bs1jQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes-Windows-Tools What does it really need?

[Drew White]

Qubes-Windows-Tools, What does it REALLY need to run properly with no stutter 
on the graphics?

I have 2 threads and 2 GB RAM assigned to a Windows Guest with the Qubes Video 
installed, NOT SEAMLESS, and it has major stutters and degradation in 
performance.

If I run with Qubes Video disabled and standard enabled, then it has no stutter 
or degradation in performance in the least, even on higher resolutions.

With 4 threads and 4 GB RAM, there is no improvement when using Qubes Video 
Driver.

This occurs with QWT version 3.2.2.3.
With 3.2.1.3 there was no issue.

This is on my laptop that had everything perfect with 3.2.1.3.
Upgrading to 3.2.2.3 caused it all to go awry.



What does QWT Qubes Video need to work properly?

-- 
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/3ecb2e4c-c832-4f0b-8672-ae38cb7a8b81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes manager not showing changes, etc.

[Jean-Philippe Ouellet]

Not sure if relevant, but I also experienced a case recently where a
just-created VM did not show up. Was resolved by simply killing &
restarting qubes-manager.

Only happened once, so didn't debug.

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

Re: [qubes-users] Fwd: HCL - Dell Latitude E7470

[taii...@gmx.com]

On 02/16/2017 05:55 AM, Elias Mårtenson wrote:


(resend, with attachments this time)

I've been using Qubes 3.2 on this laptop for a month or two now, and pretty
much everything works well.

Note that immediately after installing the system the WLAN didn't work. I
connected using ethernet and did a software update. After this the WLAN
worked correctly.

The laptop seems to have TPM, but when I try to enable it it tells me I
need to switch to UEFI. Unfortunately AEM doesn't support UEFI, so it can't
be used.

I have also been unable to disable tap-to-click on the touchpad. Apparently
this is because the touchpad isn't supported but if you're OK with having
tap-to-click enabled the touchpad itself works well.

Regards,
Elias


There is no technical reason as to why you need UEFI to use a TPM.

You have a business laptop, so you should call dell and insist to speak 
to an engineering team member who can remedy that.
Note: it may be difficult if you don't have the us based pro-support as 
the low wage outsourced techs will have no idea what you mean.


I would also insist on linux touchpad drivers, which again you can do 
(because it is a business laptop)


--
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/edeea219-d928-61f0-7798-788d8cfe22f4%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] can't customize dispvm

[raahelps]

When running qvm-run -a fedora-24-clone-dvm gnome-terminal

I get Domain '-a' doesnt; exist (service qubes.VMShell called by domain 
fedora-24-clone

If I do it without the -a I get Request refused.  Sudo doesn't help.  Any ideas?

-- 
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/91eadaa2-1a95-4b3f-b2de-ae83931512f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: can't customize dispvm

[raahelps]

On Thursday, February 16, 2017 at 11:32:37 PM UTC-5, raah...@gmail.com wrote:
> When running qvm-run -a fedora-24-clone-dvm gnome-terminal
> 
> I get Domain '-a' doesnt; exist (service qubes.VMShell called by domain 
> fedora-24-clone
> 
> If I do it without the -a I get Request refused.  Sudo doesn't help.  Any 
> ideas?

nevermind I'm an idiot was using wrong terminal please delete this thread.

-- 
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/457c45db-5f56-4ab9-b6a7-3bcc27b8fa7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes OS working on Thinkpad X220

[Grzesiek Chodzicki]

W dniu niedziela, 5 lutego 2017 17:40:48 UTC+1 użytkownik ipadr...@gmail.com 
napisał:
> Hi there,
> 
> I failed to boot Qubes from USB drive on a Thinkpad X220 whereas it should 
> work fine.
> I used Rufus (DD Image) to install the ISO on the USB drive, desactivated the 
> UEFI boot.
> Any advice ?

Create the USB drive in ISO mode and not DD mode. Worked for me.

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

[qubes-users] Re: Qubes not detecting Spidf audio out

[Grzesiek Chodzicki]

W dniu środa, 15 lutego 2017 04:31:54 UTC+1 użytkownik Nautilus Maximus napisał:
> Hi all,
> I have qubes up and running, no real issues... well... except one. Qubes has 
> detected my normal hardware audio out and my HDMI Audio out but it has not 
> detected my Spidf out. This is a real deal breaker for me as I use an SMSL 
> headphone amp with only one input "Spidf". My MB is a Ausrock 990 fx killer. 
> All other linux distro's including fedora, ubuntu, Arch, Gentoo and puppy 
> Linux can detect it. Is there any way to get this up and running Any tips and 
> or advice would be appreciated.

What is the output of sudo lspci -vk|grep -iA 10 audio in dom0 terminal?

-- 
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/174b8a84-805f-48c3-ab4e-6f3199043992%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Installation problem

[johan]

Hi, I use gigabyte x99 ultra durable mobo. AMD radeon 480 graphiccard. I have 
installed Qubes om ssd M2 disk and it seemed allright and The graphical wizard 
told me to reboot. It wont start from ssd, no grub. No other OS. Can you help 
me? 

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

[qubes-users] HCL - Dell Latitude E7470

[Elias Mårtenson]

I've been using Qubes 3.2 on this laptop for a month or two now, and pretty
much everything works well.

Note that immediately after installing the system the WLAN didn't work. I
connected using ethernet and did a software update. After this the WLAN
worked correctly.

The laptop seems to have TPM, but when I try to enable it it tells me I
need to switch to UEFI. Unfortunately AEM doesn't support UEFI, so it can't
be used.

I have also been unable to disable tap-to-click on the touchpad. Apparently
this is because the touchpad isn't supported but if you're OK with having
tap-to-click enabled the touchpad itself works well.

Regards,
Elias

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

[qubes-users] Re: Qubes OS working on Thinkpad X220

[Matt P]

On Sunday, February 5, 2017 at 10:40:48 PM UTC+6, ipadr...@gmail.com wrote:
> Hi there,
> 
> I failed to boot Qubes from USB drive on a Thinkpad X220 whereas it should 
> work fine.
> I used Rufus (DD Image) to install the ISO on the USB drive, desactivated the 
> UEFI boot.
> Any advice ?

I recently did an install onto x230. I used a utility (not sure which one) to 
extract the el torito boot image from the cd.

This wasn't the one I used, but it looks like it might do the trick?
https://www.codeproject.com/articles/11210/extracting-the-boot-image-from-a-cd-dvd-el-torito

-- 
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/60408a4d-e18c-4956-ba95-4a35b025a830%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Cuckoo Sandbox

['0xDEADBEEF00' via qubes-users]

Hi every body,

Does some of you already investigate the integration of a cuckoo sandbox with 
qubes for malware analysis?

Best regards,

0xdeadbeef00



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

[qubes-users] Fwd: HCL - Dell Latitude E7470

[Elias Mårtenson]

(resend, with attachments this time)

I've been using Qubes 3.2 on this laptop for a month or two now, and pretty
much everything works well.

Note that immediately after installing the system the WLAN didn't work. I
connected using ethernet and did a software update. After this the WLAN
worked correctly.

The laptop seems to have TPM, but when I try to enable it it tells me I
need to switch to UEFI. Unfortunately AEM doesn't support UEFI, so it can't
be used.

I have also been unable to disable tap-to-click on the touchpad. Apparently
this is because the touchpad isn't supported but if you're OK with having
tap-to-click enabled the touchpad itself works well.

Regards,
Elias

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


Qubes-HCL-Dell_Inc_-Latitude_E7470-20170216-184205.cpio.gz
Description: GNU Zip compressed data


Qubes-HCL-Dell_Inc_-Latitude_E7470-20170216-184205.yml
Description: application/yaml

[qubes-users] HCL - HP ProBook 6360b

[Antonio Misaka]

Hi,

I've been using Qubes OS since version 3.1 and last year I upgraded to 3.2
without any issues.
It's running Windows 8.1 standalone VM
I also tested Mirage firewall (Unikernel) and works fine so far.

Looking forward to see 4.0

Thanks,

Antonio Misaka

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


Qubes-HCL-Hewlett_Packard-HP_ProBook_6360b-20170216-092727.yml
Description: application/yaml

Re: [qubes-users] AEM questions

[jd87]

Thanks for answering, but i still have some questions:


(in any case, i will  use a pass phrase for aem.)

1) is there a difference between using an usb drive or using an
internal partition? (except of having a second device in case of an usb
drive)


Yes. You should keep your AEM boot with you on a separate device. If you
don't, an attacker could see your secret phrase by booting the system.


but isn't this the reason i am using a password for?
the aem data is protected by my aem pw.
after entering it, it is used to decrypt my secret + (somehow) check the
system integrity
if this fails, my aem pw is burned.
in case it succeeds, i enter my luks pw and the system data is encrypted.
at least this is how i understood it.

also if this was the case, why is there the option to leave it on the
internal disk?
from the aem readme
(https://github.com/QubesOS/qubes-antievilmaid/blob/master/anti-evil-maid/README
55-60):

"
You may want to use non-default password for the SRK key (see the
discussion in
the article referenced above), certainly if you want to save the sealed
secrets
to your internal boot partition. In that case you SHOULD NOT pass the '-z'
argument to tpm_takeownership.
"

This suggests it is safe to use an internal boot partition if a password is
passed to `tpm_takeownership`.

So what is the case?


This is also important if you want AEM to warn you after a /remote/
(non-Evil Maid) attack has affected your BIOS.


How does this work?


3) is unhiding my usb devices only required during aem setup? (i guess
so, but i thought, i would ask)


I think you refer to the option that suppresses USB devices during boot.


I refer to this (
https://github.com/QubesOS/qubes-antievilmaid/blob/master/anti-evil-maid/README
110-120)

"
Note: If you choose to use a USB device (e.g., a flash drive) as your AEM
device
and you previously created a USB qube, then you may have to unhide your USB
controller from dom0:

  1. Open the file `/etc/default/grub` in dom0.
  2. Find the line that begins with `GRUB_CMDLINE_LINUX`.
  3. If present, remove `rd.qubes.hide_all_usb` from that line.
  4. Save and close the file.
  5. Run the command `grub2-mkconfig -o /boot/grub2/grub.cfg` in dom0.
  6. Reboot.
"
here you unhide the usbcontroller so it is accessible from dom0.


3) is unhiding my usb devices only required during aem setup? (i guess
so, but i thought, i would ask)


I think you refer to the option that suppresses USB devices during boot.
This should be turned off when booting AEM (not just installing) from a
USB stick so the verification sequence can read the secret from the USB
stick.


This is not mentioned anywhere in the documentation. I think it should.

- Joe


-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/20170216011755.Horde.CWX56sY8PUOKT-USjx2MNA1%40www.vfemail.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes manager not showing changes, etc.

[qubenix]

Since the upgrade to version 3.2.8-1.fc23 of qubes manager I've been
having some issues.

1. Changes made to existing VMs or newly created VMs do not show in the
manager until I restart Qubes. Restarting only the manager does not help.

2. I have very often yellow state indicators while the VM is running.
`qvm-ls` shows state as "Running" and everything works normal in the VM
during yellow indicator. Restarting the VM usually fixes this issue.
I've noticed that this happens more often when I have many VMs starting
together, but not dependant on each other (to rule out race condition of
two VMs trying to start same proxy vm for example).

It seems others were having these issues before the upgrade, and since I
haven't noticed any complaints. My experience was the opposite. I had no
issues previous to this upgrade.

Please let me know any other info/logs that may be helpful.

-- 
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/13162574-5746-58bf-7171-9658834d10b1%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] AEM questions

[Chris Laprise]

On 02/16/2017 02:17 AM, j...@vfemail.net wrote:

Thanks for answering, but i still have some questions:


(in any case, i will  use a pass phrase for aem.)

1) is there a difference between using an usb drive or using an
internal partition? (except of having a second device in case of an usb
drive)


Yes. You should keep your AEM boot with you on a separate device. If you
don't, an attacker could see your secret phrase by booting the system.


but isn't this the reason i am using a password for?
the aem data is protected by my aem pw.
after entering it, it is used to decrypt my secret + (somehow) check the
system integrity
if this fails, my aem pw is burned.
in case it succeeds, i enter my luks pw and the system data is encrypted.
at least this is how i understood it.


Actually, you're right... I didn't see your mention of the passphrase 
earlier. Its good that you're reading the material so carefully!


Even so, there is some risk associated with leaving the boot partition 
on the internal drive. An altered boot partition could prompt for the 
SRK phrase and then send your response over Wifi or other signal. This 
could be made to look like a glitch---computer reboots after prompt, etc.






This is also important if you want AEM to warn you after a /remote/
(non-Evil Maid) attack has affected your BIOS.


How does this work?


Its automatic. Just using AEM gives you 'protection' (i.e. warnings) for 
some remote attacks. Its not comprehensive, but IMO still valuable.





3) is unhiding my usb devices only required during aem setup? (i guess
so, but i thought, i would ask)


I think you refer to the option that suppresses USB devices during boot.


I refer to this (
https://github.com/QubesOS/qubes-antievilmaid/blob/master/anti-evil-maid/README 


110-120)

"
Note: If you choose to use a USB device (e.g., a flash drive) as your AEM
device
and you previously created a USB qube, then you may have to unhide 
your USB

controller from dom0:

  1. Open the file `/etc/default/grub` in dom0.
  2. Find the line that begins with `GRUB_CMDLINE_LINUX`.
  3. If present, remove `rd.qubes.hide_all_usb` from that line.
  4. Save and close the file.
  5. Run the command `grub2-mkconfig -o /boot/grub2/grub.cfg` in dom0.
  6. Reboot.
"
here you unhide the usbcontroller so it is accessible from dom0.


Yes, IIRC the reason to do this is so AEM can read the secret file on 
the USB drive during each boot.





3) is unhiding my usb devices only required during aem setup? (i guess
so, but i thought, i would ask)


I think you refer to the option that suppresses USB devices during boot.
This should be turned off when booting AEM (not just installing) from a
USB stick so the verification sequence can read the secret from the USB
stick.


This is not mentioned anywhere in the documentation. I think it should.


It could use some explanation as to 'why'.

Chris

--
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/ee3b0bb8-b3e2-004e-5b7f-a0bc25705ced%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.