[qubes-users] Re: download new fedora-26

2017-11-26 Thread Roy Bernat
On Sunday, 26 November 2017 06:46:31 UTC-5, Frédéric Pierret (fepitre)  wrote:
> Le samedi 25 novembre 2017 13:02:33 UTC+1, Roy Bernat a écrit :
> > On Friday, 24 November 2017 07:17:44 UTC-5, Frédéric Pierret (fepitre)  
> > wrote:
> > > Le vendredi 24 novembre 2017 12:02:56 UTC+1, Yuraeitha a écrit :
> > > > On Thursday, November 23, 2017 at 6:39:26 AM UTC, Roy Bernat wrote:
> > > > > On Wednesday, 22 November 2017 11:11:17 UTC-5, Roy Bernat  wrote:
> > > > > > Hi 
> > > > > > 
> > > > > > i am trying to download fedora-26 but with no success . 
> > > > > > 
> > > > > > i succeeded a month ago but now i am getting nothing . 
> > > > > > 
> > > > > > any suggestions ? 
> > > > > > 
> > > > > > R
> > > > > 
> > > > > Thank for all answers . 
> > > > > 
> > > > > i am using qubes4.0 and i used to download the template using 
> > > > > 
> > > > >  Qubes-dom0-update command . 
> > > > > 
> > > > > manually download i tried to use wget but there is no wget availble 
> > > > > in dom 0 . 
> > > > > 
> > > > > R
> > > > 
> > > > Sorry for the extra day delay, here are my findings when I tried to 
> > > > install Fedora-26 again. 
> > > > 
> > > > Interestingly it now works for me, it did not some 2 weeks ago. 
> > > > I verified it on multiple Qubes 4 machines, all of them installed 
> > > > Fedora-26 perfectly fine now. 
> > > > 
> > > > Possibly something was fixed that changed that? 
> > > Yes there were some updates with respect to pulseaudio version notably.
> > > 
> > > > @Roy Bernat, have you tried running updates? Also the testing updates? 
> > > > Be careful with the testing updates though as they might break your 
> > > > system if unlucky, so backup first just in case. But there i a lot of 
> > > > packages in the dom0 testing repository atm. It's a possibility, that 
> > > > it might fix it, though it may also not fix it either.
> > I use to download it using update and --action=install but now it is not 
> > working ,
> 
> try in dom0: sudo qubes-dom0-update --action='clean all', and then, sudo 
> qubes-dom0-update qubes-template-fedora-26

didn't work for me .   it is very strange because i remember i did it . 
BTW   reinstall also didnt work due to error no such property root_img .  i 
thought i will succeed to clean the template . 
R

-- 
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/b59cd843-f761-4636-a35e-3314e5190de0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Random sudden reboots

2017-11-26 Thread Wael Nasreddine
I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard reboots in 
the last few hours, often around the time I start a VM. I do not see anything 
in the log.

P.S: I've been running Citrix XenServer for two years on this machine with no 
issues.

Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed for user 
root
Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 ses=2 
msg='op=PAM:session_close 
grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_
Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 ses=2 
msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" 
hostname=? addr=? 
Nov 26 22:36:38 dom0 kernel: audit: type=1106 audit(1511764598.490:447): 
pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close 
grantors=pam_keyinit,pam_limits,pam_keyi
Nov 26 22:36:38 dom0 kernel: audit: type=1104 audit(1511764598.490:448): 
pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix 
acct="root" exe="/us
Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: 
balance_when_enough_memory(xen_free_memory=97794733, 
total_mem_pref=5101760998.4, total_available_memory=60546306417.6)
Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: left_memory=24233992215 
acceptors_count=1
-- Reboot --
Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal (/run/log/journal/) 
is 8.0M, max 196.7M, 188.7M free.
Nov 26 22:38:00 dom0 kernel: Linux version 4.9.56-21.pvops.qubes.x86_64 
(user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 
SMP Wed Oct 18 00:2
Nov 26 22:38:00 dom0 kernel: Command line: placeholder 
root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro rootflags=subvol=root 
rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07-
Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 
floating point registers'
Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE 
registers'
Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX 
registers'
Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  
256
Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, context size 
is 832 bytes, using 'standard' format.
Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches.
Nov 26 22:38:00 dom0 kernel: Released 0 page(s)
Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map:
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x-0x0009bfff] 
usable
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0009c800-0x000f] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0010-0x67e1] 
usable
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e2-0x67e20fff] 
ACPI NVS
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e21000-0x67e6afff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e6b000-0x67ebcfff] 
usable
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67ebd000-0x68bedfff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x68bee000-0x6ee48fff] 
usable
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ee49000-0x6f7adfff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6f7ae000-0x6ff99fff] 
ACPI NVS
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ff9a000-0x6fffefff] 
ACPI data
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6000-0x6fff] 
usable
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x7000-0x77ff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xe000-0xefff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfe00-0xfe010fff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfec0-0xfec00fff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfed9-0xfed91fff] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfee0-0xfeef] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xff00-0x] 
reserved
Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0001-0x000191f95fff] 
usable

-- 
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/9959bd62-686c-4cd2-8d27-03f6f1b70478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: unable to start a freshly created VM (the first VM on a fresh install). Qubes 4.0-RC2

2017-11-26 Thread Wael Nasreddine
On Sunday, November 26, 2017 at 9:14:57 PM UTC-8, Yuraeitha wrote:
> On Monday, November 27, 2017 at 1:06:55 AM UTC, Wael Nasreddine wrote:
> > Hello,
> > 
> > I'm trying to create a Standalone VM to run ArchLinux dedicated for work, 
> > but the VM fails to start, and the following message appears in the journal:
> > 
> > Nov 26 16:48:13 dom0 qmemman.systemstate[2304]: Xen free = 48447639678 too 
> > small for satisfy assignments! assigned_but_unused=48423368750, 
> > domdict={'3': {'memory_maximum': 4194304000, 'slow_memset_react': False, 
> > 'no_progress': False, 'last_target': 4179545269, 'memory_current': 
> > 4181286912, 'id': '3', 'mem_used': 353308672, 'memory_actual': 4181286912}, 
> > '8': {'memory_maximum': 150994944, 'slow_memset_react': False, 
> > 'no_progress': False, 'last_target': 150994944, 'memory_current': 
> > 150994944, 'id': '8', 'mem_used': None, 'memory_actual': 150994944}, '1': 
> > {'memory_maximum': 419430400, 'slow_memset_react': False, 'no_progress': 
> > False, 'last_target': 402653184, 'memory_current': 417345536, 'id': '1', 
> > 'mem_used': None, 'memory_actual': 417345536}, '5': {'memory_maximum': 
> > 4194304000, 'slow_memset_react': False, 'no_progress': False, 
> > 'last_target': 4179396425, 'memory_current': 4181147648, 'id': '5', 
> > 'mem_used': 337453056, 'memory_actual': 4181147648}, '2': 
> > {'memory_maximum': 150994944, 'slow_memset_react': False, 'no_progress': 
> > False, 'last_target': 150994944, 'memory_current': 150994944, 'id': '2', 
> > 'mem_used': None, 'memory_actual': 150994944}, '0': {'memory_maximum': 
> > 68253908992, 'slow_memset_react': False, 'no_progress': False, 
> > 'last_target': 52683417646, 'memory_current': 4260048896, 'id': '0', 
> > 'mem_used': 929218560, 'memory_actual': 52683417646}, '11': 
> > {'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress': 
> > False, 'last_target': 401604608, 'memory_current': 419430400, 'id': '11', 
> > 'mem_used': None, 'memory_actual': 419430400}, '12': {'memory_maximum': 
> > 150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target': 
> > 150994944, 'memory_current': 150994944, 'id': '12', 'mem_used': None, 
> > 'memory_actual': 150994944}, '7': {'memory_maximum': 4194304000, 
> > 'slow_memset_react': False, 'no_progress': False, 'last_target': 
> > 4180124003, 'memory_current': 4181835776, 'id': '7', 'mem_used': 402833408, 
> > 'memory_actual': 4181835776}, '6': {'memory_maximum': 150994944, 
> > 'slow_memset_react': False, 'no_progress': False, 'last_target': 150994944, 
> > 'memory_current': 150994944, 'id': '6', 'mem_used': None, 'memory_actual': 
> > 150994944}, '4': {'memory_maximum': 150994944, 'slow_memset_react': False, 
> > 'no_progress': False, 'last_target': 150994944, 'memory_current': 
> > 150994944, 'id': '4', 'mem_used': None, 'memory_actual': 150994944}}
> > 
> > 
> > It seems to be a memory issue, which is weird given I have only the 
> > essentials + personal VM running on a 64Gb system.
> > 
> > I posted as many details about the issue and my system in this gist 
> > https://gist.github.com/kalbasit/cb3d6a0a9f068f819706d08fe073b18a
> > 
> > Am I doing it wrong or is there a problem with my installation?
> 
> I can't say if it'll work. However if this feature is turned on (should be by 
> default), maybe try disable the dynamic RAM allocation in the VM-preferences 
> GUI advanced tab, or with qvm-prefs in terminal?
> 
> It's similar with Windows VM atm, it seemingly has no Qubes tools inside the 
> VM, so it can't talk with it, and thereby not dynamically allocate any 
> memory. 
> 
> Maybe this is the fault?

Removing the dynamic memory did get rid of the error, but the VM is still dying 
on boot.

-- 
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/cd015faa-dd2b-4de9-9072-72457e0636a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: R4-rc2 consuming all my disk space (250MB)

2017-11-26 Thread Chris Laprise

On 11/26/2017 11:55 PM, Yuraeitha wrote:

On Sunday, November 26, 2017 at 10:05:46 PM UTC, Chris Laprise wrote:

I currently have 4GB remaining on my drive according to the 'lvs' based
script from issue #3240.

However, I know I don't have nearly that much in templates and data;
there was a lot more free space on Qubes 3.2. Also, adding up the DISK
column from qvm-ls shows I should have over 100GB free.

So I'm wondering if this is a real problem with R4 and what can be done
about it.

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

nvm, I found it.

Running 'rpm -aq | grep core-admin' in dom0, prints out the current 
qubes-core-admin-client version. Mine is 4.0.11-01. I'm fully updated to the 
testing repository. So since this was implemented in 4.0.12, we probably have 
to wait for that.


Thanks, but I found the underlying problem...

The dom0 root filesystem keeps allocating space because discard/TRIM 
isn't enabled by default. The output from lvs showed that root was 50% 
allocated, and since root is sized by the installer to be the same size 
as the disk, that means 100+GB was allocated (root fs contents were only 
4.5GB however).


An 'fstrim /' took care of the immediate problem and then I added 
'discard' option to /etc/fstab. I think this should be the default for 
new installs.


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3d17733b-657b-daaa-f012-49379435b60e%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] New install R3.2 - All VMs fail with libxenlight error

2017-11-26 Thread Gaijin
On 2017-11-27 05:23, Yuraeitha wrote:
> On Monday, November 27, 2017 at 5:01:36 AM UTC, pr0xy wrote:
>> On 2017-11-21 10:21, pr0xy wrote:
>> > I have a new workstation, 128GB RAM, Xeon with 10 cores, 1TB SSD, and
>> > I'm trying to get R3.2 running on it. VT-x and VT-d are enabled in the
>> > BIOS along with TPM. Had to set the machine to Legacy boot and turn off
>> > UEFI to install Qubes though.
>> >
>> > I've tried reinstalling Qubes a few times, but I get the same results.
>> > When trying to open any AppVM, and even the Fedora and Debian Templates,
>> > I get the error:
>> >
>> > internal error: libxenlight failed to create new domain
>> >
>> > In one of my tests I was able to get the default anon-whonix VM to work,
>> > but after a subsequent reinstall that is not working any longer.
>> >
>> > I'd really like to get Qubes working on this machine, but I'm not sure
>> > where to look.
>>
>> I tried setting up Qubes to do all updates thru Tor/Whonix. After
>> updating the base Qubes install, which took more than half a day, all
>> these errors went away.
> 
> You could try with Qubes 4 RC-3 instead of your Qubes 4 RC-2. It's
> supposed to come out today, the 27th November - looky here
> https://www.qubes-os.org/doc/releases/4.0/schedule/
> 
> But it's possibly to be postponed though, we'll have to see. 
> 
> Also, you made sure there are no additional virtualization settings in
> your BIOS? Some motherboards, not all, appears to have an extra
> setting, i.e. some Asus boards have both VT-d and Virtualisation,
> which both comes disabled by default.
> 
> You may not have that extra setting, but it can't hurt to be sure, at
> least this gives you a place to start until someone maybe posts better
> suggestions.

I'm on R3.2, not RC4 yet. I may wait until R4 comes out (maybe RC-3) to
play with that.

