Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

[Franz]

On Wed, Aug 2, 2017 at 9:47 PM, Eva Star  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 08/02/2017 03:04 AM, cooloutac wrote:
>
> > oh ok I see,  so a taskbar widget or something to replace the
> > manager.  I thought they lost their minds for a second. My
> > immediate thought was what about attaching drives, and seeing if
> > updates available?  Joanna addressed all my concerns but I'm gonna
> > have to wait and see what happens with this.   Hopefully it doesn't
> > turn out to be more confusing then the manager.
>
> It is a miscalculation. How about the words "we must make Qubes user
> friendly for all users non IT advanced" and release Qubes without
> manager? :(
>
> Maybe, widgets is not a good idea, but Qubes Manager is one of the
> important part that make Qubes useful to manage all vms with mouse.
> Some UX to old one QM + start menu links to right mouse action and it
> will be amazing.
>
>
Well, I never use the start menu on the left lower side of the screen
because it is too complicated, too many items and needs customization that
I am too lazy to do or have better things to do. I do everything with the
Qubes Manager that is so well organized and compact. I am afraid that the
new arrangement may make things more difficult to find for a new user since
items are spread over different buttons/places.

I would suggest to mitigate this risk putting links to the other places on
the widget/window that opens when you click on one of them. You can
separate things, but better put links to find them again.

Also I imagine that somewhere I'll find the list of VMs. There please
1. keep the "run command in VM" choice and
2. add something new: the chance to show only preferred VM

The first is very important to avoid using the start button.
The second is important to simplify the view and speed up the most common
routines

Cooloutac made me smile telling of his mother and family using Qubes.  I
had my wife using Qubes for some years, but recently she rised up against
Qubes telling that it is too complicated for her to be able to master it
without help. She wanted a Mac.  Really it is impossible to maintain Qubes
without the CLI and this makes it beyond limits for most people.  But
perhaps if we are able to find a stable architecture and then Qubes matures
enough, this may change. But we are not there yet.
Best
Fran

>
>
> - --
> Regards
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJZgnLPAAoJEGSin3PC/C0AyIUP/AuxhZfxWdFGYzLzUQX2fzn/
> 5ajxXWVNtTXWgpmUqzu1Ov/HMp9W7hFerw4GXwMotXDDXrIbf+8WEayS+q+SdXBn
> qanSZ0EmBkwoFVptP+1TNQqQIcRLEF3gN3o3vq8tGaq2dUZ4HW9hSXBUZ71WcjXR
> g95QUBBpl05/l//Vozu0GEUxpLBrzAhji95awd39vn/2BRKr6q4pGlNsi6BdqgCJ
> WzmeaSTrYjNkBHypYjgpCXT6MQLRXEmlqX8OVxI5jopP7tYNZh5+bKp+1/U9vccJ
> q4ddOTDlaCwY5bmQgWl05MNI4+OWr8xBlrfVCMmfxVO5dOBvoCjCrMTEySh3sPL7
> gGMcT1349yiIllPPP0vhdm+0d0n0hWLR160WExQoF+oUgCbXFnf5sBT1bjWxXBOl
> EEwg6IMElKgjI0jG0izCX7M3rn5m1H95KOGR2nn+IyJIzgJwk4+4YTWgFFfnwQyX
> k9EcN8vffpokLz9I3u2qZSdDDYz71KVRAHMxL3h2WxEro7RVRtOcbpXO3ctcsdV0
> QZfEwW2SAeZz798InY/Qb+7NmtpSsZUl3rCYUY7i5mubkGgnbtklCSUEzxZZ+4hx
> SD6nV8tTjrNMxSNEytvIYd6wJZYrHkvA7Kf7KtNtxa7+mMr89LzL5qLHk/W15R14
> iXk4BnVvkdfLntZ+Pa84
> =ILr0
> -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/7a4c1304-cbcb-e447-97dc-9db848eae1fd%40openmailbox.org.
> For more options, visit https://groups.google.com/d/optout.
>

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

[qubes-users] Qubes 4.0 qubes-templates-community

[Richard Brown]

Hello Qubes community.

I have just installed Qubes 4.0-rc1 on my laptop.

Im trying to install whonix.

But when trying to enable the repo is get this error;

Failed to synchronize cache for repo 'qubes-templates-community', disabling
Last metadata expiration check: 0:17:28 ago on Thu Aug 3 00:48:06 2017.


What am I doing 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/70bf467f-6fd6-423d-97f7-84929046555a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

[Eva Star]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/02/2017 03:04 AM, cooloutac wrote:

> oh ok I see,  so a taskbar widget or something to replace the
> manager.  I thought they lost their minds for a second. My
> immediate thought was what about attaching drives, and seeing if
> updates available?  Joanna addressed all my concerns but I'm gonna
> have to wait and see what happens with this.   Hopefully it doesn't
> turn out to be more confusing then the manager.

It is a miscalculation. How about the words "we must make Qubes user
friendly for all users non IT advanced" and release Qubes without
manager? :(

Maybe, widgets is not a good idea, but Qubes Manager is one of the
important part that make Qubes useful to manage all vms with mouse.
Some UX to old one QM + start menu links to right mouse action and it
will be amazing.



- -- 
Regards
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZgnLPAAoJEGSin3PC/C0AyIUP/AuxhZfxWdFGYzLzUQX2fzn/
5ajxXWVNtTXWgpmUqzu1Ov/HMp9W7hFerw4GXwMotXDDXrIbf+8WEayS+q+SdXBn
qanSZ0EmBkwoFVptP+1TNQqQIcRLEF3gN3o3vq8tGaq2dUZ4HW9hSXBUZ71WcjXR
g95QUBBpl05/l//Vozu0GEUxpLBrzAhji95awd39vn/2BRKr6q4pGlNsi6BdqgCJ
WzmeaSTrYjNkBHypYjgpCXT6MQLRXEmlqX8OVxI5jopP7tYNZh5+bKp+1/U9vccJ
q4ddOTDlaCwY5bmQgWl05MNI4+OWr8xBlrfVCMmfxVO5dOBvoCjCrMTEySh3sPL7
gGMcT1349yiIllPPP0vhdm+0d0n0hWLR160WExQoF+oUgCbXFnf5sBT1bjWxXBOl
EEwg6IMElKgjI0jG0izCX7M3rn5m1H95KOGR2nn+IyJIzgJwk4+4YTWgFFfnwQyX
k9EcN8vffpokLz9I3u2qZSdDDYz71KVRAHMxL3h2WxEro7RVRtOcbpXO3ctcsdV0
QZfEwW2SAeZz798InY/Qb+7NmtpSsZUl3rCYUY7i5mubkGgnbtklCSUEzxZZ+4hx
SD6nV8tTjrNMxSNEytvIYd6wJZYrHkvA7Kf7KtNtxa7+mMr89LzL5qLHk/W15R14
iXk4BnVvkdfLntZ+Pa84
=ILr0
-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/7a4c1304-cbcb-e447-97dc-9db848eae1fd%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Announcement: Recommended Fedora 25 TemplateVM Upgrade for Qubes 3.2

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-07-31 23:35, qubester wrote:
> So, I went through  the docs, and successfully  have F25  working. 
> So.why would I want to run the command below?
> 
> and/or  should I be doing that at this stage?
> 
> -
> 
> We also provide fresh Fedora 25 TemplateVM packages through the
> official Qubes repositories, which you can get with the following
> commands (in dom0).
> 
> Standard Fedora 25 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-25
> 

It's just an optional, alternative way to get an F25 template. If
you've already upgraded yours in-place, you're fine.

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

iQIcBAEBCgAGBQJZgm53AAoJENtN07w5UDAwKlQP/0inIpj5uzMaZv1pcSeS94FT
d+IhHmhi1ihpOj/LCHQJPTuXblY6nxxHw/jzwvjV5+dFfOZ4NpDADD2Iun6o/isC
NsC5kZXWapporSQUjq+ZT11jQD5eZ+wsEsulmYNm9ObNm61KU6cBV24+ogFD9/oI
Ek4DALWFjOL4GkUkgocIcvWKonTiNt/YTVfCshZmMi1uy1wSspZTKpnpGMC8lQod
5wwcfdS+loqXzIqQioea/yva8wz/jqsLUksMZgfKBpWWjBmCo3oezvl72fpU4VwR
FhinpajH6zaeXCe7ntKlA0bXT7RvXWTp0anbCrY6vbVs81nSc+Izp4EojMSo9emY
nAXg3b30JfyBMH2FYST+nHP8S2PGqEEOiNTkWvac0XOwb1iEOIYhe1O9v/OcgneG
+0pJbOSENPF5zAVplKNUKLhHHeGmd8qllRskGLz8jil6FiiSl2fNOcIzmhtPtSQO
lb+2fgbZNb1phJe/apfkKQRwj+YM8Sol25A0hBK2GJa8ld0AvIiSW7hDOm8TCN4f
VHHhoPduyS6fSb6t/k5uUqg9tbmQ6CLIFDjBgCrj9NBxQV44qi41FfTrkWyj1ND0
JTZQkVLOqY85ZFP5RxGMxRlIKLDOX94dkIAw0utslA0+mhntUi9v7nH25gbDtSJ+
O5c/MVbTGymOwwf/1ItU
=0zVr
-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/37e20670-35c1-873a-fc7d-9fd9f10a96cf%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't access /opt/newDirectory

[Unman]

On Wed, Aug 02, 2017 at 03:44:20PM -0700, Patrick Bouldin wrote:
> On Wednesday, August 2, 2017 at 6:33:44 PM UTC-4, Patrick Bouldin wrote:
> > Related to earlier email:
> > 
> > I installed an app called splunk, and it seems to always install here:
> > 
> > /opt/splunk/  (off the root)
> > 
> > However, even with sudo I can't event change into the directory. Why is 
> > that? Can the app itself restrict access to that directory as part of set 
> > up? I'm doing all this within a fedora-24 template.
> > 
> > Here's the line by line showing this:
> > [user@fedora-24-work-splunk opt]$ pwd
> > /opt
> > [user@fedora-24-work-splunk opt]$ ls
> > google  splunk
> > [user@fedora-24-work-splunk opt]$ cd splunk
> > bash: cd: splunk: Permission denied
> > [user@fedora-24-work-splunk opt]$ sudo cd splunk
> > [user@fedora-24-work-splunk opt]$ pwd
> > /opt
> > 
> > 
> > Thanks,
> > Patrick
> 
> Ok disregard, I just enabled su and was able to do that. Curious why 
> prefixing with sudo didn't help. Thanks.
> 

Two reasons for this: first, cd isn't an application, it's a shell
builtin( try 'type cd' )
Second, cd spawns a new process which exits when the command completes.
So even if the 'cd' were to succeed, when the process exits, the
original process is still where it started.

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

[qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

[tmc]

On Wednesday, August 2, 2017 at 2:45:30 PM UTC-7, tmc wrote:
> > We have just released Qubes 4.0-rc1:
> > 
> > https://www.qubes-os.org/news/2017/07/31/qubes-40-rc1/
> 
> On a thinkpad x1, after removing  iommu=no-igfx I got to 
> initial-setup-graphical but that is failing on "qubes-prefs default-template 
> fedora-25" with qubesadmin.exc.QubesVMNotFoundError: "No such domain: 
> "fedora-25"'.
> 
> I see a qubesd warning a little before:
> 
> WARNING: Sum of all thin volume sizes (226.01 Gib) exceeds the size of thin 
> pool qubes_dom0/pool00 and the size of the whole volume group (222.57 GiB)!
> 
> perhaps related.

FWIW: setup completed successfully after a re-install.

-- 
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/74ca9456-0a8c-4d56-8c6f-1361b19698b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Can't access /opt/newDirectory

[Patrick Bouldin]

On Wednesday, August 2, 2017 at 6:33:44 PM UTC-4, Patrick Bouldin wrote:
> Related to earlier email:
> 
> I installed an app called splunk, and it seems to always install here:
> 
> /opt/splunk/  (off the root)
> 
> However, even with sudo I can't event change into the directory. Why is that? 
> Can the app itself restrict access to that directory as part of set up? I'm 
> doing all this within a fedora-24 template.
> 
> Here's the line by line showing this:
> [user@fedora-24-work-splunk opt]$ pwd
> /opt
> [user@fedora-24-work-splunk opt]$ ls
> google  splunk
> [user@fedora-24-work-splunk opt]$ cd splunk
> bash: cd: splunk: Permission denied
> [user@fedora-24-work-splunk opt]$ sudo cd splunk
> [user@fedora-24-work-splunk opt]$ pwd
> /opt
> 
> 
> Thanks,
> Patrick

Ok disregard, I just enabled su and was able to do that. Curious why prefixing 
with sudo didn't help. Thanks.

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

[qubes-users] Can't access /opt/newDirectory

[Patrick Bouldin]

Related to earlier email:

I installed an app called splunk, and it seems to always install here:

/opt/splunk/  (off the root)

However, even with sudo I can't event change into the directory. Why is that? 
Can the app itself restrict access to that directory as part of set up? I'm 
doing all this within a fedora-24 template.

Here's the line by line showing this:
[user@fedora-24-work-splunk opt]$ pwd
/opt
[user@fedora-24-work-splunk opt]$ ls
google  splunk
[user@fedora-24-work-splunk opt]$ cd splunk
bash: cd: splunk: Permission denied
[user@fedora-24-work-splunk opt]$ sudo cd splunk
[user@fedora-24-work-splunk opt]$ pwd
/opt


Thanks,
Patrick

-- 
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/777bc932-2531-46bc-8035-02b99bb479c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: dvm removal ?

[qubester]

what I Do  see  with qvm-ls  is this:

whonix-ws-dvm  halted  whonix-ws template


though, as I said I did change it to fedora 25   few days ago.

so, will the DVMs  just keep counting up indefinitely into the 100s ?

--
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/57fc4513-96b1-3679-354b-7b4df14211bf%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

[tmc]

> We have just released Qubes 4.0-rc1:
> 
> https://www.qubes-os.org/news/2017/07/31/qubes-40-rc1/

On a thinkpad x1, after removing  iommu=no-igfx I got to 
initial-setup-graphical but that is failing on "qubes-prefs default-template 
fedora-25" with qubesadmin.exc.QubesVMNotFoundError: "No such domain: 
"fedora-25"'.

I see a qubesd warning a little before:

WARNING: Sum of all thin volume sizes (226.01 Gib) exceeds the size of thin 
pool qubes_dom0/pool00 and the size of the whole volume group (222.57 GiB)!

perhaps related.

-- 
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/43993c28-125f-466a-adff-ef9a9a985e8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] webdev wondering how to ssh to my local webserver on the lan

[Unman]

On Wed, Aug 02, 2017 at 01:59:00PM -0700, random815...@gmail.com wrote:
> hi friends. 
> 
> im new to qubes and ive looked all all the documentation and videos, however 
> i still can't figure out how to connect to my local ubuntu webserver from my 
> work qube to do some web development. i know, i know, its probably really 
> easy, but ive spent a couple of hours trying various things that haven't 
> worked, so could you help?
> 
> my lan ip is 192.168.2.0/24
> my webserver is 192.168.2.10
> my qubes appvm's are all running on 10.137.2.0/24 (so obviosuly the qubes 
> can't talk to the lan because theyre on different subnets)
> but my qubes network connection is on 192.168.2.0/24
> 
> ive tried a bunch of stuff to try to get a 192.168.2.0/24 address on my work 
> qube, but im out of ideas. please help me make my venture into qubes less 
> stressful and more productive for myself and possibly any other web 
> developers who are confused by this. 
> 
> thanks,
> -r815
> 

If you have default setup then you will have 
work -- sys-firewall -- sys-net

The default setup uses MASQUERADE, so traffic from the work qube will
appear to come from the external IP of sys-net.
So you Dona need to get an 192 address on the work qube.

You don't say what you tried - if you tried to ssh direct, or if you
started to reconfigure before trying that.
Go back to the initial setup.
Try to ssh from work qube.
Use iptables -L -nv to watch the traffic on sys-firewall and sys-net,
and you should see outgoing SSH traffic on FORWARD chain, and return
traffic.

Most of the time you can debug the problem without using a sniffer, but
if needed you could run tcpdump on sys-net, to get a handle on what is
happening.

unman

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

Re: [qubes-users] Verifying does not work with gpg

[Unman]

On Wed, Aug 02, 2017 at 01:40:23PM -0700, frkla1...@gmail.com wrote:
> Hey guys I installed the Qubes-Os and I`m very happy with it :-) The best OS 
> in my opinion- everything it`s working fine on my computer. Thanks for the 
> project!!
> 
> But I installed without verifying anything. So since two weeks I try to check 
> the .iso file because I wanna reinstall Qubes-OS with the verified .iso. 
> 
> Sorry for my English- it`s not the best and I`m also a noob with informatic 
> things. So please write simple.
> 
> 1. I downloaded the  Qubes Master Signing Key with:
> 
> $ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
> 
> 2. I checked the fingerprint with:
> 
> gpg --fingerprint
> 
> 3. I decided to trust the qubes-master-signing-key
> 
> 3.1 $ gpg --edit-key 36879494 (at the qubes-os site it`s written 0x36879494 - 
> i don`t understand why to put "0x" in front of the qubes-master-signing-key. 
> So i let it away- it worked)
> 
> i made all the steps and it worked- i had the same terminal output as in the 
> description (https://www.qubes-os.org/security/verifying-signatures/)
> 
> 4. After that I downloaded the "qubes-release-3-signing-key.asc" because I 
> would like to install Qubes-R3.2-x86_64.iso.
> 
> - I tried a lot of things.
> 1) Download it from the download page with right click and than "Save File"
> 2) Download with gpg --recv-keys 0xCB11CA1D03FA5082 (number on the 
> qubes-os.org page)
> ...
> 
> PROBLEM I can't verify the iso image.
> 
> 1) I tried with gpg -v --verify Qubes-R3.2-x86_64.iso.asc 
> Qubes-R3.2-x86_64.iso
> Answer from the terminal:
> 
> gpg: can't open 'Qubes-R3.2-x86_64.iso.asc'
> gpg: verify signatures failed: file open error
> 
> 2) Than I decided to put the files inside with drag
> Answer from the terminal:
> gpg: armor header: Version: GnuPG v1
> gpg: verify signatures failed: unexpected data
> 
> SO I DECIDED to check the DIGESTS but it does not work:
> 
> I put into the terminal: $ md5sum -c 
> '/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
> Answer from terminal: no properly formatted MD5 checksum lines found
> 
> I tried also $ md5sum -c '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DIGESTS'
> Answer from terminal: no such file or directory
> 
> I renamed than the .iso in iso.DIGESTS
> Answer from the terminal: no properly formatted MD5 checksum lines found
> 
> I renamed than the .iso.DIGESTS again in .iso and I wrote into the terminal:
> md5sum -t '/home/user/Downloads/Qubes/-R3.2-x86_64.iso' 
> 
> After writing the 't' instead of 'c' I received following answer:
> 3c951138b8b9867d8657f173c1b58b82 /home/user/Downloads/Qubes/-R3.2-x86_64.iso
> 
> I did this for all types (md5sum sha1sum sha256sum sha512sum)
> 
> After that I compared with the openssl dgst types and it worked perfect.
> 
> But in the file on the website from qubes os is written: 
> 
> `However, it is possible that an attacker replaced Qubes-R3.2-x86_64.iso with 
> a malicious ISO, computed the hash values for that ISO, and replaced the 
> values in Qubes-R3.2-x86_64.iso.DIGESTS with his own set of values. 
> Therefore, ideally, we should also verify the authenticity of the listed hash 
> values. Since Qubes-R3.2-x86_64.iso.DIGESTS is a clearsigned PGP file, we can 
> use gpg to verify it from the command line:`
> 
> I decided to check now the last step:
> 
> $ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
> Answer from the terminal: 
> gpg: no valid OpenPGP data found.
> gpg: the signature could not be verified
> Please remember that the signature file (sig. or asc.) 
> should be the first file given on the command line.
> 
> I tried the same step with the renamed the file .iso.DIGESTS
> 
> $ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DISGESTS'
> 
> The answer was the same: 
> gpg: no valid OpenPGP data found.
> gpg: the signature could not be verified
> Please remember that the signature file (sig. or asc.) 
> should be the first file given on the command line.
> 
> The terminal suggest to compare the files like I described above:
> 
> But that command does not work in my terminal:
> 
> gpg -v --verify Qubes-R3.2-x86_64.iso.asc Qubes-R3.2-x86_64.iso
> Answer: 
> 
> gpg: armor header: Version: GnuPG v1
> gpg: verify signatures failed: unexpected data
> 
> I tried now all the options and I have no Idea what I should try to solve the 
> verification problem. That's why I need help.
> 
> I checked the ~/.gnupg (Maybe it's helpful for you)
> Supported algorithms:
> Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
> Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA 
> 128, CAMELLIA192, CAMELLIA256
> Hash: MD5, SHA1, RIPMED160, SHA256, SHA384, SHA512, SHA224
> Compression: Uncompressed, ZIP, ZLIB, BZIP2
> 
> Syntax: gpg [options] [files]
> Sign, check, encrypt or decrypt
> Default operation depends on the input data
> 
> I WOULD BE VERY HAPPY IF SOMEONE HAS A SOLUTION!
> 
> Thanks!
> 

I think you should take it slowly.

First, 

[qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

[travis]

> Hello,
> 
> We have just released Qubes 4.0-rc1:

On a thinkpad x1 I proceeded past the iommu=no-igfx issue but then the 
initial-setup-graphical helper fails on execing "qubes-prefs default-template 
fedora-25" with qubesadmin.exc.QubesVMNotFoundError: 'No such domain: 
"fedora-25"'

Subsequent retires also fail, (example: "Configuring TemplateVM 
tmp-tmp-tmp-fedora-25").

I continued by opted out of initial setup but I figured I'd report. Happy to 
share any relevant logs.

-- 
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/4c413643-50f9-498e-b4e3-a80f68ac145c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] webdev wondering how to ssh to my local webserver on the lan

[random815815]

hi friends. 

im new to qubes and ive looked all all the documentation and videos, however i 
still can't figure out how to connect to my local ubuntu webserver from my work 
qube to do some web development. i know, i know, its probably really easy, but 
ive spent a couple of hours trying various things that haven't worked, so could 
you help?

my lan ip is 192.168.2.0/24
my webserver is 192.168.2.10
my qubes appvm's are all running on 10.137.2.0/24 (so obviosuly the qubes can't 
talk to the lan because theyre on different subnets)
but my qubes network connection is on 192.168.2.0/24

ive tried a bunch of stuff to try to get a 192.168.2.0/24 address on my work 
qube, but im out of ideas. please help me make my venture into qubes less 
stressful and more productive for myself and possibly any other web developers 
who are confused by this. 

thanks,
-r815

-- 
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/e53c37ea-c245-4aa3-ba55-d18bee0ad8a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 3.2 Network failure after update template to fedora-25

[jpb]

I ran a test after cloning and transforming a debian-8 template to a debian-9 
template.  The sys-net vm exhibited the same trouble with getting an IP 
assignment using the debian-9 template as the fedora-24 and 25 templates.  So, 
it looks like I have something fundamentally misconfigured in dom0 (and I try 
not to touch it) in my installation where it can only use the original 
templates for sys-net and sys-firewall.  I'm able to use the newer templates 
for all the other qubes.

I tested sys-net and sys-firewall incrementally with different underlying 
templates and the only ones that would work were fedora-23 or debian-8.  I've 
switched to debian-8 for sys-net and sys-firewall since it works.  I'll then 
start with a fresh install with Qubes 4.0 and migrate my user qubes.

When I have time I'll look into the IP assignment process and the firewall to 
see what's going on.



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

[qubes-users] Verifying does not work with gpg

[frkla1234]

Hey guys I installed the Qubes-Os and I`m very happy with it :-) The best OS in 
my opinion- everything it`s working fine on my computer. Thanks for the 
project!!

But I installed without verifying anything. So since two weeks I try to check 
the .iso file because I wanna reinstall Qubes-OS with the verified .iso. 

Sorry for my English- it`s not the best and I`m also a noob with informatic 
things. So please write simple.

1. I downloaded the  Qubes Master Signing Key with:

$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc

2. I checked the fingerprint with:

gpg --fingerprint

3. I decided to trust the qubes-master-signing-key

3.1 $ gpg --edit-key 36879494 (at the qubes-os site it`s written 0x36879494 - i 
don`t understand why to put "0x" in front of the qubes-master-signing-key. So i 
let it away- it worked)

i made all the steps and it worked- i had the same terminal output as in the 
description (https://www.qubes-os.org/security/verifying-signatures/)

4. After that I downloaded the "qubes-release-3-signing-key.asc" because I 
would like to install Qubes-R3.2-x86_64.iso.

- I tried a lot of things.
1) Download it from the download page with right click and than "Save File"
2) Download with gpg --recv-keys 0xCB11CA1D03FA5082 (number on the qubes-os.org 
page)
...

