[qubes-users] (No subject)Fedora minimal template during Qubes initial installation

[a.mcwh...@yandex.com]

Hi dear Qubers, Is it possible somehow to create default qubes (Network, Firewall, Work, Personal, Untrusted, Vault etc) based on Fedora minimal template during initial Qubes OS installation?  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/612901490154403%40web31j.yandex.ru.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Maybe a silly question

[a . mcwheel]

Hi,
KasperskyOS is system for embbeded devices, for industrial devices. I don't see 
any advantages for home usage in Qubes  OS. Besides, it's a closed source peace 
of software. Just forget about it, unless you are engineer/developer and going 
to use it for it's primary purposes.

As for Kaspersky Security for Virtualization, it could add extra security,  but 
due to it's closed source nature it could be a weakness itself.
Also, it supports Citrix Xen Server, but it doesn't support open source Xen 
Server itself... Besides, it's not for free and pretty costly, not for home 
usage.

On March 22, 2017 4:35:59 AM AEDT, Manuel Cornejo  
wrote:
>Hi everyone.
>
>As Qubes works by means of the principle of security by isolation and
>every
>part of the hardware is running in a virtual machine. Does it make any
>sense to use Kaspersky Security for virtualization over the xen
>hypervisor
>to improve security and antihacker security?
>Is going KasperskyOS to suppose a big concurrency to Qubes?
>
>Sincerely
>
>Manuel Cornejo
>
>-- 
>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/CABa7D7LqA1OdwguqYFRynJ%2BerCqYs1cNYyBPnapBNzduX%2BzQJg%40mail.gmail.com.
>For more options, visit https://groups.google.com/d/optout.

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

Re: [qubes-users] Maybe a silly question

[Desobediente]

I second this.

If it's closed source, then by definition it is impossible to improve security. 
It's the other way around, it actually compromises all prior efforts into 
security.

-- 
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/48229538-0d86-416c-a172-b9fba4b4b092%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] [FIXED] Can't read superblock

[Desobediente]

This is not really related to Qubes, but since this is a user list and the 
qubes installer usually facilitate for the user to use a LUKS+BTRFS scheme, 
I'll share this endeavour.

Long story of how my SSD drive got corrupted: I went to sleep one day after 
making sure all torrents were seeding, unaware that the power chord of 
qubestop-1 (that's how I call the computer) was loose, and therefore it ran 
from battery for some hours, but when I woke up qubestop-1 was off. I plugged 
the power cord, tried to boot and after I unencrypted the hard disk, I got a 
warning that the second partition couldn't mount because of a superblock error. 
Then I got dropped to an emergency shell.

So I was left with a disk that was mounting only the boot partition and the 
encrypted swap, but not the qubes root filesystem. I could decrypt it, but not 
mount the BTRFS filesystem.

I then boot qubestop-1 from a Kali Linux live usb. It didn't have btrfs, so I 
had to install it:

root@kali:~# apt-get update; apt-get install btrfs-tools

The next step (or could have been the prior) was to mount the qubes SSD drive 
and decrypt the partition with errors. I used gnome-disks for that. It is 
important to note that the device that I will use below is not /dev/sdb2. When 
the partition was unencrypted, gnome-disks "created" a new file which looks 
like /dev/mapper/luks-01234567-890a-bcde-f012-3456789abcde.

I first made sure that btrfs-check was going to fix the error by running in 
read only mode. This is the default and normally don't require any further 
action:

root@kali:~# btrfs check -p 
/dev/mapper/luks-01234567-890a-bcde-f012-3456789abcde

After I've done saying my prayers and convinced myself that I knew what I was 
doing, I ran the real deal with the scary --repair option:

root@kali:~# btrfs check -p --repair 
/dev/mapper/luks-01234567-890a-bcde-f012-3456789abcde

I could then mount the partition normally and resume seeding my torrents.

One thing totally unrelated but which should be noted is that KDE or some other 
tool at dom0 should have hibernated before the battery finished, and it didn't. 
I'm not sure if this was my fault.

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

[qubes-users] Error in qubes-builder: "Can't check signature"

[lokedhs]

I'm trying to use qubes-builder to build an image from source. I followed the 
instructions on the web site, but I'm getting errors when running "make 
get-sources":

=
$ make get-sources
-> Updating sources for builder...
--> Fetching from https://github.com/QubesOS/qubes-builder.git master...
--> Verifying tags...
No valid signed tag found!
---> One of invalid tag:
object 2548dc6d3d44cd04d121643b5f3c7dcc28650776
type commit
tag mm_2548dc6d
tagger Marek Marczykowski-Górecki  1490065453 
+0100

Tag for commit 2548dc6d3d44cd04d121643b5f3c7dcc28650776
gpg: Signature made Mon 20 Mar 2017 08:04:12 PM PDT using RSA key ID 42CFA724
gpg: Can't check signature: No public key
error: could not verify the tag 'mm_2548dc6d'
make: *** [builder.get-sources] Error 1
=

Note that the signature seems to be fine, as the tag command works:

=
$ git tag -v `git describe`
object 2548dc6d3d44cd04d121643b5f3c7dcc28650776
type commit
tag mm_2548dc6d
tagger Marek Marczykowski-Górecki  1490065453 
+0100

Tag for commit 2548dc6d3d44cd04d121643b5f3c7dcc28650776
gpg: Signature made Mon 20 Mar 2017 08:04:12 PM PDT using RSA key ID 42CFA724
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes OS signing key) 
"
=

