[qubes-users] Re: Installation on NUC6i7KYK

[Ely105]

Actually I was able to get it to work.   After many failed attempts I did use 
UEFI mode to do installation and then I did do those instructions for "no 
bootable device" you show. I didn't try babels instructions.  After I did that 
it booted right up.  And it's been working ok even after an update to dom0, 
even though it said after kernel updates you have to do it again.   I was 
noticing a weird issue where a browser in a given domain would freeze and I 
have to open another browser session to unfreeze it.

But one thing I did notice:  i tried using the minidisplayport connector 
instead of hdmi and it would not boot.  If I switched back to hdmi it was fine. 
 So I think one Bkm is to use HDMI ONLY for qubes.

-m

-- 
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/228d06a5-80db-4e71-9508-8870cb41ea06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[Chris Laprise]

On 04/27/2017 06:48 PM, almir.aljic1...@gmail.com wrote:

On Friday, April 28, 2017 at 12:29:57 AM UTC+2, almir.a...@gmail.com
wrote:

Alright. But I have another question. In the guide you linked, on
step 4, it tells me to add 3 lines to my openvpn-client.ovpn file.
Where do I add these 3 lines in this file? Is it fine if I just put
them at the bottom of the file?


Position in the ovpn file isn't important.

When you re-started the VPN VM, did is display a popup window saying it
connected?




I've done everything according to the guide you sent:

1) I first created the ProxyVM - not standalone - under a Debian
template

2) I did the commands found in step 2 of the Mullvad guide to install
OpenVPN on the ProxyVM


This would have to be installed in the template, not the VPN VM.

My personal preference would be to clone the template and upgrade that
to Debian 9 which already has openvpn 2.4:

https://www.qubes-os.org/doc/template/debian/upgrade-8-to-9/




3) I downloaded an Android configuration file (country: Netherlands)

4) I started following the guide you linked, and did the sudo mkdir
command in the ProxyVM to create a vpn folder in /rw/config/, and
then I moved my Android configuration file into the newly created vpn
folder

5) I then ran this command (step 2 of the qubes-OS link guide): sudo
openvpn --cd /rw/config/vpn --config openvpn-client.ovpn

and the connection seemed to work

6) I then fixed all the scripts, made them executable and then I
restarted the ProxyVM.

7) I changed the configuration of my 'personal' AppVM so that it
routes through the ProxyVM.

Here's the problem, then: when I open Firefox in my 'personal' AppVM,
I simply get a "Problem loading page" when I try to visit any
website, such as www.google.com.

What am I doing wrong?

Sincerely appreciate help!



From the appVM, can you ping a known IP address? Then try to ping a 
domain name.


--

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/c27308f5-135f-4ee1-4af4-c8e0843a433e%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Kernels: Does anyone use Bluetooth in dom0? How about alternative file systems?

[Reg Tiangha]

I have a bit of extra time again, so I've started working on my personal
project to see how far the dom0 kernel can be trimmed down. The trick
will be to find a balance between a super-minimal kernel vs. one that
will run on a variety of hardware configurations out-of-the-box, but
recognizing that there is a near-infinite number of hardware
configurations out there, I'm not stressing over it too much as this,
like the stock kernel configuration, will mostly be a baseline that
people can build up or down to suit their needs (and I would hope that
people do so).

So as I try to figure out what I just cut out that prevents
libvirt-sockets from being created and wait for my next test kernel to
finish compiling, I'm hoping to get more of an idea of what the typical
Qubes user runs in their dom0.

Specifically for right now, does anyone actually use Bluetooth in dom0?
Personally, I'd love to cut support for it out, but if people use
Bluetooth mice and keyboards to administer their Qubes workstations,
then I'll at least keep input driver and platform support to that effect
(if people are offended by Bluetooth, again, they'd be welcome to
compile their own kernel with support for it stripped out later on; the
baseline kernel which could theoretically be shipped on an iso needs to
support a variety of hardware first).

Also, what file systems do people use in dom0? Currently in my test
kernel, I've stripped out support for all file systems except for ext4
and btrfs (plus some pseudo file systems required for the system to work
like tmpfs) since those are the ones I've seen people mention they use
on the list, but if people here are using things like xfs or Reiser, I
can add those back in.

The tricky bit will be driver support, although it might be safe to
remove things such as PCMCIA support, ISDN support, floppy drive
support, Firewire, and some other legacy things. But for now, it's
easier for me to go after the low hanging fruit, which is everything else.

Once I get a good baseline going, I'll let the list know and create a
specific branch on my GitHub account just for the slim variant (I'm
basing this work off of 4.9 since that'll eventually replace 4.4 as the
official Qubes kernel) here:

https://github.com/rtiangha/qubes-linux-kernel