I was able to get past my problem, and now R3.2 works.

Turns out the R3.2 ISO needs a ton of updates before it would work on my
machine. Once I added the dom0 updates it started magically working. ;)

-- 
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/31455e97d4fc99fc9daf45f8e6641dae%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes in a corporate network behind HTTP proxy

2017-11-26 Thread pr0xy
On 2017-11-20 18:08, awokd wrote:
> On Mon, November 20, 2017 10:01, pr0xy wrote:
>> Please help a somewhat noob who wants to use Qubes in the office.
>>
>> I got the OK to try using Qubes R3.2 in my company network as a
>> workstation. They have a very restrictive proxy that forces all traffic
>> through an HTTP/HTTPS proxy like:
>>
>> proxy.example.com:8080
>>
>> How could I force all Qubes traffic to go through that proxy and that
>> port?
>>
>> Would that be in sys-net, or a Firewall VM?
> 
> Check https://www.qubes-os.org/doc/vpn/ . Ignore the parts about VPN setup
> but you should be able to set up your proxy redirect in the Proxy VM. I'm
> assuming local traffic like DNS lookups would not go through the proxy.

Thanks. I have been reading up on the ProxyVM, which seems to be the way
I would do this, but I'm a bit confused as to where I would add these
proxy settings. I'm not familiar with manipulating IP tables, or writing
the sort of scripts on that page, but is that what I would need to set?

I wanted to stay away from setting the environment variables for
http_proxy, https_proxy, ftp_proxy and no_proxy in each VM.  Ideally I
think I'd like to use a ProxyVM to proxify an entire AppVM, but the
documentation doesn't make it clear how I would attempt this. 

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


[qubes-users] Re: Yubikey in Challenge Response mode in Qubes 3.2

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 10:04:29 PM UTC, rob_66 wrote:
> Hi.
> 
> Can anybody confirm, set-up(s) described in the links below – thanks,
> mig5 ! – still work today, in completely updated Qubes 3.2, Yubikey Neo,
> usbVM Fedora 25?
> 
> I'm not interested in locking me out of the system. ;)
> 
> ( https://mig5.net/content/yubikey-challenge-response-mode-qubes )
> https://mig5.net/content/yubikey-2fa-qubes-redux-adding-backup-key
> 
> Cheers, thanks,
> 
> Rob

I believe to remember it mentioned somewhere that the hardware key is an 
additional login measure, so that you can use both password and a hardware key, 
interchangeably. Then you can make the password really long and complex, and 
keep it in a safe place. Then use your hardware key while on the go. (For 
example). For as long as both the password and the hardware key has good 
entropy and long, then it should be hard to crack open.

Whether this is correct or not, I do not have the time right now to check it, 
as I'm on my way out of the door. But maybe you can try search for this. 

Also maybe run a backup before you try anything too, so you got extra 
redundancy before trying this out.

-- 
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/4e286746-956f-44df-a3d6-b2e78d45a233%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] New install R3.2 - All VMs fail with libxenlight error

2017-11-26 Thread Yuraeitha
On Monday, November 27, 2017 at 5:01:36 AM UTC, pr0xy wrote:
> On 2017-11-21 10:21, pr0xy wrote:
> > I have a new workstation, 128GB RAM, Xeon with 10 cores, 1TB SSD, and
> > I'm trying to get R3.2 running on it. VT-x and VT-d are enabled in the
> > BIOS along with TPM. Had to set the machine to Legacy boot and turn off
> > UEFI to install Qubes though.
> > 
> > I've tried reinstalling Qubes a few times, but I get the same results.
> > When trying to open any AppVM, and even the Fedora and Debian Templates,
> > I get the error:
> > 
> > internal error: libxenlight failed to create new domain
> > 
> > In one of my tests I was able to get the default anon-whonix VM to work,
> > but after a subsequent reinstall that is not working any longer.
> > 
> > I'd really like to get Qubes working on this machine, but I'm not sure
> > where to look.
> 
> I tried setting up Qubes to do all updates thru Tor/Whonix. After
> updating the base Qubes install, which took more than half a day, all
> these errors went away.

You could try with Qubes 4 RC-3 instead of your Qubes 4 RC-2. It's supposed to 
come out today, the 27th November - looky here 
https://www.qubes-os.org/doc/releases/4.0/schedule/

But it's possibly to be postponed though, we'll have to see. 

Also, you made sure there are no additional virtualization settings in your 
BIOS? Some motherboards, not all, appears to have an extra setting, i.e. some 
Asus boards have both VT-d and Virtualisation, which both comes disabled by 
default. 

You may not have that extra setting, but it can't hurt to be sure, at least 
this gives you a place to start until someone maybe posts better suggestions. 

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


[qubes-users] Formatting and Permissions for internal HDDs

2017-11-26 Thread Gaijin
In R3.2 I have some additional internal hard drives in my PC. I wanted
to format them to be encrypted so that they will match the disk
encryption of my main Qubes disk install, and so that I won't have to
enter the disk password every time I access the drives or attach them to
a VM. I have not been able to figure this out. Is this possible?

My other issue is that whether I encrypt the drive partitions with LUKS
or just make a ext4 partition, I can't access the drives after creating
them because they're assigned ownership to the root account. Normal
Qubes use is thru the dom0 account or the user account on the VMs, not
root. What would be a good permissions setting to allow dom0 or a VM
access the hard drives? 

-- 
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/3bda050ef4e77df812d4b034383d7939%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: unable to start a freshly created VM (the first VM on a fresh install). Qubes 4.0-RC2

2017-11-26 Thread Yuraeitha
On Monday, November 27, 2017 at 1:06:55 AM UTC, Wael Nasreddine wrote:
> Hello,
> 
> I'm trying to create a Standalone VM to run ArchLinux dedicated for work, but 
> the VM fails to start, and the following message appears in the journal:
> 
> Nov 26 16:48:13 dom0 qmemman.systemstate[2304]: Xen free = 48447639678 too 
> small for satisfy assignments! assigned_but_unused=48423368750, domdict={'3': 
> {'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress': 
> False, 'last_target': 4179545269, 'memory_current': 4181286912, 'id': '3', 
> 'mem_used': 353308672, 'memory_actual': 4181286912}, '8': {'memory_maximum': 
> 150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target': 
> 150994944, 'memory_current': 150994944, 'id': '8', 'mem_used': None, 
> 'memory_actual': 150994944}, '1': {'memory_maximum': 419430400, 
> 'slow_memset_react': False, 'no_progress': False, 'last_target': 402653184, 
> 'memory_current': 417345536, 'id': '1', 'mem_used': None, 'memory_actual': 
> 417345536}, '5': {'memory_maximum': 4194304000, 'slow_memset_react': False, 
> 'no_progress': False, 'last_target': 4179396425, 'memory_current': 
> 4181147648, 'id': '5', 'mem_used': 337453056, 'memory_actual': 4181147648}, 
> '2': {'memory_maximum': 150994944, 'slow_memset_react': False, 'no_progress': 
> False, 'last_target': 150994944, 'memory_current': 150994944, 'id': '2', 
> 'mem_used': None, 'memory_actual': 150994944}, '0': {'memory_maximum': 
> 68253908992, 'slow_memset_react': False, 'no_progress': False, 'last_target': 
> 52683417646, 'memory_current': 4260048896, 'id': '0', 'mem_used': 929218560, 
> 'memory_actual': 52683417646}, '11': {'memory_maximum': 4194304000, 
> 'slow_memset_react': False, 'no_progress': False, 'last_target': 401604608, 
> 'memory_current': 419430400, 'id': '11', 'mem_used': None, 'memory_actual': 
> 419430400}, '12': {'memory_maximum': 150994944, 'slow_memset_react': False, 
> 'no_progress': False, 'last_target': 150994944, 'memory_current': 150994944, 
> 'id': '12', 'mem_used': None, 'memory_actual': 150994944}, '7': 
> {'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress': 
> False, 'last_target': 4180124003, 'memory_current': 4181835776, 'id': '7', 
> 'mem_used': 402833408, 'memory_actual': 4181835776}, '6': {'memory_maximum': 
> 150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target': 
> 150994944, 'memory_current': 150994944, 'id': '6', 'mem_used': None, 
> 'memory_actual': 150994944}, '4': {'memory_maximum': 150994944, 
> 'slow_memset_react': False, 'no_progress': False, 'last_target': 150994944, 
> 'memory_current': 150994944, 'id': '4', 'mem_used': None, 'memory_actual': 
> 150994944}}
> 
> 
> It seems to be a memory issue, which is weird given I have only the 
> essentials + personal VM running on a 64Gb system.
> 
> I posted as many details about the issue and my system in this gist 
> https://gist.github.com/kalbasit/cb3d6a0a9f068f819706d08fe073b18a
> 
> Am I doing it wrong or is there a problem with my installation?

I can't say if it'll work. However if this feature is turned on (should be by 
default), maybe try disable the dynamic RAM allocation in the VM-preferences 
GUI advanced tab, or with qvm-prefs in terminal?

It's similar with Windows VM atm, it seemingly has no Qubes tools inside the 
VM, so it can't talk with it, and thereby not dynamically allocate any memory. 

Maybe this is the fault?

-- 
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/b1e2d82b-cdd4-4737-9e02-c7323937a487%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: R3.2 Upgrading Fedora 25 --> 26 templates - PulseAudio issue

