Re: [qubes-users] Network Access dom0

[zackptg5]

On Tuesday, August 16, 2016 at 10:44:06 PM UTC-4, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2016-08-16 18:46, zackp...@gmail.com wrote:
> > On Tuesday, August 16, 2016 at 8:25:03 PM UTC-4, Andrew David Wong wrote: 
> > On 2016-08-16 17:20, zackp...@gmail.com wrote:
>  Unfortunately, I need to install bumblebee for better power 
>  management for my laptop. Copying over the rpms and installing them 
>  are easy enough but my concern is with any dependencies that may be 
>  needed
>  
> > 
> > Maybe there's a way to define your own repo and piggyback on the usual
> > dom0 update mechanism, but I've never really played around with this (due
> > to the security risks), so I don't know if it's possible.
> > 
> > The predefined repos are in /etc/yum.repos.d/. Here are the basics of the 
> > dom0 update system:
> > 
> > https://www.qubes-os.org/doc/software-update-dom0/
> > 
> > Here are the technical details:
> > 
> > https://www.qubes-os.org/doc/dom0-secure-updates/
> > 
> > And, in case it helps, an explanation of networking in Qubes:
> > 
> > https://www.qubes-os.org/doc/networking/
> > 
> > 
> > Alright, added the bumblebee repos. But when trying to install anything 
> > from them or run a qubes-dom0-update (this is all from dom0 terminal), I 
> > get "Failed to synchronize cache for repo 'bumblebee', disabling"
> > 
> > Are there some kind of special exceptions I need to add to the sys-firewall
> > vm?
> > 
> 
> Are you downloading updates via Tor (sys-whonix)? If so, try requesting a new
> identity (press 'n' in tor-arm) or just wait 10 minutes, then try again.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJXs89sAAoJENtN07w5UDAwcA4P/0VW6+igD47pX5eOa+5t3vm/
> M8WO4VKKFxRGAX0M5nweRq3J4esxaITKschfsXlpd0eHdEdbRJVB1HP+KzOeGLp7
> CyJzjqBUnxgoorDLbBcGribyg3Z2k7fVh0H/XGP2wz3StsC7LnJbRpxVq2Y4om+n
> hPsJELiJ0krO0/yYYtcd5E2tD9OhEuGgkrifc/KmBzM6HWUEdOlPpmMGDl5UT1FV
> k1NZu8hhd5TkcxdCn3MQAbMPaVhdAXe46t7C+6g4o+c4wS9AsuQYa/o/nMIVosTQ
> bA9mHcMLXKPMfUoIvgUWE+K7JbK/OJZTrVScOW3rnnm6CTcpUafKqATDLBSe8WGp
> RLYvN6xMBxZDm9gn6CMxY02fc6he9YHXMt1i9num53bn1NeDSzTyMjqIyuGJk1Aa
> nV/e5jP2V1UL1JHbbBy/PMyXzh8gj6VY7dbEaVvnMHCNvYJ5+fdnozz7QZlvbg2J
> AdB9wmPF9JrsvxOHlp+XRMXH3FkMSWRxquisGZYwIGXpxy3ags6P66g7GXJvE+8i
> x4OCLEDSGMpGI1By2h4xVbD5e+rFqHkwB5cDTVM51gjNjJZlEwf/g4w388IlMpm/
> t3VOSqljMlBzEPLVl74YdP8j6rP+06DDJmwEJDoduhqDSNmWvkBV+7cegrgsVKXu
> u+AoapfMWl/Nj6AAwmzq
> =lNtT
> -END PGP SIGNATURE-
I did not install the tor network for the whole system so it shouldn't be using 
tor. Any ideas on the cache error?

-- 
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/a50414bc-2f7e-4621-96c7-ea03eec1aaef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Why does QUBES recommend SSD drives..?

[neilhardley]

The Qubes website recommends SSD drives.

Is there any particular reason..?

Does Qubes use read/write to the hard drive any more than Windows... to the 
point where it's going to cause drive failure a lot earlier..?

Or is it simply a speed thing..?

Or what.?

-- 
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/b674086e-3c4d-4adf-9b5a-d7da5a888cfa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Network Access dom0

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 18:46, zackp...@gmail.com wrote:
> On Tuesday, August 16, 2016 at 8:25:03 PM UTC-4, Andrew David Wong wrote: 
> On 2016-08-16 17:20, zackp...@gmail.com wrote:
 Unfortunately, I need to install bumblebee for better power 
 management for my laptop. Copying over the rpms and installing them 
 are easy enough but my concern is with any dependencies that may be 
 needed
 
> 
> Maybe there's a way to define your own repo and piggyback on the usual
> dom0 update mechanism, but I've never really played around with this (due
> to the security risks), so I don't know if it's possible.
> 
> The predefined repos are in /etc/yum.repos.d/. Here are the basics of the 
> dom0 update system:
> 
> https://www.qubes-os.org/doc/software-update-dom0/
> 
> Here are the technical details:
> 
> https://www.qubes-os.org/doc/dom0-secure-updates/
> 
> And, in case it helps, an explanation of networking in Qubes:
> 
> https://www.qubes-os.org/doc/networking/
> 
> 
> Alright, added the bumblebee repos. But when trying to install anything 
> from them or run a qubes-dom0-update (this is all from dom0 terminal), I 
> get "Failed to synchronize cache for repo 'bumblebee', disabling"
> 
> Are there some kind of special exceptions I need to add to the sys-firewall
> vm?
> 

Are you downloading updates via Tor (sys-whonix)? If so, try requesting a new
identity (press 'n' in tor-arm) or just wait 10 minutes, then try again.

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

iQIcBAEBCgAGBQJXs89sAAoJENtN07w5UDAwcA4P/0VW6+igD47pX5eOa+5t3vm/
M8WO4VKKFxRGAX0M5nweRq3J4esxaITKschfsXlpd0eHdEdbRJVB1HP+KzOeGLp7
CyJzjqBUnxgoorDLbBcGribyg3Z2k7fVh0H/XGP2wz3StsC7LnJbRpxVq2Y4om+n
hPsJELiJ0krO0/yYYtcd5E2tD9OhEuGgkrifc/KmBzM6HWUEdOlPpmMGDl5UT1FV
k1NZu8hhd5TkcxdCn3MQAbMPaVhdAXe46t7C+6g4o+c4wS9AsuQYa/o/nMIVosTQ
bA9mHcMLXKPMfUoIvgUWE+K7JbK/OJZTrVScOW3rnnm6CTcpUafKqATDLBSe8WGp
RLYvN6xMBxZDm9gn6CMxY02fc6he9YHXMt1i9num53bn1NeDSzTyMjqIyuGJk1Aa
nV/e5jP2V1UL1JHbbBy/PMyXzh8gj6VY7dbEaVvnMHCNvYJ5+fdnozz7QZlvbg2J
AdB9wmPF9JrsvxOHlp+XRMXH3FkMSWRxquisGZYwIGXpxy3ags6P66g7GXJvE+8i
x4OCLEDSGMpGI1By2h4xVbD5e+rFqHkwB5cDTVM51gjNjJZlEwf/g4w388IlMpm/
t3VOSqljMlBzEPLVl74YdP8j6rP+06DDJmwEJDoduhqDSNmWvkBV+7cegrgsVKXu
u+AoapfMWl/Nj6AAwmzq
=lNtT
-END PGP SIGNATURE-

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

Re: [qubes-users] Query on upgrade process - what next after downloading the fedora23 template?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 18:06, eobail...@gmail.com wrote:
> On Wednesday, 17 August 2016 02:15:32 UTC+10, Marek Marczykowski-Górecki 
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>> 
>> On Tue, Aug 16, 2016 at 09:07:24AM -0700, Andrew David Wong wrote:
>>> On 2016-08-16 00:18, eobaillie wrote:
 
> Sorry for the misunderstanding. You do not have to (and, indeed, 
> cannot) update your TemplateBasedVMs from Fedora 21 to Fedora 23, 
> since they're Template-based.
 
 Normally speaking, though, if I'm running a computer with a
 particular operating system, I can upgrade that operating system to a
 new version. So are you saying I can't do this with the various VMs
 run by Qubes?
 
>>> 
>>> No, you certainly can. However, the way to do it in Qubes (due to the
>>> way the Template system works) is to upgrade the operating system in
>>> the TemplateVM, not the TemplateBasedVM. This is because the TemplateVM
>>> is where the operating system files reside. They do not reside in the 
>>> TemplateBasedVM -- only user data resides there.
>>> 
> This means that they don't have a root filesystem (where the OS and
>  programs are stored) of their own. Instead, they get their root 
> filesystem from the TemplateVM on which they're based. As long as 
> your TemplateVMs have been upgraded correctly, your
> TemplateBasedVMs should work with the upgraded TemplateVMs
> normally.
 
 The result of running "sudo qubes-dom0-update 
 qubes-template-fedora-23" was not to update a TemplateVM, though. It 
 created a new TemplateVM, so now I have 2: fedora-21 and fedora-23 - 
 the second of which doesn't yet seem to have a purpose unless or
 until I create new VMs
 
