[qubes-users] Problem installing KDE in Qubes 4.0.1...

[Andrew Sullivan]

Hello

XFCE isn't my favourite DM so I tried to install KDE.

First, I issued the following command from a dom0 terminal:

sudo qubes-dom0-update @kde-desktop-qubes

After downloading a lot of files (or trying to, it fails with the following 
message:

Errors during downloading metadata for repository 'qubes-dom0-current':
  - Curl error (23): Failed writing received data to disk/application for 
https://mirrors.edge.kernel.org/qubes/repo/yum/r4.0/current/dom0/fc25/repodata/389fc71cd8627e9157ef8d13cbdeb189f0791a09aea9f620736f0c405d8642fc-primary.xml.gz
 
[Failed writing body (401 != 16384)]
  - Curl error (23): Failed writing received data to disk/application for 
https://mirrors.edge.kernel.org/qubes/repo/yum/r4.0/current/dom0/fc25/repodata/5c730001e14b36382c932b29b017f5fbb519aec538fc7017bab03317192743f5-filelists.xml.gz
 
[Failed writing body (4498 != 16384)]
Error: Failed to download metadata for repo 'qubes-dom0-current': Yum repo 
downloading error: Downloading error(s): 
repodata/389fc71cd8627e9157ef8d13cbdeb189f0791a09aea9f620736f0c405d8642fc-primary.xml.gz
 
- Download failed: Curl error (23): Failed writing received data to 
disk/application for 
https://mirrors.edge.kernel.org/qubes/repo/yum/r4.0/current/dom0/fc25/repodata/389fc71cd8627e9157ef8d13cbdeb189f0791a09aea9f620736f0c405d8642fc-primary.xml.gz
 
[Failed writing body (401 != 16384)]; 
repodata/5c730001e14b36382c932b29b017f5fbb519aec538fc7017bab03317192743f5-filelists.xml.gz
 
- Download failed: Curl error (23): Failed writing received data to 
disk/application for 
https://mirrors.edge.kernel.org/qubes/repo/yum/r4.0/current/dom0/fc25/repodata/5c730001e14b36382c932b29b017f5fbb519aec538fc7017bab03317192743f5-filelists.xml.gz
 
[Failed writing body (4498 != 16384)]

I did notice that a lot of the files seem to refer to Fedora 25, while I'm 
using Fedora 30.

I suspect I'm doing something wrong?

Thanks

Andrew

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9e75b966-548d-4b33-a974-43cf9dc6476eo%40googlegroups.com.

[qubes-users] Re: Tiny Window When Opening Libre Documents

[Andrew Sullivan]

On Wednesday, 8 July 2020 22:45:33 UTC+1, Qubes wrote:
>
> Hi 
>
> When I open an office document, it does not really matter which type of 
> office document, say for example a word document, the window that opens 
> is a tiny window. The window is just big enough to display the x at the 
> top right hand corner of a window used to close it. 
>
> With every office document that I open I have to resize the window 
> manually. Has anybody else experienced this, or also experiencing the 
> same right now. Possibly a fix? 
>
> I am on the latest version. 
>

This has been discussed before - search for this topic:

Libreoffice Calc windowsize is 1x1 cm ..

A solution is to use devilspie2. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ac4d6a04-eba2-4817-a683-602fbb1f3814o%40googlegroups.com.

Re: [qubes-users] Re: HCL - Dell Latitude E5470 + Docking Station

[Andrew Sullivan]

Forgot to mention, it's an M.2 SATA SSD and all the drives in the BIOS are 
checked...

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4bd49a21-80eb-4cc2-9f31-98c9585a7e7ao%40googlegroups.com.

Re: [qubes-users] Re: HCL - Dell Latitude E5470 + Docking Station

[Andrew Sullivan]

Hi Rafael

So, I got a Transcend M.2 SSD, 2242 form. Physically fits fine, but it is 
invisible!  Can't see it in W10, Mint or Qubes - neither gparted nor Windows 
Disc Management can see it.

Can you remember exactly what you had to change in the BIOS? For some reason my 
laptop is set up in legacy mode - maybe because it originally had W7 installed; 
not sure if that would make a difference?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ef52f9dc-b8ef-4dab-9b63-9eee77167611o%40googlegroups.com.

Re: [qubes-users] Upgrading to Fedora 32...

[Andrew Sullivan]

On Sunday, 14 June 2020 21:35:46 UTC+1, Sven Semmler wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA512 
>
> On 6/14/20 3:30 PM, Andrew Sullivan wrote: 
> > The Software app in my Fedora template on Qubes 4.0.3 tells me that 
> > Fedora 30 has reached EOL and that I should upgrade to Fedora 32. 
> > Should I go ahead and do this, wait until Qubes "tells me to do 
> > it"??? 
>
> https://www.qubes-os.org/news/2020/04/30/fedora-31-template-available/ 
>
> ;-) 
>
> /Sven 
>
> - -- 
>  public key: https://www.svensemmler.org/0x8F541FB6.asc 
> fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 
> -BEGIN PGP SIGNATURE- 
>
> iQIzBAEBCgAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAl7mihcACgkQ2m4We49U 
> H7ae2A//XVRyOh76jV9dF5jZ3MLdkfwIj4B2cng2Em/kGww10E0pUY5G/+iekGXm 
> hJ4286+OUJ6N85H2QbjroGfLZV0mda22rMOQXiGacNFJdWP5zSbKEZ4wrcRz2GRR 
> HqdO7qggI5UvjNNu9aef/zByCJEkEzG+wqSQnzhUAtFO6755pM8PYqJkHa9NT0vk 
> Nbd4dsyoblJcBhue9ARwT7VfuKZf4w25Iv0aPWhC/myQ7HDOvg/uJTFmy4CXh29g 
> RmDjtkKtcVZyqw+JFxPlUIXEc+Uw2wAmnQUBwgdVl/Hx3FcnsPkHKMk4nDGDEVm4 
> WGGry87M8chmyUxUpZDo46cYUZ6LoALe5H6rURbXgVmXJPtns3+t90aBXug9pZwP 
> IIgpGdnFDmdtsnZq95ybTRDlXojlLJItjxeAbhL1HGsVcg+6g4VlwqBrDx/euePG 
> mgEij8PWwhjSIMBuByjvqwJ7nsYiY8JchMeL/kK6jLjRX9JHI8dM0HSfqak+o999 
> Iy6pCGFSOj2uN0Y13VRY7/swp7Rvdlug/mpUWePGT/mZJUCeXAOorldR+P1iIsE0 
> REIwrMhBcJ705xKnnDwdhXj5J01YpcYg8TojRWq38YbH5QuhYcyaWe2eGFs/bwCj 
> a7AwJxRthpof95e+zfPmk0tkMp/PfJV8s/D00BzKwfPTd6vRUmM= 
> =D7OH 
> -END PGP SIGNATURE- 
>