For now, if anyone wants to play with a stock 4.9 configuration, I've
got a branch there you can compile off of, plus have gotten all of the
official stable branches going back to 3.12 up-to-date with upstream
(they're still supported and 3.18 recently saw a couple of new releases
thanks to some Google funding) and even implemented the XSA 157 security
patches that still patch in. I only use 4.9/4.10 though, so if there are
bugs, let me know so I can figure out what to revert.



-- 
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/odu8fj%24e87%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[almir . aljic1998]

On Friday, April 28, 2017 at 12:29:57 AM UTC+2, almir.a...@gmail.com wrote:
> Alright. But I have another question. In the guide you linked, on step 4, it 
> tells me to add 3 lines to my openvpn-client.ovpn file. Where do I add these 
> 3 lines in this file? Is it fine if I just put them at the bottom of the file?

I've done everything according to the guide you sent:

1) I first created the ProxyVM - not standalone - under a Debian template

2) I did the commands found in step 2 of the Mullvad guide to install OpenVPN 
on the ProxyVM

3) I downloaded an Android configuration file (country: Netherlands)

4) I started following the guide you linked, and did the sudo mkdir command in 
the ProxyVM to create a vpn folder in /rw/config/, and then I moved my Android 
configuration file into the newly created vpn folder

5) I then ran this command (step 2 of the qubes-OS link guide): sudo openvpn 
--cd /rw/config/vpn --config openvpn-client.ovpn

and the connection seemed to work

6) I then fixed all the scripts, made them executable and then I restarted the 
ProxyVM.

7) I changed the configuration of my 'personal' AppVM so that it routes through 
the ProxyVM.

Here's the problem, then: when I open Firefox in my 'personal' AppVM, I simply 
get a "Problem loading page" when I try to visit any website, such as 
www.google.com.

What am I doing wrong?

Sincerely appreciate help!

-- 
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/5c01bc80-7d8d-4f2a-91bd-e2b0a4ffea63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[Manuel Amador (Rudd-O)]

On 04/27/2017 01:52 PM, jimmycarter wrote:
> I am following this guide to create a ProxyVM: 
> https://www.mullvad.net/guides/qubes-os-and-mullvad-vpn/
>
> However, when I try to execute the commands in step 2 I am not able to 
> execute the sudo bash command with the error message "permission denied". The 
> sudo apt-get update && install command doesn't work either, with the error 
> message "Are you root?"-kind of thing.
>
> I selected the "do not create root user" or something in the installation, is 
> this what's wrong? How do I get this to work? I also tried going into 
> /etc/default/openvpn according to step 5 and tried editing the openvpn file 
> but it gave me read-only access and not write access.
>
> When I use the sudo command it never prompts me to type in my root user 
> password in the terminal. By the way, I am typing those commands into a 
> terminal on the ProxyVM.
>
> Help is highly appreciated.
>

They should update their guide to use
https://github.com/Rudd-O/qubes-vpn — it works almost out of the box
with Mullvad, and I would be happy to accept contributions or
suggestions of UI and interaction to specifically configure their VPN
with qubes-vpn.

-- 
Rudd-O
http://rudd-o.com/

-- 
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/b7b61224-a945-7cd6-bebd-bd3f177c8fd8%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[almir . aljic1998]

Alright. But I have another question. In the guide you linked, on step 4, it 
tells me to add 3 lines to my openvpn-client.ovpn file. Where do I add these 3 
lines in this file? Is it fine if I just put them at the bottom of the file?

-- 
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/8def0cf0-53cf-4463-9cec-fe1b75a1467c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[Chris Laprise]

On 04/27/2017 05:28 PM, almir.aljic1...@gmail.com wrote:

Okay, I've followed the guide you linked. But on the third and final script, at 
the bottom there is the following line of code:

sg qvpn -c "$VPN_CLIENT $VPN_OPTIONS"

and the guide instructs me to; Change the VPN_CLIENT and VPN_OPTIONS variables 
to match your VPN software.

What is that? What are they referring to? What do I type in instead of 
VPN_Client and instead of VPN_Options?


You don't have to change anything if you're using openvpn. If you used a 
different VPN program, this is where you could adjust the script to use 
it instead.


I will submit changes to the doc to clarify the language.

--

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/dba2de28-a6b8-c061-677f-8ac706b522fa%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[almir . aljic1998]

Okay, I've followed the guide you linked. But on the third and final script, at 
the bottom there is the following line of code:

sg qvpn -c "$VPN_CLIENT $VPN_OPTIONS"

and the guide instructs me to; Change the VPN_CLIENT and VPN_OPTIONS variables 
to match your VPN software.

What is that? What are they referring to? What do I type in instead of 
VPN_Client and instead of VPN_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/9c77bcb1-e2a9-4ccf-a93c-62562d6cb997%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] hate to confirm 'shutdown app-VM'

[Unman]

On Thu, Apr 27, 2017 at 09:33:28AM -0700, Quser wrote:
> Hi!
> any idea in which config-file to set true/false confirmation of shutdown VM's?
> pls help,
> love the qubes - but hate confirm.
> ku
> 