>>> 
>>> That command ("sudo qubes-dom0-update qubes-template-fedora-23")
>>> installs a new fedora-23 template from the repo. It is the preferred
>>> way to obtain a fresh fedora-23 template. However, if you instead want
>>> to upgrade an existing fedora-21 template to fedora-23 (e.g., to
>>> preserve any customizations you've made), then you must use the
>>> in-place upgrade procedure:
>>> 
>>> https://www.qubes-os.org/doc/fedora-template-upgrade-21/
>>> 
> The fact that you're now asking whether you should shut down all
> of your VMs one by one suggests that you may not have followed the 
> above procedure, since rebooting dom0 entails shutting down all of 
> those VMs (but it's also possible that this is just a 
> miscommunication).
 
 no, it just means I'm doing this process gradually, leaving space for
  things like, eg, restarting a VM in order to post things on the 
 Internet
>>> 
>>> Ok, understood.
>>> 
> 
> It's also not clear to me what you mean by "tell them in
> VM-manager to be fedora-23 not fedora-21 VMs."
 
 "upgrade the operating system the VMs are using to version 23 of
 fedora rather than version 21"
 
>>> 
>>> Ok, got it.
>>> 
> If you've just performed an in-place upgrade on a template (from 
> Fedora 21 to Fedora 23) with the intention of using it, then it
> would indeed make sense to base your AppVM on this newly upgraded
> template (if it wasn't already). Again, as long as the upgrade has
> been done correctly, everything should work normally.
 
 based on that, it doesn't seem to be - I don't think my system is 
 currently in the state you describe
 
 It is possible that the step that went wrong is step one - "Upgrade 
 fedora templates". Would you normally expect that after that first 
 step, the default TemplateVM would have upgraded itself to the most 
 recent available version of Fedora? Because that didn't happen.
 
>>> 
>>> Ah, sorry for the misunderstanding. No, there are additional steps 
>>> required to upgrade an existing Fedora 21 template to Fedora 23 that
>>> are not listed on that page. They are instead listed on this page (same
>>> as linked above):
>>> 
>>> https://www.qubes-os.org/doc/fedora-template-upgrade-21/
>>> 
 
 Bearing in mind, in all of this my ultimate purpose is "make my Qubes
  installation indistinguishable from a fresh installation of version 
 3.1". Which is not yet the case!
 
>>> 
>>> If this is your goal, then as noted above, it may be easier and more 
>>> preferable to obtain a fresh fedora-23 template from the repo (as
>>> you've already done). Either way works, and which is preferable depends
>>> on things like the modifications (if any) you've made to your
>>> template(s) and how acceptable you find the results of the in-place
>>> upgrade procedure for your individual purposes.
>> 
>> I'm not sure if I understand the intention here, but isn't this all
>> thread about just switching AppVMs to the new template (either upgraded
>> in-place, or downloaded fresh one). You can do this in VM settings - just
>> change "fedora-21" to 

Re: [qubes-users] Re: Windows7 issue with Dom0 GUI Daemon

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 17:19, Drew White wrote:
> On Wednesday, 17 August 2016 07:13:06 UTC+10, Marek Marczykowski-Górecki
> wrote:
>> 
>> The updated package is uploaded to testing repository for Qubes 3.2.
>> 
> 
> So how do I get the package for the multi-monitor then?
> 

(Repeating my reply to your other thread.)

If you're on R3.2, and if you're willing to test this package (and you're
certainly under no obligation to do so), then you can do so now by following
the instructions here (under "Testing repositories"):

https://www.qubes-os.org/doc/software-update-dom0/#tocAnchor-1-1-3

I believe the correct repo is current-testing. If so, your command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing 

If this is, indeed, the right place, then you can see a list of available
packages here (or from the command line):

http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/

The only packages containing the word "windows" are different versions of
qubes-windows-tools, so I gather this is what you want. If that's correct,
then the command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing \
qubes-windows-tools

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

iQIcBAEBCgAGBQJXs7N1AAoJENtN07w5UDAw+b4P/jHps5pp2vZOIov+qJrOm8QZ
DFxHj+fsCyc1GstG1sPYt/Rc9xEWx5AyYJEOBslvVIokDYk0PJaWXBnKVMLql35T
N2a3YZJWFjQP/ZOVytNKdOZ1RgBWxOJ8K0Y8+XSWrvwT39PdindytGlTPTqFJVxS
b7BHzA8yAfGYuN6IGNTxPmtbame2KAhQCCsrEoe9Nlp4UE7z7LdKdadlVFrHjMKU
dy738/hzTaYuCDjDh5EfvYJvrLj9MVmCka2rqemxaunFX0mr0iOqAZZKCg8idg7w
ifCsZYl7ujxXCzB6ZDQNrJruZdeFYCBchorf3X/P3sGBi5JP/ArG0MjyvsrgcubO
odN9DgfsIdYgqayqryECqB4F3pYjt/kGNDHATfqxbZVrqBlEaUmJOgal0OgBcqge
ipz9IgfmtWG6pSR5yk+vTxz+rRgnh6tdcE4Me5xXChDTukbiDP7EUz1ziIm18PqP
MPjUOV7RBvuFsoIk3ObJ3SnN9BKA2GANkc/Bdc+3brC1Rg3+d0d6wv4DySgSmvtM
ZyCgE3HulLiSNYTrgkMmjCJgtlw/MmbQdnYrlYH/oByhLMGKlWu18NOc76769zf5
adBhDXUnQN+gxxM5gM3iH+J5fUY6VT5yjYjhNJuvINt7UgRicSPVcRMktrIUDVA5
Id8KdvGS8v8CYSQjlEjX
=02su
-END PGP SIGNATURE-

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

Re: [qubes-users] Current Windows instructions?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 17:18, Drew White wrote:
> On Wednesday, 17 August 2016 02:11:15 UTC+10, Andrew David Wong  wrote:
>> Are you referring to this issue?
>> 
>> https://github.com/QubesOS/qubes-issues/issues/1896
>> 
>> If so, it looks like it was closed recently, so the patch should be 
>> available for testing soon.
>> 
>>> Will the tools be working any time soon?
>>> 
>> 
> 
> Yes, that is one of the issues that I'm talking about.
> 
> I had thought if it was closed it means that there was a patch that was 
> tested and fully working. Because then that means that the issue is no 
> longer an issue and can then be closed.
> 
> Since I have not seen a patch for it and I'm still at the latest version of
>  Windows Tools and they are still broken as they have been since Qubes 2, I
>  was thinking the ticket should still be open.
> 

The way we handle issues is typically and roughly as follows: Once a commit that
purports to fix an issue is committed, the issue is closed by that commit. The
code in that commit then goes to the appropriate testing repo, where it stays
for a while (while it's being tested) before eventually moving to the stable
repo, where stable it gets installed by the majority of live systems as part of
an update or new release. So, there can be a considerable lag time between the
time when an issue is closed on GitHub and and the time when the code actually
starts running on live, stable end user systems.

> I will give it a bit of time for it to be released to the public, since it
>  must just be a private thing, and then I'll make the issue open again if
> the issue remains.
> 

So, as Marek said, in this particular case, the updated package has already been
uploaded to the testing repo for 3.2. If you're on R3.2, and if you're willing
to test this package (and you're certainly under no obligation to do so), then
you can do so now by following the instructions here (under "Testing
repositories"):

https://www.qubes-os.org/doc/software-update-dom0/#tocAnchor-1-1-3

I believe the correct repo is current-testing. If so, your command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing 

If this is, indeed, the right place, then you can see a list of available
packages here (or from the command line):

http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/

The only packages containing the word "windows" are different versions of
qubes-windows-tools, so I gather this is what you want. If that's correct,
then the command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing \
qubes-windows-tools

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

iQIcBAEBCgAGBQJXs7MlAAoJENtN07w5UDAw8QoP/3e/kxbqPng22O7IWnJ3X9i9
Nv8O5+V5e4C7gFlTAe+25nYZMZ1KhFzk1z95XWGbQtolhBYoIrOclbwo8Ef1HzlT
SG1xpMEEhw2ZKh71QDG7SsYdAXHAR1n0Zoij288xYxtfHh4FrdjYufVGQQd+QJ81
4A6u3Dd/+ApOZRVBUXzBEHmmgFCIPY+xOmSPe35sHxzBTEHhlVWP7knkVy6HkoY6
wWl12agqt/bWUShZsEmKuR7XHz3EF7BKQHkesKVjdnA8EIv1nrDdLoy/f7sRFoU5
3jl/67xyMjznhU/5fQODEEBSpH466+WrdlKScOUjcAO18QWU7PbQijeP0tpXwhSK
iqEOevM/uECoFTIeFYI5xMlgFImJ1BFtveBX3bsd78aOQgkkkC9E/+4BQmBwcXnG
HVXeEyci8p7pJNzu0pNmOiqEOza5UeZmcZ9OXqv6Fm6LrsLOmi5B4ZX3UkhMgg79
355JFTnzx2kHf3zz2HdOqfBy+qBXV/d4ZvGETJVfd5LU1VzIzgNpx432rjr8BTLJ
wffpMuc47Nr9t4tyozJWeIwyeZQrArd3aYTLPDwOt8G+N/QrRzJK8B6IZc7wBYiz
j+9hN4kFwr6ypJ8/rKgcqZlsmaJQB0E4WX4GjOD8fzkVTuD5zX0bFAhpdCPvd2bP
VQpxNU8WQCu2voAM+BFQ
=p7qg
-END PGP SIGNATURE-

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

Re: [qubes-users] Network Access dom0

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 17:20, zackp...@gmail.com wrote:
> Unfortunately, I need to install bumblebee for better power management for
> my laptop. Copying over the rpms and installing them are easy enough but
> my concern is with any dependencies that may be needed
> 

Maybe there's a way to define your own repo and piggyback on the usual dom0
update mechanism, but I've never really played around with this (due to the
security risks), so I don't know if it's possible.

The predefined repos are in /etc/yum.repos.d/. Here are the basics of the dom0
update system:

https://www.qubes-os.org/doc/software-update-dom0/

Here are the technical details:

https://www.qubes-os.org/doc/dom0-secure-updates/

And, in case it helps, an explanation of networking in Qubes:

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

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

iQIcBAEBCgAGBQJXs67YAAoJENtN07w5UDAwjPIP/ROSiZqzxc/3+H1c572bDocC
rfwgllo7mcma51wf4STq17vgJee9Pg0Zrqm5NOBP/GjnqL8oJGuQMxP8lYjzJvCR
ThW3sGEBD1kTJS6Ixt01ZEcOAdI+oTI0P2l2N9ntYO/mPfh4cMKKKjS6qovmPpHn
iZ9OTgwNNBDVWFs9OMbaKXHZ5gIhF/19+/VvNfu0mnZnLN03nJrlHhgHsR4yrZ2+
Br6b7grJW6PuTVfT4ipbS23JMAv9s0xS8XJmmobdrVpVDLs4abb6TUo7muJ6WF4A
Qtcvx4gk9asyhkd/Xm0ms23xJKoT8oYctVyt1A88PhGifJHPsv19iQ4u5gUNV5ni
q+99o9cd9faTMjhoL0h9Ks9FfiLZBDR5Y+KezsNnqXA8N+akRzVaNFlSwtauHfwm
8hJyKlzKDEGoFvqSH56miLUHnipxWR0jdw05PXWMP+2Lpnefawe2EyGEx9Eu+Nvq
4Eb0nZwAfSjuu3Y626BU2PzyKUakGJmlugtuRgeryLtIphe9X95dVMoeHRtZX9QO
UjXyIToKJAksBer1f5xOIqVcKaM0ffkXuezQgO79Zx227v3ZNb4hbovSo3E6CzXv
3YI2qZl+SdjVeBco2J9xeQzgpEx36eALgQm/sOynwbc3CMrcbZ9aWKnsYBogshXW
aUDSARs+KKB/ppwUEAEO
=LtJ3
-END PGP SIGNATURE-

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

Re: [qubes-users] Network Access dom0

[zackptg5]

Unfortunately, I need to install bumblebee for better power management for my 
laptop. Copying over the rpms and installing them are easy enough but my 
concern is with any dependencies that may be needed

-- 
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/987f4462-5cc5-450a-945f-9a533bda9560%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Windows7 issue with Dom0 GUI Daemon

[Drew White]

On Wednesday, 17 August 2016 07:13:06 UTC+10, Marek Marczykowski-Górecki  wrote:
> 
> The updated package is uploaded to testing repository for Qubes 3.2.
> 

So how do I get the package for the multi-monitor then?

-- 
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/cb99bccf-29ff-45ab-9e36-c97d69dea7f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Current Windows instructions?

[Drew White]

On Wednesday, 17 August 2016 02:11:15 UTC+10, Andrew David Wong  wrote:
> Are you referring to this issue?
> 
> https://github.com/QubesOS/qubes-issues/issues/1896
> 
> If so, it looks like it was closed recently, so the patch should be available
> for testing soon.
> 
> > Will the tools be working any time soon?
> > 
> 

Yes, that is one of the issues that I'm talking about.

I had thought if it was closed it means that there was a patch that was tested 
and fully working. Because then that means that the issue is no longer an issue 
and can then be closed.

Since I have not seen a patch for it and I'm still at the latest version of 
Windows Tools and they are still broken as they have been since Qubes 2, I was 
thinking the ticket should still be open.

I will give it a bit of time for it to be released to the public, since it must 
just be a private thing, and then I'll make the issue open again if the issue 
remains.

-- 
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/d797b0cb-9a5f-47db-bc55-8eb798e7aff8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Network Access dom0

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 13:29, zackp...@gmail.com wrote:
> I know it's unsecure and that the tempory elevation menioned in the update
>  dom0 page has been removed. So is there some way I can give network
> access to the dom0 so I can add the bumblebee repo?
> 

AFAIK, giving dom0 unfettered network access is not possible:

https://groups.google.com/d/topic/qubes-users/c2RyhLmTCm4/discussion

However, if your goal is just to get a certain package into dom0 so you can
yum/dnf install it there, then there are other ways to do that. For example,
you could download the package somewhere else, copy it to dom0, then install
it locally. Here's how you can copy files to dom0:

https://www.qubes-os.org/doc/copy-from-dom0/#tocAnchor-1-1-2

Please note the inherent risk of performing this action. Copying untrusted
files to dom0 is generally not advised and may compromise the security of your
Qubes installation.

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

iQIcBAEBCgAGBQJXs60XAAoJENtN07w5UDAw3aUP/jos3VZTef0hJ4OOXwXhc2M+
Eykv8f4QVX4Sd3yV72NPQ26RSCH8MloBxeaBqMdGoDqwCBh6g4CRq74GGSt82T0k
SSNcZVy9GgTd+D9rvMkuz6KMxxAOl4ZvPilSe5SNnElMGIUGYEJyQIeHj2hjAk2d
ZKuZH8cb4L+cauPF/+TtuxIIlIOWu7YR0h3hBfAVGdnYzAd6Ha8Id+IWNNKzAG2w
kngyts13X3J+PeMw6/N5mG3pe/sRZ+pfQUvQPQcaVGxFaJDcpqJFGO0Apvkhbdei
NURfmYe7F8jUqBIhXYnHxsLtJw9spkxXYtapDwYidS+LgGIzf5y7VO68E0VyTrXX
4RLzaj+Ocb1V+6si7/4wNe3/nTxm23ygjr03I3Iz/kZYyOO711rGj6OX9uGT0dSX
dvV36JJqEdCRoZM3BMjJBcx6KHDXQf3FMzzMjYVqvVg4u2zyWQtUYSI48/335Par
2g/BbdgEvpGF+ARhEec8kWr9A0n5sahWoiO3xwx2EU257XsWzjkS+I4knnWKbGtQ
TSwrKfld2Y1Y+mLZ3Sz5dvVO+GXs21WACx+tB7xjnYovDwkubRqzwf5zdNnrqBA5
B1TrvtuJWttaAIVqlf2rhz+NZxpS4Uyn8tQPa0H+GcxAJg7hU+r7IsMP28wRsr+Z
mZFJYhnzqSs9LEqoHSMA
=jIXz
-END PGP SIGNATURE-

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

[qubes-users] Re: Network Access dom0

[Drew White]

On Wednesday, 17 August 2016 06:29:21 UTC+10, zack...@gmail.com  wrote:
> I know it's unsecure and that the tempory elevation menioned in the update 
> dom0 page has been removed. So is there some way I can give network access to 
> the dom0 so I can add the bumblebee repo?

You need to enter it manually.

-- 
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/b6f03fa2-4e75-4b28-b60a-8c1680ef36f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No DNS with ProxyVM + OpenVPN

[Chris Laprise]

On 08/16/2016 06:56 AM, kotot...@gmail.com wrote:

To test this theory, you could put a 7sec delay in qubes-vpn-handler.sh
right before the line 'iptables -t nat -F PR-QBS'. Then the right IPs
should appear in PR-QBS.

It did work. Thank you again!

I wonder what is changing the NAT rules. I only see one 'up' directive in the 
openvpn configuration, the one calling the qubes script. Maybe something from 
Qubes itself? It's correct that the ProxyVM should be connected to sys-firewall 
right?


That was going to be my next question: Is there anything in the vpn 
config that triggers it, such as any other references to scripts. 
Ideally, there should only be up and down.


If you're comfortable posting the configuration maybe I or someone else 
could see the cause. Also the parts of the log output near the end that 
deal with PUSH data, since that is a source of configuration directives.


I also wonder if your template might have an openvpn service configured 
to autostart... creating a second openvpn process? You can check that 
with ps, systemctl, etc.


Also, Network Manager should not be running in that vm.

Finally, you could disable the /usr/lib/qubes/qubes-setup-dnat-to-ns 
script by renaming it right before openvpn starts (but it does have to 
run once on vm start). That should prevent it from steamrolling over the 
vpn-specific IPs.


Chris

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

Re: [qubes-users] Re: Windows7 issue with Dom0 GUI Daemon

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Aug 16, 2016 at 09:14:57AM -0700, Andrew David Wong wrote:
> On 2016-08-16 00:26, Drew White wrote:
> > On Tuesday, 16 August 2016 11:33:18 UTC+10, Andrew David Wong  wrote:
> >> The issue for this was recently closed:
> >> 
> >> https://github.com/QubesOS/qubes-issues/issues/1704
> >> 
> >> Rafał, is the fix for this available in a testing repo (or already 
> >> live)?
> >> 
> > 
> > 
> > How does a person re-open the issue?
> > 
> 
> If you're logged into GitHub, there should be a "reopen" button (not sure if
> visibility is permissions-based). You should probably test the patch that is
> supposed to fix the issue before reopening it, though. The patch should be
> available for testing soon.

The updated package is uploaded to testing repository for Qubes 3.2.

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

iQEcBAEBCAAGBQJXs4HZAAoJENuP0xzK19csZjAH/RRPmmiGCzQ8MmshPw9TomMD
nig+jJpsZxeImETR3dhXn+8Lhf1gnVahxUcyAeAElJRVfmJ4iOn1Bpf8XfHR6+9g
etVhEdBCY99D7GrPzkK+BSaxTFL6Kh6lQ9fYEg9wHG14R4xqlYcQQuOISrJb74gd
b1Q5Fzxp/zGDFJHeKq8FZ0loPq6dgtKHv0uqxDP+8unJBKws8MYNGZRboSJBJis8
Rag7XMR2jSSflqrLu1vKluSMVKp0bzGL5muiQEI0KqigdJQdiewh/C1BDuCOaNlf
0wPdCvGHDRAYIbDMrTw/x72JRfrbLN7CLflpvZnzW46AcZno4G0p5wQAwzEnPQI=
=KsaF
-END PGP SIGNATURE-

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

[qubes-users] Network Access dom0

[zackptg5]

I know it's unsecure and that the tempory elevation menioned in the update dom0 
page has been removed. So is there some way I can give network access to the 
dom0 so I can add the bumblebee repo? 

-- 
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/525fdc5a-ec77-4f00-8112-418dcbbe9ee0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] BCM Driver Install

[zackptg5]

On Tuesday, August 16, 2016 at 3:21:14 PM UTC-4, zack...@gmail.com wrote:
> On Tuesday, August 16, 2016 at 3:10:14 PM UTC-4, Andrew David Wong wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > On 2016-08-16 10:40, zackp...@gmail.com wrote:
> > > On Tuesday, August 16, 2016 at 1:38:08 PM UTC-4, Andrew David Wong wrote: 
> > > On 2016-08-16 10:35, zackp...@gmail.com wrote:
> >  On Tuesday, August 16, 2016 at 1:33:05 PM UTC-4, Andrew David Wong 
> >  wrote: On 2016-08-16 10:27, zackp...@gmail.com wrote:
> > >>> I've been trying to install the drivers for my bcm4352 but I\ve
> > >>> been unable so far. I'm on 3.2 rc2. Here's what I'm trying to
> > >>> do:
> > >>> 
> > >>> [...]
> > >>> 
> > >>> However I get "No package aknod-wl available"
> > >>> 
> >  
> >  Is your TemplateVM set to allow allow connections to RPMFusion's 
> >  servers? You should be to do this either by enabling the RPMFusion 
> >  repo or by allowing all connections for N minutes.
> >  
> >  
> >  Aren't connections allowed by default on the sys-net? Am I doing all
> >   of this on the wrong vm? I'm trying to get this working for dom0
> >  
> > > 
> > > Ah, sorry. I misunderstood the original message (thought you were trying
> > > to install something in a TemplateVM).
> > > 
> > > Yes, by default, all connections should be allowed from the default 
> > > sys-net. Are you sure that the package actually exists in the repo?
> > > 
> > > 
> > > Yes, it should exist based on everything I've read. I've also tried adding
> > >  the bumblebee repos (which the files definitely exist there) and I'm 
> > > getting the same errors which is why I believe that the repos aren't 
> > > actually being added
> > > 
> > 
> > Let's step back for a moment.
> > 
> > 1. You're doing all this from the sys-net terminal just to check whether the
> > packages are available (because all connections should be allowed from
> > sys-net) and/or temporary install the packages to test compatibility or
> > something, right? You're not actually attempting to install a package in
> > sys-net with the intention of having it persist there, right?
> > 
> > 2. You said you're trying to get this working for dom0. Normally, you'd
> > install the drivers for a Wi-Fi device in the TemplateVM on which the NetVM 
> > is
> > based, not dom0. Are you doing something special, such as trying to force
> > network access in dom0? If you actually wanted to install a package in dom0,
> > you'd use qubes-dom0-update, e.g.,
> > 
> > $ sudo qubes-dom0-update 
> > 
> > 3. How are you attempting to add/enable repos? The first place I'd check is
> > /etc/yum.repos.d/ .
> > 
> > - -- 
> > Andrew David Wong (Axon)
> > Community Manager, Qubes OS
> > https://www.qubes-os.org
> > -BEGIN PGP SIGNATURE-
> > 
> > iQIcBAEBCgAGBQJXs2UKAAoJENtN07w5UDAwkrUP/RFFippKtY3B9yjEcuSqZMjL
> > UJlowICR/OEN+UqLWnHIGAbu6NjXuqbjY258874Gqand/88yKwWrxdO5sxBotpyP
> > EcawKZ1zOJcWenbY5KPMFEpjAxCAgS5w+xLt7lSdjSkcozRVJ+9DI8irKTnFZIn8
> > CRr8y4wGfpwIos5bx281XSoNMJdsTIvOh7JcoWbFvJX0zy3yAVzKAP/Jko9MWkoh
> > jX/aKmeFZarA3oinfsxIHBQvGljUJ26YsI5laDOFk/zgAwarJYNZl57/FvkJ802N
> > EiS8b5kEvYgwuZfpUC0m/AtKsVvdmjGcKQSEhyRLfHnS+hRBBmahmRN3lssTSNbD
> > ussMFfJaWe2ycffrMXBWpsUg9n1YJnZie8qGv5cPzC8za6naETvmreLk94Nszjs6
> > wWW5a2MehWG92y8d8yBkLEorumYU9AYOajm4F7eZGTfLTpPC2b+GFrZnsFigdRcv
> > WHGppovvUpc3C64l0K/jBSWfbnCCEQDezcCYaG06haYhIs/WhCKEhtAG6X8MSe/P
> > TbeA9a7rfRU0IrCPFRz/1aJHTaSe+zzBAFOKeWTWfhktFS+2+1+M/5rft5AI90Cn
> > UgpT0IiJW+k2UIHoiOC+wRmGEiwT5ukRS/3jdyybvDtIB0FMBU4qwO3ymuMtqv68
> > AzcVAgfTdiGZZVyrUJC4
> > =YGie
> > -END PGP SIGNATURE-
> 
> Oh duh, that's why it's not persisting. I'm trying to install the wireless 
> drivers and bumblebee (for my nvidia card) on the dom0. So I do all of this 
> on the fedora template?

Ok, so I got it installed on the fedora template. I had to do the additional 
step of enabling the repos as they were disabled by default. After this though, 
when I try modprobe wl, I get "Module not found in directory 
/lib/modules/4.4.14-11.pvops.qubes.x86_64|

-- 
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/e2009e5d-3ad2-4d94-bad5-e608db3d4448%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] BCM Driver Install

[zackptg5]

On Tuesday, August 16, 2016 at 3:10:14 PM UTC-4, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2016-08-16 10:40, zackp...@gmail.com wrote:
> > On Tuesday, August 16, 2016 at 1:38:08 PM UTC-4, Andrew David Wong wrote: 
> > On 2016-08-16 10:35, zackp...@gmail.com wrote:
>  On Tuesday, August 16, 2016 at 1:33:05 PM UTC-4, Andrew David Wong 
>  wrote: On 2016-08-16 10:27, zackp...@gmail.com wrote:
> >>> I've been trying to install the drivers for my bcm4352 but I\ve
> >>> been unable so far. I'm on 3.2 rc2. Here's what I'm trying to
> >>> do:
> >>> 
> >>> [...]
> >>> 
> >>> However I get "No package aknod-wl available"
> >>> 
>  
>  Is your TemplateVM set to allow allow connections to RPMFusion's 
>  servers? You should be to do this either by enabling the RPMFusion 
>  repo or by allowing all connections for N minutes.
>  
>  
>  Aren't connections allowed by default on the sys-net? Am I doing all
>   of this on the wrong vm? I'm trying to get this working for dom0
>  
> > 
> > Ah, sorry. I misunderstood the original message (thought you were trying
> > to install something in a TemplateVM).
> > 
> > Yes, by default, all connections should be allowed from the default 
> > sys-net. Are you sure that the package actually exists in the repo?
> > 
> > 
> > Yes, it should exist based on everything I've read. I've also tried adding
> >  the bumblebee repos (which the files definitely exist there) and I'm 
> > getting the same errors which is why I believe that the repos aren't 
> > actually being added
> > 
> 
> Let's step back for a moment.
> 
> 1. You're doing all this from the sys-net terminal just to check whether the
> packages are available (because all connections should be allowed from
> sys-net) and/or temporary install the packages to test compatibility or
> something, right? You're not actually attempting to install a package in
> sys-net with the intention of having it persist there, right?
> 
> 2. You said you're trying to get this working for dom0. Normally, you'd
> install the drivers for a Wi-Fi device in the TemplateVM on which the NetVM is
> based, not dom0. Are you doing something special, such as trying to force
> network access in dom0? If you actually wanted to install a package in dom0,
> you'd use qubes-dom0-update, e.g.,
> 
> $ sudo qubes-dom0-update 
> 
> 3. How are you attempting to add/enable repos? The first place I'd check is
> /etc/yum.repos.d/ .
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJXs2UKAAoJENtN07w5UDAwkrUP/RFFippKtY3B9yjEcuSqZMjL
> UJlowICR/OEN+UqLWnHIGAbu6NjXuqbjY258874Gqand/88yKwWrxdO5sxBotpyP
> EcawKZ1zOJcWenbY5KPMFEpjAxCAgS5w+xLt7lSdjSkcozRVJ+9DI8irKTnFZIn8
> CRr8y4wGfpwIos5bx281XSoNMJdsTIvOh7JcoWbFvJX0zy3yAVzKAP/Jko9MWkoh
> jX/aKmeFZarA3oinfsxIHBQvGljUJ26YsI5laDOFk/zgAwarJYNZl57/FvkJ802N
> EiS8b5kEvYgwuZfpUC0m/AtKsVvdmjGcKQSEhyRLfHnS+hRBBmahmRN3lssTSNbD
> ussMFfJaWe2ycffrMXBWpsUg9n1YJnZie8qGv5cPzC8za6naETvmreLk94Nszjs6
> wWW5a2MehWG92y8d8yBkLEorumYU9AYOajm4F7eZGTfLTpPC2b+GFrZnsFigdRcv
> WHGppovvUpc3C64l0K/jBSWfbnCCEQDezcCYaG06haYhIs/WhCKEhtAG6X8MSe/P
> TbeA9a7rfRU0IrCPFRz/1aJHTaSe+zzBAFOKeWTWfhktFS+2+1+M/5rft5AI90Cn
> UgpT0IiJW+k2UIHoiOC+wRmGEiwT5ukRS/3jdyybvDtIB0FMBU4qwO3ymuMtqv68
> AzcVAgfTdiGZZVyrUJC4
> =YGie
> -END PGP SIGNATURE-

Oh duh, that's why it's not persisting. I'm trying to install the wireless 
drivers and bumblebee (for my nvidia card) on the dom0. So I do all of this on 
the fedora template?

-- 
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/7d44c34b-8193-4429-82ff-1321ef3ec60a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] BCM Driver Install

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 10:40, zackp...@gmail.com wrote:
> On Tuesday, August 16, 2016 at 1:38:08 PM UTC-4, Andrew David Wong wrote: 
> On 2016-08-16 10:35, zackp...@gmail.com wrote:
 On Tuesday, August 16, 2016 at 1:33:05 PM UTC-4, Andrew David Wong 
 wrote: On 2016-08-16 10:27, zackp...@gmail.com wrote:
>>> I've been trying to install the drivers for my bcm4352 but I\ve
>>> been unable so far. I'm on 3.2 rc2. Here's what I'm trying to
>>> do:
>>> 
>>> [...]
>>> 
>>> However I get "No package aknod-wl available"
>>> 
 
 Is your TemplateVM set to allow allow connections to RPMFusion's 
 servers? You should be to do this either by enabling the RPMFusion 
 repo or by allowing all connections for N minutes.
 
 
 Aren't connections allowed by default on the sys-net? Am I doing all
  of this on the wrong vm? I'm trying to get this working for dom0
 
> 
> Ah, sorry. I misunderstood the original message (thought you were trying
> to install something in a TemplateVM).
> 
> Yes, by default, all connections should be allowed from the default 
> sys-net. Are you sure that the package actually exists in the repo?
> 
> 
> Yes, it should exist based on everything I've read. I've also tried adding
>  the bumblebee repos (which the files definitely exist there) and I'm 
> getting the same errors which is why I believe that the repos aren't 
> actually being added
> 

Let's step back for a moment.

1. You're doing all this from the sys-net terminal just to check whether the
packages are available (because all connections should be allowed from
sys-net) and/or temporary install the packages to test compatibility or
something, right? You're not actually attempting to install a package in
sys-net with the intention of having it persist there, right?