2017-11-26 Thread Gaijin
On 2017-11-20 08:39, Frédéric Pierret wrote:
> Le dimanche 19 novembre 2017 22:51:10 UTC+1, Gaijin a écrit :
>> On 2017-11-19 11:53, Frédéric Pierret wrote:
>> > For pulseaudio issue in Fedora 26, you need to enable the
>> > current-testing to update the qubes-gui-agent-linux for which the spec
>> > has been updated (see
>> > https://github.com/fepitre/qubes-gui-agent-linux/commit/251f5a4be505d6a268fd16bf15e33d9957c36b49).
>> > Also, if you want, you can build the Fedora 26 for R3.2 and soon
>> > Fedora 27 (see my post
>> > https://groups.google.com/d/msg/qubes-devel/MLjj0RNYTe8/H-85bI8cBQAJ).
>> >
>> > Do not hesitate to check what happen on the qubes-devel list notably
>> > for such problem related to newer version of Fedora.
>>
>> I see the documentation to enable current-testing in the VM
>> https://www.qubes-os.org/doc/software-update-vm/ and I assume that we
>> would add that in the upgrade step in the template somewhat like this:
>>
>> sudo dnf --releasever=26 distro-sync
>> --enablerepo=qubes-vm-fedora-26-current-testing
> It's only 'qubes-vm-r3.2-current-testing'.
> 
>> However, I don't seem to be able to guess the correct repo-name to add
>> in here. I get 'unknown repo' with "fedora-26", "fedora26", & "fc26".
>> How would I find the correct Repo name to put in here?

Thanks! That worked to get the Fedora 26 templates updated for me:

sudo dnf --releasever=26 distro-sync
--enablerepo=qubes-vm-r3.2-current-testing

I was able to update all my templates in R3.2 and they appear to be
working fine now.

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


[qubes-users] Re: R4-rc2 consuming all my disk space (250MB)

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 10:05:46 PM UTC, Chris Laprise wrote:
> I currently have 4GB remaining on my drive according to the 'lvs' based 
> script from issue #3240.
> 
> However, I know I don't have nearly that much in templates and data; 
> there was a lot more free space on Qubes 3.2. Also, adding up the DISK 
> column from qvm-ls shows I should have over 100GB free.
> 
> So I'm wondering if this is a real problem with R4 and what can be done 
> about it.
> 
> -- 
> 
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

What is puzzling however is that looking down in the status links in the last 
link above, it shows that the core-admin v4.0.12 (r4.0) was already build and 
uploaded to the testing repositories. 

I ran 
qubes-dom0-update --action='clean all' 
and 
qubes-dom-update --enablerepo=qubes-dom0-update-testing 

I still don't see the 4.0.12 version, that potentially proves this fix. What 
gives?

-- 
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/64bb7662-29a8-442d-aeb1-770891116bd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] New install R3.2 - All VMs fail with libxenlight error

2017-11-26 Thread pr0xy
On 2017-11-21 10:21, pr0xy wrote:
> I have a new workstation, 128GB RAM, Xeon with 10 cores, 1TB SSD, and
> I'm trying to get R3.2 running on it. VT-x and VT-d are enabled in the
> BIOS along with TPM. Had to set the machine to Legacy boot and turn off
> UEFI to install Qubes though.
> 
> I've tried reinstalling Qubes a few times, but I get the same results.
> When trying to open any AppVM, and even the Fedora and Debian Templates,
> I get the error:
> 
> internal error: libxenlight failed to create new domain
> 
> In one of my tests I was able to get the default anon-whonix VM to work,
> but after a subsequent reinstall that is not working any longer.
> 
> I'd really like to get Qubes working on this machine, but I'm not sure
> where to look.

I tried setting up Qubes to do all updates thru Tor/Whonix. After
updating the base Qubes install, which took more than half a day, all
these errors went away. 

-- 
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/45f456a1cbd03724e9a641999ce7857d%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4-rc2 consuming all my disk space (250MB)

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 10:05:46 PM UTC, Chris Laprise wrote:
> I currently have 4GB remaining on my drive according to the 'lvs' based 
> script from issue #3240.
> 
> However, I know I don't have nearly that much in templates and data; 
> there was a lot more free space on Qubes 3.2. Also, adding up the DISK 
> column from qvm-ls shows I should have over 100GB free.
> 
> So I'm wondering if this is a real problem with R4 and what can be done 
> about it.
> 
> -- 
> 
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

nvm, I found it.

Running 'rpm -aq | grep core-admin' in dom0, prints out the current 
qubes-core-admin-client version. Mine is 4.0.11-01. I'm fully updated to the 
testing repository. So since this was implemented in 4.0.12, we probably have 
to wait for that.

-- 
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/830d83a2-fd15-41d6-a13e-37f6eeaf3ae4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How To Replace Libvirt Drivers

2017-11-26 Thread Wael M. Nasreddine
On Sun, Nov 26, 2017 at 8:22 PM Person  wrote:

> On Saturday, November 25, 2017 at 11:11:30 PM UTC-5, Wael Nasreddine wrote:
> > On Saturday, November 25, 2017 at 8:06:27 PM UTC-8, Person wrote:
> > > “In an earlier install, after I got this error, I switched all VMs to
> using pv virt_mode and managed to get `qubes-dom0-update` to run, after
> doing that, I still got the same weird /proc/cpuinfo and lscpu output but
> VMs were booting OK with hvm.”
> > >
> > > How exactly do you switch VMs to using pv virt_mode? The only thing I
> actually want is for the VMs to book correctly, and that would save me a
> lot of trouble.
> >
> > sudo qvm-prefs  virt_mode pv
>
> I tried the command on my only HVM, and I received the message:
> ***Running the tool as root is strongly discouraged, this will lead you in
> permissions problems. Retry as unprivileged user or use "--force-root" to
> continue anyway.
> I wasn't using root user at the time, so I found that strange. And after I
> changed the HVM to pv virt_mode, I got the same virtualization error.
>
> I then tried the command on every single VM. I still received the
> "--force-root" message, but there were no other errors in the command. When
> I submitted the commands, I received lists of information about the VMs.
> And when I changed them to pv virt_mode, I still got the same
> virtualization error.
>
> (If dom0 doesn't say that the command was unsuccessful, it was successful,
> right? Otherwise, I may not have successfully set the VMs to pv virt_mode.)
>
> It seems that we have different versions of Qubes (you have Qubes 4.0 and
> I have Qubes 3.2), so I can see why your method might not work for me.
>
> My apologies, yes I'm running 4.0. My issue is not similar to yours
afterall, as I understand it (never tried R3) it defaults to PV anyway.


>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/qubes-users/Go04b5VsYfw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/c5a3a98e-70ab-4c31-b87a-5ad31c87d3eb%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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


[qubes-users] Re: R4-rc2 consuming all my disk space (250MB)

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 10:05:46 PM UTC, Chris Laprise wrote:
> I currently have 4GB remaining on my drive according to the 'lvs' based 
> script from issue #3240.
> 
> However, I know I don't have nearly that much in templates and data; 
> there was a lot more free space on Qubes 3.2. Also, adding up the DISK 
> column from qvm-ls shows I should have over 100GB free.
> 
> So I'm wondering if this is a real problem with R4 and what can be done 
> about it.
> 
> -- 
> 
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

I believe this in-depth thread discussion on github may be in particular useful 
for your disk issues, as it pretty much appears to be a discussion on your 
exact issue.
https://github.com/QubesOS/qubes-issues/issues/3240

I don't think it was clarified to only happen on 'LVM Thin Provisioning', or 
LVM in general, but it seems like 'LVM Thin Provisioning' might be the culprit 
here?

So the solution appears to be a missing design in Qubes 4, which means either
1) Use a series of commands to detect the missing pool spaces (question is 
still how to approach this method though).
2) Possibly (big maybe), re-insteall QUbes with LVM instead of LVM Thin 
Provisioning?
3) Wait for a possible update in the future, i.e. by adding disk space uses to 
the 'qvm-volume list' output, or similar solutions.

>From how I read it, it appears like the idea suggested late in the github 
>thread of using qvm-volume (for example 'qvm-volume list --all' or another 
>command?) to show the available total pool space and the total used pool 
>space, for each storage pool, has been adopted as a major (UX user experience) 
>bug in Qubes to-do in the Qubes 4 release (i.e. not waiting for Qubes 4.1. to 
>fix this). 

Albeit a brief read, I found the 'man qvm-volume' manual an intriguing read in 
combination to that github thread.

It also looks like Marek is working on implementing this approach into the 
qubes tools. If you scroll all down and follow the commit and reference trails. 
This looks really interesting.

This seems to have been implemented into the "core-admin v4.0.12 (r4.0)"
found here, https://github.com/QubesOS/updates-status/issues/313

This line specifically "QubesOS/qubes-core-admin@439d9b8 storage/lvm: fix 
importing different-sized volume from another pool" but notice the other volume 
change lines too.

If I'm not mistaken, the core-admin has not been released as of yet? So we have 
to wait for it to be released? At least I can't find it in my dom0 rpm search.

-- 
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/2c78eedb-2656-42be-9c17-e3d4e949d531%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-26 Thread Person
On Saturday, November 25, 2017 at 11:11:30 PM UTC-5, Wael Nasreddine wrote:
> On Saturday, November 25, 2017 at 8:06:27 PM UTC-8, Person wrote:
> > “In an earlier install, after I got this error, I switched all VMs to using 
> > pv virt_mode and managed to get `qubes-dom0-update` to run, after doing 
> > that, I still got the same weird /proc/cpuinfo and lscpu output but VMs 
> > were booting OK with hvm.”
> > 
> > How exactly do you switch VMs to using pv virt_mode? The only thing I 
> > actually want is for the VMs to book correctly, and that would save me a 
> > lot of trouble.
> 
> sudo qvm-prefs  virt_mode pv

I tried the command on my only HVM, and I received the message: 
***Running the tool as root is strongly discouraged, this will lead you in 
permissions problems. Retry as unprivileged user or use "--force-root" to 
continue anyway.
I wasn't using root user at the time, so I found that strange. And after I 
changed the HVM to pv virt_mode, I got the same virtualization error.

I then tried the command on every single VM. I still received the 
"--force-root" message, but there were no other errors in the command. When I 
submitted the commands, I received lists of information about the VMs. And when 
I changed them to pv virt_mode, I still got the same virtualization error. 

(If dom0 doesn't say that the command was unsuccessful, it was successful, 
right? Otherwise, I may not have successfully set the VMs to pv virt_mode.)

It seems that we have different versions of Qubes (you have Qubes 4.0 and I 
have Qubes 3.2), so I can see why your method might not work for me.
 

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


Re: [qubes-users] Re: will uninstalling a base template delete a clone of the template?

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 1:38:44 PM UTC, Unman wrote:
> On Sun, Nov 26, 2017 at 02:12:30AM -0800, Yuraeitha wrote:
> > On Sunday, November 26, 2017 at 9:38:03 AM UTC, Chris Laprise wrote:
> > > On 11/26/2017 04:26 AM, Yuraeitha wrote:
> > > > On Sunday, November 26, 2017 at 4:31:35 AM UTC, 
> > > > cybe...@national.shitposting.agency wrote:
> > > >> I recently made a kali template vm by cloning the qubes debian 8 
> > > >> template and converting it to kali.
> > > >>
> > > >> If I were to remove the base debian 8 template from dom0, would this 
> > > >> also remove the cloned kali template vm?
> > > >
> > > 
> > > The answer is No. Cloned templates are not dependent on each other.
> > > 
> > > If you have appVMs dependent on the debian-8 template, you'll have to 
> > > re-assign them to another template before you do the removal.
> > > 
> > > -- 
> > > 
> > > Chris Laprise, tas...@posteo.net
> > > https://github.com/tasket
> > > https://twitter.com/ttaskett
> > > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
> > 
> > Are you sure? or was it maybe changed in between older Qubes and current 
> > perhaps?
> > 
> > Also you're making a distinction between "qvm-remove" and "dnf remove" here?
> > 
> 
> Chris is absolutely right, and this is not dependent on Qubes version.
> 
> The difference between qvm-remove and dnf-remove is that you cannot
> remove a template installed using dnf by qubes-remove.
> SO if you have a base debian-8 template installed using
> qubes-dom0-update or at original install, then you must remove it using
> dnf remove.
> 
> If you have cloned a template you can remove the clone using qvm-remove,
> but NOT dnf remove.
> 
> As Chris says, you must make sure that you have no appVMs using the
> template you want to remove before you remove it. This applies whether
> you use a clone or not.
> 
> unman

aha, so the qvm-remove is there to handle the clones or backup-restoed VM's, 
and not just intended to be a single VM removal tool in regards to templates. 
While both understandings are similar, the slight misunderstanding in the 
variation between the two, can have quite the difference in certain impacts, 
indeed.

It's not that I have any doubts in what you said, but I had to go and try it 
out on a custom installed fedora-26 template, in order to beat the 
misunderstanding out of my self by doing it in practice. Cloned the template I 
planned to remove, and performed a "sudo dnf remove qubes-template-fedora-26", 
which indeed only removed the fedora-26, and left alone the clone thereof. 

Essentially I had to beat it out of my self, because the other understanding 
between the correct way of seeing it, and the wrong way of seeing it, are so 
close to each others that it can be tricky to make a lasting distinction. It 
seems so counter intuitive once the wrong interpretation has taken root.

I wonder how such misunderstandings, or false interpretations, can be avoided 
among the people, like me, who are learning about Qubes (and Linux in general). 
But that's something for another time and topic, but an interesting one 
nonetheless.

Thanks for the clarification btw, you nailed this one.