Use 'qvm-shutdown' in dom0, and you skip the prompt.
You can put together a script from a shortcut to kill the front window
if you want.

Otherwise you will have to edit the qubes-manager main.py in dom0 - it's
a python file and you could replace the prompt with a True statement.
There have been some discussions on the list about hacking the
Qubes Manager which you can use as a starting point.

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/20170427180021.GA8023%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[Chris Laprise]

On 04/27/2017 12:26 PM, almir.aljic1...@gmail.com wrote:

Yes, I just used su and did everything listed in the guide (with su I could 
edit files via terminal etc without any problems) but it still does not work. 
The VPN won't work, I did everything according to the guide in the link in my 
first post.

For instance I did everything in the ProxyVM then I configured my personal VM 
to route through the ProxyVM but when I open Firefox and try to enter any 
website on my personal VM it does not connect. I cannot connect to any website.

I have no idea what is wrong. Is that guide faulty by any chance?



That guide wasn't well researched, IMO. A really knowledgeable Qubes 
user would avoid some of the choices they made. For example:



"replace 10.137.4.1 with the IP address of your vif* interface"
 That could easily stop working if you change the netVM, restore from 
backup, etc.


It would be better to follow the Qubes VPN instructions:

https://www.qubes-os.org/doc/vpn/

So you would use the Mullvad (Android) config downloader to get the 
openvpn config file(s), then copy that into /rw/config/vpn in a proxyVM 
(don't use the standalone you created earlier; create a normal proxyVM). 
The idea is to first test the connection using the Mullvad-supplied 
config files, then add the other 3 scripts.


There is a chance Mullvad doesn't supply DNS addresses over DHCP; I say 
this because their instructions have you hard-coding their DNS 
addresses. If that is the case, in Step 4 you can add this additional line:


setenv vpn_dns "10.8.0.1 10.114.0.1"


--

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/f88d7e34-de92-05b6-f96b-a43f3bd7892e%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Installing qubes -hard drive detection problem

[Mystic Buyer]

On Thursday, April 27, 2017 at 11:31:53 AM UTC-4, cooloutac wrote:
> On Thursday, April 27, 2017 at 9:52:15 AM UTC-4, Mystic Buyer wrote:
> > On Thursday, April 27, 2017 at 2:44:57 AM UTC-4, cooloutac wrote:
> > > On Wednesday, April 26, 2017 at 11:43:35 AM UTC-4, Mystic Buyer wrote:
> > > > I am trying to install Qubes on to my xps 15 9560 but having problems 
> > > > with detecting the hard drive on my computer.
> > > > 
> > > > 1. I burned the image as DD on my usb with Rufus
> > > > 2. Turned off secure boot in BIOS
> > > > 3. Booted successfully from the usb
> > > > 4. Proceeded with the installation
> > > > 5. While choosing the installation device there was no device detected.
> > > > 
> > > > Am I missing anything here that I have to do before installation. 
> > > > Really having a hard time solving this issue.
> > > 
> > > what hdd you installing to? how is it attached, shows up in bios?  whats 
> > > your pc specs? what is hdd settings in bios? legacy boot mode?  you dual 
> > > booting?
> > > 
> > > Did you do a integrity check from the qubes menu before installing?  
> > > Check key sigs before burning iso?
> > > 
> > > Maybe try this program instead of rufus: 
> > > https://www.netbsd.org/~martin/rawrite32/
> > > 
> > > even better use dd from a linux machine if possible.
> > 
> > I am trying to install it on my Dell xps 15 9560 - 16GB DDR, 512GB SSD. I 
> > am trying to install it on the SSD on my laptop, its a Toshiba make it is 
> > set to RAID enabled in Bios, booting in UEFI mode. Any pointers on how to 
> > check the integrity of the qubes os. I did the first option to check if 
> > qubes is original before installing but it gave up on me and froze, so I 
> > suppose I'll have to do it by comparing my self. I tried installing on my 
> > Acer Aspire V, which is of much lower architecture with 6GB DDR and lower 
> > specs than xps 15 and it was installed and working good except the touch 
> > pad isn't recognized. I am wondering what is wrong with my xps 15. Any 
> > suggestions? And also pointers on checking the Integrity of Qubes.
> 
> Don't set it to raid if only a single drive try AHCI if installing Qubes only 
> on the drive.  Also try legacy boot mode instead of uefi if your bios have 
> the option.  The installer should verify the files automatically but its one 
> of the options next to install qubes when the usb first boots.  Is that what 
> you mean that it froze?  that shouldn't happen.

Thank you for the quick reply. So I did think about changing from RAID to AHCI, 
but I am not sure how I should go about it safely if anything could go wrong 
with the os.

There is an option for Legacy boot mode but I think since I am able to boot 
into the installer that shouldn't be a problem, or is it?

And yes I did select the verify qubes before the install qubes option, and it 
did for upto 8% and it said it failed and froze on me. 

Just to make sure that the problem was with the internal ssd not being 
recognized I connected via a usb and external HDD and qubes did recognized that 
in the installation destination page. So I really don't know how should I get 
internal disk to be detected for installation.

-- 
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/441d3459-84b9-469a-a967-1345ac27c550%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] hate to confirm 'shutdown app-VM'