Any suggestions as to what I'm supposed to do?

Regards,
Elias

-- 
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/92f8f402-768d-4ce0-ac89-01c7b460732b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - ASUS KGPE-D16

[Thierry Laurion]

Any recommendations for tpm?

-- 
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/2b14f0d3-5677-43da-9014-b5a22190220d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: HCL - Dell Latitude 7480

[lokedhs]

On Tuesday, 21 March 2017 21:46:25 UTC+8, Mike Keehan  wrote:

> On Sun, 19 Mar 2017 21:39:15 -0700 (PDT)
> loke...@gmail.com wrote:
> 
> > On Monday, 20 March 2017 12:27:43 UTC+8, lok...@gmail.com  wrote:
> > > I have not been able to install Qubes 3.2 on this machine.
> > > 
> > > The installer cannot start as the graphics card is not supported.
> > > The result is that you get dropped into the text-based installer
> > > which does not work.
> > > 
> > > This is kind of disappointing as this is a very light laptop that
> > > supports up to 32 GB RAM, which would be very nice to have with
> > > Qubes.  
> > 
> > I forgot to include the actual specs for the machine I used for
> > testing:
> > 
> > Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
> > 16 GB RAM
> > Intel Integrated HD Graphics 620
> > 
> > Specs at: http://www.dell.com/sg/business/p/latitude-14-7480-laptop/pd
> > 
> 
> Have you booted in UEFI mode?  I had the same problem when using legacy
> boot.

Thank you. Doing that allowed me to do a normal install. However, the resulting 
installation does not have working networking (neither wired nor wireless). 
Doing "ip link" does not show any physical devices, so I suspect that this is a 
driver issue.

I will build a new installer image in the hope that it will contain the 
appropriate drivers. I will update this post when this is done.

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

Re: [qubes-users] show NetworkManager for AppVM? (aka AppVM with WiFi device in Hotspot Mode)

[Unman]

On Wed, Mar 22, 2017 at 12:35:00AM +, Joonas Lehtonen wrote:
> Hi,
> 
> I'd like to use the WiFi adapter in my laptop in hotspot mode.
> 
> Target setup:
> 
> wired-netvm <->proxyvm <-> hotspotVM (has the wifi device assigned)
> 
> (hotspotVM acts as an access point to other devices)
> 
> 
> Creating a NetVM with gets the WiFi adapter assigned and using
> NetworkManager to create a hotspot is easy and works fine, but in that
> case the hotspot has no "uplink" connectivity.
> 
> On the other side creating an AppVM and assigning the WiFi device to it
> would solve the "uplink" problem, but in that case the NetworkManager
> does not show up next to the clock.
> 
> Is there an easy way to tell the hotspotVM to show/expose the
> NetworkManager icon next to the clock?
> 
> thanks!
> Joonas