-- 
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/4279361a-0c25-4af6-9171-b51232318512%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: sys-whonix / tor / thunderbird

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 1:49:21 PM UTC, Unman wrote:
> On Sun, Nov 26, 2017 at 03:07:38AM -0800, Yuraeitha wrote:
> > On Friday, November 24, 2017 at 6:48:13 PM UTC, entr0py wrote:
> > > Yuraeitha:
> > > > On Friday, November 24, 2017 at 9:01:24 AM UTC, Bernhard wrote:
> > > >> Hello,
> > > >>
> > > >> one of the most useful features of tor-browser is Ctl-Shift-L to change
> > > >> the tor-path (and so, with high proba, the exit node IP) : this way,
> > > >> websites that block a specific exit node for a certain time can be 
> > > >> still
> > > >> loaded (of course some fascist websites block all tor-exits and so that
> > > >> this measure does not help) .
> > > >>
> > > >> I feel that the same feature would be useful in other applications (in
> > > >> particular in thunderbird). How can this be done? Maybe a "forced
> > > >> reconnect" of IMAP connections suffices, but apart totally restarting
> > > >> thunderbird I don't see how this can be done. Any hints? Or is there
> > > >> good reason not to torify mail-fetching? Or never via IMAP?
> > > >>
> > > >> thank you, Bernhard
> > > 
> > > Each request to your Tor client (in sys-whonix) via SocksPort is 
> > > accompanied by a SOCKS username and password. By clicking "New Tor 
> > > Circuit for this Site" in Tor Browser, you are changing the password 
> > > component, which causes the Tor client to generate a new circuit for the 
> > > same first-person domain when a request is received.
> > > 
> > > Thunderbird is torrified by an extension called TorBirdy. Your requested 
> > > feature has been tracked for quite some time (5 years) but appears 
> > > nearing implementation now that Thunderbird-related roadblocks have been 
> > > cleared. (https://trac.torproject.org/projects/tor/ticket/6359) Also, the 
> > > main reason for that ticket is not circuit swapping but stream isolation. 
> > > At present (Whonix bonus), each different email server you connect to is 
> > > given a different circuit. With #6359, multiple accounts at the same 
> > > email provider can also be isolated by circuit.
> > > 
> > > Currently, you can generate new circuits for all future Tor requests by 
> > > using the "New Identity" feature via one of the following equivalent 
> > > options:
> > > 1. From anon-whonix, use "New Identity" in Tor Browser. (applies to all 
> > > Tor connections, not just the browser.)
> > > 2. From sys-whonix, use arm/nyx (monitoring tool) to send New Identity 
> > > request
> > > 3. From sys-whonix, send SIGNAL NEWNYM via telnet to 127.0.0.1:9051
> > > 
> > > 
> > > > More specially towards the question at hand, I think it's tricky to do 
> > > > something like that in Thunderbird, but I'm not a programmer, so I 
> > > > wouldn't know for sure. However, if you think about how it works in 
> > > > Qubes/Whonix/Tor, then the Tor browser appears to be tunneling 
> > > > Tor-Browser within Tor(Sys-whonix), basically doubling the onion layers 
> > > > compared to a regular Tor browser. I'm not entirely sure if this is the 
> > > > case, it's just something I figured must be the case. 
> > > 
> > > This is not correct. Tor-over-Tor is discouraged[1] and unlikely to work 
> > > in the future[2]. Whonix prevents Tor-over-Tor.[3][4]
> > > 
> > > [1] 
> > > https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO#ToroverTor
> > > [2] https://trac.torproject.org/projects/tor/ticket/2667
> > > [3] https://www.whonix.org/wiki/DoNot#Prevent_Tor_over_Tor_Scenarios
> > > [4] https://www.whonix.org/wiki/Dev/anon-ws-disable-stacked-tor
> > 
> > ah, good I made a disclaimer :') 
> > Though, it does seem rather unsafe to run multiple of qubes over the same 
> > exit nodes in the Tor network. 
> > 
> > The most dangerous security issue out there, imho at least, is the 
> > assumption you are safe, when you are not. If what you're saying is true, 
> > and I'm confident it is given your background, then this might cause some 
> > dangerous user habits on Qubes in particular, beyond that what is a concern 
> > by using just Whonix/Tor? Similar issue probably exits between Whonix and 
> > Tor, but to a lesser extent as Qubes does not have any warnings about this, 
> > which is particular a concern when it's easier to mess up in Qubes, and run 
> > the same applications over the same exit nodes, at the same time. 
> > 
> > I did hear the warning of not running Tor over Tor before, though it was so 
> > long back that only the Tor browser was around back then. I had assumed 
> > it'd been fixed by now on Whonix and in particular Qubes. Especially 
> > considering the dangerous trap Whonix and in particular Qubes creates when 
> > running more on the same exit node. 
> > 
> 
> You misunderstand.
> It's not that qubes run over the same EXIT NODES, as you say.
> Because of stream isolation they may run over the same entry node, but have
> different circuits, so will probably exit Tor over different exit nodes. 
> 
> There is nothing to "fix" in Tor over Tor - you can do 

Re: [qubes-users] Qubes 3.2 only booting with onboard GPU ?? (ASUS KGPE-D16 + AMD Radeon 6450)

2017-11-26 Thread taii...@gmx.com

On 11/26/2017 04:47 PM, qubes...@openmailbox.org wrote:


Hi everyone,

I recently got an ASUS KGPE-D16 mainboard, since I read over here, that it 
would be fully compatible with Qubes OS.
Installation went fine, the only problem is the low screen resolution (VGA). 
Unfortunately, I can't get any external graphic cards to work.

As soon as I connect my graphic card to the mainboard (AMD Radeon 6450), the 
boot process halts shortly after I enter my LUKS password.
After entering my password, the boot screen switches back from graphics into 
text mode (black/white) with the following error message:

ERST:   Failed to get Error Log Address Range.
BERT:   Can't request iomem region 

_

And that's it.. Nothing happening from that point on. I can only reboot / force 
shutdown.

Overall, what I find weird as well, is that it takes much longer for the screen 
to get a video signal when the external GPU is plugged in. When I use the 
onboard VGA graphics, the screen reacts / shows the boot screen already a few 
seconds after booting compared to 30-40 seconds with external GPU ?? Any idea 
how to fix that as well ?

Important notes:

I upgraded the kernel in dom0 to the latest version. Although I didn't try any 
GPU with the old Kernel (4.4), thus I don't know if the issues are also present 
with the older kernel. Does anyone know ? I thought upgrading kernel would 
always increase hardware support.

I also tried to boot with a NVIDIA 980 GTX graphics card, I had exactly the 
same boot issue. So I guess it's nothing related to any NVIDIA/AMD driver 
issues.

Motherboard: ASUS KGPE-D16
GPU: AMD Radeon 6450
dom0 Kernel: 4.9.56-21

Thanks you for help!

So far I tried to use 2 different graphics cards, first a NVIDIA 980 GTX and 
then an AMD Radeon 6450.
The Radeon card is supposedly fully supported according to the Qubes and Xen 
Wiki's.
  
The problem is exactly the same for both cards, so I don't really believe it is an AMD/NVIDIA driver issue. But maybe I am wrong ?


I take it you are using coreboot? if you aren't you should, otherwise 
you need to change the "primary video" option in the BIOS - which will 
solve your issue.


--
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/24f0bd97-7d01-4e10-bd45-eebf77376463%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] some dom0 launcher options disappeared after upgrading to fedora 25

2017-11-26 Thread ehakanduran
Dear all,

Please treat me kindly since I am quite a newbie. I recently installed Qubes to 
my laptop and upgraded template VM from fedora 23 to 25, via 24. I just noticed 
that some options in qubes launcher (one indicated by the Q logo) disappeared, 
including opening a terminal and System Settings, both at dom0 level. I can 
still right click the desktop and open a terminal there, which would allow me 
do things I need to do, but would anyone happen to know how to repopulate those 
items in the launcher?

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/a6be9a45-a91b-4c4a-bb14-fd3f9e01a28c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] unable to start a freshly created VM (the first VM on a fresh install). Qubes 4.0-RC2

2017-11-26 Thread Wael Nasreddine
Hello,

I'm trying to create a Standalone VM to run ArchLinux dedicated for work, but 
the VM fails to start, and the following message appears in the journal:

Nov 26 16:48:13 dom0 qmemman.systemstate[2304]: Xen free = 48447639678 too 
small for satisfy assignments! assigned_but_unused=48423368750, domdict={'3': 
{'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress': 
False, 'last_target': 4179545269, 'memory_current': 4181286912, 'id': '3', 
'mem_used': 353308672, 'memory_actual': 4181286912}, '8': {'memory_maximum': 
150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target': 
150994944, 'memory_current': 150994944, 'id': '8', 'mem_used': None, 
'memory_actual': 150994944}, '1': {'memory_maximum': 419430400, 
'slow_memset_react': False, 'no_progress': False, 'last_target': 402653184, 
'memory_current': 417345536, 'id': '1', 'mem_used': None, 'memory_actual': 
417345536}, '5': {'memory_maximum': 4194304000, 'slow_memset_react': False, 
'no_progress': False, 'last_target': 4179396425, 'memory_current': 4181147648, 
'id': '5', 'mem_used': 337453056, 'memory_actual': 4181147648}, '2': 
{'memory_maximum': 150994944, 'slow_memset_react': False, 'no_progress': False, 
'last_target': 150994944, 'memory_current': 150994944, 'id': '2', 'mem_used': 
None, 'memory_actual': 150994944}, '0': {'memory_maximum': 68253908992, 
'slow_memset_react': False, 'no_progress': False, 'last_target': 52683417646, 
'memory_current': 4260048896, 'id': '0', 'mem_used': 929218560, 
'memory_actual': 52683417646}, '11': {'memory_maximum': 4194304000, 
'slow_memset_react': False, 'no_progress': False, 'last_target': 401604608, 
'memory_current': 419430400, 'id': '11', 'mem_used': None, 'memory_actual': 
419430400}, '12': {'memory_maximum': 150994944, 'slow_memset_react': False, 
'no_progress': False, 'last_target': 150994944, 'memory_current': 150994944, 
'id': '12', 'mem_used': None, 'memory_actual': 150994944}, '7': 
{'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress': 
False, 'last_target': 4180124003, 'memory_current': 4181835776, 'id': '7', 
'mem_used': 402833408, 'memory_actual': 4181835776}, '6': {'memory_maximum': 
150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target': 
150994944, 'memory_current': 150994944, 'id': '6', 'mem_used': None, 
'memory_actual': 150994944}, '4': {'memory_maximum': 150994944, 
'slow_memset_react': False, 'no_progress': False, 'last_target': 150994944, 
'memory_current': 150994944, 'id': '4', 'mem_used': None, 'memory_actual': 
150994944}}


It seems to be a memory issue, which is weird given I have only the essentials 
+ personal VM running on a 64Gb system.

I posted as many details about the issue and my system in this gist 
https://gist.github.com/kalbasit/cb3d6a0a9f068f819706d08fe073b18a

Am I doing it wrong or is there a problem with my installation?

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


[qubes-users] R4-rc2 consuming all my disk space (250MB)

2017-11-26 Thread Chris Laprise
I currently have 4GB remaining on my drive according to the 'lvs' based 
script from issue #3240.


However, I know I don't have nearly that much in templates and data; 
there was a lot more free space on Qubes 3.2. Also, adding up the DISK 
column from qvm-ls shows I should have over 100GB free.


So I'm wondering if this is a real problem with R4 and what can be done 
about it.


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

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


[qubes-users] Yubikey in Challenge Response mode in Qubes 3.2

2017-11-26 Thread rob_66
Hi.

Can anybody confirm, set-up(s) described in the links below – thanks,
mig5 ! – still work today, in completely updated Qubes 3.2, Yubikey Neo,
usbVM Fedora 25?

I'm not interested in locking me out of the system. ;)

( https://mig5.net/content/yubikey-challenge-response-mode-qubes )
https://mig5.net/content/yubikey-2fa-qubes-redux-adding-backup-key

Cheers, thanks,

Rob

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


[qubes-users] Qubes 3.2 only booting with onboard GPU ?? (ASUS KGPE-D16 + AMD Radeon 6450)

2017-11-26 Thread qubesfan
Hi everyone,

I recently got an ASUS KGPE-D16 mainboard, since I read over here, that it 
would be fully compatible with Qubes OS.
Installation went fine, the only problem is the low screen resolution (VGA). 
Unfortunately, I can't get any external graphic cards to work.

As soon as I connect my graphic card to the mainboard (AMD Radeon 6450), the 
boot process halts shortly after I enter my LUKS password.
After entering my password, the boot screen switches back from graphics into 
text mode (black/white) with the following error message:

ERST:   Failed to get Error Log Address Range.
BERT:   Can't request iomem region 

_

And that's it.. Nothing happening from that point on. I can only reboot / force 
shutdown.

Overall, what I find weird as well, is that it takes much longer for the screen 
to get a video signal when the external GPU is plugged in. When I use the 
onboard VGA graphics, the screen reacts / shows the boot screen already a few 
seconds after booting compared to 30-40 seconds with external GPU ?? Any idea 
how to fix that as well ?

Important notes:

I upgraded the kernel in dom0 to the latest version. Although I didn't try any 
GPU with the old Kernel (4.4), thus I don't know if the issues are also present 
with the older kernel. Does anyone know ? I thought upgrading kernel would 
always increase hardware support.

I also tried to boot with a NVIDIA 980 GTX graphics card, I had exactly the 
same boot issue. So I guess it's nothing related to any NVIDIA/AMD driver 
issues.

Motherboard: ASUS KGPE-D16
GPU: AMD Radeon 6450
dom0 Kernel: 4.9.56-21

Thanks you for help!






So far I tried to use 2 different graphics cards, first a NVIDIA 980 GTX and 
then an AMD Radeon 6450.
The Radeon card is supposedly fully supported according to the Qubes and Xen 
Wiki's.
 
The problem is exactly the same for both cards, so I don't really believe it is 
an AMD/NVIDIA driver issue. But maybe I am wrong ?

-- 
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/20171126214729.B84A14E000E%40mta-1.openmailbox.og.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: update dom0 offline

2017-11-26 Thread Wael Nasreddine
On Sunday, November 26, 2017 at 1:12:49 AM UTC-8, Yuraeitha wrote:
> On Saturday, November 25, 2017 at 6:33:29 PM UTC, Wael Nasreddine wrote:
> > Hello,
> > 
> > As I described in the other topic titled "How To Replace Libvirt Drivers"; 
> > Upon installation, I get the error `libvirtError.libvirt: libxenlight 
> > failed to create new domain “domain name”` and updating the system seems to 
> > have helped. I want to attempt to update all packages before continuing the 
> > initial_setup, so how can I update dom0 offline?
> > 
> > Another option I have is to perform a net-install, I tried using 
> > `https://mirrors.kernel.org/qubes/repo/yum/r4.0/current-testing/dom0/fc25/` 
> > as an additional repository in the installer but I got "Error setting up 
> > base repository".
> > 
> > Wael
> 
> Do you have any solid reasoning for suspecting these packages? It's not 
> always the package itself that is the problem, but a package or a tie to 
> another patckage, or that other package, which is causing the issue. Simply 
> replacing libvirt probably won't do you much good, especially if you need to 
> find all those possible dependencies on something so fundamental as libvirt 
> in Qubes.
> 
> It might be better to first find out why it happens, and then perform a clean 
> re-install. 

So after some 10 re-installs, I finally managed to get it error-free all the 
way. I do not know which package it is (although I can tell you libvirt was not 
updated) but there is definitely a broken package in RC2. I ended up 
brute-forcing the virt_mode to PV[0] in order to go through the setup without 
any errors; knowing how to switch the default to PV would have helped, 
unfortunately I'm fairely new to Qubes (first install). Once the initial setup 
was over, I performed a qubes-dom0-update with testing repo enabled, switched 
all VMs back to hvm and voila works like a charm.

> 
> Also Qubes 4 RC-3 will be out either tomorrow, the day after tomorrow, or if 
> freezing failed, then possibly next week. 
> https://www.qubes-os.org/doc/releases/4.0/schedule/ It's uncertain for sure, 
> however, you have reasonable chances are that it'll be out tomorrow.
> 

I'm sure RC-3 would work out of the box, too bad I got stubborn on getting it 
running this weekend :D

> However, are you sure you got VT-D enabled in your UEFI (BIOS)? You also 
> enabled Virtualisation in general, in case the motherboard has a double 
> enable/disable function like some boards do? Libvirt errors does sound like 
> it could be related to missing hardware features that Qubes 4 requires. 
> 
> Remember that Qubes 4 is much less happy with missing security features, 
> compared to Qubes 3.2. You muight get Qubes 4 running without, but it will 
> likely be ugly, i.e. like your libvirt errors. 
> 
> There is even talks to prevent Qubes 4 to install at all if the hardware is 
> not living up to the security requirements, in order to avoid situations like 
> this. For example, something like that might even be in Qubes 4 RC-3 for all 
> we know.

My hardware is good, but I do not have a TPM yet. I'm thinking of switching the 
motherboard/CPU with something more performant, maybe a Xeon based system but I 
want to play more with Qubes before I do that. Any recommendation on hardware?

> 
> You made absolutely sure, that your hardware meets the requirements, and also 
> absolutely sure, that all of them are enabled?

Yes :)