[Quser]

Hi!
any idea in which config-file to set true/false confirmation of shutdown VM's?
pls help,
love the qubes - but hate confirm.
ku

-- 
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/e2e47c12-67cd-485b-b9ac-1cfdf91ff0b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[almir . aljic1998]

Yes, I just used su and did everything listed in the guide (with su I could 
edit files via terminal etc without any problems) but it still does not work. 
The VPN won't work, I did everything according to the guide in the link in my 
first post.

For instance I did everything in the ProxyVM then I configured my personal VM 
to route through the ProxyVM but when I open Firefox and try to enter any 
website on my personal VM it does not connect. I cannot connect to any website.

I have no idea what is wrong. Is that guide faulty by any chance?

-- 
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/7ae31e6f-0216-45e6-a1d8-bd8ea4ab682a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Severe Lagging after latest dom0 , seeking backup solution

[Quser]

latest dom0 update broke my system, at least qubes-manager seem broken.
at same time i created new app-vm (fedora23 based) - but not believe the new VM 
shld be reason of break.

-- 
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/5ca8cda3-f47f-4797-9ca3-d37f4e1594c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[Unman]

On Thu, Apr 27, 2017 at 04:41:48PM +0100, Unman wrote:
> On Thu, Apr 27, 2017 at 06:52:44AM -0700, jimmycarter wrote:
> > I am following this guide to create a ProxyVM: 
> > https://www.mullvad.net/guides/qubes-os-and-mullvad-vpn/
> > 
> > However, when I try to execute the commands in step 2 I am not able to 
> > execute the sudo bash command with the error message "permission denied". 
> > The sudo apt-get update && install command doesn't work either, with the 
> > error message "Are you root?"-kind of thing.
> > 
> > I selected the "do not create root user" or something in the installation, 
> > is this what's wrong? How do I get this to work? I also tried going into 
> > /etc/default/openvpn according to step 5 and tried editing the openvpn file 
> > but it gave me read-only access and not write access.
> > 
> > When I use the sudo command it never prompts me to type in my root user 
> > password in the terminal. By the way, I am typing those commands into a 
> > terminal on the ProxyVM.
> > 
> > Help is highly appreciated.
> > 
> I'm not sure what you mean about your choice on installation. If you are
> talking about when you installed Qubes, then the option you selected on
> install does not affect what you are doing in the individual qubes.
> 
> In those qubes you dont need to enter a password to gain root
> privileges.
> Read this explanation of why not:
> www,qubes-os.org/doc/vm-sudo
> 
> Almost all the commands on that page need to be run with root privilege,
> as you realise. 
> Did you use a standard Debian template to create the proxyVM? Thise
> commands work for me.  Exactly what error are you getting with 'sudo'?
> 
> unman

Have you tried just running su to get a root shell, and then using the
documented commands (without sudo)

-- 
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/20170427154636.GB7326%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Cannot execute commands in terminal - not root?

[Unman]

On Thu, Apr 27, 2017 at 06:52:44AM -0700, jimmycarter wrote:
> I am following this guide to create a ProxyVM: 
> https://www.mullvad.net/guides/qubes-os-and-mullvad-vpn/
> 
> However, when I try to execute the commands in step 2 I am not able to 
> execute the sudo bash command with the error message "permission denied". The 
> sudo apt-get update && install command doesn't work either, with the error 
> message "Are you root?"-kind of thing.
> 
> I selected the "do not create root user" or something in the installation, is 
> this what's wrong? How do I get this to work? I also tried going into 
> /etc/default/openvpn according to step 5 and tried editing the openvpn file 
> but it gave me read-only access and not write access.
> 
> When I use the sudo command it never prompts me to type in my root user 
> password in the terminal. By the way, I am typing those commands into a 
> terminal on the ProxyVM.
> 
> Help is highly appreciated.
> 
I'm not sure what you mean about your choice on installation. If you are
talking about when you installed Qubes, then the option you selected on
install does not affect what you are doing in the individual qubes.

In those qubes you dont need to enter a password to gain root
privileges.
Read this explanation of why not:
www,qubes-os.org/doc/vm-sudo

Almost all the commands on that page need to be run with root privilege,
as you realise. 
Did you use a standard Debian template to create the proxyVM? Thise
commands work for me.  Exactly what error are you getting with 'sudo'?

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/20170427154148.GA7326%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: a cumulative post about some issues i'm having with my qubes installation (looking forward for help)

[cooloutac]