Hi Joonas,

You'll need a qube with the Network Manager service enabled - using a
proxy makes sense.

By default the applet is hidden - there's a script to govern this:
/usr/lib/qubes/show-hide-nm-applet.sh

Enable the service:
'qvm-service  -e network-manager
Start the qube, and the nm-applet should appear in the panel.

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

[qubes-users] Re: [qubes-devel] Re: Announcing the Xen Security Advisory (XSA) Tracker

[Reg Tiangha]

On 03/21/2017 08:15 PM, Marek Marczykowski-Górecki wrote:
>
>> If not, is
>> it just stock Xen or does Qubes modify it in some way? Is this something
>> that we can build and compile ourselves? And would manually upgrading
>> Xen affect any other Qubes packages? I know that the security risk of
>> running an older version is low, but a bug is still a bug and if it's
>> already been squashed, then it might as well be pushed out. I don't mind
>> running qubes-builder myself and I've started building my own dom0
>> kernels using the qubes-linux-kernel build scripts just so I can be
>> kept-up-to-date with the latest releases, so if it's just a matter of
>> plugging in a newer version of Xen and compiling various bits against
>> it, I'm willing to play around with that on a personal level if someone
>> can point me in what direction to go.
> If you want to compile it yourself using qubes-builder, simply increasing
> version number in "qubes-src/vmm-xen/version" file should be enough. Ah,
> and probably removing patches (series.conf) already included upstream.
> If you do that, please provide any feedback (positive or negative) about
> the update.
>
Understood. I had to do the same sort of thing when trying to get both
4.9 and 4.10 kernels working with the Qubes build script (am currently
running 4.10.4 in dom0; seems to work fine). I might give that a try
this weekend.