[0]: while true; do qvm-ls | grep -v NAME | awk '{print $1}' | xargs -I{} sudo 
qvm-prefs {} virt_mode pv; sleep 0.5; done

-- 
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/893d6e91-ca42-428a-a5d2-bade68bd96e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - ASRock Z170 Pro4 - i7-6700k

2017-11-26 Thread Wael Nasreddine
On Sunday, November 26, 2017 at 2:59:21 AM UTC-8, Yuraeitha wrote:
> On Sunday, November 26, 2017 at 6:38:01 AM UTC, Wael Nasreddine wrote:
> > Just installed Qubes 4.0-RC2. I had issues with the installation (was 
> > getting libvirt errors), I solved the errors by temporarily switching all 
> > VMs to PV, update dom0 and restore them back to HVM.
> 
> I got Qubes 4 RC-2 running on a similar motherboard for someone else, the 
> Asus z170 Pro Gaming. I don't use this system actively my self, but it ran 
> smoothly from the hours I used to set it all up and to configure it, and it 
> had no libvirt errors. 
> 
> So the basic chipset features of the z170 line should not be an issue, and 
> you got immou enabled in your HCL rapport file, so I assume your VT-d must be 
> enabled in your UEFI (BIOS). Also the processor doesn't look like an issue 
> either.
> 
> However, I remember this particular motherboard had two separate places to 
> activate the virtualisation technology, you may have only enabled one of them 
> in the UEFI? Both settings came disabled on the Asus z170 Pro Gaming board I 
> set up with Qubes 4.
> 
> In your UEFI Advanced menu, try look for both:
> - VT-d. (I suspect this is the one you enabled). 
> - Virtualization (something closely worded to this, I suspect this might be 
> the setting you miss to enable).
> 
> So if the two boards are anything alike, then this might be it. If you can't 
> find this extra setting, then perhaps your model is different and it doesn't 
> have it extra required step. But it may very well be similar.

Yes, there are two places to enable on this motherboard, both in Advanced 
settings, one under CPU configuration and another one under Chipset 
configuration and they are both enabled.

-- 
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/f06bc5da-cc0c-4fd8-bea4-5fdbc318d120%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-convert-img: ValueError: No icon received

2017-11-26 Thread Unman
On Sun, Nov 26, 2017 at 04:52:04PM +, Holger Levsen wrote:
> On Sun, Nov 26, 2017 at 04:40:08PM +, Unman wrote:
> > On Sun, Nov 26, 2017 at 04:22:04PM +, Holger Levsen wrote:
> > > on 3.2:
> 
> using debian-9 I should have said too…
> 
> > > $ qvm-convert-img image.jpg image_clean.jpg
> [...]
> > > ValueError: No icon received
> > > 
> > > which package do I need to install where?
> > It's a bug Holger.
> > Scoot on over to GitHub and raise an issue
> 
> is it really? I cannot believe it's broken (in 3.2) and noone has raised
> an issue yet…
> 
> 
> -- 
> cheers,
>   Holger

Well someone has to be first :-)

truth , I dont think that many people use the feature.
But this is a bug for sure - same in deb8 and Fedora, at least for my
3.2

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


Re: [qubes-users] qvm-convert-img: ValueError: No icon received

2017-11-26 Thread Holger Levsen
On Sun, Nov 26, 2017 at 04:40:08PM +, Unman wrote:
> On Sun, Nov 26, 2017 at 04:22:04PM +, Holger Levsen wrote:
> > on 3.2:

using debian-9 I should have said too…

> > $ qvm-convert-img image.jpg image_clean.jpg
[...]
> > ValueError: No icon received
> > 
> > which package do I need to install where?
> It's a bug Holger.
> Scoot on over to GitHub and raise an issue

is it really? I cannot believe it's broken (in 3.2) and noone has raised
an issue yet…


-- 
cheers,
Holger

-- 
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/20171126165204.4pjwysrbqrwv72s3%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature


[qubes-users] qvm-convert-img: ValueError: No icon received

2017-11-26 Thread Holger Levsen
hi,

on 3.2:

$ qvm-convert-img image.jpg image_clean.jpg
Traceback (most recent call last):
  File "/usr/lib/qubes/qimg-convert-client", line 47, in 
main()
  File "/usr/lib/qubes/qimg-convert-client", line 41, in main
img = qubes.imgconverter.Image.get_through_dvm(args.src)
  File "/usr/lib/python2.7/dist-packages/qubes/imgconverter.py", line 207, in 
get_through_dvm
return cls.get_from_stream(sys.stdin, **kwargs)
  File "/usr/lib/python2.7/dist-packages/qubes/imgconverter.py", line 131, in 
get_from_stream
raise ValueError('No icon received')
ValueError: No icon received

which package do I need to install where?


-- 
cheers,
Holger

-- 
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/20171126162204.vqqb4feb5xdtjtlk%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature


Re: [qubes-users] how to forward webcam to a VM?

2017-11-26 Thread awokd
On Sun, November 26, 2017 15:13, evo wrote:
>
>
> Am 26.11.2017 um 16:10 schrieb Unman:
>> On Sun, Nov 26, 2017 at 01:04:39PM +0100, evo wrote:

>>> Hey! Thanks!
>>> i installed qubes-usb-proxy on the webcam-VM and tried to attach it
>>> there, but i get this error: "device attach failed: Invalid speed
>>> received"
>>>
>>> find nothing about such error in the docs.
>>
>> Which Qubes version are you using?
>>
>> What's the device you are trying to use?
>> Can you provde more information?
>>
>> This is an error that has been reported before and there's an open
>> ticket on qubes issues.
>> It seems to be device and circumstance dependent. (e.g an android in
>> debug mode throws this error but the same device NOT in debug mode
>> attaches properly.)
>>
>
>
> i use qubes 3.2
> and i try to use logitech hd C920 webcam
>
> i found some postings to such kind of error, yes... and it seems to be a
> bug, isn't it?
>
> So there is no chance to solve it?

Might be fixed in 4.0 or a future version, but as a temporary workaround
for problem USB devices like that you can assign an entire USB controller
to your webcam-VM. It's not as nice because you lose isolation for that
controller but it should work. If you want to try it, unplug all
unnecessary USB devices. Shutdown both webcam-VM and sys-usb. Look in
sys-usb device list for a USB controller, note the number, remove from
selected list. Add it to webcam-VM Devices, and uncheck Include in memory
balancing in Advanced. You might also need to up the initial memory while
you are in here, try 1024 MB.

Start webcam-VM. Each USB controller only handles some of the USB ports,
so it might be trial and error to find one that handles the empty port you
are plugging the webcam into. Once you figure out which USB port or ports
are now assigned to the webcam-VM, try to avoid plugging anything else
into them besides the webcam.


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


Re: [qubes-users] how to forward webcam to a VM?

2017-11-26 Thread evo


Am 26.11.2017 um 16:10 schrieb Unman:
> On Sun, Nov 26, 2017 at 01:04:39PM +0100, evo wrote:
>>
>>
>> Am 26.11.2017 um 00:58 schrieb awokd:
>>> On Sat, November 25, 2017 16:46, evo wrote:
>>>
 I have connected a webcam and i see it via lsusb on sys-usb. I also can
 use it with "cheese" programm on the sys-usb-VM. But how can i forward
 it to webcam-VM and use it there??
>>>
>>> Many webcams can be used over USB proxy. From dom0, enter "qvm-usb" with
>>> the webcam connected. You should see a list of available USB devices,
>>> including the webcam. From there, you'd enter "qvm-usb -a webcam-VM
>>> sys-usb:12.3". Use the correct name for your VM and sys-usb:device
>>> identifier for your webcam.
>>>
>>> See https://www.qubes-os.org/doc/usb/ for more instructions.
>>>
>>>
>>
>>
>> Hey! Thanks!
>> i installed qubes-usb-proxy on the webcam-VM and tried to attach it
>> there, but i get this error: "device attach failed: Invalid speed received"
>>
>> find nothing about such error in the docs.
> 
> Which Qubes version are you using?
> 
> What's the device you are trying to use?
> Can you provde more information?
> 
> This is an error that has been reported before and there's an open
> ticket on qubes issues.
> It seems to be device and circumstance dependent. (e.g an android in
> debug mode throws this error but the same device NOT in debug mode
> attaches properly.)
> 


i use qubes 3.2
and i try to use logitech hd C920 webcam

i found some postings to such kind of error, yes... and it seems to be a
bug, isn't it?

So there is no chance to solve 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/369c1722-e005-dbde-0f40-69e3da6f1c64%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] how to forward webcam to a VM?

2017-11-26 Thread Unman
On Sun, Nov 26, 2017 at 01:04:39PM +0100, evo wrote:
> 
> 
> Am 26.11.2017 um 00:58 schrieb awokd:
> > On Sat, November 25, 2017 16:46, evo wrote:
> > 
> >> I have connected a webcam and i see it via lsusb on sys-usb. I also can
> >> use it with "cheese" programm on the sys-usb-VM. But how can i forward
> >> it to webcam-VM and use it there??
> > 
> > Many webcams can be used over USB proxy. From dom0, enter "qvm-usb" with
> > the webcam connected. You should see a list of available USB devices,
> > including the webcam. From there, you'd enter "qvm-usb -a webcam-VM
> > sys-usb:12.3". Use the correct name for your VM and sys-usb:device
> > identifier for your webcam.
> > 
> > See https://www.qubes-os.org/doc/usb/ for more instructions.
> > 
> > 
> 
> 
> Hey! Thanks!
> i installed qubes-usb-proxy on the webcam-VM and tried to attach it
> there, but i get this error: "device attach failed: Invalid speed received"
> 
> find nothing about such error in the docs.

Which Qubes version are you using?

What's the device you are trying to use?
Can you provde more information?

This is an error that has been reported before and there's an open
ticket on qubes issues.
It seems to be device and circumstance dependent. (e.g an android in
debug mode throws this error but the same device NOT in debug mode
attaches properly.)

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


Re: [qubes-users] Re: sys-whonix / tor / thunderbird