On Tuesday, April 25, 2017 at 6:34:22 PM UTC-4, Francesco Rmp wrote:
> Il giorno martedì 25 aprile 2017 17:00:30 UTC+2, cooloutac ha scritto:
> > On Monday, April 24, 2017 at 7:41:46 PM UTC-4, Francesco Rmp wrote:
> > > Il giorno martedì 25 aprile 2017 00:32:51 UTC+2, cooloutac ha scritto:
> > > > On Monday, April 24, 2017 at 3:45:52 PM UTC-4, Chris Laprise wrote:
> > > > > On 04/24/2017 12:20 PM, cooloutac wrote:
> > > > > > linux always lags a few years behind hardware support. looking at 
> > > > > > this https://bugzilla.redhat.com/show_bug.cgi?id=1411830  makes me 
> > > > > > think 1060 not gonna work with nouveau on any kernel right now.
> > > > > >
> > > > > >  another solution would be to try and install the proprietary 
> > > > > > nvidia driver from rpm fusion in dom0 but prop drivers are 
> > > > > > considered insecure.  Not sure it will even work but maybe worth a 
> > > > > > shot.
> > > > > 
> > > > > Somewhere in this thread belongs a diatribe against Nvidia being 
> > > > > FOSS-hostile. But I'll let you all search Youtube for "Torvalds 
> > > > > nvidia" 
> > > > > to see -- graphically -- what I mean. ;)
> > > > > 
> > > > > -- 
> > > > > 
> > > > > Chris Laprise, tas...@openmailbox.org
> > > > > https://twitter.com/ttaskett
> > > > > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
> > > > 
> > > > lmao just watched it.  Personally I never had any problems with nvidia 
> > > > on linux, with either open source or prop drivers.  I've always 
> > > > prefered it over ati.   But then again I would never buy bleeding edge 
> > > > hardware to run linux.
> > > 
> > > Indeedbleeding edge VGAs are not really the best idea for a linux OS in 
> > > general, but with other "mainstream" distributions, i don't have these 
> > > problems, mainly because they are more frequently updated then qubes.
> > > 
> > > I'm not blaming qubes for being conservative, don't misunderstand me, a 
> > > system focusing primarly on security for the end user needs to be 
> > > throughly tested and you can't simply pick up packages and import them 
> > > into the repo without previously making sure that they don't breake the 
> > > security model in any possible way.. also XEN is a b*** when it comes to 
> > > hardware compatibility.. so.. yeah i just hope i'll find a way to solve 
> > > my problem, as said, i'm not looking for high end 3d graphics in qubes at 
> > > all, but at least an even non accelerated decent resolution.. I'd love to 
> > > gain that :)
> > 
> > you would have same issue on mainstream linux apparently man.  Nouveau is 
> > about the kernel version you are using.  Apparently even 4.9 might still 
> > not work correctly for you even on a baremetal fedora system with that 
> > card, as seen by the amount of people complaining on fedora forum threads.  
> > Most people buy cards like that for gpu intensive processing like graphics 
> > design and gaming and use the nvidia proprietary drivers.  There seems to 
> > be no choice,  I guess if you want to use open source drivers,  your nvidia 
> > card has to be at least over two years old to ensure compatibility.
> 
> 
> It'd be fine to install the nvidia proprietary drivers in dom0, but looking 
> at the documentation on the qubes project site, the guidelines are a bit 
> outdated and i cant seem to be able to follow the procedure, do you know any 
> other more updated tutorial that would work on an updated qubes installation?
> 
> what version of fedora is it based on, now?

I believe 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/57460da7-5e98-46c2-8b08-4045302b6f54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Installing qubes -hard drive detection problem

[cooloutac]

On Thursday, April 27, 2017 at 9:52:15 AM UTC-4, Mystic Buyer wrote:
> On Thursday, April 27, 2017 at 2:44:57 AM UTC-4, cooloutac wrote:
> > On Wednesday, April 26, 2017 at 11:43:35 AM UTC-4, Mystic Buyer wrote:
> > > I am trying to install Qubes on to my xps 15 9560 but having problems 
> > > with detecting the hard drive on my computer.
> > > 
> > > 1. I burned the image as DD on my usb with Rufus
> > > 2. Turned off secure boot in BIOS
> > > 3. Booted successfully from the usb
> > > 4. Proceeded with the installation
> > > 5. While choosing the installation device there was no device detected.
> > > 
> > > Am I missing anything here that I have to do before installation. Really 
> > > having a hard time solving this issue.
> > 
> > what hdd you installing to? how is it attached, shows up in bios?  whats 
> > your pc specs? what is hdd settings in bios? legacy boot mode?  you dual 
> > booting?
> > 
> > Did you do a integrity check from the qubes menu before installing?  Check 
> > key sigs before burning iso?
> > 
> > Maybe try this program instead of rufus: 
> > https://www.netbsd.org/~martin/rawrite32/
> > 
> > even better use dd from a linux machine if possible.
> 
> I am trying to install it on my Dell xps 15 9560 - 16GB DDR, 512GB SSD. I am 
> trying to install it on the SSD on my laptop, its a Toshiba make it is set to 
> RAID enabled in Bios, booting in UEFI mode. Any pointers on how to check the 
> integrity of the qubes os. I did the first option to check if qubes is 
> original before installing but it gave up on me and froze, so I suppose I'll 
> have to do it by comparing my self. I tried installing on my Acer Aspire V, 
> which is of much lower architecture with 6GB DDR and lower specs than xps 15 
> and it was installed and working good except the touch pad isn't recognized. 
> I am wondering what is wrong with my xps 15. Any suggestions? And also 
> pointers on checking the Integrity of Qubes.