As an aside, I know that people would like to get more current kernels
running (although I just noticed that we now have an official 4.4.55 so
thanks!), and I'd be happy to share my work if someone could teach me
the proper way to *create* a patch (this stuff isn't my area of expertise).

What I've been doing was migrating the kernel patches that still apply
by hand and then running diff -Nuar between the two to generate a patch
file that I could plug into the build scripts, but then when I run make
rpms, it asks me to manually input what file I'm trying to patch (so
obviously, that isn't the right way to do it). If someone could teach me
the proper way to do that part, and if figuring out the patch situation
with each kernel release is a big bottleneck in the development
pipeline, then I'd be happy to give back the results of my work if that
would help out the project. I've booted both dom0 and domUs with both
4.9 and 4.10 kernels, and I haven't noticed any issues and the patches
that still apply seem to work fine.


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

[qubes-users] Re: [qubes-devel] Re: Announcing the Xen Security Advisory (XSA) Tracker

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, Mar 21, 2017 at 07:54:44PM -0600, Reg Tiangha wrote:
> I have a question, just as a regular user: Because Qubes isn't affected
> by the most recent XSA, does this mean we probably won't get Xen 4.6.5
> pushed out? Or is that something that will come eventually? 

We will release updated package, but it isn't top priority right now.
Probably will happen in 2-3 weeks.

> If not, is
> it just stock Xen or does Qubes modify it in some way? Is this something
> that we can build and compile ourselves? And would manually upgrading
> Xen affect any other Qubes packages? I know that the security risk of
> running an older version is low, but a bug is still a bug and if it's
> already been squashed, then it might as well be pushed out. I don't mind
> running qubes-builder myself and I've started building my own dom0
> kernels using the qubes-linux-kernel build scripts just so I can be
> kept-up-to-date with the latest releases, so if it's just a matter of
> plugging in a newer version of Xen and compiling various bits against
> it, I'm willing to play around with that on a personal level if someone
> can point me in what direction to go.

If you want to compile it yourself using qubes-builder, simply increasing
version number in "qubes-src/vmm-xen/version" file should be enough. Ah,
and probably removing patches (series.conf) already included upstream.
If you do that, please provide any feedback (positive or negative) about
the update.

- -- 
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

iQEcBAEBCAAGBQJY0d4/AAoJENuP0xzK19cs7KAH/2ZpcbNYXnBuYqqAYecs+ey5
+X8OO/dpiZs4tvYLJ9u7Key1QJHkGZm1CRzy/NuDdaU93yt6HJYsnjsQNOdhUWbS
sNKNdNgMFBhQxeAA1sDs0mEQ0njKypuRuo14xI/cvPDxKS5uBXXRm5RNx4xlcyaJ
VtMPq9/BCbCOYAQWC7Ew2R8ybqvJQihX9H3ED/9gUCqR7YX6Zrf6DMKLVmyqCh2k
Ip+VPL+TNJN8trdT/r3RzfEDMAoo+Fwn6bNQDf1XM7IOxioRxfuApll/LIltQJxI
tErVPSXVfzKDfyP7cdtNQtSu9dZEdPfno22sqB5igzIkfeFK2NzBKSlEWMCLdUc=
=YIYo
-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/20170322021526.GU1208%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Turn standalone VM to a template VM

['qubes-user-000' via qubes-users]

Hello,
I have a Standalone Windows 7 VM that I want to convert to a Template VM so I 
can deploy clones from it like in vSphere Server.

Is there a way to convert an existing Standalone VM to a Template VM?

-- 
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/e356b6d2-9363-4d61-a48d-5f2d2de54ea3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Announcing the Xen Security Advisory (XSA) Tracker

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Qubes community,

We're pleased to announce the new Xen Security Advisory (XSA) Tracker
[1]. This tracker clearly shows whether the security of Qubes OS is
(or was) affected by any given XSA [2] in a simple "Yes" or "No"
format. Since Qubes OS uses Xen for virtualization, we know that many
of our users follow new XSA announcements. However, we also understand
that most of our users aren't Xen experts and may not be able to
easily determine whether an XSA affects the security of Qubes. We know
that this uncertainty can be unsettling, so our aim with the
XSA Tracker is to remove any doubt by communicating this information
clearly and directly to users, as we already do with Qubes Security
Bulletins (QSBs) [3].

It's worth noting that Qubes has typically not been affected by new
XSAs. At present, it has been over six years since the first XSA was
published on March 14, 2011. Since that time, 203 XSAs have been
published (excluding unused XSA numbers and currently embargoed XSAs).
However, only 17 (8.37%) of these XSAs have affected the security of
Qubes OS. These statistics [4] will continue to be updated on the
tracker page as new XSAs are published.

Most recently, XSA-211 was published on 2017-03-14. The security of
Qubes OS is not affected by this XSA, as you can see here:

https://www.qubes-os.org/security/xsa/#211

Best,
Andrew


[1] https://www.qubes-os.org/security/xsa/
[2] https://xenbits.xen.org/xsa/
[3] https://www.qubes-os.org/security/bulletins/
[4] https://www.qubes-os.org/security/xsa/#statistics

This announcement is also available on the Web:
https://www.qubes-os.org/news/2017/03/21/xsa-tracker/

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

iQIcBAEBCgAGBQJY0db+AAoJENtN07w5UDAw0mIQAJC5Ga1qQwQJwb+dsCUV3SfA
EJ4uyPHPQwpUt4oQ3WfhjSbdaXPkUxXgweR074WNJxh+05O0F4W+0hU1O+hlYnJc
Xld6XUaVzS5o7i80E6xHp7WStcGmyj1CE+WjOCla2HxbSuVLOsKg+zVyY/5Ob3X8
auV3MofH/2xZuxRWD34al56ZtTEXVyDH3PtngmMVz0JBhxPGWZEDp0zd25Kri1Ej
92ZF1W0C4fpVHu3Ve0SgpJmXX7HI8s0a88VR3eyaIuSyjHJCFd7hhNuVcwBt4VW5
uTrYnCz+GD+RtFbILMmScetz+PqdMlNSINVGZFIdWtieiMnugApq6PTVdsOtay9a
6KWnh3byeivui2lO6jVp/9XjAWekZpa0boLNIaRoQ0491suXpattxeLlWyqQU6ng
wGLrHzfbpVqYJeBM//FM+eyezFVMxblzhUemv1GG9AWO1wCh6hif9sskSxVXCjaQ
t0hnFFGYRy5/L1qyc/4jVgH/IXqlXTArcAHoh/Tc43pRztJHEVL/aswJaoOYQp+d
zdimQXvSS4HszsW2bzy0vKvSGNTswc7mnxfFM9vKHKobL+GtxXxooPGqFzqXMvLV
woUoiLf0yhrWEk+GhpI7HiU4ZzD/6F774ZB56xo32VonBSq7jDI7+oI+kdYaPafR
m8B+o2Ecel5bcRMvaWNu
=VXzx
-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/c89aa580-698a-3dbb-9e19-4836068753a0%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Lenovo ThinkPad T460s 20FAS5WM00

[elimisteve]

On Sunday, November 13, 2016 at 6:57:42 AM UTC-8, bertho...@web.de wrote:
> all working as intended, only exception: no sound @hdmi yet.

How is battery life on your T460s using Qubes? I'm considering buying one, but 
there's lots of complaints online about that.

And is the CPU fast enough? I'm looking at machines with 4 cores as well.

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/9c91666f-638d-45dd-ad6a-f8479b6de3e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] New Qubes installer image?