I'll take that as a "No" then!  If I don't upgrade to Fedora 31 now, will I 
beable to go straight to Fedors 32 when it's available, or can't you "jump" 
a release?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1be62ed5-4540-4274-90ce-d569744266fco%40googlegroups.com.

[qubes-users] Upgrading to Fedora 32...

[Andrew Sullivan]

The Software app in my Fedora template on Qubes 4.0.3 tells me that Fedora 
30 has reached EOL and that I should upgrade to Fedora 32.  Should I go 
ahead and do this, wait until Qubes "tells me to do it"???

Many 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1b0edc91-97cb-4abb-9e13-93d7b1d1309ao%40googlegroups.com.

Re: [qubes-users] Dell Latitude E5470 running Qubes 4.0.3 - no web cam...

[Andrew Sullivan]

On Friday, 12 June 2020 13:06:01 UTC+1, Rafael Reis wrote:
>
> I’ve also started with no sys-usb and a flash drive. Then imaged the usb 
> drive to the internal ssd, and installed sys-usb afterwards. Everything 
> went smoothly. 
> You indeed cannot have sys-usb if you are booting from the usb stick. 
>
> Never tried the webcam to be honest. I find it counterintuitive to use a 
> facecam on a privacy and security oriented os. I’d tape the thing shut. But 
> you should probably try kernel-latest . It is stable on my 5470 and fixed 
> the sd card reader for me, which back then when I first installed was not 
> working. 
>
>
Hi Rafael

I have an M.2 SSD for the WWAN slot on my laptop on order, so the problem 
will be sorted soon.  If indeed it is a problem - you make a valid point 
about using a webcam on a security-focused system.  If I really have to 
(rarely) I could always revert to Windows or Mint.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4d67b967-e1c8-4cf4-9e83-b522c067f39eo%40googlegroups.com.

Re: [qubes-users] Dell Latitude E5470 running Qubes 4.0.3 - no web cam...

[Andrew Sullivan]

On Tuesday, 9 June 2020 13:13:52 UTC+1, haaber wrote:
>
> On 6/9/20 2:07 PM, Andrew Sullivan wrote: 
> > As per the Subject, I have installed 4.0.3 on my Latitude E5470. 
> > Everything seems to work, except the webcam.  If I fire up Cheese, it 
> > just says "No device found". The camera works fine in Windows 10 and 
> > Linux Mint.  Running lsusb in a Dom0 terminal shows the following entry: 
> > 
> > Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. 
> > 
> > So Qubes can sort of see it.  What am I missing? 
>
> You use sys-usb (->make sure it is started, otherwise you don not see 
> usb devices). Since you see your cam, I presume that is OK. 
> Then you only need to attach the webcam to your cheese-running VM !! Use 
> the widget on right top corner of your screen for that. 
>

Well, you were both correct, I am missing sys-usb.  I also now know one way 
to break a Qubes installation!  In the absence of this being installed at 
the start, I attempted to do it manually, as per the Documentation.  The 
qube got created OK, but when I went to open it the whole system froze...  
I did a "hard" powerdown and tried to restart; wasn't asked for a 
passphrase to decrypt the system and eventually I got a lot of 
incomprehensible (to me) messages.  Time for a re-install (not a big deal, 
I'm still learning Qubes rather than using it for real).  I then noticed 
that the option to create sys-usb was greyed out, because I was installing 
to a USB flash drive (and have a wireless USB mouse) so that's one mystery 
solved.  All more-or-less working again, and I have a "proper" SSD on order.

Thanks again for your help.

Andrew

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cb3bdd9f-9004-423e-a518-e86ea564a00co%40googlegroups.com.

[qubes-users] Re: HCL - HP_ZBook_15_G4

[Andrew Sullivan]

On Thursday, 10 May 2018 20:58:50 UTC+1, Tom Marciniak wrote:
>
> Hello Qubes Team,
>
> See attached for .yml file with my hardware information.
>
> I haven't had a chance to test TPM/AEM yet, because I'm having trouble 
> accessing the BIOS after installing Qubes.
>
> I need to verify that TXT and TPM are both enabled there and possibly 
> update the BIOS firmware.
>
> Thanks for all your efforts on this badass platform!
>
> -- 
> Take care,
> Tom Marciniak
>

Hello

I'm no expert, but isn't BIOS usually accessed during POST?   In which 
case, I don't see why having installed Qubes (or any other OS for that 
matter) would affect the ability to access it...

Got this from the HP web site:

Methods to open the BIOS settings depend on the CPU, BIOS version, and 
notebook manufacture date. If the procedure fails and Windows launches, 
shut down the computer and perform the process again.

   - *Notebooks manufactured after mid-2011*: Turn off the computer, press 
   the power button, and then repeatedly press the Esc key until the 
   Startup Menu opens. Press F10 to enter the BIOS Setup Utility.
   - *Notebooks manufactured between 2008 and mid-2011*: If a Compaq or HP 
   splash screen displays after the computer starts, press Escape when 
   prompted to enter the Startup Menu, and then press F10 to enter the BIOS 
   Setup Utility. Some models might support pressing F10 immediately after 
   powering on the notebook to enter the Startup Menu.
   - *Notebooks manufactured in 2007 and earlier*: Turn off the computer, 
   press the power button, and then repeatedly press the F10 key. Normally, 
   the Compaq or HP splash screen displays press F10 to enter the BIOS just 
   before the BIOS menu opens.
   

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1e3575db-a54f-43a6-9a8d-8c83daecf015o%40googlegroups.com.

[qubes-users] Personal VM no longer opens on boot...

[Andrew Sullivan]

 I have installed 4.0.3 on my Latitude E5470.  I altered the settings of 
the personal Domain so that it would start automatically on boot.  It did 
this for a few days then stopped doing so.

Any thoughts?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/930361be-1d39-4a95-8fcf-0fa2abdcbafeo%40googlegroups.com.

[qubes-users] Dell Latitude E5470 running Qubes 4.0.3 - no web cam...

[Andrew Sullivan]

As per the Subject, I have installed 4.0.3 on my Latitude E5470.  
Everything seems to work, except the webcam.  If I fire up Cheese, it just 
says "No device found". The camera works fine in Windows 10 and Linux 
Mint.  Running lsusb in a Dom0 terminal shows the following entry:

Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc.

So Qubes can sort of see it.  What am I missing?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/83231f20-bed6-446c-9f9d-d738e67621c5o%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Monday, 8 June 2020 00:50:58 UTC+1, brend...@gmail.com wrote:
>
> On Sunday, June 7, 2020 at 12:29:28 PM UTC-4, Andrew Sullivan wrote:
> ...
>
> On the fedora-based VMs, the tool `gnome-disks` is a gui way of manually 
> mounting filesystems.
>
> [I tend to forget the order of operations and/or flags for things like 
> mount (which is the mountpoint? which is the source device?) so either 
> script it or use GUI tools when my brain is a bit fuzzy.]
>
> Brendan
>