2. You said you're trying to get this working for dom0. Normally, you'd
install the drivers for a Wi-Fi device in the TemplateVM on which the NetVM is
based, not dom0. Are you doing something special, such as trying to force
network access in dom0? If you actually wanted to install a package in dom0,
you'd use qubes-dom0-update, e.g.,

$ sudo qubes-dom0-update 

3. How are you attempting to add/enable repos? The first place I'd check is
/etc/yum.repos.d/ .

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

iQIcBAEBCgAGBQJXs2UKAAoJENtN07w5UDAwkrUP/RFFippKtY3B9yjEcuSqZMjL
UJlowICR/OEN+UqLWnHIGAbu6NjXuqbjY258874Gqand/88yKwWrxdO5sxBotpyP
EcawKZ1zOJcWenbY5KPMFEpjAxCAgS5w+xLt7lSdjSkcozRVJ+9DI8irKTnFZIn8
CRr8y4wGfpwIos5bx281XSoNMJdsTIvOh7JcoWbFvJX0zy3yAVzKAP/Jko9MWkoh
jX/aKmeFZarA3oinfsxIHBQvGljUJ26YsI5laDOFk/zgAwarJYNZl57/FvkJ802N
EiS8b5kEvYgwuZfpUC0m/AtKsVvdmjGcKQSEhyRLfHnS+hRBBmahmRN3lssTSNbD
ussMFfJaWe2ycffrMXBWpsUg9n1YJnZie8qGv5cPzC8za6naETvmreLk94Nszjs6
wWW5a2MehWG92y8d8yBkLEorumYU9AYOajm4F7eZGTfLTpPC2b+GFrZnsFigdRcv
WHGppovvUpc3C64l0K/jBSWfbnCCEQDezcCYaG06haYhIs/WhCKEhtAG6X8MSe/P
TbeA9a7rfRU0IrCPFRz/1aJHTaSe+zzBAFOKeWTWfhktFS+2+1+M/5rft5AI90Cn
UgpT0IiJW+k2UIHoiOC+wRmGEiwT5ukRS/3jdyybvDtIB0FMBU4qwO3ymuMtqv68
AzcVAgfTdiGZZVyrUJC4
=YGie
-END PGP SIGNATURE-

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

Re: [qubes-users] Qubes 3.2-rc2 very high hard disk activity

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Aug 16, 2016 at 12:55:03PM +0200, donoban wrote:
> Hi
> 
> The computer which I upgraded from 3.1 to 3.2 is having some
> performance problems when I have a few VMs running. It has a non-SSD
> hard disk so I know it's going to do a bottleneck and I don't expect a
> fast perform, but I'm sure that it's running very worse than it did
> with 3.1.
> 
> 
> Using iotop on dom0 I examined the process which use the hard disk when
> it goes totally lagged. I see:
> 
> - Some [loopX] processess... are them loops for the VMs? I suppose it's
>   normal to have a pretty high I/O work from this processes.

Take a look at `losetup -a` output to match which VM corresponds to
which loop device.

> - systemd-journald is pretty common when the lag starts, in
>   fact I have 873Mb's on /var/log/journal , is this standard?

Yes, this is where journald keep logs.

> - I also see some rsyslogd process and qvm-sync-clock 

Does rsyslogd use a lot of CPU, or is just idle?

> I have to say that this never happened with Qubes 3.1, I just couldn't
> open more than 4/5 AppVM's, but it always worked pretty fine.

Take a look at `top` in dom0 and sort processes on memory usage (single
'>' key press). If it's about some dom0 process using too much memory,
you should see it there. Normally at the top should be Xorg process (on
my system it has just under 200M in RES column, but you probably have
even less).

Also check swap usage in VMs - maybe its about some VM, not dom0?

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

iQEcBAEBCAAGBQJXs2FmAAoJENuP0xzK19csVscH/37bToT7CWefM59YUYmF1Wby
fGwURNsuLxeMiZl+27q5A1dX0H5MtvG+awSr1qzLtjh+TVxA7ENKmJ/OiYfMd7go
f1Sb0v8P4CN0rZxWl58AQhvTAnHl1A2U2TliN2dgdLWTFDDnyxNmNc2s92NbCB0A
x+Lp9r8bdQXAWjtO8+vcLtjXSY/d1BThBSaFAJqIMmQQVM7B8cLMl3MqqqUqfgay
2iwpr7hsTNvU4iFwpNBucv7Tn48a+BiSRZALwI5/sOD11UbYCdcyYQL/UkRnVL+J
HZ2ZqDOZVgxAFE3Aw7XXMJdiZbZqvIfbLPA7nFhy1JgpP+Jc0z2O/p/xmTbKZlo=
=+U30
-END PGP SIGNATURE-

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

Re: [qubes-users] Qubes 3.2-rc2 very high hard disk activity

[donoban]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 08/16/2016 08:42 PM, Chris Laprise wrote:
> Each vm has its own swap. If you misconfigure the vm with too
> little memory (this can easily happen if you inadvertently turn off
> memory balancing) then it can exhibit the symptoms you describe.
> 
> Chris
> 

oh, maybe my problem is a custom qmemman.conf I will check it.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXs2BIAAoJEBQTENjj7Qilo9sP/jhXRxTt296dI/iOURA/QPBm
hmKpuUcl/2MHsfrIkLrTjgrLkZL8EozkSbvR2bL3QStwax8KrA/roMZIvmf0E+BI
Zzm2d0bpM32NKU7kr0WtDIC0unOT+nhezoFBzo+RW/YZDwlmJG/7fSVNaWb2JH0J
QAlbDylSPMEgUBI8OKCs3JNV/IAzsI5F4IxRLvQb/JYMDVYkYmaqMRUW3BdD+qOv
cmFqT2dc5IQOSMqqe87Q84VoUr83mH4mO4QMeggbuPfi6q46XEq9YrS7YTtM2UKy
3YCFvMDrjuD13dtNzYZkPDbe7nynB5crO65u4mttG0Q0xb8gfN9QR893NSIoW7p5
/zOqjoHazUjO/pzsETFCr76fZ16JRh/DaIMD5x8yQXwB/iQhIodsaAMpyO/6ViBD
6TVZiOkGnuovrRpMS6I0Fitb0Qk6SL4hFL1UNeM1wEhMF3hTKn5cjQXAgm4MDjzS
hfsQzKBf1eI5A+7sab+F8raIexm1S2r/D0g680OQIh5O9lw9WldXdXOgUWW4POHV
751yfzYuCl4WNHL/5UoXbLhyER0p9AHDu3QCd0CLsN24ChP8J5WQC8VyrYVpSFJG
K3eIzRCPO1gZmGEd6naItbDUfggSI+bbrNl8+7aW2QHDMx26Hd7e731+CiaYwvz1
+DvCGkZ5e5nIANId7pDi
=gWb1
-END PGP SIGNATURE-

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

Re: [qubes-users] Qubes 3.2-rc2 very high hard disk activity

[Chris Laprise]

On 08/16/2016 01:39 PM, donoban wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 08/16/2016 06:17 PM, Andrew David Wong wrote:

On 2016-08-16 03:58, donoban wrote:

I also have experienced a lot of process killed because I run out
of memory. This never happened with 3.1.


Is it possible that the high HDD activity is excessive swap usage
due to low memory?



I don't use swap at this moment and with 3.1 I didn't too. I should
add it probably, but if I "fix" the "hard disk problem".