PROBLEM I can't verify the iso image.

1) I tried with gpg -v --verify Qubes-R3.2-x86_64.iso.asc Qubes-R3.2-x86_64.iso
Answer from the terminal:

gpg: can't open 'Qubes-R3.2-x86_64.iso.asc'
gpg: verify signatures failed: file open error

2) Than I decided to put the files inside with drag
Answer from the terminal:
gpg: armor header: Version: GnuPG v1
gpg: verify signatures failed: unexpected data

SO I DECIDED to check the DIGESTS but it does not work:

I put into the terminal: $ md5sum -c 
'/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
Answer from terminal: no properly formatted MD5 checksum lines found

I tried also $ md5sum -c '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DIGESTS'
Answer from terminal: no such file or directory

I renamed than the .iso in iso.DIGESTS
Answer from the terminal: no properly formatted MD5 checksum lines found

I renamed than the .iso.DIGESTS again in .iso and I wrote into the terminal:
md5sum -t '/home/user/Downloads/Qubes/-R3.2-x86_64.iso' 

After writing the 't' instead of 'c' I received following answer:
3c951138b8b9867d8657f173c1b58b82 /home/user/Downloads/Qubes/-R3.2-x86_64.iso

I did this for all types (md5sum sha1sum sha256sum sha512sum)