[roberto . riveraz]

On Monday, March 20, 2017 at 7:19:34 PM UTC-7, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Mon, Mar 20, 2017 at 07:01:43PM -0700, Andrew David Wong wrote:
> > On 2017-03-20 02:58, loke...@gmail.com wrote:
> > > Since Qubes cannot be easily installed if things like networking or
> > > graphics is not available during installation, is there any plan to
> > > create a new installer image that has newer drivers?
> > > 
> > > On my old Dell Latitude E7470, I was unable to get WLAN working
> > > until I had performed a dom0 update. I was lucky to have access to
> > > a wired connection at the time, but if I had not, this would have
> > > been a difficult problem.
> > > 
> > > The newest laptop I have is a Dell Latitude 7480, where pretty much
> > > nothing works using the drivers that are included in the installer
> > > (To be fair, this machine is new enough that I'm doubtful that even
> > > the latest dom0 update would have support for it. But that does not
> > > change the question).
> > > 
> > > Are there any plans to create an updated installer image?
> > > 
> > > Regards, Elias
> > > 
> > 
> > We almost never publish new ISOs for Qubes OS versions that have
> > already been released. It's likely that the next time a new ISO will
> > be published with updated drivers will be when Qubes 4.0 is released.
> 
> Actually, for Qubes Os 3.2, which will be supported for a while, we do plan
> release new ISO image, lets name it Qubes OS 3.2.1. It will have updated
> templates, especially newer default Fedora template, and also updated
> kernel. We haven't decided for specific versions yet, but I'd like to
> have Fedora 25 and kernel 4.9.x there. Both need some testing first and
> need to hit stable repository before building new ISO image (kernel
> 4.9.x isn't even in testing repository yet).
> 
> - -- 
> 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
> 
> iQEcBAEBCAAGBQJY0I2xAAoJENuP0xzK19csd+0H/3WvmjHYLA7FezXobPlAGuqJ
> gwc7zFZtUVjjLJYbHCsdkC4xclrGkrDFjUfqwwyhhqwnpaajVwnJ/7WLPe/D25yD
> X5TTBfFNvcbIPEd2bonoOiuScZlXncyk3tVADuO016dDSbAPGHXj/bLPaM+lr07A
> BjzUWasbDDR2XZ0Ycq1cVt7WMTF45ZFzrZhTC8cxRKf2nA4Lgw5fjzY9+lavEOVN
> qe+ion46p8cLiZadx/CzkdY1MfumCxOIam31sda2UkGnS7vyOIjwAdZJd3cdGTnZ
> feHBmhF/jCgPK+60an4zdPp63e7vCGzeHc2qJI9+u1eoV/w8KeVs9D3of4FzZMs=
> =KfnL
> -END PGP SIGNATURE-

Regarding "Qubes OS 3.2.1" new ISO... would the AMD Ryzen CPU be supported? 

-- 
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/d6095d66-5eb1-4cb0-9077-17f106dd8790%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] show NetworkManager for AppVM? (aka AppVM with WiFi device in Hotspot Mode)