Each vm has its own swap. If you misconfigure the vm with too little 
memory (this can easily happen if you inadvertently turn off memory 
balancing) then it can exhibit the symptoms you describe.


Chris

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

Re: [qubes-users] BCM Driver Install

[zackptg5]

On Tuesday, August 16, 2016 at 1:38:08 PM UTC-4, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2016-08-16 10:35, zackp...@gmail.com wrote:
> > On Tuesday, August 16, 2016 at 1:33:05 PM UTC-4, Andrew David Wong wrote:
> > On 2016-08-16 10:27, zackp...@gmail.com wrote:
>  I've been trying to install the drivers for my bcm4352 but I\ve been
>   unable so far. I'm on 3.2 rc2. Here's what I'm trying to do:
>  
>  [...]
>  
>  However I get "No package aknod-wl available"
>  
> > 
> > Is your TemplateVM set to allow allow connections to RPMFusion's servers? 
> > You should be to do this either by enabling the RPMFusion repo or by
> > allowing all connections for N minutes.
> > 
> > 
> > Aren't connections allowed by default on the sys-net? Am I doing all of
> > this on the wrong vm? I'm trying to get this working for dom0
> > 
> 
> Ah, sorry. I misunderstood the original message (thought you were trying to
> install something in a TemplateVM).
> 
> Yes, by default, all connections should be allowed from the default sys-net.
> Are you sure that the package actually exists in the repo?
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJXs09cAAoJENtN07w5UDAweKIP/2BURtS0rn4c/I88E+gXGQ41
> TizmSMCdVDFiZYZrnv9N5xJLocQW1f5xVnCU8cz1RLRuDO3DDK10aphQ8ZZ3AI2p
> kHi/knLFUq2ZI1JrF85t7HNGugPLnZRQyTgMEadpR1FAYOrXeACbpQIyGe8PmiSX
> i9oyZt4JW1tlsWYBFOergIhea6qh9Z5LXImcyQ3Nyus4+2fElLzDpmQMEKIEBf0n
> a5V/69bJoShwnFB269+wzjIKUXjwuVszycAV5ahzDx9u9II4+opEeNwvFXkNEmox
> wmtSkOOYTUgNXuH6ALkldy9LI0p27H2fuAvSyfXetRmfusOkc9W+W2tdXa3tIqOi
> mcqmNdx3+gQ9V55LqwbbGBJXUSyJkhd8s0p8UdZajjFbwoMd3TI9w4j8dN+0g7c3
> fbzWzM9SOUzvZYs/s6W3v+uT/U5cUWz9jtgwucalJVeWR+5/X4xMyE1zZG66Yf9B
> mFQ8H1DmcRlBuCsSBq3HQKninUrSl9MUGEnS5QjyJ7OPMandiG43Q16GbEu7pEvP
> w2DcuMubMA/3dBrddUF/7CeHqzVBfL0a9PrkRGecWPQL3abrnzo3IW2008wZBTEM
> SpS6VFLuxLrSHZ+9FuqK1wusrD6SqjPO5hs84Us9aeIHN/Qb13VIklJcEeHAtebK
> /wmfz1/gkcoUXv2ByDLV
> =53qC
> -END PGP SIGNATURE-

Yes, it should exist based on everything I've read. I've also tried adding the 
bumblebee repos (which the files definitely exist there) and I'm getting the 
same errors which is why I believe that the repos aren't actually being added

-- 
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/52a04328-4d8b-4e55-b487-c27669d77065%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] 3.2rcX Default Display (Login) Manager

[entr0py]

entr0py:
> donoban:
>> On Mon, 15 Aug 2016 12:06:36 -0700 (PDT)
>> 3n7r0...@gmail.com wrote:
>>
>>> I haven't had a chance to try out 3.2rc yet. Can someone please tell
>>> me what the default DM is to launch XFCE4? Thanks!
>>>
>>
>>
>> It is the same of Qubes 3.1, lightdm if I'm not wrong.
>>

>From 
>https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/comps-qubes.xml
> :

xfce-desktop-qubes
Xfce4
A lightweight desktop environment that works well on low end 
machines.
true
false

  xfce4-panel
  xfce4-session
  xfce4-settings
  xfce4-settings-qubes
  xfconf
  xfwm4
  xfdesktop
  
  lightdm-gtk

Going with lightdm then unless someone tells me otherwise... Thanks.

-

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

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

Re: [qubes-users] BCM Driver Install

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 10:35, zackp...@gmail.com wrote:
> On Tuesday, August 16, 2016 at 1:33:05 PM UTC-4, Andrew David Wong wrote:
> On 2016-08-16 10:27, zackp...@gmail.com wrote:
 I've been trying to install the drivers for my bcm4352 but I\ve been
  unable so far. I'm on 3.2 rc2. Here's what I'm trying to do:
 
 [...]
 
 However I get "No package aknod-wl available"
 
> 
> Is your TemplateVM set to allow allow connections to RPMFusion's servers? 
> You should be to do this either by enabling the RPMFusion repo or by
> allowing all connections for N minutes.
> 
> 
> Aren't connections allowed by default on the sys-net? Am I doing all of
> this on the wrong vm? I'm trying to get this working for dom0
> 

Ah, sorry. I misunderstood the original message (thought you were trying to
install something in a TemplateVM).

Yes, by default, all connections should be allowed from the default sys-net.
Are you sure that the package actually exists in the repo?

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

iQIcBAEBCgAGBQJXs09cAAoJENtN07w5UDAweKIP/2BURtS0rn4c/I88E+gXGQ41
TizmSMCdVDFiZYZrnv9N5xJLocQW1f5xVnCU8cz1RLRuDO3DDK10aphQ8ZZ3AI2p
kHi/knLFUq2ZI1JrF85t7HNGugPLnZRQyTgMEadpR1FAYOrXeACbpQIyGe8PmiSX
i9oyZt4JW1tlsWYBFOergIhea6qh9Z5LXImcyQ3Nyus4+2fElLzDpmQMEKIEBf0n
a5V/69bJoShwnFB269+wzjIKUXjwuVszycAV5ahzDx9u9II4+opEeNwvFXkNEmox
wmtSkOOYTUgNXuH6ALkldy9LI0p27H2fuAvSyfXetRmfusOkc9W+W2tdXa3tIqOi
mcqmNdx3+gQ9V55LqwbbGBJXUSyJkhd8s0p8UdZajjFbwoMd3TI9w4j8dN+0g7c3
fbzWzM9SOUzvZYs/s6W3v+uT/U5cUWz9jtgwucalJVeWR+5/X4xMyE1zZG66Yf9B
mFQ8H1DmcRlBuCsSBq3HQKninUrSl9MUGEnS5QjyJ7OPMandiG43Q16GbEu7pEvP
w2DcuMubMA/3dBrddUF/7CeHqzVBfL0a9PrkRGecWPQL3abrnzo3IW2008wZBTEM
SpS6VFLuxLrSHZ+9FuqK1wusrD6SqjPO5hs84Us9aeIHN/Qb13VIklJcEeHAtebK
/wmfz1/gkcoUXv2ByDLV
=53qC
-END PGP SIGNATURE-

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

Re: [qubes-users] BCM Driver Install

[zackptg5]

On Tuesday, August 16, 2016 at 1:33:05 PM UTC-4, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2016-08-16 10:27, zackp...@gmail.com wrote:
> > I've been trying to install the drivers for my bcm4352 but I\ve been
> > unable so far. I'm on 3.2 rc2. Here's what I'm trying to do:
> > 
> > [...]
> > 
> > However I get "No package aknod-wl available"
> > 
> 
> Is your TemplateVM set to allow allow connections to RPMFusion's servers? You
> should be to do this either by enabling the RPMFusion repo or by allowing all
> connections for N minutes.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJXs05EAAoJENtN07w5UDAw6S0QAJ4t0nRuBrk14MmXfRQJYYSb
> 6muforTZJIfQcd+3j/IRIazJaxgKAcxEyUv+kKuPZ3DbWmfO3rAJpyKwn2jolE5+
> 3cphXa7r9YNMyxKKTaKoQBs16wfwMHjtTWDaCCfK8mmtYdYZm45bkcNDtK3RGlD5
> DyuJWEbHE1PE2AedI4LR0nmwKhynBaHxMmzB9QQ461layI6wRI6vIEjl2HVYyol9
> Ixje8clRdZ6gdH9Bl0tRT04ExVUWlkPwIG1f+2eBX1Hpg4Y2V1hQ4GNA1JF+vhIh
> TdIR8ubyXJYLg4LoFISv2K6in81o8rQww12kY2qwubG9IvJgEtdrtzm51wnTJFnc
> Y5HXh8ypNzidzsFSzsjWSzmHwHuV+uqR0md1kyIyqmoMTMG0Kz339TKoN5eYU9Gk
> ImxajOFq6fFYI2zkkqKLKHX3otEhxaH15DEKlU4+uFkfPIhq1d5rBbYdpUWnxT2G
> fUfIjBDXLpFhfsjDEJ1YmVEmjc6tNA4nIQXdg8ecAWgJKux2HtSGrbNntZdllMPD
> F0TK8XegkO6XYr3547MX3oyIcJhrrrdS7H52NgD/QMVi0GierXTpE41W2ZOT3+W1
> Xra7AzczTEnaHVtX9WRlKE+yEZAM7MA4Re978MMQ2wexLmg4/iSazf49MLyRUeNb
> 2khyArlTTWk3eEOi1/RK
> =Azfh
> -END PGP SIGNATURE-

Aren't connections allowed by default on the sys-net? Am I doing all of this on 
the wrong vm? I'm trying to get this working for dom0

-- 
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/b3af4f18-1281-40b7-81b1-5d11916dc4cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: BCM Driver Install

[zackptg5]

On Tuesday, August 16, 2016 at 1:27:11 PM UTC-4, zack...@gmail.com wrote:
> I've been trying to install the drivers for my bcm4352 but I\ve been unable 
> so far. I'm on 3.2 rc2. Here's what I'm trying to do:
> 
> 
> su -c 'dnf install 
> http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E 
> %fedora).noarch.rpm 
> http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm 
> -E %fedora).noarch.rpm'
> dnf install akmod-wl kernel-devel
> 
> However I get "No package aknod-wl available"

Update on this, in trying to add bumblebee to this I get the same error with 
those packages so I believe that the repos are not getting added. Any idea as 
to why? I am running all of this on the sys-net terminal

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/860487ae-54ca-480a-80df-2ec883fff484%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] BCM Driver Install

[zackptg5]

I've been trying to install the drivers for my bcm4352 but I\ve been unable so 
far. I'm on 3.2 rc2. Here's what I'm trying to do:


su -c 'dnf install 
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E 
%fedora).noarch.rpm 
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm 
-E %fedora).noarch.rpm'
dnf install akmod-wl kernel-devel

However I get "No package aknod-wl available"

-- 
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/7e78e1cf-864b-402d-aae1-d3f726950c79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Backup Encryption Options

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 10:07, entr0py wrote:
> According to:
> 
> https://www.qubes-os.org/doc/backup-restore/ 
> https://groups.google.com/forum/#!searchin/qubes-users/ 
> backup$20encryption|sort:relevance/qubes-users/sS4A3vJdCQ8/w9-jIj5VW9oJ
> 
> Qubes backup system has a "weak key derivation scheme".
> 
> Is a reasonable workaround to just put the backups (with or without Qubes 
> encryption) on a LUKS device?
> 

Yes.

You can also read more about the key derivation issue here:

https://github.com/QubesOS/qubes-issues/issues/971

> And a general cryptsetup question: Is there any security benefit to 
> encrypting an entire drive versus encrypting individual partitions (ie 
> /dev/sda vs /dev/sda1)?
> 

Hm. Good question. One case where encrypting the entire drive would be better
is if the OS might potentially write metadata, temp files, etc. to unencrypted
partitions. If we're only considering an encrypted volume for storing data at
rest (e.g., encrypting an entire external hard drive versus just a partition
on that external hard drive), then I'd wager there's not much of a difference.
It would be best to ask the cryptsetup devs, though (or just anyone more
knowledgeable than me).

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

