[qubes-users] Re: #ReactOS 0.4.11 is out!! Supported new AHCI SATA controllers, but still not installing in Qubes 4.0

2019-03-12 Thread nosugarmaxtaste
On Wednesday, 13 March 2019 00:20:59 UTC+11, nosugar...@gmail.com  wrote:
> On Tuesday, 5 March 2019 05:44:29 UTC+11, Sergio Matta  wrote:
> > ReactOS 0.4.11 is out!! Supported new AHCI SATA controllers, more #Software 
> > working thanks to correct manifest loading, #RTL support, new Update 
> > feature... More info: 
> > https://reactos.org/project-news/reactos-0411-released … Download it from: 
> > https://reactos.org/download 
> > It boots but does not recognize any drive to install.
> 
> Meanwhile Android-x86 Orio installs fine and detects the HDD under Qubes, but 
> the Settings app crashes everytime making it useless.

Whoops, nvm me, thought ReactOS was just another Android OS.

-- 
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/8c909b06-7040-4a06-8864-67107012fcf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: #ReactOS 0.4.11 is out!! Supported new AHCI SATA controllers, but still not installing in Qubes 4.0

2019-03-12 Thread nosugarmaxtaste
On Tuesday, 5 March 2019 05:44:29 UTC+11, Sergio Matta  wrote:
> ReactOS 0.4.11 is out!! Supported new AHCI SATA controllers, more #Software 
> working thanks to correct manifest loading, #RTL support, new Update 
> feature... More info: https://reactos.org/project-news/reactos-0411-released 
> … Download it from: https://reactos.org/download 
> It boots but does not recognize any drive to install.

Meanwhile Android-x86 Orio installs fine and detects the HDD under Qubes, but 
the Settings app crashes everytime making it useless. 

-- 
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/b37e68b1-16be-48fb-b6b5-a3b183086564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

2019-02-24 Thread nosugarmaxtaste
On Monday, 25 February 2019 08:16:32 UTC+11, 799  wrote:
> Hello Alex,
> 
> 
> I have succesfully used your .ISO to build a test-android AppVM, following 
> your howto.
> 
> 
> > Create android VM in dom0:
> > qvm-create --class StandaloneVM --label green --property virt_mode=hvm 
> > android
> > qvm-prefs android kernel ''
> > qvm-prefs android 'sys-android'
> 
> I think this is a typo and should be:
> 
> qvm-prefs android netvm 'sys-android'
> 
> (while I have used sys-firewall as netvm)
> 
> > qvm-prefs android memory '2048'
> > qvm-prefs android maxmem '2048'
> > qvm-volume extend android:root 20g
> > Start the android VM with iso:
> > qvm-start android 
> > --cdrom=android-builder:/home/user/android-x86/out/target/product/x86_64/android_x86_64.iso
> > Install android-x86 on xvda and reboot.
> > Start android VM without iso:
> > qvm-start android
> > When it'll start, kill the VM and wait for it to halt.
> > Configure android VM to use the mouse in dom0:
> > sudo mkdir -p /etc/qubes/templates/libvirt/xen/by-name/
> > sudo cp /etc/libvirt/libxl/android.xml 
> > /etc/qubes/templates/libvirt/xen/by-name/android.xml
> > sudo sed -i -e 's/tablet/mouse/g' 
> > /etc/qubes/templates/libvirt/xen/by-name/android.xml
> > Start android VM without iso and it should work fine:
> > qvm-start android
> 
> 
> Two Questions:
> 
> 1) Is there any way to change the display resolution of the Android AppVM, as 
> I am running it on a LowRes x230 and the window is slightly to high.
> 
> 2) Even after launching the android AppVM without the ISO, the ISO-Boot-Up 
> windows comes and I need to choose Other Options and then Boot from local 
> harddisk to continue booting the AppVM - any idea how to change this?
> 
> 3) The mouse seems strange, as I see two mouse pointers, the one in dom0 and 
> the one in android and they are not synchronized.
> While it is possible to use the mouse, it would be nice if there is only one 
> mouse pointer. Can this be done?
>  
> 
> 
> - O