Don't set it to raid if only a single drive try AHCI if installing Qubes only 
on the drive.  Also try legacy boot mode instead of uefi if your bios have the 
option.  The installer should verify the files automatically but its one of the 
options next to install qubes when the usb first boots.  Is that what you mean 
that it froze?  that shouldn't happen.

-- 
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/ac2aa584-25fb-4859-985f-56adce65cd5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] No Network Connection in Qubes 3.2

[babel]

I have a Kaby Lake Intel Nuc and after a fresh install of Qubes, the kernel is 
not loading the ethernet driver or the wlan driver...

>From within sys-net, I see..

lspci
00:00.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V 
(rev 21)
00:01.0 Network controller: Intel Corporation Device 24fd (rev 78)


[user@sys-net ~]$ lspci -k
00:00.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V 
(rev 21)
Subsystem: Intel Corporation Device 2068
00:01.0 Network controller: Intel Corporation Device 24fd (rev 78)
Subsystem: Intel Corporation Device 9010


No kernel module being loaded there...

Anyone have any advice?  

-- 
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/5440096d-7a5f-44af-90cd-b84f270aea7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Cannot execute commands in terminal - not root?

[jimmycarter]

I am following this guide to create a ProxyVM: 
https://www.mullvad.net/guides/qubes-os-and-mullvad-vpn/

However, when I try to execute the commands in step 2 I am not able to execute 
the sudo bash command with the error message "permission denied". The sudo 
apt-get update && install command doesn't work either, with the error message 
"Are you root?"-kind of thing.

I selected the "do not create root user" or something in the installation, is 
this what's wrong? How do I get this to work? I also tried going into 
/etc/default/openvpn according to step 5 and tried editing the openvpn file but 
it gave me read-only access and not write access.

When I use the sudo command it never prompts me to type in my root user 
password in the terminal. By the way, I am typing those commands into a 
terminal on the ProxyVM.

Help is highly appreciated.

-- 
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/d2ff9a38-dff9-42a4-81d2-5de068f9a900%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Installing qubes -hard drive detection problem

[Mystic Buyer]

On Thursday, April 27, 2017 at 2:44:57 AM UTC-4, cooloutac wrote:
> On Wednesday, April 26, 2017 at 11:43:35 AM UTC-4, Mystic Buyer wrote:
> > I am trying to install Qubes on to my xps 15 9560 but having problems with 
> > detecting the hard drive on my computer.
> > 
> > 1. I burned the image as DD on my usb with Rufus
> > 2. Turned off secure boot in BIOS
> > 3. Booted successfully from the usb
> > 4. Proceeded with the installation
> > 5. While choosing the installation device there was no device detected.
> > 
> > Am I missing anything here that I have to do before installation. Really 
> > having a hard time solving this issue.
> 
> what hdd you installing to? how is it attached, shows up in bios?  whats your 
> pc specs? what is hdd settings in bios? legacy boot mode?  you dual booting?
> 
> Did you do a integrity check from the qubes menu before installing?  Check 
> key sigs before burning iso?
> 
> Maybe try this program instead of rufus: 
> https://www.netbsd.org/~martin/rawrite32/
> 
> even better use dd from a linux machine if possible.

I am trying to install it on my Dell xps 15 9560 - 16GB DDR, 512GB SSD. I am 
trying to install it on the SSD on my laptop, its a Toshiba make it is set to 
RAID enabled in Bios, booting in UEFI mode. Any pointers on how to check the 
integrity of the qubes os. I did the first option to check if qubes is original 
before installing but it gave up on me and froze, so I suppose I'll have to do 
it by comparing my self. I tried installing on my Acer Aspire V, which is of 
much lower architecture with 6GB DDR and lower specs than xps 15 and it was 
installed and working good except the touch pad isn't recognized. I am 
wondering what is wrong with my xps 15. Any suggestions? And also pointers on 
checking the Integrity of Qubes. 

-- 
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/a6eae9b2-405e-4635-87ec-cf0d62f0cb4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Installing windows-tools in template

[Franz]