[Joonas Lehtonen]

Hi,

I'd like to use the WiFi adapter in my laptop in hotspot mode.

Target setup:

wired-netvm <->proxyvm <-> hotspotVM (has the wifi device assigned)

(hotspotVM acts as an access point to other devices)


Creating a NetVM with gets the WiFi adapter assigned and using
NetworkManager to create a hotspot is easy and works fine, but in that
case the hotspot has no "uplink" connectivity.

On the other side creating an AppVM and assigning the WiFi device to it
would solve the "uplink" problem, but in that case the NetworkManager
does not show up next to the clock.

Is there an easy way to tell the hotspotVM to show/expose the
NetworkManager icon next to the clock?

thanks!
Joonas

-- 
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/1d5ba1ef-0f87-c0fe-fa7d-d2aff4aaae7e%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: Tip: Restoring functionality of Windows AppVMs after a crash or forced termination

[Grzesiek Chodzicki]

W dniu poniedziałek, 20 marca 2017 13:29:50 UTC+1 użytkownik Max napisał:
> On Wednesday, 8 March 2017 06:53:09 UTC+8, Grzesiek Chodzicki  wrote:
> > After a Windows AppVM running in Seamless Gui mode crashes it often fails 
> > to connect to qrexec agent at subsequent boot causing the user to be forced 
> > to kill the AppVM which causes the machine to fail to connect co qrexec 
> > agent which causes a spiral of misery. Here's how to fix that:
> > 
> > 1. Disable Seamless GUI and enable debug mode of Windows VM
> > 2. Start Windows VM
> > 3. In the VM window You'll see the Safe Mode prompt. This prompt is the 
> > real cause of the issue as the 30 second timer prolongs the boot process 
> > which in turns causes qrexec to timeout. Select "Start Windows normally.
> > 4. In Windows AppVM launch Command Prompt as Administrator
> > 5. Use following commands in the Commands Prompt: "bcdedit /set {bootmgr} 
> > displaybootmenu no" (no quotes) and "bcdedit /set {default} 
> > bootstatuspolicy ignoreallfailures" (no quotes)
> > 6. Shutdown Windows machine
> > 7. (optionally) change how long the qrexec waits for connection from the 
> > default 60 seconds to 120 seconds
> > 8. Enable Seamless GUI back and disable debug mode
> > 
> > Your Windows VM should start normally after a crash now.
> 
> Hi,
> 
> Thanks for putting these steps together. I believe I am suffering from the 
> same issue but I can't follow the steps fully. If this is not the same issue, 
> I will delete this and start another thread.
> 
> When I try to start my Win 7 VM, it fails to start. If I start it using the 
> Debug mode I get the following error when using safe mode: 
> 
> "Cannot connect to 'windows-7' qrexec agent for 300 seconds, giving up ERROR: 
> Cannot execute qrexec-daemon!"
> 
> Looking at previous similar issues, I have attempted to re download the 
> Windows Tools again but this has not worked.
> 
> If I start Windows normally however using the debug option, Windows just 
> hangs at a "Starting Windows" screen and the Dom0 Terminal just shows 
> "Waiting for user 'Max' login..." without progressing.
> 
> Any suggestions as to how to troubleshoot this?
> 
> Thanks