Brendan - that certainly is an easy way to do it (even if it doesn't 
present the mental challenges of the method described earlier!).  It can be 
made permanent, and it can use the UUID as recommended above.  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1331b7be-77ac-406d-8dcb-62cc2139379co%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Sunday, 7 June 2020 16:28:54 UTC+1, unman wrote:
>
> On Sun, Jun 07, 2020 at 04:04:25AM -0700, Andrew Sullivan wrote: 
> > 
> > 
> > On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote: 
> > > 
> > > On 6/6/20 6:33 PM, Andrew Sullivan wrote: 
> > > > 
> > > > If you use qvm-block in dom0 can you see the 
> disk/partitions? 
> > > > 
> > > > 
> > > >   Don't know, I'll give it a try and post back. 
> > > > 
> > > > 
> > > > OK, if I click on the  Devices widget I can indeed see all the 
> > > > partitions on my internal SSD, with an arrow next to each.  If I 
> click 
> > > > the arrow I get a list of qubes, which I believe allows me to attach 
> the 
> > > > selected partition to where I want.  However, when I do this I can't 
> > > > find the partition in the Files application in the qube.  Think I'm 
> > > > still missing something...  Also, am I correct that this attachment 
> will 
> > > > only persist until I close the qube? 
> > > 
> > > they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ... 
> > > [vd = virtual device, I guess]. The existence of a device does not 
> mean 
> > > mounting it. I do that by hand: in a terminal, type 
> > > 
> > > sudo mount /dev/xvdi /media 
> > > 
> > > will mount the attached device to /media and allow file access. If it 
> is 
> > > a luks-encrypted system, do 
> > > 
> > > sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL 
> > > sudo mount  /dev/mapper/MYSSDVOL/media 
> > > 
> > > cheers 
> > > 
> > 
> > Many thanks for that, works exactly as described!  Seems a bit strange 
> that 
> > the partition isn't mounted at the time it was attached (not sure why 
> you'd 
> > want to attach it if you didn't plan to read or write to it?).   
> Anyways... 
>
> You may want to read/write *without* mounting - for example, when using 
> dd to write a disk image. 
>
> > 
> > Is there any way the attachment and mounting can be made permanent? 
> > 
>
> `man` is your friend - specifically `man qvm-block`. 
> You will see that there is indeed a `--persistent` option. 
>
> Mounting could be a simple (and standard) entry in /etc/fstab - nothing 
> Qubes 
> specific here. Or simply a call to `mount`. 
> Make sure that you use a good identifier - /dev/xvdi may or may not work 
> - a label or UUID would be much better. 
> Again `man fstab` and `man mount` will help. 
>
> The Qubes specific part will be to make sure that any changes you  make 
> to /etc/fstab are persistent - you could do this using bind-dirs or by 
> an entry in /rw/config/rc.local 
>
>
>
>
> > Next challenge - access files on another Linux laptop on the same 
> network! 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/da8f0bd7-8736-4e32-b64c-9721ab8fabaco%40googlegroups.com.
>  
>
>