iQIcBAEBCgAGBQJXs0tHAAoJENtN07w5UDAw/HMQAKayEjqVm8iVj6kQN7oMy9G5
R2mCXRXRy1YOB13lbiLhAt5P0xokp8TWVUedVV5Ysx/64mW2tTwCzwfdQvBSzZUn
JmK7PbhGOgkK+Az5QZhVC9iYk+QtuamVesjvcorc+V2+321guKOj3nC7rNA32KTV
qKrN+ows67P+ASfHP7K3Gf+KMVOVIFxqUP1olbOomEolVGXgIImBFK896kGyowN4
VPSH2AJhp1X1i5EhBsGWvBVvqZnH1S+FvT1f948RBJzpEeQBWfSlTdv+U79l6nsB
X1q1uhm1wWQmung+UMtqVnRlJq2Qo/QSUZt7TOYxGWI1PjX7+2BoV4DqB/2dYW5r
Yy8a7MEXZcKWFTAAu2qksGfglFwy2W1mMb6/0Pcmi/QQvbzmgcGKV9k2IaNfwXpA
J6GSrzEpCoaR5rYUjuTm7dDT41XhPZuHM0dAgdg8MPvppjIDLh6cjZF+y0fogMIm
PshSa4hgRGouxwAb1wfh8C5Y1J/tixm1bU9MNgQCTD6SXL/bP1wKAHWZLWV7cORM
66dg4ZQk83JaY0Wcc4ByoVWsxRVXfIi5ALlcDdGI/2VAg+MCTTxsCfXDcFO6KyPh
so6DotmuMQr+6NlYE0kvRcHeoVb6xc+vUIX9eSZMXoSlyZgMW1CuXZ4pICQHsr68
E2Km5Pp6SiuYbsVgP6G/
=Tmo2
-END PGP SIGNATURE-

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

Re: [qubes-users] 3.2rcX Default Display (Login) Manager

[entr0py]

donoban:
> On Mon, 15 Aug 2016 12:06:36 -0700 (PDT)
> 3n7r0...@gmail.com wrote:
> 
>> I haven't had a chance to try out 3.2rc yet. Can someone please tell
>> me what the default DM is to launch XFCE4? Thanks!
>>
> 
> 
> It is the same of Qubes 3.1, lightdm if I'm not wrong.
> 

Thanks. Somewhat confused though - I thought 3.1 was KDM? KDM would have many 
dependencies for an XFCE system...



-

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

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

Re: [qubes-users] QUBES 4.0 release date...?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 08:44, neilhard...@gmail.com wrote:
> Does anybody have any rough idea of the Qubes 4.0 release date...?
> 

No official release date has been announced yet, but to get an idea, you can
take a look at the currently open issues for 4.0 here:

https://github.com/QubesOS/qubes-issues/milestones/Release%204.0

You can also see our roadmap, which includes the goals for 4.0, here (but
please note that this roadmap hasn't been updated in a while, so some of the
dates are off):

https://github.com/rootkovska/qubes-roadmap

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

iQIcBAEBCgAGBQJXsz3IAAoJENtN07w5UDAwWBUQAKBYoTcm1MJ0d/gwgkJACQm3
bTJ/iVwAh7P41y7lxHzVWQqRShU4RB+YW9j1oHhgv04tbwkSbFTSOGB92f1V8gOk
ZvT8GB45ZmQyt3CqtkrQeTp9dyUZ+W++Nn9v3cyvGWin7msJIcl9b4YCBNPVyFHh
3nCZTVxjz5jlssqi2CUCF2pxJzhM1sqTVv2ckJCrt6ggP+tzOmqG1WRTHbw/A5hA
rCeqmjVk2vxrVJl/Uf5+4pnms1njcpRgj1Y855BhWRVAEPscAc4JzzsQEygSkPJo
hHD29E6YAnyLWBlvFJc+olqw5rG9qHDfoJYwaE8m5xTNnpVhnzIbCSDTdywxn3Rl
CD20uMHSIgFoep4VATJugGNiOIAsd9E91gPKc+Luob4qF0KaoaEkPhngOZop07tn
to4Ix10dxjGej78Q8AjW6aDxejSTozbq1k/1ahS2donRCOoFRgX3DM2GPF+rA4Qa
ljRoBdaJv2H4AoU6t52t7Dhm6gqYJPhCcxuUeZcc8hqhSMzmfBShmeAbH9JA5B7d
tlsfQUq5FdphY0rPzhJy/qG98hJWVriYc7y/8IDEx9XPqIQU/+R9wB2pBpSj/WRZ
1UwfDogdJno6l9K/v8dD6FnPtis2ucV8OpzTM9keJV1bDiWPDSKq1YunonjvarGD
U9O147/RhTqpQ/dGJxC2
=994B
-END PGP SIGNATURE-

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

Re: [qubes-users] Qubes 3.2-rc2 very high hard disk activity

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 03:58, donoban wrote:
> I also have experienced a lot of process killed because I run out of 
> memory. This never happened with 3.1.
> 

Is it possible that the high HDD activity is excessive swap usage due to low
memory?

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

iQIcBAEBCgAGBQJXszyCAAoJENtN07w5UDAwzkEP/A/9ugXJzH778Mz1Npg4z87+
1310lQghrK6bcQpMB6tnRLrRKKOJuWVKow1vRDdDVJCZ+W2lhK0XetHUVyBeD6VZ
N8UZO6o3DbSeuVxVvRl6mcFvE6NlG9udNWX2zpM3MG64ArQkNu5gLm15RStV/xlY
Np1orD6HbqWHn+YY9ZreEztHSs8bOD//ge7SqAplXfyDiFeJf2X/Rv1eOnrYxYLj
oYvx2B91faS6KmU5gzHLZbGoCntp93+bDasKD0UtDsEN6Dy9AtAiqpLE11IEUr1g
8iJ4IFuixtlq/dnxIF/yqFVaZT+MJWqKRYiPUhM7l8yN4kYyYtIS/HvRt0yst8CK
+JLkULkk0eEw2qZE7y+e9peZW6+NFjnfVKhnXv/RABrdInnC3mFifVjWnuRfA6RJ
ub8rYXOq/32pCp/jd6zQU7u+zyvuvoflRF5RxsTPSYlWZ5wxy4+PXwG2yM7FHVNK
D1L8fjJeFoYZMtbRwwnhCaycIwSKo/YE5NcAN0HJCZ0f6YVdDXcXrp1aMpw7ROGW
SQX9hqCBWlKMzK6QEpxkDo+WhabPFXr2d0377SOikwk2PwocpG73v8mpq54fWhV+
pHsgU9+ZkrCckhGPSOGxFjT9qEZWKDbPmsYw2+yTng2/+oWaJcHKASmn4f1M4ZYl
KBDlAl/mD7q6pcZJE/O7
=iePj
-END PGP SIGNATURE-

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

Re: [qubes-users] Query on upgrade process - what next after downloading the fedora23 template?

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Aug 16, 2016 at 09:07:24AM -0700, Andrew David Wong wrote:
> On 2016-08-16 00:18, eobail...@gmail.com wrote:
> > 
> >> Sorry for the misunderstanding. You do not have to (and, indeed, cannot)
> >>  update your TemplateBasedVMs from Fedora 21 to Fedora 23, since they're
> >>  Template-based.
> > 
> > Normally speaking, though, if I'm running a computer with a particular 
> > operating system, I can upgrade that operating system to a new version. So 
> > are you saying I can't do this with the various VMs run by Qubes?
> > 
> 
> No, you certainly can. However, the way to do it in Qubes (due to the way the
> Template system works) is to upgrade the operating system in the TemplateVM,
> not the TemplateBasedVM. This is because the TemplateVM is where the operating
> system files reside. They do not reside in the TemplateBasedVM -- only user
> data resides there.
> 
> >> This means that they don't have a root filesystem (where the OS and 
> >> programs are stored) of their own. Instead, they get their root
> >> filesystem from the TemplateVM on which they're based. As long as your
> >> TemplateVMs have been upgraded correctly, your TemplateBasedVMs should
> >> work with the upgraded TemplateVMs normally.
> > 
> > The result of running "sudo qubes-dom0-update qubes-template-fedora-23"
> > was not to update a TemplateVM, though. It created a new TemplateVM, so now
> > I have 2: fedora-21 and fedora-23 - the second of which doesn't yet seem
> > to have a purpose unless or until I create new VMs
> > 
> 
> That command ("sudo qubes-dom0-update qubes-template-fedora-23") installs a
> new fedora-23 template from the repo. It is the preferred way to obtain a
> fresh fedora-23 template. However, if you instead want to upgrade an existing
> fedora-21 template to fedora-23 (e.g., to preserve any customizations you've
> made), then you must use the in-place upgrade procedure:
> 
> https://www.qubes-os.org/doc/fedora-template-upgrade-21/
> 
> >> The fact that you're now asking whether you should shut down all of your 
> >> VMs one by one suggests that you may not have followed the above
> >> procedure, since rebooting dom0 entails shutting down all of those VMs
> >> (but it's also possible that this is just a miscommunication).
> > 
> > no, it just means I'm doing this process gradually, leaving space for
> > things like, eg, restarting a VM in order to post things on the Internet
> 
> Ok, understood.
> 
> >> 
> >> It's also not clear to me what you mean by "tell them in VM-manager to be
> >>  fedora-23 not fedora-21 VMs."
> > 
> > "upgrade the operating system the VMs are using to version 23 of fedora 
> > rather than version 21"
> > 
> 
> Ok, got it.
> 
> >> If you've just performed an in-place upgrade on a template (from Fedora
> >> 21 to Fedora 23) with the intention of using it, then it would indeed
> >> make sense to base your AppVM on this newly upgraded template (if it
> >> wasn't already). Again, as long as the upgrade has been done correctly, 
> >> everything should work normally.
> > 
> > based on that, it doesn't seem to be - I don't think my system is
> > currently in the state you describe
> > 
> > It is possible that the step that went wrong is step one - "Upgrade fedora 
> > templates". Would you normally expect that after that first step, the
> > default TemplateVM would have upgraded itself to the most recent available
> > version of Fedora? Because that didn't happen.
> > 
> 
> Ah, sorry for the misunderstanding. No, there are additional steps required to
> upgrade an existing Fedora 21 template to Fedora 23 that are not listed on
> that page. They are instead listed on this page (same as linked above):
> 
> https://www.qubes-os.org/doc/fedora-template-upgrade-21/
> 
> > 
> > Bearing in mind, in all of this my ultimate purpose is "make my Qubes 
> > installation indistinguishable from a fresh installation of version 3.1". 
> > Which is not yet the case!
> > 
> 
> If this is your goal, then as noted above, it may be easier and more
> preferable to obtain a fresh fedora-23 template from the repo (as you've
> already done). Either way works, and which is preferable depends on things
> like the modifications (if any) you've made to your template(s) and how
> acceptable you find the results of the in-place upgrade procedure for your
> individual purposes.

I'm not sure if I understand the intention here, but isn't this all
thread about just switching AppVMs to the new template (either upgraded
in-place, or downloaded fresh one). You can do this in VM settings -
just change "fedora-21" to "fedora-23" in template selection drop-down.
You need to do this for every VM (unless you want to keep some of VMs
using old template for some reason).

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

Re: [qubes-users] Re: Windows7 issue with Dom0 GUI Daemon

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 00:26, Drew White wrote:
> On Tuesday, 16 August 2016 11:33:18 UTC+10, Andrew David Wong  wrote:
>> The issue for this was recently closed:
>> 
>> https://github.com/QubesOS/qubes-issues/issues/1704
>> 
>> Rafał, is the fix for this available in a testing repo (or already 
>> live)?
>> 
> 
> 
> How does a person re-open the issue?
> 

If you're logged into GitHub, there should be a "reopen" button (not sure if
visibility is permissions-based). You should probably test the patch that is
supposed to fix the issue before reopening it, though. The patch should be
available for testing soon.

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