Enable Debug, Disable Seamless GUI and then mash F8 as soon as the OS window 
appears, enter either Safe Mode with Networking or Last Known Good 
Configuration and then do a clean shutdown from within a VM. Helped me several 
times.

-- 
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/757bdff3-cccf-496f-9235-da12b4c9d4b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Lenovo Z50-70

[Stefan Pietzonke]

Hello,

I run Qubes 3.2 on a Lenovo Z50-70. It runs well. The notebook has a 
core I5 CPU and Nvidia optimus graphics. So it is switchable between 2D 
and 3D graphics mode. The nouveau driver shows a "chipset not supported" 
message at boot.


I did check: sleep mode, ethernet, graphics, keyboard, touchpad.

Not tested yet: wifi, bluetooth. Note: I had to disable wifi on the BIOS 
in order to install Qubes.


With wifi turned on it hangs at the "configuring network" in the installer.


cheers

Stefan Pietzonke


--
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/b51a9129-e1c5-6f14-86a5-60a85f0353a1%40gmx.net.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-LENOVO-20354-20170320-223741.yml
Description: application/yaml

[qubes-users] Maybe a silly question

[Manuel Cornejo]

Hi everyone.

As Qubes works by means of the principle of security by isolation and every
part of the hardware is running in a virtual machine. Does it make any
sense to use Kaspersky Security for virtualization over the xen hypervisor
to improve security and antihacker security?
Is going KasperskyOS to suppose a big concurrency to Qubes?

Sincerely

Manuel Cornejo

-- 
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/CABa7D7LqA1OdwguqYFRynJ%2BerCqYs1cNYyBPnapBNzduX%2BzQJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: HCL - Dell Latitude 7480

[Mike Keehan]

On Sun, 19 Mar 2017 21:39:15 -0700 (PDT)
loke...@gmail.com wrote:

> On Monday, 20 March 2017 12:27:43 UTC+8, lok...@gmail.com  wrote:
> > I have not been able to install Qubes 3.2 on this machine.
> > 
> > The installer cannot start as the graphics card is not supported.
> > The result is that you get dropped into the text-based installer
> > which does not work.
> > 
> > This is kind of disappointing as this is a very light laptop that
> > supports up to 32 GB RAM, which would be very nice to have with
> > Qubes.  
> 
> I forgot to include the actual specs for the machine I used for
> testing:
> 
> Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
> 16 GB RAM
> Intel Integrated HD Graphics 620
> 
> Specs at: http://www.dell.com/sg/business/p/latitude-14-7480-laptop/pd
> 

Have you booted in UEFI mode?  I had the same problem when using legacy
boot.

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

Re: [qubes-users] Installing Qubes 3.2 on an Alienware

[Mike Keehan]

On Fri, 17 Mar 2017 19:18:03 -0400
Tristan Fleming  wrote:

> Has anyone found a work around for Qubes on an Alienware 17 r4?
> 
> I just bought this laptop thinking that it would work with Qubes. So
> far, I havent had any luck. It was a good excuse to buy a new laptop,
> though! ;)
> 
> I bought the Alienware 17 r4
> Intel(R) Core(TM) i7-7700HQ
> 8gb ram DDR4
> NVIDIA GeForce GTX 1060 with 6GB GDDR5 (problem numero uno)
> 
> So, to the point, I have two problems. One is the GFX card. And the
> other is UEFI.
> 
> Oh, and lest we forget the Qubes bugs.
> 
> I booted in Legacy mode, initial graphics GUI starts, Boot into basic
> graphics mode;
> 
> Basic Graphics Mode FAILS
> 
> Txt based install has common bugs: "LUKS was not provided a pw" Cannot
> partition, cannot install!
> 
> On the Hardware Compatibility List, it says Alienware works but
> without sound. So, how did that person get Alienware to work!?
> 
> Any help is appreciated. My problems are common, but someone figured
> this out, right?
> 
> Thanks, crew!
> 

I found that I had to boot in UEFI mode for the graphical installer
to work with my new laptop - legacy booting the usb stick gave me the 
same text installer problems you are seeing.

Mike.

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