2017-11-26 Thread Unman
On Sun, Nov 26, 2017 at 03:07:38AM -0800, Yuraeitha wrote:
> On Friday, November 24, 2017 at 6:48:13 PM UTC, entr0py wrote:
> > Yuraeitha:
> > > On Friday, November 24, 2017 at 9:01:24 AM UTC, Bernhard wrote:
> > >> Hello,
> > >>
> > >> one of the most useful features of tor-browser is Ctl-Shift-L to change
> > >> the tor-path (and so, with high proba, the exit node IP) : this way,
> > >> websites that block a specific exit node for a certain time can be still
> > >> loaded (of course some fascist websites block all tor-exits and so that
> > >> this measure does not help) .
> > >>
> > >> I feel that the same feature would be useful in other applications (in
> > >> particular in thunderbird). How can this be done? Maybe a "forced
> > >> reconnect" of IMAP connections suffices, but apart totally restarting
> > >> thunderbird I don't see how this can be done. Any hints? Or is there
> > >> good reason not to torify mail-fetching? Or never via IMAP?
> > >>
> > >> thank you, Bernhard
> > 
> > Each request to your Tor client (in sys-whonix) via SocksPort is 
> > accompanied by a SOCKS username and password. By clicking "New Tor Circuit 
> > for this Site" in Tor Browser, you are changing the password component, 
> > which causes the Tor client to generate a new circuit for the same 
> > first-person domain when a request is received.
> > 
> > Thunderbird is torrified by an extension called TorBirdy. Your requested 
> > feature has been tracked for quite some time (5 years) but appears nearing 
> > implementation now that Thunderbird-related roadblocks have been cleared. 
> > (https://trac.torproject.org/projects/tor/ticket/6359) Also, the main 
> > reason for that ticket is not circuit swapping but stream isolation. At 
> > present (Whonix bonus), each different email server you connect to is given 
> > a different circuit. With #6359, multiple accounts at the same email 
> > provider can also be isolated by circuit.
> > 
> > Currently, you can generate new circuits for all future Tor requests by 
> > using the "New Identity" feature via one of the following equivalent 
> > options:
> > 1. From anon-whonix, use "New Identity" in Tor Browser. (applies to all Tor 
> > connections, not just the browser.)
> > 2. From sys-whonix, use arm/nyx (monitoring tool) to send New Identity 
> > request
> > 3. From sys-whonix, send SIGNAL NEWNYM via telnet to 127.0.0.1:9051
> > 
> > 
> > > More specially towards the question at hand, I think it's tricky to do 
> > > something like that in Thunderbird, but I'm not a programmer, so I 
> > > wouldn't know for sure. However, if you think about how it works in 
> > > Qubes/Whonix/Tor, then the Tor browser appears to be tunneling 
> > > Tor-Browser within Tor(Sys-whonix), basically doubling the onion layers 
> > > compared to a regular Tor browser. I'm not entirely sure if this is the 
> > > case, it's just something I figured must be the case. 
> > 
> > This is not correct. Tor-over-Tor is discouraged[1] and unlikely to work in 
> > the future[2]. Whonix prevents Tor-over-Tor.[3][4]
> > 
> > [1] https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO#ToroverTor
> > [2] https://trac.torproject.org/projects/tor/ticket/2667
> > [3] https://www.whonix.org/wiki/DoNot#Prevent_Tor_over_Tor_Scenarios
> > [4] https://www.whonix.org/wiki/Dev/anon-ws-disable-stacked-tor
> 
> ah, good I made a disclaimer :') 
> Though, it does seem rather unsafe to run multiple of qubes over the same 
> exit nodes in the Tor network. 
> 
> The most dangerous security issue out there, imho at least, is the assumption 
> you are safe, when you are not. If what you're saying is true, and I'm 
> confident it is given your background, then this might cause some dangerous 
> user habits on Qubes in particular, beyond that what is a concern by using 
> just Whonix/Tor? Similar issue probably exits between Whonix and Tor, but to 
> a lesser extent as Qubes does not have any warnings about this, which is 
> particular a concern when it's easier to mess up in Qubes, and run the same 
> applications over the same exit nodes, at the same time. 
> 
> I did hear the warning of not running Tor over Tor before, though it was so 
> long back that only the Tor browser was around back then. I had assumed it'd 
> been fixed by now on Whonix and in particular Qubes. Especially considering 
> the dangerous trap Whonix and in particular Qubes creates when running more 
> on the same exit node. 
> 

You misunderstand.
It's not that qubes run over the same EXIT NODES, as you say.
Because of stream isolation they may run over the same entry node, but have
different circuits, so will probably exit Tor over different exit nodes. 

There is nothing to "fix" in Tor over Tor - you can do this if you wish,
(except in Whonix), but the behaviour carries risks.

If you are concered about running qubes over the same ENTRY node then
you can use different TorVMs or Whonix-gws as proxies for different sets
of qubes, so ensuring complete 

Re: [qubes-users] will uninstalling a base template delete a clone of the template?

2017-11-26 Thread Unman
On Sat, Nov 25, 2017 at 08:31:35PM -0800, cyberian@national.shitposting.agency 
wrote:
> I recently made a kali template vm by cloning the qubes debian 8 template and 
> converting it to kali.
> 
> If I were to remove the base debian 8 template from dom0, would this also 
> remove the cloned kali template vm?
> 

The short answer: NO

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


Re: [qubes-users] Re: will uninstalling a base template delete a clone of the template?

2017-11-26 Thread Unman
On Sun, Nov 26, 2017 at 02:12:30AM -0800, Yuraeitha wrote:
> On Sunday, November 26, 2017 at 9:38:03 AM UTC, Chris Laprise wrote:
> > On 11/26/2017 04:26 AM, Yuraeitha wrote:
> > > On Sunday, November 26, 2017 at 4:31:35 AM UTC, 
> > > cybe...@national.shitposting.agency wrote:
> > >> I recently made a kali template vm by cloning the qubes debian 8 
> > >> template and converting it to kali.
> > >>
> > >> If I were to remove the base debian 8 template from dom0, would this 
> > >> also remove the cloned kali template vm?
> > >
> > 
> > The answer is No. Cloned templates are not dependent on each other.
> > 
> > If you have appVMs dependent on the debian-8 template, you'll have to 
> > re-assign them to another template before you do the removal.
> > 
> > -- 
> > 
> > Chris Laprise, tas...@posteo.net
> > https://github.com/tasket
> > https://twitter.com/ttaskett
> > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
> 
> Are you sure? or was it maybe changed in between older Qubes and current 
> perhaps?
> 
> Also you're making a distinction between "qvm-remove" and "dnf remove" here?
> 

Chris is absolutely right, and this is not dependent on Qubes version.

The difference between qvm-remove and dnf-remove is that you cannot
remove a template installed using dnf by qubes-remove.
SO if you have a base debian-8 template installed using
qubes-dom0-update or at original install, then you must remove it using
dnf remove.

If you have cloned a template you can remove the clone using qvm-remove,
but NOT dnf remove.

As Chris says, you must make sure that you have no appVMs using the
template you want to remove before you remove it. This applies whether
you use a clone or not.

unman

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


[qubes-users] Re: HCL - X220 (Coreboot - SeaBios + Coreinfo, Qubes Release 4.0-rc2)

2017-11-26 Thread Finsh
Am Samstag, 25. November 2017 15:59:06 UTC+1 schrieb oowo...@gmail.com:
> Hi, Qubes work out of box. Strange, TPM chip in coreboot enabled, but Qubes 
> didn't find it. Laptop cost 140$ , lol.

That is because of a bug in SEAbios.if you need TPM, you should use a payload 
like Grub.

cheers

-- 
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/185a8f67-f310-47a2-9755-b0a049f69b3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] how to forward webcam to a VM?

2017-11-26 Thread evo


Am 26.11.2017 um 00:58 schrieb awokd:
> On Sat, November 25, 2017 16:46, evo wrote:
> 
>> I have connected a webcam and i see it via lsusb on sys-usb. I also can
>> use it with "cheese" programm on the sys-usb-VM. But how can i forward
>> it to webcam-VM and use it there??
> 
> Many webcams can be used over USB proxy. From dom0, enter "qvm-usb" with
> the webcam connected. You should see a list of available USB devices,
> including the webcam. From there, you'd enter "qvm-usb -a webcam-VM
> sys-usb:12.3". Use the correct name for your VM and sys-usb:device
> identifier for your webcam.
> 
> See https://www.qubes-os.org/doc/usb/ for more instructions.
> 
> 


Hey! Thanks!
i installed qubes-usb-proxy on the webcam-VM and tried to attach it
there, but i get this error: "device attach failed: Invalid speed received"

find nothing about such error in the docs.

-- 
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/749eed28-62ce-1b8f-9f4f-0ea15852a23a%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: download new fedora-26

2017-11-26 Thread fepitre
Le samedi 25 novembre 2017 13:02:33 UTC+1, Roy Bernat a écrit :
> On Friday, 24 November 2017 07:17:44 UTC-5, Frédéric Pierret (fepitre)  wrote:
> > Le vendredi 24 novembre 2017 12:02:56 UTC+1, Yuraeitha a écrit :
> > > On Thursday, November 23, 2017 at 6:39:26 AM UTC, Roy Bernat wrote:
> > > > On Wednesday, 22 November 2017 11:11:17 UTC-5, Roy Bernat  wrote:
> > > > > Hi 
> > > > > 
> > > > > i am trying to download fedora-26 but with no success . 
> > > > > 
> > > > > i succeeded a month ago but now i am getting nothing . 
> > > > > 
> > > > > any suggestions ? 
> > > > > 
> > > > > R
> > > > 
> > > > Thank for all answers . 
> > > > 
> > > > i am using qubes4.0 and i used to download the template using 
> > > > 
> > > >  Qubes-dom0-update command . 
> > > > 
> > > > manually download i tried to use wget but there is no wget availble in 
> > > > dom 0 . 
> > > > 
> > > > R
> > > 
> > > Sorry for the extra day delay, here are my findings when I tried to 
> > > install Fedora-26 again. 
> > > 
> > > Interestingly it now works for me, it did not some 2 weeks ago. 
> > > I verified it on multiple Qubes 4 machines, all of them installed 
> > > Fedora-26 perfectly fine now. 
> > > 
> > > Possibly something was fixed that changed that? 
> > Yes there were some updates with respect to pulseaudio version notably.
> > 
> > > @Roy Bernat, have you tried running updates? Also the testing updates? Be 
> > > careful with the testing updates though as they might break your system 
> > > if unlucky, so backup first just in case. But there i a lot of packages 
> > > in the dom0 testing repository atm. It's a possibility, that it might fix 
> > > it, though it may also not fix it either.
> I use to download it using update and --action=install but now it is not 
> working ,

try in dom0: sudo qubes-dom0-update --action='clean all', and then, sudo 
qubes-dom0-update qubes-template-fedora-26

-- 
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/e37f01ba-a200-4f33-a8b3-dc09b805ec83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Mobile broadband-not enabled