Thanks, that's very helpful, I'll give it a try. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bb4154fe-0d93-440c-bca5-49752b2e8214o%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Sunday, 7 June 2020 15:25:02 UTC+1, haaber wrote:
>
> On 6/7/20 1:04 PM, Andrew Sullivan wrote: 
> > 
> > 
> > On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote: 
> > 
> > they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ... 
> > [vd = virtual device, I guess]. The existence of a device does not 
> mean 
> > mounting it. I do that by hand: in a terminal, type 
> > 
> >  sudo mount /dev/xvdi /media 
> > 
> > will mount the attached device to /media and allow file access. If 
> > it is 
> > a luks-encrypted system, do 
> > 
> >  sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL 
> >  sudo mount  /dev/mapper/MYSSDVOL/media 
> > 
> >  cheers 
> > 
> > 
> > Many thanks for that, works exactly as described!  Seems a bit strange 
> > that the partition isn't mounted at the time it was attached (not sure 
> > why you'd want to attach it if you didn't plan to read or write to 
> > it?).   Anyways... 
>
> like any device that lurks in your machine(say a WIN partition. Unless 
> you ask for mounting in fstab it won't be done. 
>
> > Is there any way the attachment and mounting can be made permanent? 
> no clue. never tried that. 
>
> > Next challenge - access files on another Linux laptop on the same 
> network! 
>
> use scp to copy individual files  and use 
>
> rsync -auv --rsh=ssh user@anotherlinuxmachine:path/  new-qubes-path/ 
>
> is your friend to mass-copy data. 
>

Thanks for that - useful to know but not exactly what I need right now.  I 
want to be able to access a folder on another Linux laptop on the same 
network (like I can access another disk in the same laptop).  I currently 
do this (in Linux Mint) using Samba.  I'll give that a try in Qubes and if 
I get problems I probably ought to start a new  thread (I got into trouble 
before when I raised a new topic in a 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/89ec1490-5409-4b56-954c-17a370fe3b06o%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote:
>
> On 6/6/20 6:33 PM, Andrew Sullivan wrote: 
> > 
> > If you use qvm-block in dom0 can you see the disk/partitions? 
> > 
> > 
> >   Don't know, I'll give it a try and post back. 
> > 
> > 
> > OK, if I click on the  Devices widget I can indeed see all the 
> > partitions on my internal SSD, with an arrow next to each.  If I click 
> > the arrow I get a list of qubes, which I believe allows me to attach the 
> > selected partition to where I want.  However, when I do this I can't 
> > find the partition in the Files application in the qube.  Think I'm 
> > still missing something...  Also, am I correct that this attachment will 
> > only persist until I close the qube? 
>
> they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ... 
> [vd = virtual device, I guess]. The existence of a device does not mean 
> mounting it. I do that by hand: in a terminal, type 
>
> sudo mount /dev/xvdi /media 
>
> will mount the attached device to /media and allow file access. If it is 
> a luks-encrypted system, do 
>
> sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL 
> sudo mount  /dev/mapper/MYSSDVOL/media 
>
> cheers 
>

Many thanks for that, works exactly as described!  Seems a bit strange that 
the partition isn't mounted at the time it was attached (not sure why you'd 
want to attach it if you didn't plan to read or write to it?).   Anyways...

Is there any way the attachment and mounting can be made permanent?

Next challenge - access files on another Linux laptop on the same network!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/da8f0bd7-8736-4e32-b64c-9721ab8fabaco%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Saturday, 6 June 2020 16:21:35 UTC+1, Andrew Sullivan wrote:
>
>
>
> On Saturday, 6 June 2020 16:13:11 UTC+1, unman wrote:
>>
>> On Sat, Jun 06, 2020 at 07:59:14AM -0700, Andrew Sullivan wrote: 
>> > Well, just done my first Qubes install - onto a USB 3 stick attached to 
>> a 
>> > Dell Latitude E5470 (only a temporary arrangement pending installing a 
>> > second SSD in the laptop).  I was pleasantly surprised how smoothly it 
>> went 
>> > (although it took a while to complete the install and updates seem to 
>> take 
>> > an age) and most things I need to work, do. 
>> > 
>> > One thing I can't figure out...  I have data files on the internal SSD 
>> > which I would like to access from Qubes.  I can find reference in the 
>> > documentation to accessing USB sticks, but not a SSD.  I would like to 
>> have 
>> > the access permanent (in a "conventional" Linux installation, I think I 
>> > would edit fstab appropriately?).  Neither lsblk or fdisk -l seem to 
>> show 
>> > me anything about the internal SSD. 
>> > 
>> > I think I must be missing something, any pointer would be welcome. 
>> > 
>> > Thanks 
>> > 
>>
>> Do you want the SSD partitions permanently attached to one qube? 
>>
>
>   That might work, or maybe better permanently attached to two qubes?
>  
>
>> If you use qvm-block in dom0 can you see the disk/partitions? 
>>
>
>  Don't know, I'll give it a try and post back. 
>

OK, if I click on the  Devices widget I can indeed see all the partitions 
on my internal SSD, with an arrow next to each.  If I click the arrow I get 
a list of qubes, which I believe allows me to attach the selected partition 
to where I want.  However, when I do this I can't find the partition in the 
Files application in the qube.  Think I'm still missing something...  Also, 
am I correct that this attachment will only persist until I close the qube?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/01992459-e7c3-43e1-9540-5d0a318ad83fo%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Saturday, 6 June 2020 16:13:11 UTC+1, unman wrote:
>
> On Sat, Jun 06, 2020 at 07:59:14AM -0700, Andrew Sullivan wrote: 
> > Well, just done my first Qubes install - onto a USB 3 stick attached to 
> a 
> > Dell Latitude E5470 (only a temporary arrangement pending installing a 
> > second SSD in the laptop).  I was pleasantly surprised how smoothly it 
> went 
> > (although it took a while to complete the install and updates seem to 
> take 
> > an age) and most things I need to work, do. 
> > 
> > One thing I can't figure out...  I have data files on the internal SSD 
> > which I would like to access from Qubes.  I can find reference in the 
> > documentation to accessing USB sticks, but not a SSD.  I would like to 
> have 
> > the access permanent (in a "conventional" Linux installation, I think I 
> > would edit fstab appropriately?).  Neither lsblk or fdisk -l seem to 
> show 
> > me anything about the internal SSD. 
> > 
> > I think I must be missing something, any pointer would be welcome. 
> > 
> > Thanks 
> > 
>
> Do you want the SSD partitions permanently attached to one qube? 
>

  That might work, or maybe better permanently attached to two qubes?
 

> If you use qvm-block in dom0 can you see the disk/partitions? 
>

 Don't know, I'll give it a try and post back. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ead448ea-c4c6-4409-9c03-25e9d3da267fo%40googlegroups.com.

[qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

Well, just done my first Qubes install - onto a USB 3 stick attached to a 
Dell Latitude E5470 (only a temporary arrangement pending installing a 
second SSD in the laptop).  I was pleasantly surprised how smoothly it went 
(although it took a while to complete the install and updates seem to take 
an age) and most things I need to work, do.

One thing I can't figure out...  I have data files on the internal SSD 
which I would like to access from Qubes.  I can find reference in the 
documentation to accessing USB sticks, but not a SSD.  I would like to have 
the access permanent (in a "conventional" Linux installation, I think I 
would edit fstab appropriately?).  Neither lsblk or fdisk -l seem to show 
me anything about the internal SSD.

I think I must be missing something, any pointer would be welcome.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/26ffa360-01c3-4b89-849f-cdca7034117ao%40googlegroups.com.

Re: [qubes-users] X Startup Failed, Aborting Installation. Pane is Dead.

[Andrew Sullivan]

Did you check the ISO you downloaded was good? As described here:

https://www.qubes-os.org/security/verifying-signatures/

Apologies if I'm teaching you to suck eggs!

Andrew

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/070d0900-1703-4000-ab82-be58a754720f%40googlegroups.com.

Re: [qubes-users] X Startup Failed, Aborting Installation. Pane is Dead.

[Andrew Sullivan]

On Friday, 29 May 2020 16:58:14 UTC+1, dennis...@gmail.com wrote:
>
> Hey Peter! 
>
> I did install Fedora successfully using the same USB device. No problems 
> at all. 
>
> I’m running an Alienware M15 R3 which is on the Qubes compatible list. 
>
> Could it be Rufus not writing the DD properly? 
>
> Thanks so much for your help!


Hello Dennis

Might be a bit of a long way round, but if you have aLinux Live system on a 
USB stick, could you boot from that then try to write the Qubes installer 
using dd from the command line?

Good luck 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/59400fad-1194-46e0-878d-968ea7abb67c%40googlegroups.com.

Re: [qubes-users] Re: HCL - Dell Latitude E5470 + Docking Station

[Andrew Sullivan]

On Tuesday, 26 May 2020 18:58:28 UTC+1, Rafael Reis wrote:
>
> Quoting myself:
>
> After some deep research I discovered that the WWAN slot indeed takes a* 
>> SATA M.2 *SSD. (source 
>> <http://forum.notebookreview.com/threads/new-latitude-5470.785426/page-9#post-10227440>
>> ).
>> You'd better go for the shorter ones, otherwise they'll collide with the 
>> inner plastic frame and won't fit. I believe you can fit 32 and 40mm length 
>> drives without any trouble.  
>
>
> So a SATA M.2 2242 or 2230 should fit. Examples 
> <https://www.ebay.com/sch/i.html?_from=R40&_trksid=m570.l1313&_nkw=sata+m.2+2242&_sacat=0_TitleDesc=0&_osacat=0&_odkw=sata+m.2+2230>
>
> I couldn't find those sizes here in my country. So as I explained on the 
> same post, I disassembled and broke away pieces of the inner frame to fit a 
> 2280 size drive.
>
>  
>
> On Tue, May 26, 2020 at 2:50 PM Andrew Sullivan  > wrote:
>
>>
>>
>> On Thursday, 14 May 2020 13:52:59 UTC+1, Rafael Reis wrote:
>>>
>>> Hey Andrew,
>>>
>>> Glad I could help.
>>>
>>> Yes you can manually enable and disable drives on BIOS, although it is a 
>>> somewhat cumbersome workflow if you dual boot a lot. Especially if you have 
>>> BIOS password enabled as well.
>>>
>>> Windows sees the Qubes drive enabled, initialized but not formatted. It 
>>> does not touch the drive and does not prompt to format it or anything. Yes, 
>>> it is there, exposed but again, depending on your threat model this isn’t 
>>> that big of a deal. I have custom software highest encryption bitlocker 
>>> enabled on the windows drive as well.
>>>
>>> You may always encrypt qubes boot partition as well. It’s one more 
>>> password. There’s docs for that.
>>>
>>> As far as laptop size goes that’s entirely personal. I’m 95% of the time 
>>> docked, with a full desktop setup around me, so I favor the portability 
>>> when on the go. You may consider the dock station + monitors + keyboard 
>>> mouse combo. You also get a ton of additional I/O, charging, and many perks 
>>> with this configuration. It’s awesome, and a Single eject away of being 
>>> untethered.
>>>
>>> I’ve worked with the precisions before, and to me they are absolute 
>>> mammoths. But I’d probably go for a bigger laptop if I didn’t have the 
>>> docking setup.
>>>
>>> Good luck on your Qubes adventure.
>>>
>>> Rafael 
>>>
>>> Em qui, 14 de mai de 2020 às 09:13, Andrew Sullivan <
>>> andrew@gmail.com> escreveu:
>>>
>>>>
>>>>
>>>> On Monday, 11 May 2020 23:13:21 UTC+1, Rafael Reis wrote:
>>>>>
>>>>> Hey Andrew!
>>>>>
>>>>> Sorry for the late reply, haven't checked the mailing list in a while. 
>>>>>
>>>>> I have a 5470 service tag # 5V2GBG2 
>>>>> You may see the full original config here 
>>>>> <https://www.dell.com/support/home/en-us/product-support/servicetag/0-dHBZdFAzUVN4THRPN0NkTzFYWlNWdz090/overview>
>>>>> . 
>>>>>
>>>>> Basically it came stock with a quad core i7-6820HQ. Sata drive with 
>>>>> the tiny sata cable. No m.2 bracket or SSD installed to the NVME ngff 
>>>>> slot. 
>>>>> Nothing installed on the wwan ngff slot, and intel's wifi card installed 
>>>>> to 
>>>>> the ngff wireless slot. 
>>>>>
>>>>> It has 3 ngff slots (M.2 NVME, WIFI, WWAN) keyed differently (Key A, B 
>>>>> etc) and the sata data+power cable for 1 sata drive.
>>>>>
>>>>> I've upgraded ram to 2x8GB DDR4, removed the stock sata hdd and 
>>>>> replaced it with a sata ssd. Since I needed more capacity than 
>>>>> performance, 
>>>>> I got a 512GB Crucial BX500. It was way more affordable than an nvme 
>>>>> drive 
>>>>> atm, and I didn't have the m.2 bracket either, which would mean I would 
>>>>> only be able to secure the nvme ssd with double sided tape or other 
>>>>> improvised solution. The BX500 is known to have an exploitable hardware 
>>>>> encryption, so be advised to use only software encryption on that drive.
>>>>>
>>>>> That drive became my Windows 10 drive, GPT / UEFI enabled.
>>>>> Started using Qubes on a USB 3.0 64GB flash drive, it worked pretty 
>>&

Re: [qubes-users] Re: HCL - Dell Latitude E5470 + Docking Station

[Andrew Sullivan]

On Thursday, 14 May 2020 13:52:59 UTC+1, Rafael Reis wrote:
>
> Hey Andrew,
>
> Glad I could help.
>
> Yes you can manually enable and disable drives on BIOS, although it is a 
> somewhat cumbersome workflow if you dual boot a lot. Especially if you have 
> BIOS password enabled as well.
>
> Windows sees the Qubes drive enabled, initialized but not formatted. It 
> does not touch the drive and does not prompt to format it or anything. Yes, 
> it is there, exposed but again, depending on your threat model this isn’t 
> that big of a deal. I have custom software highest encryption bitlocker 
> enabled on the windows drive as well.
>
> You may always encrypt qubes boot partition as well. It’s one more 
> password. There’s docs for that.
>
> As far as laptop size goes that’s entirely personal. I’m 95% of the time 
> docked, with a full desktop setup around me, so I favor the portability 
> when on the go. You may consider the dock station + monitors + keyboard 
> mouse combo. You also get a ton of additional I/O, charging, and many perks 
> with this configuration. It’s awesome, and a Single eject away of being 
> untethered.
>
> I’ve worked with the precisions before, and to me they are absolute 
> mammoths. But I’d probably go for a bigger laptop if I didn’t have the 
> docking setup.
>
> Good luck on your Qubes adventure.
>
> Rafael 
>
> Em qui, 14 de mai de 2020 às 09:13, Andrew Sullivan  > escreveu:
>
>>
>>
>> On Monday, 11 May 2020 23:13:21 UTC+1, Rafael Reis wrote:
>>>
>>> Hey Andrew!
>>>
>>> Sorry for the late reply, haven't checked the mailing list in a while. 
>>>
>>> I have a 5470 service tag # 5V2GBG2 
>>> You may see the full original config here 
>>> <https://www.dell.com/support/home/en-us/product-support/servicetag/0-dHBZdFAzUVN4THRPN0NkTzFYWlNWdz090/overview>
>>> . 
>>>
>>> Basically it came stock with a quad core i7-6820HQ. Sata drive with the 
>>> tiny sata cable. No m.2 bracket or SSD installed to the NVME ngff slot. 
>>> Nothing installed on the wwan ngff slot, and intel's wifi card installed to 
>>> the ngff wireless slot. 
>>>
>>> It has 3 ngff slots (M.2 NVME, WIFI, WWAN) keyed differently (Key A, B 
>>> etc) and the sata data+power cable for 1 sata drive.
>>>
>>> I've upgraded ram to 2x8GB DDR4, removed the stock sata hdd and replaced 
>>> it with a sata ssd. Since I needed more capacity than performance, I got a 
>>> 512GB Crucial BX500. It was way more affordable than an nvme drive atm, and 
>>> I didn't have the m.2 bracket either, which would mean I would only be able 
>>> to secure the nvme ssd with double sided tape or other improvised solution. 
>>> The BX500 is known to have an exploitable hardware encryption, so be 
>>> advised to use only software encryption on that drive.
>>>
>>> That drive became my Windows 10 drive, GPT / UEFI enabled.
>>> Started using Qubes on a USB 3.0 64GB flash drive, it worked pretty well 
>>> considering the constraints, but decided I needed a drive for Qubes itself.
>>>
>>> After some deep research I discovered that the WWAN slot indeed takes a 
>>> SATA M.2 SSD. (source 
>>> <http://forum.notebookreview.com/threads/new-latitude-5470.785426/page-9#post-10227440>
>>> ).
>>> You'd better go for the shorter ones, otherwise they'll collide with the 
>>> inner plastic frame and won't fit. I believe you can fit 32 and 40mm length 
>>> drives without any trouble.  I couldn't find an affordable SATA M.2 with at 
>>> least 256GB for Qubes (that was my personal need), so I ended up getting a 
>>> regular 80mm lenght one. To make it fit, I had to "mod" the inner plastic 
>>> frame, and disassemble 50% of the laptop.  I opted simply to break pieces 
>>> of the plastic frame in order to free space for the lengthier drive. Then, 
>>> I isolated the surroundings with tape and secured the ssd (don't remember 
>>> how, if I was able to bolt it in, tape it, or pressure). The SSD I used in 
>>> the WWAN port is https://www.lexar.com/portfolio_page/ssd-nm100/ 256GB 
>>> version
>>>
>>> You have to change BIOS settings under drive configuration to enable the 
>>> required sata ports. 
>>>
>>> Initialized that drive as GPT, and installed Qubes to it.
>>>
>>> You are right regarding the "dual boot". I don't have Grub. I use the 
>>> "BIOS" UEFI bootmanager to choose which OS I'd like to boot. All I have to 
>>> do is press 

Re: [qubes-users] HCL search facility

[Andrew Sullivan]

On Friday, 15 May 2020 14:13:18 UTC+1, unman wrote:
>
> On Thu, May 14, 2020 at 12:30:11PM -0700, Andrew Sullivan wrote: 
> > Good evening 
> > 
> > Is there a way to search the HCL? If not, could such a function be 
> provided? The list is long, and presumably will get longer, so it would 
> save a lot of scrolling. 
> > 
> > Just a thought. 
> > 
>
> / 
> Ctrl+F 
>
> ;-) 
>

Doh... Simples!

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d48de0d7-2ed1-4e62-82c8-e34fd23c184a%40googlegroups.com.

[qubes-users] HCL search facility

[Andrew Sullivan]

Good evening

Is there a way to search the HCL? If not, could such a function be provided? 
The list is long, and presumably will get longer, so it would save a lot of 
scrolling.

Just a thought.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/51016560-70d4-4b27-899d-d6606eb9e642%40googlegroups.com.

[qubes-users] Re: HCL - Dell Latitude E5470 + Docking Station

[Andrew Sullivan]

On Monday, 11 May 2020 23:13:21 UTC+1, Rafael Reis wrote:
>
> Hey Andrew!
>
> Sorry for the late reply, haven't checked the mailing list in a while. 
>
> I have a 5470 service tag # 5V2GBG2 
> You may see the full original config here 
> 
> . 
>
> Basically it came stock with a quad core i7-6820HQ. Sata drive with the 
> tiny sata cable. No m.2 bracket or SSD installed to the NVME ngff slot. 
> Nothing installed on the wwan ngff slot, and intel's wifi card installed to 
> the ngff wireless slot. 
>
> It has 3 ngff slots (M.2 NVME, WIFI, WWAN) keyed differently (Key A, B 
> etc) and the sata data+power cable for 1 sata drive.
>
> I've upgraded ram to 2x8GB DDR4, removed the stock sata hdd and replaced 
> it with a sata ssd. Since I needed more capacity than performance, I got a 
> 512GB Crucial BX500. It was way more affordable than an nvme drive atm, and 
> I didn't have the m.2 bracket either, which would mean I would only be able 
> to secure the nvme ssd with double sided tape or other improvised solution. 
> The BX500 is known to have an exploitable hardware encryption, so be 
> advised to use only software encryption on that drive.
>
> That drive became my Windows 10 drive, GPT / UEFI enabled.
> Started using Qubes on a USB 3.0 64GB flash drive, it worked pretty well 
> considering the constraints, but decided I needed a drive for Qubes itself.
>
> After some deep research I discovered that the WWAN slot indeed takes a 
> SATA M.2 SSD. (source 
> 
> ).
> You'd better go for the shorter ones, otherwise they'll collide with the 
> inner plastic frame and won't fit. I believe you can fit 32 and 40mm length 
> drives without any trouble.  I couldn't find an affordable SATA M.2 with at 
> least 256GB for Qubes (that was my personal need), so I ended up getting a 
> regular 80mm lenght one. To make it fit, I had to "mod" the inner plastic 
> frame, and disassemble 50% of the laptop.  I opted simply to break pieces 
> of the plastic frame in order to free space for the lengthier drive. Then, 
> I isolated the surroundings with tape and secured the ssd (don't remember 
> how, if I was able to bolt it in, tape it, or pressure). The SSD I used in 
> the WWAN port is https://www.lexar.com/portfolio_page/ssd-nm100/ 256GB 
> version
>
> You have to change BIOS settings under drive configuration to enable the 
> required sata ports. 
>
> Initialized that drive as GPT, and installed Qubes to it.
>
> You are right regarding the "dual boot". I don't have Grub. I use the 
> "BIOS" UEFI bootmanager to choose which OS I'd like to boot. All I have to 
> do is press F12 after powering up. I've renamed Qubes to Recovery, so it is 
> inconspicuous. Default boot drive is the BX500 with windows. 
>
> The level of compatibility of the E5470 with Qubes is outstanding. The 
> performance is incredible.
> The only thing that didn't work OOB was the SD card reader, which was 
> easily fixed by opting to  kernel-latest . Docking station works 100%, with 
> multiple monitors. Even 2 monitors + laptop monitor works perfectly. I wish 
> it was possible to nuke Intel ME on 6th gen laptops and have it fully 
> Opensource. It would make a great candidate for certification.
>
> My only concern right now is the decisions for the GUI of Qubes 4.1. I 
> wonder if the separation of the GUI and dom0 would result in 
> incompatibility with E5470 or even a big decrease in performance. This 
> thing is perfect for Qubes if your threat model isn't government agencies 
> high.
>
> Hope I could help, and let me know if you have further questions.
> Em quarta-feira, 6 de maio de 2020 20:51:29 UTC-3, andrew@gmail.com 
> escreveu:
>>
>> Hi Rafael
>>
>> Interested to see you got an SSD drive to work in the WWAN slot in your 
>> E5470. Could you tell me what drive you used, and the spec for your laptop. 
>> Am I right in thinking that you have Windows installed on one drive and 
>> Qubes on the other, and that you actually choose which drive to boot from 
>> at power up? So it's not "dual-boot" in the usual sense (ie multiple OSs on 
>> the same drive)?
>>
>> Thanks
>>
>
Hi Rafael

Very many thanks for your comprehensive reply, lots of good information 
there.  What I hope to end up with is pretty similar to what you have - a 
large(ish) drive with Windws and Linux Mint in a conventional dual boot 
setup, and a drive in the WWAN slot to run Qubes.  I think it is possible 
to inactivate drives individually on Dell laptops so if I feel it necessary 
I could switch off the W/LM drive when using Qubes and vice versa.  I think 
this would largely get around the potential risk of the Qubes /boot 
partition getting compromised when using one of the other OSs?  Depends how 
paranoid I feel!

Regarding choice of laptop, I am torn between the E5470 and the 

Re: [qubes-users] Can I have Windows & Qubes on the same laptop?

[Andrew Sullivan]

On Monday, 11 May 2020 12:08:22 UTC+1, unman wrote:
>
> On Mon, May 11, 2020 at 02:31:52AM -0700, Andrew Sullivan wrote: 
> > Sorry if I have double-posted this... 
> > 
> > The link to "multiboot" seems to refer to a conventional dual-boot 
> > installation, where the two OSs are on the same disc.  If the OSs were 
> > installed n physically separate (internal) drives, would this mitigate 
> the 
> > risk (accepting that /boot would be exposed)? 
> > 
> > Probably a naive idea, but is it possible to somhow "switch off" or 
> > inactivate one disc (short of physically removing it)? 
> > 
> > On Monday, 11 May 2020 10:11:47 UTC+1, dhorf-hfr...@hashmail.org wrote: 
> > > 
> > > On Mon, May 11, 2020 at 01:48:58AM -0700, matteochi...@gmail.com 
> > >  wrote: 
> > > 
> > > > Firstly, is it safe to have Windows and Qubes on the same machine? I 
> > > > use VeraCrypt for full disc encryption 
> > > 
> > > veracrypt does not support actual full disc encryption. 
> > > 
> > > 
> > > > Also, I've got a 2TB external HDD, would it be safer to run Qubes 
> from 
> > > > that and keep Windows on my internal drive or is that worse? 
> > > 
> > > if that HDD is connected via USB, i would not recommend installing 
> > > qubes to it. 
> > > while both "install to usb" and "install to hdd" are supported, they 
> > > have major drawbacks. 
> > > 
> > > 
> > > > I want to keep maximum security and keep Windows and Qubes seperate. 
> > > 
> > > this is not possible. 
> > > if you multiboot, you are very far from "maximum security". 
> > > 
> > > 
> > > > Any answers to questions or installation guidance is greatly 
> > > 
> > > https://www.qubes-os.org/doc/multiboot/ 
> > > 
>
>
> Not *double* but *top-posted*. Please don't do this. 
>
> It's not a naive idea - it's a good one. Depending on your machine you 
> may be able to find ways to do this, by installing a kill switch, or by 
> BIOS configuration. 
> You may find that your BIOS allows you to disable certain devices pre 
> boot, and this may enable you to switch between active disks. Have a 
> look.(Depending on what's available this may determine what sort of disk 
> you use to install Qubes) 
> I have an x230 with some extra hardware switches installed to allow for 
> device isolation. With minimal skills you could do the same yourself. 
> Take a look at what's already there and have a think about what you 
> might manage to do. If it's important enough you'll find a way. 
>

A quick update on this.  I've had a look at the User Manuals for some Dell 
laptops (specifically E5470 and M4800) and it seems that it is possible to 
deactivate hard drives on an individual basis in BIOS. It is also possible, 
again in BIOS, to choose what theWiFi on/off switch actually does - it can 
be set to switch off the WWAN card, so if there is a SSD installed there 
that could be easily switched off.

I think this could be used to reduce the risk when two OSs are installed on 
separate drives in the same machine?

Things were easier in the "old days" of PATA drives - I guess you could 
just put a switch in thepower lead to the drive(s)...

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ddaabaf4-4acd-4180-a817-fe9b39b3ddd4%40googlegroups.com.

Re: [qubes-users] Can I have Windows & Qubes on the same laptop?

[Andrew Sullivan]

On Monday, 11 May 2020 12:08:22 UTC+1, unman wrote:
>
> On Mon, May 11, 2020 at 02:31:52AM -0700, Andrew Sullivan wrote: 
> > Sorry if I have double-posted this... 
> > 
> > The link to "multiboot" seems to refer to a conventional dual-boot 
> > installation, where the two OSs are on the same disc.  If the OSs were 
> > installed n physically separate (internal) drives, would this mitigate 
> the 
> > risk (accepting that /boot would be exposed)? 
> > 
> > Probably a naive idea, but is it possible to somhow "switch off" or 
> > inactivate one disc (short of physically removing it)? 
> > 
> > On Monday, 11 May 2020 10:11:47 UTC+1, dhorf-hfr...@hashmail.org wrote: 
> > > 
> > > On Mon, May 11, 2020 at 01:48:58AM -0700, matteochi...@gmail.com 
> > >  wrote: 
> > > 
> > > > Firstly, is it safe to have Windows and Qubes on the same machine? I 
> > > > use VeraCrypt for full disc encryption 
> > > 
> > > veracrypt does not support actual full disc encryption. 
> > > 
> > > 
> > > > Also, I've got a 2TB external HDD, would it be safer to run Qubes 
> from 
> > > > that and keep Windows on my internal drive or is that worse? 
> > > 
> > > if that HDD is connected via USB, i would not recommend installing 
> > > qubes to it. 
> > > while both "install to usb" and "install to hdd" are supported, they 
> > > have major drawbacks. 
> > > 
> > > 
> > > > I want to keep maximum security and keep Windows and Qubes seperate. 
> > > 
> > > this is not possible. 
> > > if you multiboot, you are very far from "maximum security". 
> > > 
> > > 
> > > > Any answers to questions or installation guidance is greatly 
> > > 
> > > https://www.qubes-os.org/doc/multiboot/ 
> > > 
>
>
> Not *double* but *top-posted*. Please don't do this. 
>
> It's not a naive idea - it's a good one. Depending on your machine you 
> may be able to find ways to do this, by installing a kill switch, or by 
> BIOS configuration. 
> You may find that your BIOS allows you to disable certain devices pre 
> boot, and this may enable you to switch between active disks. Have a 
> look.(Depending on what's available this may determine what sort of disk 
> you use to install Qubes) 
> I have an x230 with some extra hardware switches installed to allow for 
> device isolation. With minimal skills you could do the same yourself. 
> Take a look at what's already there and have a think about what you 
> might manage to do. If it's important enough you'll find a way. 
>

Not *double* but *top-posted*. Please don't do this. - oops, sorry; is this 
the right place?

When I get a suitable laptop (I have a separate post on this) I'll look 
into that.  Are you able to share
how you implemented hardware switches on your X230? Do you find the X230 
"man enough" to run Qubes?  They're not expensive...

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c0c67440-0541-4a9f-abbd-3d3be78fd49d%40googlegroups.com.

[qubes-users] Choice of hardware for Qubes...

[Andrew Sullivan]

Good morning

I plan to try Qubes, with a view to maybe using it as my main OS.  Happily 
I also need to update my laptop.

I've been looking at the HCL, and see that Dell and Lenovo machines seem to 
rate quite well.  The Dell Outlet web site has some (apparently) compatible 
machines at what look like good prices, and maybe buying from them might be 
safer than Amazon/eBay (I'm in the UK btw).  Two that I am considering are:

Latitude E5470 - claimed to be fully compatible with R4.0, can install 32GB 
RAM, but only has a 14" (FHD) screen, might take a second 2242-format SSD 
(although mixed reports on this)

M4800 - bit of a monster, but portability isn't really an issue; also takes 
32GB RAM, lots of potential storage space, 15" screen (it won't be the QHD 
screen).

Any thoughts would be appreciated.

TIA

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e69d48c0-0db3-4ee0-8dae-bcffe1307f52%40googlegroups.com.

Re: [qubes-users] Can I have Windows & Qubes on the same laptop?

[Andrew Sullivan]

Sorry if I have double-posted this...

The link to "multiboot" seems to refer to a conventional dual-boot 
installation, where the two OSs are on the same disc.  If the OSs were 
installed n physically separate (internal) drives, would this mitigate the 
risk (accepting that /boot would be exposed)?

Probably a naive idea, but is it possible to somhow "switch off" or 
inactivate one disc (short of physically removing it)?

On Monday, 11 May 2020 10:11:47 UTC+1, dhorf-hfr...@hashmail.org wrote:
>
> On Mon, May 11, 2020 at 01:48:58AM -0700, matteochi...@gmail.com 
>  wrote: 
>
> > Firstly, is it safe to have Windows and Qubes on the same machine? I 
> > use VeraCrypt for full disc encryption 
>
> veracrypt does not support actual full disc encryption. 
>
>
> > Also, I've got a 2TB external HDD, would it be safer to run Qubes from 
> > that and keep Windows on my internal drive or is that worse? 
>
> if that HDD is connected via USB, i would not recommend installing 
> qubes to it. 
> while both "install to usb" and "install to hdd" are supported, they 
> have major drawbacks. 
>
>
> > I want to keep maximum security and keep Windows and Qubes seperate. 
>
> this is not possible. 
> if you multiboot, you are very far from "maximum security". 
>
>
> > Any answers to questions or installation guidance is greatly 
>
> https://www.qubes-os.org/doc/multiboot/ 
>
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6f036494-8cae-4c78-bb35-007a33c6fe77%40googlegroups.com.

Re: [qubes-users] Privacy Beast vs Nitropad comparison?

[Andrew Sullivan]

No apology necessary!  I would also be interested in this information - 
given that I currently have time on my hands (!) and that second-hand X230s 
are quite inexpensice, maybe I'll try the DIY route.

BTW, I am only interested in the Nitropad and the Insurgo machines, I'd 
previously ruled out the Purism/Librem...

On Wednesday, 15 April 2020 14:49:35 UTC+1, Catacombs wrote:
>
> Librem pricing shows two prices for including a Nitrokey  sending key 
> separately or with laptop.  I assumed that would be to verify shipment had 
> not been tampered with.  I guess I misunderstood how that really worked. 
>  If it is not encrypted properly. Then that would not be close enough to 
> Insurgo options.  
>
> Apologies for changing the subject.  But this would be a good time to ask 
> the last poster, or anyone else, do you have any experience with the 
> project, I now face, flashing Core Boot onto a Lenovo X 230?  Last Poster 
> seems to have more knowledge than I in hardware.   
>
> Thanks for correction. Details are more important than impressions.   
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0fb3c647-86fa-4717-9b56-68941a1bea31%40googlegroups.com.

Re: [qubes-users] Privacy Beast vs Nitropad comparison?

[Andrew Sullivan]

Thanks for the reply.  I'm in the UK, so I think you're right, the Insurgo 
machine would probably cost me in terms of shipping, import duty etc.  So 
the Nitropad (from Germany I think) is probably a better bet.

I also think you're right in that both machines use a Nitrokey.  The 
difference I think is that Insurgo put their security key on the machine, 
and then force you to change it when you first boot up.  With the Nitropad, 
there is just a default key (something like "changemenow") which obviously 
needs to be changed (!) but I don't know if there is a formal reowning 
process.

Never heard of easyOS, I'll have a look.

"noobs need Qubes" wasn't my quote!!!


On Tuesday, 14 April 2020 15:04:54 UTC+1, Catacombs wrote:
>
> Your choice between NitroPad or Insurgo might depend on where you live.  I 
> think Insurgo is based in north America, and Nitro is based in Europe.  
> Different taxes, shipping problems, searches.  I thought they both allowed 
> for non-tampered shipping security with NitroKey.
>
> Option three is is the laptop from Puri, Librem.  From north America, also 
> allows for non-tampered shipping security with NitroKey.  https://puri.sm/
>
> Besides there standard offering they have a sale on what they call 
> refurbished, which some believe is Puri/Librem clearing their warehouse 
> shelves.  
>
> https://forums.puri.sm/t/refurbished-librem-laptops-on-sale/8841
>
> For their Pure OS, they offer another service, (for a monthly fee).  
> Despite being Debian based, these do not install so easily on other Linux 
> OS's.  https://librem.one/
>
> They offer their own Debian based OS, Pure OS.Pure uses Boxes for 
> security.   These is free OS, and you can give it a whirl without buying 
> anything.  https://www.pureos.net/  
>
> Puri/Librem  will install Qubes for you, (I think for a charge) or you can 
> do that on your own.
>
> The other OS's which one might use is Tails Linux (yeah, you knew that, 
> but I had to mention it.)  and Easy OS.  
>
> Easy OS some might not consider to be secure, only one developer, Barry 
> Kauler, uses Boxes for security.  
> http://murga-linux.com/puppy/viewtopic.php?t=109958
>
> I guess noobs need Qubes is a joke, because it has some intensive learning 
> associated with using it properly.  or at 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b5a8aadb-e75d-4ab5-94de-3d58f2e76dac%40googlegroups.com.