Hi, please note that Alex's guide was created just before Android-x86 Oreo was 
released. If you change 'repo init -u 
git://git.osdn.net/gitroot/android-x86/manifest -b android-x86-7.1-r2' to 'repo 
init -u git://git.osdn.net/gitroot/android-x86/manifest -b oreo-x86', you'll 
have no mouse issues. Just rememeber not to do Alex's steps on fixing the mouse 
if you do, as you'll just recreate the mouse problem. 

When you rebooted the appvm, and shut down the builder VM, the iso should have 
detached from the android appvm. Reboot Qubes if it hasn't. 

I've been changing resolution by affixing 'vga=(desired resolution code)' to 
the end of the kernel. You can type vga=ask to get a list of resolution codes. 
You do this by pressing 'e' when you get the boot options, and then 'e' again. 
It will look something like 'kernel /android-2019-02-18/kernelvga=ask quiet 
etc, etc'.

-- 
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/4ec3c459-cdf2-4c2d-8989-76536a3e55bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

2019-02-24 Thread nosugarmaxtaste
On Sunday, 24 February 2019 20:18:11 UTC+11, nosugar...@gmail.com  wrote:
> On Sunday, 24 February 2019 01:45:09 UTC+11, alex.jo...@gmail.com  wrote:
> > On Tuesday, February 19, 2019 at 10:38:39 AM UTC, nosugar...@gmail.com 
> > wrote:
> > > Hi Alex,
> > > 
> > > Let me just start by saying a massive thank you. This guide has been 
> > > great. I have used it for the 8.1 - Oreo - which was just changing:
> > >  'repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b 
> > > android-x86-7.1-r2' to 'repo init -u 
> > > git://git.osdn.net/gitroot/android-x86/manifest -b oreo-x86.'
> > > 
> > > With 8.1, mouse support comes out the box and completing the last part of 
> > > the guide actually makes the mouse worse in Oreo. So, disregard that part 
> > > anyone following this guide for 8.1. You can change resolution by 
> > > affixing 'vga=ask' and choosing your desired resolution 
> > > (https://groups.google.com/forum/#!topic/qubes-users/KZm8aGJuiO0).
> > > 
> > > I have come across one issue, and I am wondering if you could help me. 
> > > Android has installed great, and loads up fine. However, I simply cannot 
> > > open the Settings app, as it crashes every single time. Others who have 
> > > encountered this issue modified it using adb 
> > > (https://stackoverflow.com/questions/3480201/how-do-you-install-an-apk-file-in-the-android-emulator?rq=1),
> > >  but I don't know how to do this with a Qubes HVM. Any help with this?
> > > 
> > > Thanks in advance :)
> > 
> > You can use adb via network:
> > Create tmpvm with adb.
> > Select Networking vm for tmpvm with adb to sys-android.
> > Select Networking vm for Android VM to sys-android.
> > 
> > In sys-android run:
> > sudo nft add rule ip qubes-firewall forward meta iifname eth0 accept
> > sudo iptables -I FORWARD 2 -i vif+ -s 10.137.0.0/24 -d 10.137.0.0/24 -p tcp 
> > -m conntrack --ctstate NEW -j ACCEPT
> > 
> > In android terminal run:
> > su
> > setprop service.adb.tcp.port 
> > stop adbd
> > start adbd
> > 
> > In tmpvm witd adb run:
> > adb connect 10.137.0.xx:
> > Where 10.137.0.xx - android IP
> > And then run your commands.
> 
> Okay, adb works perfectly with your method. Thank you!
> 
> However, my settings is still broken after clearing the data of 
> com.android.settings. I do wonder if this is part of a bigger problem, as the 
> google play store says checking for info.. then the screen turns black. I 
> didn't see any issues when compiling the iso, so not sure what's going on.

Think my issue might be because 'No WebView installed'? Can't open up playstore 
as it fails to load webview provider. 

-- 
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/e9b1e1ac-4a2a-4674-b610-91a25faf42ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

2019-02-24 Thread nosugarmaxtaste
On Sunday, 24 February 2019 01:45:09 UTC+11, alex.jo...@gmail.com  wrote:
> On Tuesday, February 19, 2019 at 10:38:39 AM UTC, nosugar...@gmail.com wrote:
> > Hi Alex,
> > 
> > Let me just start by saying a massive thank you. This guide has been great. 
> > I have used it for the 8.1 - Oreo - which was just changing:
> >  'repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b 
> > android-x86-7.1-r2' to 'repo init -u 
> > git://git.osdn.net/gitroot/android-x86/manifest -b oreo-x86.'
> > 
> > With 8.1, mouse support comes out the box and completing the last part of 
> > the guide actually makes the mouse worse in Oreo. So, disregard that part 
> > anyone following this guide for 8.1. You can change resolution by affixing 
> > 'vga=ask' and choosing your desired resolution 
> > (https://groups.google.com/forum/#!topic/qubes-users/KZm8aGJuiO0).
> > 
> > I have come across one issue, and I am wondering if you could help me. 
> > Android has installed great, and loads up fine. However, I simply cannot 
> > open the Settings app, as it crashes every single time. Others who have 
> > encountered this issue modified it using adb 
> > (https://stackoverflow.com/questions/3480201/how-do-you-install-an-apk-file-in-the-android-emulator?rq=1),
> >  but I don't know how to do this with a Qubes HVM. Any help with this?
> > 
> > Thanks in advance :)
> 
> You can use adb via network:
> Create tmpvm with adb.
> Select Networking vm for tmpvm with adb to sys-android.
> Select Networking vm for Android VM to sys-android.
> 
> In sys-android run:
> sudo nft add rule ip qubes-firewall forward meta iifname eth0 accept
> sudo iptables -I FORWARD 2 -i vif+ -s 10.137.0.0/24 -d 10.137.0.0/24 -p tcp 
> -m conntrack --ctstate NEW -j ACCEPT
> 
> In android terminal run:
> su
> setprop service.adb.tcp.port 
> stop adbd
> start adbd
> 
> In tmpvm witd adb run:
> adb connect 10.137.0.xx:
> Where 10.137.0.xx - android IP
> And then run your commands.

Okay, adb works perfectly with your method. Thank you!

However, my settings is still broken after clearing the data of 
com.android.settings. I do wonder if this is part of a bigger problem, as the 
google play store says checking for info.. then the screen turns black. I 
didn't see any issues when compiling the iso, so not sure what's going on. 

-- 
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/3dea61e5-c2b6-45b5-8a35-429d094d6151%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Best ideal laptop for Qubes?

2019-02-24 Thread nosugarmaxtaste
On Sunday, 24 February 2019 20:02:37 UTC+11, Frank Beuth  wrote:
> On Sun, Feb 24, 2019 at 12:39:56AM -0800, nosugarmaxta...@gmail.com wrote:
> >You say laptops are flexible? But are they? you can't just rip out parts 
> >(apart from ram/hdd) like a desktop. And their actual upgrade paths are 
> >limited. With my desktop I have parts from multiple build/years. It is just 
> >that flexible.
> >
> >Also, space requirements? you living in a tent?
> 
> Greetings from a beach on a lesser-known Greek island. I tried using a 
> desktop 
> but the sand kept clogging the fans, and the powerstrip, and the GPU cooler, 
> whenever I brought it outside. After the 10th international flight I also got 
> really tired of having to explain to airlines why my luggage was so big and 
> heavy. (The vintage IBM Model M keyboard probably didn't help, they made me 
> check that because they thought it could be used as a weapon, which really 
> sucked because I was hoping to get some work done on the flight!)

Hahaha, greetings, Frank. I do envy a well travelled gent such as yourself. My 
poor qubes doesn't get to go mobile as it is only used in a secure setting with 
motion detection cameras giving it physical protection. 

I travel through airports with vanilla distros.. (yes, yes, I am a windows user 
too.. still can't rid myself of it). 

-- 
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/46b7190a-1ea4-460f-a00f-56b43a6052b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

2019-02-24 Thread nosugarmaxtaste
On Sunday, 24 February 2019 01:45:09 UTC+11, alex.jo...@gmail.com  wrote:
> On Tuesday, February 19, 2019 at 10:38:39 AM UTC, nosugar...@gmail.com wrote:
> > Hi Alex,
> > 
> > Let me just start by saying a massive thank you. This guide has been great. 
> > I have used it for the 8.1 - Oreo - which was just changing:
> >  'repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b 
> > android-x86-7.1-r2' to 'repo init -u 
> > git://git.osdn.net/gitroot/android-x86/manifest -b oreo-x86.'
> > 
> > With 8.1, mouse support comes out the box and completing the last part of 
> > the guide actually makes the mouse worse in Oreo. So, disregard that part 
> > anyone following this guide for 8.1. You can change resolution by affixing 
> > 'vga=ask' and choosing your desired resolution 
> > (https://groups.google.com/forum/#!topic/qubes-users/KZm8aGJuiO0).
> > 
> > I have come across one issue, and I am wondering if you could help me. 
> > Android has installed great, and loads up fine. However, I simply cannot 
> > open the Settings app, as it crashes every single time. Others who have 
> > encountered this issue modified it using adb 
> > (https://stackoverflow.com/questions/3480201/how-do-you-install-an-apk-file-in-the-android-emulator?rq=1),
> >  but I don't know how to do this with a Qubes HVM. Any help with this?
> > 
> > Thanks in advance :)
> 
> You can use adb via network:
> Create tmpvm with adb.
> Select Networking vm for tmpvm with adb to sys-android.
> Select Networking vm for Android VM to sys-android.
> 
> In sys-android run:
> sudo nft add rule ip qubes-firewall forward meta iifname eth0 accept
> sudo iptables -I FORWARD 2 -i vif+ -s 10.137.0.0/24 -d 10.137.0.0/24 -p tcp 
> -m conntrack --ctstate NEW -j ACCEPT
> 
> In android terminal run:
> su
> setprop service.adb.tcp.port 
> stop adbd
> start adbd
> 
> In tmpvm witd adb run:
> adb connect 10.137.0.xx:
> Where 10.137.0.xx - android IP
> And then run your commands.

Hi Alex, good to hear from you again.

Been pulling my hair out trying to get Android working. It installs great, but 
i can't open settings at all, so can't even do anything with the OS.

Have you had success with Oreo?

I'll try your adb steps.

-- 
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/6ff65e60-5217-4f0d-a134-e504dfc64095%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Best ideal laptop for Qubes?

2019-02-24 Thread nosugarmaxtaste
On Sunday, 24 February 2019 03:44:51 UTC+11, 799  wrote:
>  schrieb am Sa., 23. Feb. 2019, 14:35:
> 
> 
> Not quite sure why people try use Qubes with laptops. I found far better 
> performance on desktops. Laptops are the opposite of flexible. PC's you can 
> upgrade to your hearts content. 
> 
> 
> 
> Maybe because for 90% a laptop offers enough performance, has much lower 
> space & power requirement and can be used flexible?
> And because maybe more people "have to use" computers than they "like to 
> build" them thereselves.
> Just a guess ;-)
> 
> 
> I was asking the other question:
> Who is buying those desktop PCs today? 
> 
> 
> - O

Who are buying desktops? Anyone who is serious about computing. Developers, 
gamers, businesses, those interested in VR, those interested in security, those 
interested in a build that can be upgraded to their hearts content. 

Laptops have their purpose. They can provide a mobile computing experience. I 
use one for work purposes. But, lets be real. That is the only advantage over a 
desktop (even power usage can be just as low on a desktop if you want it to 
be). You don't even have to build one yourself for Qubes. You can easily buy a 
SSF Dell Optiplex off ebay for $200 with a Intel 4770/4790 and 16/32gb of ram. 

I have an i7 laptop from 2011 that can't even run Qubes 4.0 because laptop cpus 
get shafted in the specs (thankfully they at least get vt'd these days). I have 
others that have heating problems because there is only so much cooling you can 
give a laptop, while some of my desktops have 5 14cm fans keeping them cool at 
5ghz overclocks.

You say laptops are flexible? But are they? you can't just rip out parts (apart 
from ram/hdd) like a desktop. And their actual upgrade paths are limited. With 
my desktop I have parts from multiple build/years. It is just that flexible. 

Also, space requirements? you living in a tent? 

I speak out about this.. because I have 5 laptops sitting around collecting 
dust. They have limited use because they are laptops. Desktops can always be 
adapted to another use. One of my older builds became a pfsense router, for 
example. 



-- 
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/b15e02ee-b2aa-48ed-852c-8386a09a0dea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Best ideal laptop for Qubes?

2019-02-23 Thread nosugarmaxtaste
On Thursday, 21 February 2019 11:49:27 UTC+11, dexint...@gmail.com  wrote:
> I've been spending hours and hours looking at laptop configs from dell to 
> lenovo and I still have yet to make a decision. I'm hoping you guys can help 
> me. 
> 
> Uses:
> 
> - Programming
> - Web Dev
> - Tor
> - Screen real estate
> - Regular web surfing and videos
> - Some video and photo editing but I have a PC for that 
> 
> I'd like to keep cost as low as possible but my budget is very flexible if I 
> need to stretch it. I want something that will last me 3-5 years.

Not quite sure why people try use Qubes with laptops. I found far better 
performance on desktops. Laptops are the opposite of flexible. PC's you can 
upgrade to your hearts content. 

-- 
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/ae42b5a1-e412-4ec7-ac27-1b160f695c0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

2019-02-21 Thread nosugarmaxtaste
On Thursday, 21 February 2019 16:20:52 UTC+11, vadimkly...@gmail.com  wrote:
> пятница, 30 ноября 2018 г., 15:22:13 UTC пользователь alex.jo...@gmail.com 
> написал:
> > I've successfully build android-x86 7.1-r2 with gapps in whonix-14-ws AppVM.
> > You'll need 120GB for android-x86 sources and temp build files and 30GB for 
> > swap.
> > Extend private storage size to 160GB via GUI or in dom0:
> > qvm-volume extend android-builder:private 160g
> 
> You need 120GB + 30 GB or 160GB of space just to compile a AndroidVM? Am I 
> reading this right?

Hi,

Yes you need the 160GB of space. I accidentally ran it with less and it failed 
due to no space. 

-- 
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/20255960-30ec-4300-8407-b46f0b7c6994%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide

2019-02-19 Thread nosugarmaxtaste
Hi Alex,

Let me just start by saying a massive thank you. This guide has been great. I 
have used it for the 8.1 - Oreo - which was just changing:
 'repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b 
android-x86-7.1-r2' to 'repo init -u 
git://git.osdn.net/gitroot/android-x86/manifest -b oreo-x86.'

With 8.1, mouse support comes out the box and completing the last part of the 
guide actually makes the mouse worse in Oreo. So, disregard that part anyone 
following this guide for 8.1. You can change resolution by affixing 'vga=ask' 
and choosing your desired resolution 
(https://groups.google.com/forum/#!topic/qubes-users/KZm8aGJuiO0).

I have come across one issue, and I am wondering if you could help me. Android 
has installed great, and loads up fine. However, I simply cannot open the 
Settings app, as it crashes every single time. Others who have encountered this 
issue modified it using adb 
(https://stackoverflow.com/questions/3480201/how-do-you-install-an-apk-file-in-the-android-emulator?rq=1),
 but I don't know how to do this with a Qubes HVM. Any help with this?

Thanks in advance :)

-- 
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/66b1a620-8d3a-49b9-aa96-6294d81145cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Effectiveness of the VM compartimentation

2019-02-15 Thread nosugarmaxtaste
On Friday, 15 February 2019 16:37:17 UTC+11, Chris Laprise  wrote:
> On 2/14/19 10:02 PM, nosugarmaxta...@gmail.com wrote:
> > Hi all,
> > 
> > Right now I use Qubes for a bit of fun - setting up VPN's - chaining them, 
> > trying to get HVM's up and running, just messing about. I do plan to 
> > totally phase out my other OS's for it, but theres one thing that keeps 
> > going through my mind.. how isolated are the VM's from each other actually?
> > 
> > I know Qubes is 'reasonably' secure, but how secure? Could a whistle blower 
> > have a whonix VM open handling sensitive materials while at the same time 
> > have a personal VM with ISP connection and google/facebook/work sites open, 
> > with no issue at all? If the whistleblower would only be able to use the 
> > machine for sensitive purposes due to leak potentials, etc, wouldn't this 
> > make using Qubes pointless?
> 
> Of the myriad remote attacks that can be used against traditional 
> operating systems, basically one type is thought to be effective against 
> Qubes in general: Side-channel attacks.
> 
> https://en.wikipedia.org/wiki/Side-channel_attack
> 
> The best way to mitigate these is to not run public key crypto in 
> trusted VMs at the same time untrusted VMs are running (although this 
> can be a problem when VMs like sys-net and sys-usb are considered). 
> Also, test your hardware to see if its susceptible to rowhammer.
> 
> In contrast, even a physically isolated system can be less secure than a 
> Qubes system. This is because the devices and drivers used for 
> interfacing (SD cards, DVDs, USB drives - even occasionally) are much 
> more complex and vulnerable than the interfaces on a Qubes VM. And if a 
> Qubes VM does become compromised, chances are much better that the core 
> system and firmware will remain safe.
> 
> https://blog.invisiblethings.org/2014/08/26/physical-separation-vs-software.html
> 
> Finally, assuming that attacks will succeed at least occasionally (and 
> Qubes is built with this assumption for guest VMs): How recoverable is 
> the situation? A Windows system that had its firmware compromised will 
> continue to run malware even after the OS is wiped and re-installed. A 
> Qubes system OTOH probably has intact firmware and malware can be 
> removed by removing the affected VM.
> 
> -- 
> 
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

Thanks for the reply, Chris.

So, apart from the rare chance of a side-channel attack. One should be able to 
surf safely in Whonix, or a private VPN'd VM, while being able to surf regular 
sites such as this google hosted mail group on another without overlap, or the 
data from Whonix hitting a non-torified machine?

-- 
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/959953e2-7216-4af2-9251-10f1a433b82f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Effectiveness of the VM compartimentation

2019-02-14 Thread nosugarmaxtaste
Hi all,

Right now I use Qubes for a bit of fun - setting up VPN's - chaining them, 
trying to get HVM's up and running, just messing about. I do plan to totally 
phase out my other OS's for it, but theres one thing that keeps going through 
my mind.. how isolated are the VM's from each other actually?

I know Qubes is 'reasonably' secure, but how secure? Could a whistle blower 
have a whonix VM open handling sensitive materials while at the same time have 
a personal VM with ISP connection and google/facebook/work sites open, with no 
issue at all? If the whistleblower would only be able to use the machine for 
sensitive purposes due to leak potentials, etc, wouldn't this make using Qubes 
pointless?

Thanks.

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


[qubes-users] Re: Is it safe to install Qubes4 on laptop used windows10 before?

2019-02-14 Thread nosugarmaxtaste
When you format a HDD, whatever OS was on there previously is gone. Be it 
Windows, Qubes, or whatever. None of the windows phone home features will 
survive the format and you can happily install Qubes on the formated HDD. 

I really don't believe Microsoft is able to track your hardware, UUID, if 
you've installed Qubes. Nor would this effect your activities on Qubes anyway?

-- 
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/d228906b-1907-40de-81d7-74ceca04ab5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Valid Concerns Regarding Integrity of Whonix Project

2019-02-14 Thread nosugarmaxtaste
'This law was only recently introduced and is already being used to great 
effect according to recent reports.'

Great effect? Where are your sources? I can't take you seriously without proper 
sources. Gut feelings, suspicions, it all means nothing without evidence. 
Should we all bust out the tin foil while we're here, too?

In what ways could Whonix be modified to pose a threat to us? They can't modify 
Tor, and any change they do to the OS is in clear visibility. How will they 
back door it? Any existing case examples?


-- 
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/26996f92-b6f5-4132-a3b3-3d3e6cd1f736%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.