2017-11-26 Thread Yuraeitha
On Friday, November 24, 2017 at 2:55:35 PM UTC, beso wrote:
> On Thursday, November 23, 2017 at 1:50:53 AM UTC+2, Yuraeitha wrote:
> > On Wednesday, November 22, 2017 at 11:13:35 PM UTC, beso wrote:
> > > On Thursday, November 23, 2017 at 1:07:28 AM UTC+2, Yuraeitha wrote:
> > > > On Wednesday, November 22, 2017 at 10:49:46 PM UTC, beso wrote:
> > > > > On Thursday, November 23, 2017 at 12:37:59 AM UTC+2, Yuraeitha wrote:
> > > > > > On Wednesday, November 22, 2017 at 10:03:22 PM UTC, beso wrote:
> > > > > > > On Wednesday, November 22, 2017 at 11:49:16 PM UTC+2, Yuraeitha 
> > > > > > > wrote:
> > > > > > > > On Wednesday, November 22, 2017 at 9:37:38 PM UTC, beso wrote:
> > > > > > > > > On Wednesday, November 22, 2017 at 11:22:47 PM UTC+2, 
> > > > > > > > > Yuraeitha wrote:
> > > > > > > > > > On Wednesday, November 22, 2017 at 9:11:18 PM UTC, beso 
> > > > > > > > > > wrote:
> > > > > > > > > > > On Wednesday, November 22, 2017 at 5:48:43 PM UTC+2, beso 
> > > > > > > > > > > wrote:
> > > > > > > > > > > > On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, 
> > > > > > > > > > > > beso wrote:
> > > > > > > > > > > > > On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso 
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, 
> > > > > > > > > > > > > > One7two99 wrote:
> > > > > > > > > > > > > > > Hello Beso,
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > Mobile Broadband is enabled in 
> > > > > > > > > > > > > > > > NetworkManager Applet. 
> > > > > > > > > > > > > > > > I can create new Mobile Broadband 
> > > > > > > > > > > > > > > > connection but it keeps connecting 
> > > > > > > > > > > > > > > > and nothing else
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > >  I am using mobile broadband within Qubes and am 
> > > > > > > > > > > > > > > happy to help, but honestly your question/problem 
> > > > > > > > > > > > > > > is to unqualified. 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > - what version of Qubes are you running?
> > > > > > > > > > > > > > > - what modell of mobile broadband card are you 
> > > > > > > > > > > > > > > using? 
> > > > > > > > > > > > > > > - how is the broadband card connected? Probably 
> > > > > > > > > > > > > > > as an internal USB device. 
> > > > > > > > > > > > > > > - are you using sys-usb to connect the card to 
> > > > > > > > > > > > > > > your sys-net VM? Or are you passing through the 
> > > > > > > > > > > > > > > whole USB controller?
> > > > > > > > > > > > > > > - have you tried to boot up a Fedora live Linux 
> > > > > > > > > > > > > > > and check if your mobile broadband is working 
> > > > > > > > > > > > > > > there?
> > > > > > > > > > > > > > > - what does "keeps connecting" means?
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > My suggestion:
> > > > > > > > > > > > > > > Try to get the mobile broadband card working 
> > > > > > > > > > > > > > > without Qubes (Linux Live Boot from USB-Stick).
> > > > > > > > > > > > > > > If you got it working try to make it work in 
> > > > > > > > > > > > > > > Qubes.
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > [799]
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > - Laptop is ThinkPad X1 Carbon 4th gen.
> > > > > > > > > > > > > > - Qubes release 3.2(R3.2)
> > > > > > > > > > > > > > - Previous linux distros worked (ubuntu 16.04)
> > > > > > > > > > > > > > - from qvm-usb I can see that card is: Sierra 
> > > > > > > > > > > > > > Wireless Incorporated Sierra Wireless EM7455 
> > > > > > > > > > > > > > Qualcomm Snapdragon X7
> > > > > > > > > > > > > > - do I have to attach it somewhere?
> > > > > > > > > > > > > > - As I mentioned I can create new broadband 
> > > > > > > > > > > > > > connection and even select it from applet menu but 
> > > > > > > > > > > > > > it keeps connecting(applet shows "circles" as 
> > > > > > > > > > > > > > trying connect).
> > > > > > > > > > > > > > I am trying to make screenshot if it helps
> > > > > > > > > > > > 
> > > > > > > > > > > > PS.
> > > > > > > > > > > > [user@sys-net ~]$ ifconfig
> > > > > > > > > > > > enp0s1f6: flags=4099  mtu 1500
> > > > > > > > > > > > ether 54:ee:75:aa:4d:e3  txqueuelen 1000  
> > > > > > > > > > > > (Ethernet)
> > > > > > > > > > > > RX packets 0  bytes 0 (0.0 B)
> > > > > > > > > > > > RX errors 0  dropped 0  overruns 0  frame 0
> > > > > > > > > > > > TX packets 0  bytes 0 (0.0 B)
> > > > > > > > > > > > TX errors 0  dropped 0 overruns 0  carrier 0  
> > > > > > > > > > > > collisions 0
> > > > > > > > > > > > device interrupt 26  memory 0xe120-e122 
> > > > > > > > > > > >  
> > > > > > > > > > > > 
> > > > > > > > > > > > lo: flags=73  mtu 65536
> > > > > > > > > > > > inet 127.0.0.1  netmask 255.0.0.0
> > > > > > > > > > > > inet6 ::1  prefixlen 128  scopeid 0x10
> > > > > 

Re: [qubes-users] Re: sys-whonix / tor / thunderbird