After that I compared with the openssl dgst types and it worked perfect.

But in the file on the website from qubes os is written: 

`However, it is possible that an attacker replaced Qubes-R3.2-x86_64.iso with a 
malicious ISO, computed the hash values for that ISO, and replaced the values 
in Qubes-R3.2-x86_64.iso.DIGESTS with his own set of values. Therefore, 
ideally, we should also verify the authenticity of the listed hash values. 
Since Qubes-R3.2-x86_64.iso.DIGESTS is a clearsigned PGP file, we can use gpg 
to verify it from the command line:`

I decided to check now the last step:

$ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
Answer from the terminal: 
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified
Please remember that the signature file (sig. or asc.) 
should be the first file given on the command line.

I tried the same step with the renamed the file .iso.DIGESTS

$ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DISGESTS'

The answer was the same: 
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified
Please remember that the signature file (sig. or asc.) 
should be the first file given on the command line.

The terminal suggest to compare the files like I described above:

But that command does not work in my terminal:

gpg -v --verify Qubes-R3.2-x86_64.iso.asc Qubes-R3.2-x86_64.iso
Answer: 

gpg: armor header: Version: GnuPG v1
gpg: verify signatures failed: unexpected data

I tried now all the options and I have no Idea what I should try to solve the 
verification problem. That's why I need help.