Re: [qubes-users] Privacy Beast vs Nitropad comparison?

[Andrew Sullivan]

Hello

I'm thinking of trying my hand at Qubes (currently a long-time Linux Mint 
user), and I need a new laptop anyway so I'm thinking of the Nitropad or 
Insurgo machines. 

You say that the Insurgo is "more secure" and "exceeds" the requirements of 
Qubes certification; in what ways is this?  Is it just the reownership 
process (which I admit does look more stringent in the as of the Insurgo, 
but they end up re-owned just the same?).

If I got one of these machines and for some reason decided that Qubes 
wasn't for me, would it be easy to "nuke" the Qubes and just install Linux 
Mint or whatever?  Would a Linux installer have any problems with Coreboot 
etc?

Thanks in advance

Andrew

On Wednesday, 8 April 2020 11:40:23 UTC+1, Maillist wrote:
>
> Hello, 
>
> the Privacy Beast is more secure. As they write, it meets and exceeds 
> the Qubes os certification, the Nitropad only meets them.They differ in 
> the OEM reownership process. 
>
>
> cheers. 
>
> On 4/8/20 1:03 AM, 'dcon' via qubes-users wrote: 
> > Are there any significant differences between the two? It seems that 
> Nitropad has more hardware configuration options. With ME inactivation, is 
> there any reason to swap out the WiFi module? 
> > 
> > I’d like to thank both vendors for bringing these to the market!   
> > 
> > Noobs need 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/93fd27f8-2838-43c3-9f84-0c3865382d0d%40googlegroups.com.