2017-11-26 Thread Yuraeitha
On Friday, November 24, 2017 at 6:48:13 PM UTC, entr0py wrote:
> Yuraeitha:
> > On Friday, November 24, 2017 at 9:01:24 AM UTC, Bernhard wrote:
> >> Hello,
> >>
> >> one of the most useful features of tor-browser is Ctl-Shift-L to change
> >> the tor-path (and so, with high proba, the exit node IP) : this way,
> >> websites that block a specific exit node for a certain time can be still
> >> loaded (of course some fascist websites block all tor-exits and so that
> >> this measure does not help) .
> >>
> >> I feel that the same feature would be useful in other applications (in
> >> particular in thunderbird). How can this be done? Maybe a "forced
> >> reconnect" of IMAP connections suffices, but apart totally restarting
> >> thunderbird I don't see how this can be done. Any hints? Or is there
> >> good reason not to torify mail-fetching? Or never via IMAP?
> >>
> >> thank you, Bernhard
> 
> Each request to your Tor client (in sys-whonix) via SocksPort is accompanied 
> by a SOCKS username and password. By clicking "New Tor Circuit for this Site" 
> in Tor Browser, you are changing the password component, which causes the Tor 
> client to generate a new circuit for the same first-person domain when a 
> request is received.
> 
> Thunderbird is torrified by an extension called TorBirdy. Your requested 
> feature has been tracked for quite some time (5 years) but appears nearing 
> implementation now that Thunderbird-related roadblocks have been cleared. 
> (https://trac.torproject.org/projects/tor/ticket/6359) Also, the main reason 
> for that ticket is not circuit swapping but stream isolation. At present 
> (Whonix bonus), each different email server you connect to is given a 
> different circuit. With #6359, multiple accounts at the same email provider 
> can also be isolated by circuit.
> 
> Currently, you can generate new circuits for all future Tor requests by using 
> the "New Identity" feature via one of the following equivalent options:
> 1. From anon-whonix, use "New Identity" in Tor Browser. (applies to all Tor 
> connections, not just the browser.)
> 2. From sys-whonix, use arm/nyx (monitoring tool) to send New Identity request
> 3. From sys-whonix, send SIGNAL NEWNYM via telnet to 127.0.0.1:9051
> 
> 
> > More specially towards the question at hand, I think it's tricky to do 
> > something like that in Thunderbird, but I'm not a programmer, so I wouldn't 
> > know for sure. However, if you think about how it works in 
> > Qubes/Whonix/Tor, then the Tor browser appears to be tunneling Tor-Browser 
> > within Tor(Sys-whonix), basically doubling the onion layers compared to a 
> > regular Tor browser. I'm not entirely sure if this is the case, it's just 
> > something I figured must be the case. 
> 
> This is not correct. Tor-over-Tor is discouraged[1] and unlikely to work in 
> the future[2]. Whonix prevents Tor-over-Tor.[3][4]
> 
> [1] https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO#ToroverTor
> [2] https://trac.torproject.org/projects/tor/ticket/2667
> [3] https://www.whonix.org/wiki/DoNot#Prevent_Tor_over_Tor_Scenarios
> [4] https://www.whonix.org/wiki/Dev/anon-ws-disable-stacked-tor

ah, good I made a disclaimer :') 
Though, it does seem rather unsafe to run multiple of qubes over the same exit 
nodes in the Tor network. 

The most dangerous security issue out there, imho at least, is the assumption 
you are safe, when you are not. If what you're saying is true, and I'm 
confident it is given your background, then this might cause some dangerous 
user habits on Qubes in particular, beyond that what is a concern by using just 
Whonix/Tor? Similar issue probably exits between Whonix and Tor, but to a 
lesser extent as Qubes does not have any warnings about this, which is 
particular a concern when it's easier to mess up in Qubes, and run the same 
applications over the same exit nodes, at the same time. 

I did hear the warning of not running Tor over Tor before, though it was so 
long back that only the Tor browser was around back then. I had assumed it'd 
been fixed by now on Whonix and in particular Qubes. Especially considering the 
dangerous trap Whonix and in particular Qubes creates when running more on the 
same exit node. 

-- 
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/d56719b1-dcaf-4cd8-bc24-249ca7455989%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - ASRock Z170 Pro4 - i7-6700k

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 6:38:01 AM UTC, Wael Nasreddine wrote:
> Just installed Qubes 4.0-RC2. I had issues with the installation (was getting 
> libvirt errors), I solved the errors by temporarily switching all VMs to PV, 
> update dom0 and restore them back to HVM.

I got Qubes 4 RC-2 running on a similar motherboard for someone else, the Asus 
z170 Pro Gaming. I don't use this system actively my self, but it ran smoothly 
from the hours I used to set it all up and to configure it, and it had no 
libvirt errors. 

So the basic chipset features of the z170 line should not be an issue, and you 
got immou enabled in your HCL rapport file, so I assume your VT-d must be 
enabled in your UEFI (BIOS). Also the processor doesn't look like an issue 
either.

However, I remember this particular motherboard had two separate places to 
activate the virtualisation technology, you may have only enabled one of them 
in the UEFI? Both settings came disabled on the Asus z170 Pro Gaming board I 
set up with Qubes 4.

In your UEFI Advanced menu, try look for both:
- VT-d. (I suspect this is the one you enabled). 
- Virtualization (something closely worded to this, I suspect this might be the 
setting you miss to enable).

So if the two boards are anything alike, then this might be it. If you can't 
find this extra setting, then perhaps your model is different and it doesn't 
have it extra required step. But it may very well be similar.

-- 
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/73dec1cb-e047-46bb-b5d1-58d0f7959676%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Looking for Qubes OS-Users in Munich-Germany

2017-11-26 Thread Yuraeitha
On Friday, November 24, 2017 at 3:34:57 PM UTC, kai@gmail.com wrote:
> btw, i know of at least one more person using qubes os in Munich (even 
> selling laptops with preinstaled qubes os 3.2)
> 
> Al the best
> Kai

aye, that certainly rises the bar quite a bit, this is a strong factor if he's 
having even remote success in setting laptops, up from the 4-6 evenly 
distributed calculation expectation.
Including the factor meinene...@gmail.com mentioned.

So it's probably reasonable to assume that there should at the very least be 
some 10-15+ people in Munich, given those 2 extra factors up from the even 
distribution. But that extra estimation is a subjective estimation though.

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


[qubes-users] Re: download new fedora-26

2017-11-26 Thread Yuraeitha
On Friday, November 24, 2017 at 12:17:44 PM UTC, Frédéric Pierret (fepitre) 
wrote:
> Le vendredi 24 novembre 2017 12:02:56 UTC+1, Yuraeitha a écrit :
> > On Thursday, November 23, 2017 at 6:39:26 AM UTC, Roy Bernat wrote:
> > > On Wednesday, 22 November 2017 11:11:17 UTC-5, Roy Bernat  wrote:
> > > > Hi 
> > > > 
> > > > i am trying to download fedora-26 but with no success . 
> > > > 
> > > > i succeeded a month ago but now i am getting nothing . 
> > > > 
> > > > any suggestions ? 
> > > > 
> > > > R
> > > 
> > > Thank for all answers . 
> > > 
> > > i am using qubes4.0 and i used to download the template using 
> > > 
> > >  Qubes-dom0-update command . 
> > > 
> > > manually download i tried to use wget but there is no wget availble in 
> > > dom 0 . 
> > > 
> > > R
> > 
> > Sorry for the extra day delay, here are my findings when I tried to install 
> > Fedora-26 again. 
> > 
> > Interestingly it now works for me, it did not some 2 weeks ago. 
> > I verified it on multiple Qubes 4 machines, all of them installed Fedora-26 
> > perfectly fine now. 
> > 
> > Possibly something was fixed that changed that? 
> Yes there were some updates with respect to pulseaudio version notably.
> 
> > @Roy Bernat, have you tried running updates? Also the testing updates? Be 
> > careful with the testing updates though as they might break your system if 
> > unlucky, so backup first just in case. But there i a lot of packages in the 
> > dom0 testing repository atm. It's a possibility, that it might fix it, 
> > though it may also not fix it either.

stuck*, not suck... gee, these e-mail threads give me a hedache with the 
inability to edit the really bad typo'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 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/94dfa24a-56e2-4174-8eb9-60b42903eb7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] How to Setup Wireless

2017-11-26 Thread Yuraeitha
On Friday, November 24, 2017 at 3:15:06 PM UTC, Ray Joseph wrote:
> Yuraeitha,
> 
> 
> Thank you.  That was great detail.  
> 
> 
> I think I will redirect output to one continuos file to collect all VM info 
> and use that file to record my progress.
> 
> 
> My biggest obstacle is that when the machine boots up, I do not always get a 
> keyboard (laptop).  Plugging in a USB keyboard and mouse does not always work
>   
> Maybe this is related to the VMs.  My fist install of V4 was with a docking 
> station attached.  Keyboard and mouse functionality was intermittent but if 
> the embedded set did not work, I could plug kbd into the laptop USB slots or 
> docking station.  To fix this, I reinstalled V4 without the docking station.  
> The kbd is less predictable/controllable.  
> 
> 
> In both cases, I have found that repeated reboots sometimes production es a 
> functioning keyboard.  I have also found that letting the laptop sit for a 
> while will sometimes provide the keyboard.  This latter feature is what leads 
> me to consider that service VMs may be at play. 
> 
> 
> I have "newly" loaded the latest two versions of Debian over 30 times and 3 
> installs of Qubes-os.  I am open to experimenting.  My challenge with Debian 
> was getting wireless to work with Xen bridging.  
> 
> 
> On Nov 24, 2017 4:02 AM, "Yuraeitha"  wrote:
> On Friday, November 24, 2017 at 2:01:18 AM UTC, Ray Joseph wrote:
> 
> > Yuraeitha,
> 
> >
> 
> > Thank you.  All of that was news.  The need to run all VMs as HVM is the 
> > only one that seems to be a concern.  When I get wifi working, I never lose 
> > it.
> 
> >     This was a fresh install and I am testing with this machine.
> 
> >
> 
> > I haven't been able to find how to convert existing VMs to HVM.  Please 
> > suggest where I might find this.  I've been going through docs and have not 
> > found it.
> 
> >
> 
> > Ray
> 
> 
> 
> Good to hear you got stable WiFi :)
> 
> 
> 
> Almost all (if not all) the docs are currently out-of-date when it comes to 
> Qubes 4, but up-to-date when it comes to Qubes 3.2.
> 
> 
> 
> This is why there is currently no doc for changing PV to HVM, or vice versa. 
> HVM is prefered for security in Qubes 4, however both modes can give 
> different hardware trouble. For example I personally get issues running PV, 
> despite having PV working flawlessly back in Qubes 3.2. Others from what I 
> can read might have issues with HVM, and need to fall back to PV instead.
> 
> 
> 
> That's why you can switch to whichever mode is preferred. But in terms of 
> security HVM is better than PV. However HVM is not perfect either, but 
> nontheless an improvement over PV. From what I've seen the developers 
> discuss, it seems like the plan is to move towards PVH in a future Qubes 
> release. This is in turn an improvement over HVM. So PV < HVM < PVH. So you 
> want HVM for now, but can change to PVH in a future Qubes release, probably 
> with the same command by then.
> 
> 
> 
> Unfortunately there is no easy way to print out which VM is in PV or HVM. At 
> least, I haven't found it if there is any. The usual 'qvm-ls' command, 
> usually used to print VM information like disk usages, network use, template 
> use, etc. still appears to be in Qubes 3.2. version. For example a PV/HVM 
> print in qvm-ls would seem like something extremely useful to add into the 
> qvm-ls tool, so my guess is it's still something that needs fixing. 
> Especially when PVH is added to the mix in a future Qubes release. the 
> format, for example 'qvm-ls --format-help' doesn't give any PV/HVM 
> information either in any of the various flags to print more details of 
> different kinds. (btw, the qvm-ls --format disk' command is useful if you 
> want to know how much each VM is using disk space, now that the Qubes Manager 
> has been removed in Qubes 4. It can be troublesome if one of your VM's is 
> eating up a lot of disk space and you can't find which one, especially on 
> small SSD drives. That command can help with that.
> 
> 
> 
> Anyway, back to the PV/HVM issue. The command to print PV/HVM, if you're not 
> familiar with the command already, then it can also give other VM 
> information, try type 'qvm-prefs vm-name' on whichever vm you want to check 
> VM preferences on. You'll see the virt_mode in here for the PV/HVM, along 
> with various other VM specific preferences for that VM.
> 
> 
> 
> Optionally; for less terminal spam, you can type in this instead:
> 
> qvm-prefs vm-name virt_mode
> 
> 
> 
> If it gives you back PV print in terminal chat, then use keyboard arrow-up, 
> so you can re-use the same command again, and then add HVM afterwards, so it 
> becomes like this
> 
> 
> 
> qvm-prefs vm-name virt_mode HVM
> 
> 
> 
> Then repeat, go through all your VM's that might be in a PV state, be it 
> TemplateVM's, AappVMs, ServiceVM's, DisposableVM's, etc.
> 
> Probably all your VM's originating from Qubes 4, are already set to HVM, but 
> almost 

Re: [qubes-users] How to Setup Wireless

2017-11-26 Thread Yuraeitha
On Friday, November 24, 2017 at 3:15:06 PM UTC, Ray Joseph wrote:
> Yuraeitha,
> 
> 
> Thank you.  That was great detail.  
> 
> 
> I think I will redirect output to one continuos file to collect all VM info 
> and use that file to record my progress.
> 
> 
> My biggest obstacle is that when the machine boots up, I do not always get a 
> keyboard (laptop).  Plugging in a USB keyboard and mouse does not always work
>   
> Maybe this is related to the VMs.  My fist install of V4 was with a docking 
> station attached.  Keyboard and mouse functionality was intermittent but if 
> the embedded set did not work, I could plug kbd into the laptop USB slots or 
> docking station.  To fix this, I reinstalled V4 without the docking station.  
> The kbd is less predictable/controllable.  
> 
> 
> In both cases, I have found that repeated reboots sometimes production es a 
> functioning keyboard.  I have also found that letting the laptop sit for a 
> while will sometimes provide the keyboard.  This latter feature is what leads 
> me to consider that service VMs may be at play. 
> 
> 
> I have "newly" loaded the latest two versions of Debian over 30 times and 3 
> installs of Qubes-os.  I am open to experimenting.  My challenge with Debian 
> was getting wireless to work with Xen bridging.  
> 
> 
> On Nov 24, 2017 4:02 AM, "Yuraeitha"  wrote:
> On Friday, November 24, 2017 at 2:01:18 AM UTC, Ray Joseph wrote:
> 
> > Yuraeitha,
> 
> >
> 
> > Thank you.  All of that was news.  The need to run all VMs as HVM is the 
> > only one that seems to be a concern.  When I get wifi working, I never lose 
> > it.
> 
> >     This was a fresh install and I am testing with this machine.
> 
> >
> 
> > I haven't been able to find how to convert existing VMs to HVM.  Please 
> > suggest where I might find this.  I've been going through docs and have not 
> > found it.
> 
> >
> 
> > Ray
> 
> 
> 
> Good to hear you got stable WiFi :)
> 
> 
> 
> Almost all (if not all) the docs are currently out-of-date when it comes to 
> Qubes 4, but up-to-date when it comes to Qubes 3.2.
> 
> 
> 
> This is why there is currently no doc for changing PV to HVM, or vice versa. 
> HVM is prefered for security in Qubes 4, however both modes can give 
> different hardware trouble. For example I personally get issues running PV, 
> despite having PV working flawlessly back in Qubes 3.2. Others from what I 
> can read might have issues with HVM, and need to fall back to PV instead.
> 
> 
> 
> That's why you can switch to whichever mode is preferred. But in terms of 
> security HVM is better than PV. However HVM is not perfect either, but 
> nontheless an improvement over PV. From what I've seen the developers 
> discuss, it seems like the plan is to move towards PVH in a future Qubes 
> release. This is in turn an improvement over HVM. So PV < HVM < PVH. So you 
> want HVM for now, but can change to PVH in a future Qubes release, probably 
> with the same command by then.
> 
> 
> 
> Unfortunately there is no easy way to print out which VM is in PV or HVM. At 
> least, I haven't found it if there is any. The usual 'qvm-ls' command, 
> usually used to print VM information like disk usages, network use, template 
> use, etc. still appears to be in Qubes 3.2. version. For example a PV/HVM 
> print in qvm-ls would seem like something extremely useful to add into the 
> qvm-ls tool, so my guess is it's still something that needs fixing. 
> Especially when PVH is added to the mix in a future Qubes release. the 
> format, for example 'qvm-ls --format-help' doesn't give any PV/HVM 
> information either in any of the various flags to print more details of 
> different kinds. (btw, the qvm-ls --format disk' command is useful if you 
> want to know how much each VM is using disk space, now that the Qubes Manager 
> has been removed in Qubes 4. It can be troublesome if one of your VM's is 
> eating up a lot of disk space and you can't find which one, especially on 
> small SSD drives. That command can help with that.
> 
> 
> 
> Anyway, back to the PV/HVM issue. The command to print PV/HVM, if you're not 
> familiar with the command already, then it can also give other VM 
> information, try type 'qvm-prefs vm-name' on whichever vm you want to check 
> VM preferences on. You'll see the virt_mode in here for the PV/HVM, along 
> with various other VM specific preferences for that VM.
> 
> 
> 
> Optionally; for less terminal spam, you can type in this instead:
> 
> qvm-prefs vm-name virt_mode
> 
> 
> 
> If it gives you back PV print in terminal chat, then use keyboard arrow-up, 
> so you can re-use the same command again, and then add HVM afterwards, so it 
> becomes like this
> 
> 
> 
> qvm-prefs vm-name virt_mode HVM
> 
> 
> 
> Then repeat, go through all your VM's that might be in a PV state, be it 
> TemplateVM's, AappVMs, ServiceVM's, DisposableVM's, etc.
> 
> Probably all your VM's originating from Qubes 4, are already set to HVM, but 
> almost 

Re: [qubes-users] Re: will uninstalling a base template delete a clone of the template?

2017-11-26 Thread Chris Laprise

On 11/26/2017 04:26 AM, Yuraeitha wrote:

On Sunday, November 26, 2017 at 4:31:35 AM UTC, 
cybe...@national.shitposting.agency wrote:

I recently made a kali template vm by cloning the qubes debian 8 template and 
converting it to kali.

If I were to remove the base debian 8 template from dom0, would this also 
remove the cloned kali template vm?




The answer is No. Cloned templates are not dependent on each other.

If you have appVMs dependent on the debian-8 template, you'll have to 
re-assign them to another template before you do the removal.


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

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


[qubes-users] Re: will uninstalling a base template delete a clone of the template?

2017-11-26 Thread Yuraeitha
On Sunday, November 26, 2017 at 4:31:35 AM UTC, 
cybe...@national.shitposting.agency wrote:
> I recently made a kali template vm by cloning the qubes debian 8 template and 
> converting it to kali.
> 
> If I were to remove the base debian 8 template from dom0, would this also 
> remove the cloned kali template vm?

I imagine it's possible to see directly if your kali is acting like a debian-8 
template, despite being converted to kali. I'm not entirely sure how to go 
about that though, maybe wait till someone can answer this possibility. 

As far as I know though, it will yes. But I'm only almost sure, someone might 
say otherwise. Just, don't take the risk unless you're ready for the 
possibility of loosing it. 

qvm-remove should remove specific VM's, while dnf remove should remove all of 
the templates and copies thereof. 

You could however perform a hack, and make a backup of your template. Then 
ensure the integrity of the backup, and then throw yourself into deepwater and 
see if you can remove only one of them. If the other also goes, then you can 
rely on your backup to return it. 

Just be sure to have multiple of backups for anything important data. Though 
templates shouldn't be much of a loose for you if it turns out badly? I mean, 
you can just re-install all the app's you require in a fresh new template. 

I.e. 'qubes-dom0-update qubes-template-debian-8' would re-install your debian 8 
template if it is lost, and then you can just re-install all your apps in a 
whole new fresh template. 

So that's 3 different approaches. Also you would need somewhere to temporary 
put your AppVM template in your AppVM settings, i.e. debian-9 maybe if you got 
it installed? Then just don't start it until it's back to debian-8 template. 
Possibly you can use a fedora temporary template too, since if you don't start 
it, then ""nothing should"" be changed in the home folder.

Just be very careful and have redundancy backups if you're doing this on 
anything important.

Perhaps, the better question is why do you want to remove debian-8? Is it to 
gain drive space? Maybe there are other solutions you can have a look at for 
that, i.e. checking if trimming is working as it should. 

In Qubes 3.2. trimming is manual, in Qubes 4 it's supposed to be automatic. 
Which Qubes are you 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/2bbe751b-641a-4452-992e-ac1077ffe2d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - Lenovo Yoga 2 Pro

2017-11-26 Thread dylen
Hi,

This works very well. Install was only working using a usb rj45 adapter,
but after the install the wireless worked.

Sincerely
/D

-- 
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/8c6ebca50c4f1133d087c4b15764af3c%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-LENOVO-20266-20171126-101248.cpio.gz
Description: GNU Zip compressed data
---
layout:
  'hcl'
type:
  'notebook'
hvm:
  'yes'
iommu:
  'no'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'no'
brand: |
  LENOVO
model: |
  20266
bios: |
  76CN38WW
cpu: |
  Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Intel Corporation Wireless 7260 (rev 6b)
memory: |
  8108
scsi: |
  SAMSUNG MZMTD512 Rev: 3L0Q
usb: |
  2
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R3.2
  xen: |
4.6.6
  kernel: |
4.9.56-21
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---