On Thu, Apr 27, 2017 at 2:26 AM, Reg Tiangha 
wrote:

> On 04/26/2017 05:25 PM, Franz wrote:
> > My win7-x64-template is up, network-connected and even already
> > received and installed security updates. It is also fast enough to be
> > really usable. So many thanks for the hard work.
> >
> > What puzzles me is windows tools installation. I installed it in dom0
> > using testing rep (it did not work for normal rep), but the command
> >
> > qvm-start win7-x64-template --install-windows-tools
> >
> > just starts perfectly the template, but no mention or error or
> > whatever sign of life is made for the windows tools option. So it
> > seems that even after many tries and reboots windows tools is not
> > installed.
> >
> > This impression is confirmed by
> >
> > qvm-prefs win7-x64-template
> >
> > that gives False for both qrexec_installed and  gui_agent_installed.
> >
> > Trying to find a solution in old threads found no answer, but instead
> > found lots of users (the usual permanent crying Drew above all)
> > complaining that windows tools has serious bugs or that reverting to
> > old releases is better. So wonder if it is worth fighting to install
> > windows tools at all.
> >
> > But perhaps windows tools will allow a larger screen? If yes it would
> > be of critical importance to find a way to install windows tools.
> >
> > Any help?
> > Best
> > Fran
> > --
> > 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/CAPzH-qAXPb-
> cnBhQUaCgGJsTaiLTW7v3NcpqnDBhi7BhO3%2Bq%3Dg%40mail.gmail.com
> >  cnBhQUaCgGJsTaiLTW7v3NcpqnDBhi7BhO3%2Bq%3Dg%40mail.gmail.
> com?utm_medium=email&utm_source=footer>.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> When you invoke qvm-start like that, the Windows Tools ISO gets mounted
> in a virtual Windows CD-ROM drive. Access that as you would a normal CD
> in Windows Explorer and then double click on the installer.
>
>
>
Many thanks, now it is working full screen and even faster. Wonderful work
really.
Best
Fran

>
> --
> 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/odrvdn%2447s%241%40blaine.gmane.org.
> 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/CAPzH-qA6DGbS8gyeRehO87bTGJfA%3DnPo%3DY6qQRPVwMjvDOwL_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Installation on NUC6i7KYK

[informationcascade]

Did you ultimately succeed?  

I have also have an Intel NUC 6i7KYK and have gotten Qubes 3.2 installed on 
the M2 SSD.
However, it won't boot.
I'm going to try the helpful instructions from babel, but there are some 
questions.  Here are the files on the USB install drive:
-rwxr-xr-x 1 982K Dec 10  2015 BOOTX64.efi
drwxr-xr-x 2 2.0K Sep 20  2016 fonts
-rw-r--r-- 1 1.1K Sep 20  2016 grub.cfg
-rw--- 1  22M Sep 20  2016 initrd.img
-r--r--r-- 1 1.6K Sep 20  2016 TRANS.TBL
-rw-r--r-- 1 5.7M Jul 18  2016 vmlinuz
-rw-r--r-- 1  586 Sep 20  2016 xen.cfg
-rw-r--r-- 1 2.1M Jul 26  2016 xen.efi

The instructions under Boot Device Not Recognized After Installing say:
Copy /boot/efi/EFI/qubes/ to /boot/efi/EFI/BOOT/.
Rename /boot/efi/EFI/BOOT/xen.efi to /boot/efi/EFI/BOOT/BOOTX64.efi.
Rename /boot/efi/EFI/BOOT/xen.cfg to /boot/efi/EFI/BOOT/BOOTX64.cfg.

However, 
1. There is no qubes directory
2. Do they really mean to *overwrite* the BOOTX64.efi file?

I'm guessing these instructions might have been meant for a previous version of 
Qubes.

Anyway, I can go ahead and try it.  I was just curious how it went for you.
Also, I'm slightly concerned about driver support for the various NUC 
capabilities.

-- 
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/96957cbc-531a-47fc-b5dc-df6bde623a55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Severe Lagging after latest dom0 , seeking backup solution

[Ilpo Järvinen]

On Wed, 26 Apr 2017, Mike ru q fed wrote:

> Update of qubes.foo.* and Xen-4.6.4-26.fc23 x86_64 packages in Dom0 -> slow
> lagging mouse and window behavior  ; luckily  I new qube user and just kept
> reinstalling,  which fixed the behaviour,  I've update debian and fedora and
> whonix now  and all is well,  however,  I'd like to update dom0  but  don't
> trust it, after  specifically updating only the packages labeled  qubes-xxx
> and Xen-xxx   , rebooting and confirming the problem.
>
> I was told on reddit that this is a known issue, however, reviewing the
> newsgroup  I don't see any mention of lag after dom0  updates,  I not expert
> level with linux , but used Debian back in the day , so can handle a certain
> level of tweaking only