I checked the ~/.gnupg (Maybe it's helpful for you)
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA 
128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPMED160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

Syntax: gpg [options] [files]
Sign, check, encrypt or decrypt
Default operation depends on the input data

I WOULD BE VERY HAPPY IF SOMEONE HAS A SOLUTION!

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 

Re: [qubes-users] Use of qubes question

[Patrick Bouldin]

On Wednesday, August 2, 2017 at 2:40:26 PM UTC-4, Chris Laprise wrote:
> On 08/02/2017 01:51 PM, Patrick Bouldin wrote:
> > Hi, I'm trying to use app vms to test an app called splunk..
> > 
> > Anyway, am I thinking about this correctly? This is what I did:
> > 
> > * I created a special template vm called - splunk-template
> > 
> > * I then downloaded the rpm package to that template's tmp folder
> > 
> > * I verified it was there.
> > 
> > * I then restarted the template.
> > 
> > * Then I created an appVM pointed to the splunk-template
> > 
> > I then looked in the /tmp folder and it wasn't there by name, here was the 
> > contents of that folder:
> > 
> > firefox_user  qubes-session-env  qubes-session-waiter  ssh-fnBwiL4QxbUY  
> > systemd-private-1789b20d2d894850aa8d42bf8e0075f7-rtkit-daemon.service-d4xIHy
> > 
> > 
> > I thought I would be able to install it from the appVM at that point, is 
> > this some kind of security thing?
> > 
> > Am I even thinking about the process correctly? Because I want to be able 
> > to install it in different appVMs as part of my learning process.
> > 
> > Thanks.
> > Patrick
> > 
> 
> The /tmp folder would not hold onto files after a shutdown. You could 
> put the rpm in a folder like /opt, or you could install it into the 
> template with 'rpm -i'.
> 
> Or it may be simpler not to use a special template at all and put the 
> rpm in the /rw folder of the appVM.
> 
> -- 
> 
> Chris Laprise, tas...@openmailbox.org
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

Thanks Chris, I decided to go ahead and install it in the template. I had tried 
that once and had another problem, tried it again, same thing. Once installed I 
can't access the folder where it was created, which was the /opt/splunk/ 
folder, check this:

[user@fedora-24-work-splunk /]$ cd opt
[user@fedora-24-work-splunk opt]$ ls
google  splunk
[user@fedora-24-work-splunk opt]$ cd splunk
bash: cd: splunk: Permission denied
[user@fedora-24-work-splunk opt]$ sudo cd splunk
[user@fedora-24-work-splunk opt]$ ls
google  splunk
[user@fedora-24-work-splunk opt]$ 

So it didn't choke, no feedback, but I didn't get into the splunk directory...

What's happening?

Thanks, Patrick

-- 
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/37bc2366-4c80-45d4-829f-9c9f90f06b62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Use of qubes question

[Unman]

On Wed, Aug 02, 2017 at 10:51:53AM -0700, Patrick Bouldin wrote:
> Hi, I'm trying to use app vms to test an app called splunk..
> 
> Anyway, am I thinking about this correctly? This is what I did:
> 
> * I created a special template vm called - splunk-template
> 
> * I then downloaded the rpm package to that template's tmp folder
> 
> * I verified it was there.
> 
> * I then restarted the template.
> 
> * Then I created an appVM pointed to the splunk-template
> 
> I then looked in the /tmp folder and it wasn't there by name, here was the 
> contents of that folder:
> 
> firefox_user  qubes-session-env  qubes-session-waiter  ssh-fnBwiL4QxbUY  
> systemd-private-1789b20d2d894850aa8d42bf8e0075f7-rtkit-daemon.service-d4xIHy
> 
> 
> I thought I would be able to install it from the appVM at that point, is this 
> some kind of security thing?
> 
> Am I even thinking about the process correctly? Because I want to be able to 
> install it in different appVMs as part of my learning process.
> 
> Thanks.
> Patrick
> 

Patrick,

there's a fundamental flaw in what you're doing.
Run 'mount' in a Template or an appVM, and you will see that /tmp is a tmpfs - 
it's stored in memory, not on disk.
So, I doubt it survived  a reboot of the template, and it certainly wont
appear in a qube.

Apart from that you've done the right thing.

If you want to be able to use it store the file on the filesystem where
it WILL be inherited in a qube. (Not /usr/local as that is linked to 
/rw/usrlocal in a qube.)

unman

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

Re: [qubes-users] Use of qubes question

[Chris Laprise]

On 08/02/2017 01:51 PM, Patrick Bouldin wrote:

Hi, I'm trying to use app vms to test an app called splunk..

Anyway, am I thinking about this correctly? This is what I did:

* I created a special template vm called - splunk-template

* I then downloaded the rpm package to that template's tmp folder

* I verified it was there.

* I then restarted the template.

* Then I created an appVM pointed to the splunk-template

I then looked in the /tmp folder and it wasn't there by name, here was the 
contents of that folder:

firefox_user  qubes-session-env  qubes-session-waiter  ssh-fnBwiL4QxbUY  
systemd-private-1789b20d2d894850aa8d42bf8e0075f7-rtkit-daemon.service-d4xIHy


I thought I would be able to install it from the appVM at that point, is this 
some kind of security thing?

Am I even thinking about the process correctly? Because I want to be able to 
install it in different appVMs as part of my learning process.

Thanks.
Patrick



The /tmp folder would not hold onto files after a shutdown. You could 
put the rpm in a folder like /opt, or you could install it into the 
template with 'rpm -i'.


Or it may be simpler not to use a special template at all and put the 
rpm in the /rw folder of the appVM.


--

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

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

[qubes-users] Use of qubes question

[Patrick Bouldin]

Hi, I'm trying to use app vms to test an app called splunk..

Anyway, am I thinking about this correctly? This is what I did:

* I created a special template vm called - splunk-template

* I then downloaded the rpm package to that template's tmp folder

* I verified it was there.

* I then restarted the template.

* Then I created an appVM pointed to the splunk-template

I then looked in the /tmp folder and it wasn't there by name, here was the 
contents of that folder:

firefox_user  qubes-session-env  qubes-session-waiter  ssh-fnBwiL4QxbUY  
systemd-private-1789b20d2d894850aa8d42bf8e0075f7-rtkit-daemon.service-d4xIHy


I thought I would be able to install it from the appVM at that point, is this 
some kind of security thing?

Am I even thinking about the process correctly? Because I want to be able to 
install it in different appVMs as part of my learning process.

Thanks.
Patrick

-- 
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/34256af1-d5b1-4967-bea0-8c46d3d34f32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 3.2 Network failure after update template to fedora-25

[jpb]

Thanks Unman for the info and suggestion.

I switched the template for sys-net to debian-8. This one came along with Qubes 
3.2.  sys-net had no trouble getting an IP assigned to the vif.

I then switched the template for sys-net back to fedora-25 and the IP 
assignment to the vif again failed as before.

I then issued:
qvm-prefs sys-net -s netvm none

That didn't resolve the problem - sys-net still didn't get an IP assigned to 
the vif.

Next I thought maybe it is upstream and ran the qvm-prefs against the 
sys-firewall:
qvm-prefs sys-firewall -s netvm sys-net

Same problem - no IP assigned to the sys-net vif.

I use debian for some of the qubes but have not used it for the sys-net or 
sys-firewall.  I'm also suspect that since debian-8 came with the qubes 3.2 
release, it may be working just like fedora-23 has been working.  I'll follow 
the clone and upgrade instructions to take the debian-8 and transform it into a 
debian-9 template and try it.  If that works, I'll shift the netvm's over to 
debian and then reevaluate with Qubes 4.0.

-- 
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/f6ddc75d-612c-4434-9d76-596398c720f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 3.2 Network failure after update template to fedora-25

[Unman]

On Wed, Aug 02, 2017 at 07:01:15AM -0700, j...@stonequarter.com wrote:
> I've been doing more digging and came across an FAQ that suggested checking:
> systemctl enable NetworkManager-dispatcher.service
> 
> In reviewing the fedora-23 and 25 templates, the service is enabled in both.
> 
> This morning I shutdown all qubes and brought sys-net up under fedora-25.  
> The network interfaces showed enp0s0 and lo - both properly plumbed and I 
> could ping the external world.  But there was no vif interface.  
> NetworkManager-dispatcher.service showed it ran successfully.
> 
> I then started sys-firewall (also under fedora-25).  When sys-firewall 
> started successfully, I looked at the network interfaces on sys-net and now 
> vif10.0 was added, but it carries no inet or inet6 IP addresses.
> 
> I'm not finding any logs in dom0 or sys-net that would tell me why the vif 
> didn't get an IP. Any suggestions on where I might look for the problem?
> 

I've noticed after one of the recent updates, that my Debian qubes
sometimes dont get allocated an IP address on first connection -
particularly if I change netvm. (I dont use Fedora) 
What works for me is just running the connection again -
qvm-prefs  -s netvm 

After the second "bump" the IP address is allocated as expected.
I haven't bothered to debug.

I'd be interested to know if you see this behaviour when using Debian
templates, and if it's particular to sys-net or if it affects any
netvm, including sys-firewall.

NetworkManager-dispatcher is an old service that should trigger on
change in external IP - I dont think it's relevant to your issue.
It's expected that there wont be a vif interface until you attach a qube
downstream.

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

Re: [qubes-users] dvm removal ?

[Unman]

On Tue, Aug 01, 2017 at 12:59:23PM -1000, yreb-qusw wrote:
> On 08/01/2017 01:05 AM, Marek Marczykowski-Górecki wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > On Mon, Jul 31, 2017 at 10:01:50PM -1000, qubester wrote:
> > > Hello,
> > > 
> > > when I create a dvm  i'm now up to dvm-17  , is one supposed to be 
> > > removing
> > > dvm's manually?  because I do see how,  though each ititeration, continues
> > > to count up  would that be expected behavior?
> > 
> > No, it isn't. For which Disposable VMs it happens? Started from menu,
> > opening a file in DispVM, or something else?
> .often I have done, open pdf  in DispVM  and then when I close the pdf
> the DispVM disappears.  Rarely from the menu.
> 
> ..fwiw, I had  been  using the Whonix suggested default DVM , but
> wanted/want to go back to the default method,  as I think the Whonix way
> is/was "over my head" ; so just recently I changed the default back to
> Fedora 25 template  FWIW.
> 
> 
> I don't really recall which of the 3 options I used for the Whonix DVM
> setup  but 
> (https://www.whonix.org/wiki/Qubes/Disposable_VM#Creating_a_New_DisposableVM-Template_Based_on_Whonix-Workstation)
> 
> 
> How  would I now  delete  DVMs  that are not  in my list,  even when all
> hidden VMs  are enabled ?
> 

It isn't clear to me what OP's problem was.
It's expected that the number will iterate upwards, but there is no need
to remove dvm's manually. They are (should be) culled when the called
application exits.
Very occasionally I have seen this fail.

If you have DVMs that are still on disk, but don't appear in Manager,
or qvm-ls , just delete the files off disk.
If they DO appear under qvm-ls, just delete with qvm-remove.

But if they arent on the list and arent on disk, then they've been
automatically culled as expected.

If they consistently fail to be removed, I'd suggest removing the
DVMTemplate and recreating it. I'd also examine any customizations made
to the default templates.

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

[qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

[turboacan]

Have successful fresh install on T430

>Removing iommu=no-igfx from
>the Xen command line fixed it

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

[qubes-users] Re: Qubes 3.2 Network failure after update template to fedora-25

[jpb]

I've been doing more digging and came across an FAQ that suggested checking:
systemctl enable NetworkManager-dispatcher.service

In reviewing the fedora-23 and 25 templates, the service is enabled in both.

This morning I shutdown all qubes and brought sys-net up under fedora-25.  The 
network interfaces showed enp0s0 and lo - both properly plumbed and I could 
ping the external world.  But there was no vif interface.  
NetworkManager-dispatcher.service showed it ran successfully.

I then started sys-firewall (also under fedora-25).  When sys-firewall started 
successfully, I looked at the network interfaces on sys-net and now vif10.0 was 
added, but it carries no inet or inet6 IP addresses.

I'm not finding any logs in dom0 or sys-net that would tell me why the vif 
didn't get an IP. Any suggestions on where I might look for the problem?

-- 
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/dcb20459-9a87-43b0-837e-8679a6586061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

[justinfhsu]

On Wednesday, August 2, 2017 at 7:58:24 AM UTC-4, PR wrote:
> Hello,
> 
> 
> 
> Am 02.08.2017 1:45 nachm. schrieb  :
> 
> On Monday, July 31, 2017 at 5:23:20 PM UTC-4, Micah Lee wrote:
> 
> > On 07/31/2017 04:43 AM, Marek Marczykowski-Górecki wrote:
> (...), when I boot up, grub
> 
> > works, but then as soon as Qubes starts to boot the computer reboots,
> 
> > and I end up back in grub.
> 
> 
> 
> Having the EXACT same issue with my T430s
> 
> 
> 
> Have you tried the suggestions from "Rusty Bird":
> 
> 
> I ran into the same behavior on a T420. Removing iommu=no-igfx from
> the Xen command line fixed it. [1]
> If that doesn't help, _adding_ console=vga should let you see what's
> going on.
> 
> 
> @codgedodger:
> Did this help in your case?
> 
> 
> Kind regards
> 
> 
> - PhR

I had this issue on my Thinkpad X230 with a fresh install of 4.0-rc1 and the 
fix let me boot, but, when I shutdown, the system hangs and when I hit escape 
on the shutdown screen, I see errors in device-mapper failing to remove ioctl 
on the VMs and then a bunch of the error "failed to write error node for 
backend/" for xen-pciback and vbd.

-- 
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/6cebecec-caa7-4367-8cd7-90f0795258e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - Dell XPS 15 9560

[Eric]

On Wednesday, August 2, 2017 at 5:16:52 AM UTC-7, Eric wrote:
> Thanks for the info! I've been eyeing this hardware as Qubes 4 becomes 
> visible on the horizon - ordering through Dell allows for customizing things 
> to a great degree. I was able to spec out a 1TB SSD, i7 processor, and no 
> fingerprint reader or QHD screen, to save battery and power options! pretty 
> cheap, too - just under 2K with 16GB of RAM.
> 
> For future reference, because I couldn't find the info anywhere, this machine 
> supposedly has a TPM 2.0 chip 
> (https://www.microsoft.com/en-us/store/d/Dell-XPS-15-9560-Laptop/91076TJJ2WFB/FD4C).
> 
> Have you been able to get AEM working? And, how is your battery life? It 
> sounds like the Killer AC chip is working ok, since it's just a rebranded 
> Atheros chipset, other than the standby issue - can you confirm?

Some follow up, since I've been attempting to ascertain whether or not the 
discrete GPU can be disabled completely: 
https://wiki.archlinux.org/index.php/Dell_XPS_15_9560

Does not appear so, which is a shame - significant power draw from that even 
when idle, and according to everything I can find, there are NO options to 
disable the discrete GPU in BIOS.

However, if you're comfortable with dumping and rewriting the BIOS slightly, it 
seems like there might be a way to disable it. This guy's trying to disable the 
*integrated* graphics, but he claims that tweaking a certain bit completely 
removes the ability for windows to see the card.

http://forum.notebookreview.com/threads/xps-9560-disabling-integrated-graphics.806855/#post-10563153

probably no easy way to check, but, does blacklisting the noveau driver prevent 
the GPU from coming online *at all* ??

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To 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/4e20937f-9aad-448f-9901-cf9a3410f9d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL - Dell XPS 15 9560

[Eric]

On Monday, February 20, 2017 at 12:16:35 AM UTC-8, Stefan wrote:
> Hi,
> 
> installed Qubes 3.2 on my new laptop. After some initial problems, it
> seems to be working great!
> 
> After installing from the ISO image, the graphics driver was working
> fine (at least I remember it this way), only suspend to RAM crashed the
> machine. I updated all packages (fedora template and dom0), and after a
> reboot, X used the framebuffer driver and did not detect the Intel
> graphics chip :-(
> 
> Both problems were solved by enabling the qubes-dom0-unstable repo and
> updating the dom0 kernel to the version provided there. Intel VGA and
> Suspend to RAM are working fine now.
> 
> 
> The nvidia chip (GTX 1050) is not supported by the nouveau driver, and I
> didn't go through the pain (not to speak of the security concerns) of
> manually installing the latest proprietary driver from nVidia on dom0.
> 
> 
> Suspend to RAM seems to have some problem with the WLAN driver, though.
> After some suspend cycles, WLAN won't come up again. I put the driver
> ath10k_pci to the suspend-module-blacklist, I think this did the trick.
> 
> 
> Stefan.

Thanks for the info! I've been eyeing this hardware as Qubes 4 becomes visible 
on the horizon - ordering through Dell allows for customizing things to a great 
degree. I was able to spec out a 1TB SSD, i7 processor, and no fingerprint 
reader or QHD screen, to save battery and power options! pretty cheap, too - 
just under 2K with 16GB of RAM.

For future reference, because I couldn't find the info anywhere, this machine 
supposedly has a TPM 2.0 chip 
(https://www.microsoft.com/en-us/store/d/Dell-XPS-15-9560-Laptop/91076TJJ2WFB/FD4C).

Have you been able to get AEM working? And, how is your battery life? It sounds 
like the Killer AC chip is working ok, since it's just a rebranded Atheros 
chipset, other than the standby issue - can you confirm?

-- 
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/bb279f61-2c21-404c-9bb0-1132478e9952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

['P R' via qubes-users]

Hello,

Am 02.08.2017 1:45 nachm. schrieb :

On Monday, July 31, 2017 at 5:23:20 PM UTC-4, Micah Lee wrote:
> On 07/31/2017 04:43 AM, Marek Marczykowski-Górecki wrote:
(...), when I boot up, grub
> works, but then as soon as Qubes starts to boot the computer reboots,
> and I end up back in grub.

Having the EXACT same issue with my T430s


Have you tried the suggestions from "Rusty Bird":

I ran into the same behavior on a T420. Removing iommu=no-igfx from
the Xen command line fixed it. [1]
If that doesn't help, _adding_ console=vga should let you see what's
going on.

@codgedodger:
Did this help in your case?

Kind regards

- PhR

-- 
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/CAM8xnvKyi0Ydsq3Kq%3D0ZAUn4RzDD0xwSqf7ThJ0C8r3fN69oTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.