iQIcBAEBCgAGBQJXszwAAAoJENtN07w5UDAwG68P/id8COtBc12eAS5k/SY+jM6f
L/c07vYQlOe2vFnZ9sTerZyNOexJkzxEZO+GH/mF0I7hQEaHkMnW9uPFyFb87sjO
cePuSbhid4atjWRER/jlkTc0RS5nExwUPcLkKtNu+iPs0rS7cvRjl1w85V78b4to
py3j+bgAwd9Tm/1xxLHRhSeQXiCaX9gX3ENa5BcV/FkvwWRaw8yqFeLIFh7+LpdB
vu1CV2j8SV5qMQ8IJvPYPhXWAzMSw89d5oOcEAn8WDc4L4qBnHdtRZk4EiqtG8H6
fBWCWq6Lm/Hu8cSPYLGF4jXgnmyf21CloMaIyQy0pbHUrWK9azxk4semjxE9z1kR
aAF8W3xMM9FBRrvLUD2zbfx+PSzc5quRFoyUGh7F57ZlzQpOMBsPVZ2eYYUo+pNE
PXryQTbUPSLmrF+NZ1VerepUVHPTm/5baDfSUV8+U3THLn42oA6Ntf4DwZqhA+SI
LCgV9PBvkv/dAGfO1OFGvFux0ijAu6xBN4EP2aNXIxh0oQCptdYTzvm1k69DwS7X
TDlc4w5tlo0WYRL3QzYgtO6QaU3Y9AacmDysOvqju1aNlbwUcCtZOdR7yGQTCW0d
vBgUb3AIAEEHMG+N8SxsmNzheuCkBu/t3u2dDnaeRFSljX3UwWUIk6p4uLBBE7HC
gjKUGst06SH8o+1oHxBB
=KluW
-END PGP SIGNATURE-

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

Re: [qubes-users] Current Windows instructions?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 00:24, Drew White wrote:
> On Tuesday, 16 August 2016 11:40:44 UTC+10, Andrew David Wong  wrote:
>> Here it is:
>> 
>> https://www.qubes-os.org/doc/windows-appvms/
>> 
>> I'll update that other page. Thanks!
>> 
> 
> I see the instructions, but has the seamless issues been resolved yet? Or
> do they still remain?
> 

Are you referring to this issue?

https://github.com/QubesOS/qubes-issues/issues/1896

If so, it looks like it was closed recently, so the patch should be available
for testing soon.

> Will the tools be working any time soon?
> 

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

iQIcBAEBCgAGBQJXszsaAAoJENtN07w5UDAwNF0QAJdblELCYGhiCyoUp4VGIt5v
pt0nprLLyPozcuAbLTuUTNftBd+s/8O0jszEYDixdIJuO0IBeSALk2xLzIvB3rI/
RAxNrptMabaEaK9/S4tnVFmKvQpogbLx1GotmWuk5G+veDUjXk4WhiCzeuY/XwVA
60DEj1JpBbilASsoKNkPpHLeD1g4IMcv/oiZ54DvzokhCFb1L99Ob61Aeyu/1m3j
oz2e5eqvUxqaM1BkI3ZqdXMAyhGkqHsrlV0uO5gHJmaIJs/erSb6QCcTTocrH4xr
egtQgZFJ0fDYgQZp/mFVfLJgb6BH7GyX0O7HE0Qks+3d0VClmZFb/7ZiC8pFul9u
yx+CI7oOrtk02LbBxzfrZymlDFzfPocyS0l1OrEM55PcGIBbGqVqf9kPXma9a3Ft
PKM8Z6d9DzZhijSkl85noenzCR5ls7B363pYPeZEY1OFbTlorTiGE3A5y/Vi07r+
l+RyGbyvrUuG4Uv6xaxE6ONSZMHiW497Qiz3LdeLeY6tQrEg+yxh8v9VeXXQc8EZ
t+UaAbP34FFe4saUBubuCBVVL0aAZf/iF0GJC1JNJBF+G0NslBBzhAKW1qcUirrY
Rc3mMFTZBG69mf6s9su2iwo+oNid16rIwlETa6zRsmduw6Src4VLeScaKkE1t1SP
CRrNe+TVljQcTUzMGSaj
=sF0Q
-END PGP SIGNATURE-

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

Re: [qubes-users] Query on upgrade process - what next after downloading the fedora23 template?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 00:18, eobail...@gmail.com wrote:
> 
>> Sorry for the misunderstanding. You do not have to (and, indeed, cannot)
>>  update your TemplateBasedVMs from Fedora 21 to Fedora 23, since they're
>>  Template-based.
> 
> Normally speaking, though, if I'm running a computer with a particular 
> operating system, I can upgrade that operating system to a new version. So 
> are you saying I can't do this with the various VMs run by Qubes?
> 

No, you certainly can. However, the way to do it in Qubes (due to the way the
Template system works) is to upgrade the operating system in the TemplateVM,
not the TemplateBasedVM. This is because the TemplateVM is where the operating
system files reside. They do not reside in the TemplateBasedVM -- only user
data resides there.

>> This means that they don't have a root filesystem (where the OS and 
>> programs are stored) of their own. Instead, they get their root
>> filesystem from the TemplateVM on which they're based. As long as your
>> TemplateVMs have been upgraded correctly, your TemplateBasedVMs should
>> work with the upgraded TemplateVMs normally.
> 
> The result of running "sudo qubes-dom0-update qubes-template-fedora-23"
> was not to update a TemplateVM, though. It created a new TemplateVM, so now
> I have 2: fedora-21 and fedora-23 - the second of which doesn't yet seem
> to have a purpose unless or until I create new VMs
> 

That command ("sudo qubes-dom0-update qubes-template-fedora-23") installs a
new fedora-23 template from the repo. It is the preferred way to obtain a
fresh fedora-23 template. However, if you instead want to upgrade an existing
fedora-21 template to fedora-23 (e.g., to preserve any customizations you've
made), then you must use the in-place upgrade procedure:

https://www.qubes-os.org/doc/fedora-template-upgrade-21/

>> The fact that you're now asking whether you should shut down all of your 
>> VMs one by one suggests that you may not have followed the above
>> procedure, since rebooting dom0 entails shutting down all of those VMs
>> (but it's also possible that this is just a miscommunication).
> 
> no, it just means I'm doing this process gradually, leaving space for
> things like, eg, restarting a VM in order to post things on the Internet

Ok, understood.

>> 
>> It's also not clear to me what you mean by "tell them in VM-manager to be
>>  fedora-23 not fedora-21 VMs."
> 
> "upgrade the operating system the VMs are using to version 23 of fedora 
> rather than version 21"
> 

Ok, got it.

>> If you've just performed an in-place upgrade on a template (from Fedora
>> 21 to Fedora 23) with the intention of using it, then it would indeed
>> make sense to base your AppVM on this newly upgraded template (if it
>> wasn't already). Again, as long as the upgrade has been done correctly, 
>> everything should work normally.
> 
> based on that, it doesn't seem to be - I don't think my system is
> currently in the state you describe
> 
> It is possible that the step that went wrong is step one - "Upgrade fedora 
> templates". Would you normally expect that after that first step, the
> default TemplateVM would have upgraded itself to the most recent available
> version of Fedora? Because that didn't happen.
> 

Ah, sorry for the misunderstanding. No, there are additional steps required to
upgrade an existing Fedora 21 template to Fedora 23 that are not listed on
that page. They are instead listed on this page (same as linked above):

https://www.qubes-os.org/doc/fedora-template-upgrade-21/

> 
> Bearing in mind, in all of this my ultimate purpose is "make my Qubes 
> installation indistinguishable from a fresh installation of version 3.1". 
> Which is not yet the case!
> 

If this is your goal, then as noted above, it may be easier and more
preferable to obtain a fresh fedora-23 template from the repo (as you've
already done). Either way works, and which is preferable depends on things
like the modifications (if any) you've made to your template(s) and how
acceptable you find the results of the in-place upgrade procedure for your
individual purposes.

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

iQIcBAEBCgAGBQJXszo7AAoJENtN07w5UDAwvzsP/Ay2mCUF6WdEmAkpESHtJMj7
R+s3tHarYYS1MnEFAt/kTziT1iOi6a6eiO90Xt1Zh9BqGeUvR6y4cYPE8D21fNVY
AEcmd/k2zI3mkQYRQNEK4PxbdCE3nPvWX7RdXNtmb/lloM6ol5oCB+5XTymYUyq+
J8WShC1PF/Kl2GghDeHHgOf4QHEBZZsQKpBTlUjK3pCbFNI6GwWfjh8hFqNlA6Fm
MDKn9x/rrNcGg1zQ96pMjq31Pb9oxB13o09Rjq67VTCnbWoCvxCw/Y2Ayn5QVDuh
6Eb5ydKs2UMT8mwx+Tqsk+Yna77K3SyRaXRYpxklKMFzrw+7P29eaEW4uCpvhxH7
8e/NPnk5YYDkiAbrDDI6ut5mKfT/KWZvWeBHakCiIWhib8RJGBQg1sUDNjvzmRBW
BCa9APvrz3irisUJUckBm2Ru/DYSUkAH05YSvtTjnV0/zTRhUYIKMRMundzOUJ08
DVGlHN85diLgER4bZsFBTJWl/pFs6TxlmFAJZFY1FwOTAJArNBh0u0c6mwW77k7N
TBZqhrbwQib5g8ITTJNaD86yoYvfcrnF7uKy4BWpRoOUIa6fuGR/E+pu0UdqaRBc
VdrC4Ui1Fr2V4ZWjsDrRB2KiJEKubOW0+RJ88g8GIjYVyrlGFgYnZBRuiuq2Yapv
ie3T8oYIrdKOcwiV83He

Re: [qubes-users] metadata between vms

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-16 00:30, Adi Carlisle wrote:
> Ok ithis instance im dding from rufus/windows10 If i wipe metadata before i
> dd to disk will there be any after the write process?
> 

I'm not sure what you mean by "wipe metadata before" I suppose it depends
on what tool you use to do that, as well as what Rufus and Windows 10 do. I
don't think anyone here can answer that question definitively for you. It's
certainly far outside the scope of Qubes OS. You may want to ask the author of
Rufus. Better yet, consider using a privacy-respecting live OS to create the
bootable Qubes medium.

P.S. - Please keep the list CCed, and please don't top-post.

> On 16 Aug 2016 2:16 a.m., "Andrew David Wong"  wrote:
> 
> On 2016-08-15 02:31, adicarli...@gmail.com wrote:
 Writing OS being where i dd from my old, potentially at risk OS
 
> 
> I think that depends entirely on the OS and tools you used to create the 
> bootable USB drive. In principle, the Qubes ISO should be the same as any 
> ISO in that respect. In other words: Whether your OS or tools keep
> metadata about ISOs after you dd them somewhere is beyond the control of
> the ISO being copied. The ISO is just a file, a blob of data. It can't
> control whether the OS or tools manipulating it leave traces of it behind.
> 

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

iQIcBAEBCgAGBQJXszUuAAoJENtN07w5UDAwePwP/1wekXS+fWAN0dy7UgYFfsQg
vdfPn6mWb7DuFL0GIL8L97AD69JO2HxpjY9U8EJBe8SX0P6k43/DwO9cDPtMISaE
BujUOO5x6lJTR+r9Qpx1rnpw3Rifddm926YV6wlAbaQTOdYNt85vXs9R8aMTD+WG
U4V/vyzyIsbh8aNZF4ipXpjef1P9yRJX/wq414oV+HtzGsIlTvB9LqKI9dc/xegq
mUAwm8/RTj3eo9KfjdPXiXSbVE1/S2xfchxg28rlvrAfEEEoDhqqRaUd2kVg6fkO
Bp8NpaA+67/dSbhuCEdPXYN283+76dtN2pDoNhcAe9cSaeOfXnNvu5GrHGkmZq2D
JKahoJjj5L5YP9whxi762nE9Kapnmc62jLRhcJSdf5QO8k1LP665HIkx3Y307cr0
NVxGkOpDNw1vrZ03QI4jgJPVbs9fE6xEfn3Vdx2MBBFqzRJcp9Ol7bsroqwmhSyk
1/wQN7PY3/39R7VRDMbtuYXcaTX20U0pBAu7ZJDs1sNPfrS1iY2pM2+CKe85hTpz
+Duf7UDZWObiJYazq0JOqCU3Yik4lj/JbvtcLq300WViNfj28aK+zr8TSyTd/L69
ZK2g8e8JLl6RenbMrm8qd2MlfZiOIbI+jVoX3qfewWdq6ClcD+H7o8hSvxbkM6Rd
ng6Fkv9Iai2r2UbLbRdB
=R4Zg
-END PGP SIGNATURE-

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

[qubes-users] Service VM Size, Memory, Security

[johnyjukya]

One of the banes of a Qubes addict's existence is memory.

Too many times I see that red stop sign and breathe a sigh of frustration,
that I need to shut down or mem-set other VM's to start up another AppVM. 
I like my VM separation, dammit, which means lots of VMs.

In a perfect world, I'd have a kick-ass server with 64G.  In the real
world, I have to make do with 4G.

And in the domain of laptops (which I personally just can't trust any
more, lol), memory constraints of 4G-8G are going to be present for
awhile.

A few questions and observations:

- Have the Qubes devs ever had any thoughts of making the service VM's of
sys-net and sys-firewall "headless," or generally more minimalistic?

For a netcard-hosting packet slinger and a packet filter firewall VM to
both have most of their memory used up by 30M X servers, pulseaudio, and
so on, is a bit ironic.  And exposes a lot more attack surface, yadda,
yadda.

(More templates is a pain, for sure, just as Whonix-Cubes uses two more
templates of its own.  But in the case of these important service VM's, I
think the benefits of memory saving and reduced attack surface would be
worth it.)

Those 300M VM's add up pretty quickly on a 4G system.  I think the
evolution of Qubes is probably going towards having *more* service (and
user) VM's; e.g. a actual storage domain, a default USB domain, maybe even
a sound/keyboard/mouse domain, maybe bluetooth isolation, or whatever.

(The concept of Qubes is awesome vs. a traditional metal kernel and
multiple Qemu's on top, for example.  But dom0 has so much in it right
now, that benefit is partly theoretical at the current time, IMHO.)

The more separation, and the more stuff moved out of dom0 the better,
which is going to mean more VM's.  If these were headless 80M (or
whatever) VM's instead of honkin' 300M VM's, it becomes a *lot* more
practical for those without super-machines.