Now that you mention, I've also recently seen some GUI lagging I've not 
experienced before. However, also the combination of vms/applications
I'm using while the lag appears is something I've not used before so I 
cannot be sure if it's new or not.

If it is a new issue, I don't think xen has much to do with it since I've 
run 4.6.4 for quite long time already.

And before somebody suggests, this GUI lagging is unrelated to the VM 
freeze issue that is known to be caused by the gui-agent changes (and a 
fixed version of it is already in -testing repo). No freezing occurs,
just slow to draw and somewhat lagging input side.


-- 
 i.

-- 
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/alpine.DEB.2.20.170427100.522%40whs-18.cs.helsinki.fi.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Compromise recovery on Qubes OS

[cooloutac]

On Wednesday, April 26, 2017 at 9:27:11 AM UTC-4, Chris Laprise wrote:
> On 04/26/2017 07:40 AM, Joanna Rutkowska wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hello,
> >
> > Just a FYI that we have recently implemented a so called "Paranoid Mode" 
> > backup
> > recovery for Qubes OS. Arguably this is a new approach to dealing with full
> > system compromises (thanks to Qubes architecture (TM)).
> >
> > The packages for Qubes 3.2 that bring this functionality are currently in 
> > the
> > qubes-dom0-current-testing repository [1]. Note that you need these 
> > packages on
> > a fresh system where you want to restore to, and only there.
> >
> > I also wrote a post [2] explaining the rationale for this, as well as how 
> > it is
> > implemented, and what are still the limitation in 3.2, and how these will 
> > gone
> > in 4.0. The post also touches on AppVM compromise recovery challenges and 
> > how
> > Qubes OS might help here also.
> >
> > Of course I wish we all didn't have to use this feature too often... :/
> >
> > Cheers,
> > joanna.
> >
> > [1] https://github.com/QubesOS/qubes-issues/issues/2737
> > [2] https://www.qubes-os.org/news/2017/04/26/qubes-compromise-recovery/
> 
> 
> Its good to see a detailed exploration of recovery from compromised 
> state. As News items go, its a doozy (quite large)! Maybe the document 
> could be migrated to docs?
> 
> Some initial thoughts about paranoid mode and recovery:
> 
> 1. Its not clear from the news item whether TemplateVMs are restored (I 
> would guess they are not).
> 
> 2. Dom0 files could be restored into a 'quarantine' or 'old' 
> subdirectory. I always wanted restore to do this for dom0 anyway, by 
> default or via an option.
> 
> 3. Good that forensics VM is shown as a thing that's potentially 
> worthwhile. Of course, I half expected the usual warning about 
> corrupted/exploited filesystem.
> 
> 4. A more accurate term for the option would be 'precaution' mode or 
> similar. 'Paranoid' is a loaded word.
> 
> 
> On Prevention:
> 
> Its worth noting the uncertainties that exist in #3 (cleaning scripts) 
> largely apply to #2 (qvm-copy then analyze). This is because 
> clean/protect scripts such as in Qubes-VM-hardening [1] are a natural 
> place to run verification procedures as well -- and I expect to have 
> this implemented in Qubes-VM-hardening by next week. The user will be 
> able to create file lists with SHA hashes, and mismatch will trigger 
> popup and log events. Of course, a manual analysis can utilize a wider 
> array of tools vs what can be used inside of a startup service.
> 
> Also note the prevention issue is not limited to the home directory 
> If an attacker succeeds in privilege escalation, then they can alter 
> /rw/config and other root-owned parts of the private.img volume. In that 
> case, it could be advantageous to have some/most VMs automatically 
> disable or even reset /rw files, assuming those VMs don't need special 
> configuration. Unlike home scripts protection, such a countermeasure is 
> a leveraging of templates' non-persistence.
> 
> Lastly, there is some distinction between whatever apps could 
> (inadvertently) launch malware code /sometime/ in the runtime of the VM, 
> and what apps could launch malware when a VM has just finished booting. 
> In the latter case, an aware user knows the attack surface expands 
> greatly once more apps are run.
> 
> 
> 'Qubes OS vs conventional systems?' ...could have mentioned that Qubes 
> holds out the promise of being able to sanitize at least some data 
> formats after a restore.
> 
> 
> In the FAQ, it seems like AEM could be mentioned as firmware protection. 
> IIUC, AEM should be especially effective against remote attacks (against 
> BIOS/firmware) and I think remote is what most of the document is 
> addressing.
> 
> --
> 
> Chris Laprise, tas...@openmailbox.org
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

Here is what would be awesome for linux 
https://software.intel.com/en-us/forums/intel-trusted-execution-technology-intel-txt/topic/391211
I mean I know how TXT is nothing to brag about but,   This intel employee 
says you need 3 things,  secure boot, trusted boot, and measured boot.  And 
throw some malware detection in there too.

This is why guys like Brad Spengler use windows 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/d62aa5b4-fc23-4588-b93d-25e34a6e7f83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.