You'd need some way to access the VM, but the aforementioned X clients
talking X protocol to an outside X server, or, even leaner, sshd would
meet those needs.

Any need for an xterm or X apps from these headless VM's could easily be
done by the X clients connecting to another VM's (or dom0's) X server
directly, without needing their own.  Just a bit of iptables and X
config'ing.

You'd be putting more trust in ssh, but doing certificate based auth
between VM's, could reduce the pain, and the ssh attack surface is
probably a lot smaller than a having whole damn X server in your packet
slinger/filter.

I started work last night on making a headless sys-net accessible via
ssh/X protocol, but got a big bogged down in iptables.  I'm a bit rusty,
and I need to do a good re-education of myself on iptables and hit it
again (and not at 3am :P).

Also, I spun my wheels for a bit because I didn't realize at first that
everybody on 10.137.2.* isn't really on the same subnet in the traditional
sense, but has to send everything through 10.137.2.1 sys-firewall,
correct?  Seems a bit odd, but I can understand the restriction from a
security standpoint, and with ipt forwarding, the desired effect can be
achieved--with some concentration, which I didn't have last night, lol.

Actually, part of me wonders if being forced to send everything through
sys-firewall for 10.137.2.*'s to talk to each other is *more* of a
security risk.  (If sys-firewall is compromised, it gets to see all the
VM's talking to each other, which wouldn't be the case of 10.137.2.*/24
acted like a normal LAN.  Plus, it'd probably be more efficient without
the additional iptables relaying.  But that's a secondary concern.)

(- A bit of an oblique thought, might be the sharing of memory between the
common pages of X server (and other app) instances in different VM's.  But
that strikes me as having a whole nightmare of complications to implement,
along with a host of security issues.  Just trimming unnecessary stuff out
of the VM's seems a lot more straight-forward.)

- It might make sense to have the sys-net and sys-firewall service VM's
based upon a different, more minimal template than the
user-app-vm-intended fedora-23.

Having pulseaudio, alsa, modemmanager (what even is that??) and a bunch of
other stuff running in a VM that is dedicated to just slinging packets or
providing an iptables firewall seems terribly wasteful.  (And I'm talking
using up real resident RSS memory, not just Virtual space.)

It's definitely a side-project of mine to take sys-net and sys-firewall
down to the most minimal state/size possible.  Saves memory, and reduces
attack surface, allows for more work VM's.

Plus, for the truly paranoid (me, in case you haven't picked up on that
yet; although I prefer the term "cautious"), there has been talk about
sound cards being as covert channels (potentially between VMs in this
case).  So it seems like an unnecessary security risk.

Yes, in order for sys-net or sys-firewall to talk to other VM's via the
sound card, you need both ends to be compromised, in which case you're

Re: [qubes-users] Screen corruption on nvidia

[johnyjukya]

>> However, under Qubes, I experience random screen corruption.
>>
>> See: https://i.imgur.com/ovEFgYO.png

> Looks like it could be this issue:
>
> https://github.com/QubesOS/qubes-issues/issues/1028
>
> As you can see from the qubes-builder-github comments, some patches for
> this
> are already in the testing repos. You may want to give those a try.

Awesome!  Will give that a shot.  Thanks for the reply!  :)

-- 
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/2380dfd0340bdf4025341dff82056852.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 3.2-rc2 very high hard disk activity

[donoban]

I also have experienced a lot of process killed because I run out of
memory. This never happened with 3.1.

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

Re: [qubes-users] No DNS with ProxyVM + OpenVPN

[kototamo]

> To test this theory, you could put a 7sec delay in qubes-vpn-handler.sh 
> right before the line 'iptables -t nat -F PR-QBS'. Then the right IPs 
> should appear in PR-QBS.

It did work. Thank you again!

I wonder what is changing the NAT rules. I only see one 'up' directive in the 
openvpn configuration, the one calling the qubes script. Maybe something from 
Qubes itself? It's correct that the ProxyVM should be connected to sys-firewall 
right?

-- 
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/0b146266-ed8f-43fc-a0d3-f933d3c49f6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 3.2-rc2 very high hard disk activity

[donoban]

Hi

The computer which I upgraded from 3.1 to 3.2 is having some
performance problems when I have a few VMs running. It has a non-SSD
hard disk so I know it's going to do a bottleneck and I don't expect a
fast perform, but I'm sure that it's running very worse than it did
with 3.1.


Using iotop on dom0 I examined the process which use the hard disk when
it goes totally lagged. I see:

- Some [loopX] processess... are them loops for the VMs? I suppose it's
  normal to have a pretty high I/O work from this processes.

- systemd-journald is pretty common when the lag starts, in
  fact I have 873Mb's on /var/log/journal , is this standard?

- I also see some rsyslogd process and qvm-sync-clock 


I have to say that this never happened with Qubes 3.1, I just couldn't
open more than 4/5 AppVM's, but it always worked pretty fine.

Any idea?

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

Re: [qubes-users] 3.2rcX Default Display (Login) Manager

[donoban]

On Mon, 15 Aug 2016 12:06:36 -0700 (PDT)
3n7r0...@gmail.com wrote:

> I haven't had a chance to try out 3.2rc yet. Can someone please tell
> me what the default DM is to launch XFCE4? Thanks!
> 


It is the same of Qubes 3.1, lightdm if I'm not 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/20160816115441.2bf1b38f%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes VM Manager: Organize?

[Drew White]

On Sunday, 14 August 2016 13:28:10 UTC+10, el...@tutanota.com  wrote:
> > don't
> > yet know what the new system will look like, so I can't say whether a
> > folder-based system (like the app menu) will make sense, but something like
> > that could be a good idea. I've added this suggestion as a comment with a 
> > link
> > back to this thread.
> 
> Thanks.  
> 
> If you do make it, please try to remember to try to be intuitive... Copy shit 
> that everyone knows..  (Click on triangle to reveal subdirectory or something 
> that runs through most OS guis).  Not trying to be rude or imply that qubes 
> is overly complicated.. It just is by its very nature.  
> 
> I am not sure about other people, but I connect to different AppVM's via 
> different VPN locales (of the same VPN provider).  Perfect?  No, but it saves 
> money, and I bet a bunch of users do something like this.  Most VPN's give 
> you 20+ different locales to connect to (London, Paris, Sydney, etc..)  It is 
> desirable (when not using tor at least) to set up different ProxyVm's for 
> each AppVM that you use, even if you are using the same vpn company.  
> If I am not the only one out there doing that, it would be really helpful to 
> be able to visualize which appvm connects to which proxyvm (maybe by shading 
> background colour or a dotted line denoting parents/children/siblings when 
> you scroll over the app/proxy to indicate relationships?).  
> 
> And I probably just came up with an unintuitive idea.  But if it's intuitive 
> to you too, maybe it would be for more people.  Maybe a mouse-hover would 
> bring up a small explanation of 'taint/relationships with other appvm's that 
> are using the same ip?  
> 
> My couple nunsense.

You are right, they should add in that into the Qubes Manager for the 
networking visibility. These are things that I've got in my system and I find 
very useful.

AppVMs should never have use of the same IP, unless you have over 254 VMs on 
the PC (including templates) under the same networking partition.

I do not VPN often, but I have everything set out, and I can look at my manager 
and see what VPN I'm connected to because different Proxys have different VPNs, 
and thus a different name for their NetVM.

I know I'm speaking as a PRACTICAL person, not a "wanky GUI" lover type person, 
but I do agree with subdirectory style, but there has to be many methods of 
sorting and categorising.

For example, I might click on a button to categorise by NetVM, so it has the 
NetVM, then the Proxy VM under it, then the AppVMs under it.

If the ProxyVM has 3 NetVMs assigned to it, then it should be under all three 
NetVMs.
If an AppVM has 4 ProxyVMs attached to it, then it should also be under each of 
those ProxyVMs.

But then again I might want to sort on CPU cores. So I want to see what ones 
have use of Thread 
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24 .. etc..

So I click on 1, and it showes me which are able to use thread 1.
If I click on 1+2 it showes me all that can use 1 OR 2, or I click the AND 
button to show only the VMs that are allowed to use core 1 AND 2.


But then I may want to see template based sorting. So parent to child there too.

Then there is the custom sorting.
I may want to make my own methodolgy, but also switch between them all.


It's not really asking much at all.
It's a simple task, and easy enough to perform. (Depending on what you are 
programming in)

They are just some thoughts that I used to develop my manager.







-- 
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/d5503439-2fdd-4a66-a39b-09add88b6481%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Windows7 issue with Dom0 GUI Daemon

[Drew White]

On Tuesday, 16 August 2016 11:33:18 UTC+10, Andrew David Wong  wrote:
> The issue for this was recently closed:
> 
> https://github.com/QubesOS/qubes-issues/issues/1704
> 
> Rafał, is the fix for this available in a testing repo (or already live)?
> 


How does a person re-open the 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/cfb4b87f-51e7-4feb-b189-a0a63d16b3ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Current Windows instructions?

[Drew White]

On Tuesday, 16 August 2016 11:40:44 UTC+10, Andrew David Wong  wrote:
> Here it is:
> 
> https://www.qubes-os.org/doc/windows-appvms/
> 
> I'll update that other page. Thanks!
> 

I see the instructions, but has the seamless issues been resolved yet?
Or do they still remain?

Will the tools be working any time soon?

-- 
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/e9cb390f-de92-4017-a587-719065498f14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.