Qubes awarded MOSS Mission Partners grant!
https://www.qubes-os.org/news/2020/05/22/moss-mission-partners-grant/

We’re proud to announce that the Qubes OS Project has been awarded a
Mozilla Open Source Support (MOSS) (https://www.mozilla.org/en-US/moss/) awards program grant in the amount
of 128,000 USD. This generous one-year grant will fund the work of
Frédéric Pierret (https://www.qubes-os.org/team/#fr%C3%A9d%C3%A9ric-pierret) on making Qubes more robust and stable, as well as
several key parts of Nina Alter (https://www.qubes-os.org/team/#nina-eleanor-alter)’s extensive work on making Qubes more
user-friendly.

There are three separate tracks for MOSS awards. Qubes has been awarded
a grant in the Mission Partners (https://www.mozilla.org/en-US/moss/mission-partners/) track. As Mozilla explains, “The
Mission Partners track supports open source projects that significantly
advance Mozilla’s mission.” It is a great honor for Qubes to be
recognized as such a project, and we’re thrilled by the important work
that this grant will enable.

Google Summer of Code & Season of Docs 2020
https://www.qubes-os.org/news/2020/05/23/google-summer-of-code-and-season-of-docs-2020/

We’re pleased to announce that the Qubes OS Project will be
participating in both Google Summer of Code (https://summerofcode.withgoogle.com/) and Google Season of
Docs (https://developers.google.com/season-of-docs) for 2020!

For Google Summer of Code this year, William Huang will be working on
Template Manager and Package Handling Improvements (https://summerofcode.withgoogle.com/projects/#6190965460566016) under the
mentorship of Qubes project lead Marek Marczykowski-Górecki (https://www.qubes-os.org/team/#marek-marczykowski-g%C3%B3recki).
Specifically, William will be “designing a better mechanism for handling
template installation and creating a user-facing application to deal
with such mechanism and other template-related configuration,
consolidating the management of templates.” For more information about
Google Summer of Code in relation to the Qubes OS project, please see
our information page (https://www.qubes-os.org/gsoc/).

Meanwhile, with Google Season of Docs, we’re still in the technical
writer exploration phase (https://developers.google.com/season-of-docs/docs/timeline), in which “interested technical writers
discuss project ideas with mentoring organizations.” If you’re
interested in participating in Google Season of Docs with Qubes (https://www.qubes-os.org/gsod/),
the technical writer application period begins on June 9, 2020 at 18:00
UTC, and the deadline is July 9, 2020 at 18:00 UTC.

QSB #057: Special Register Buffer speculative side channel (XSA-320)
https://www.qubes-os.org/news/2020/06/11/qsb-057/

We have just published Qubes Security Bulletin (QSB) #057:
Special Register Buffer speculative side channel (XSA-320).
The text of this QSB is reproduced below. This QSB and its accompanying
signatures will always be available in the Qubes Security Pack (qubes-secpack).

View QSB #057 in the qubes-secpack:

https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-057-2020.txt

Learn about the qubes-secpack, including how to obtain, verify, and read it:

https://www.qubes-os.org/security/pack/

View all past QSBs:

https://www.qubes-os.org/security/bulletins/

View XSA-320 in the XSA Tracker:

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



---===[ Qubes Security Bulletin #57 ]===---

2020-06-11


Special Register Buffer speculative side channel (XSA-320)

Summary
========

On 2020-06-09, the Xen Security Team published Xen Security Advisory
320 (CVE-2020-0543 / XSA-320) [1] with the following denoscription:

| This issue is related to the MDS and TAA vulnerabilities. Please see
| https://xenbits.xen.org/xsa/advisory-297.html (MDS) and
| https://xenbits.xen.org/xsa/advisory-305.html (TAA) for details.
|
| Certain processor operations microarchitecturally need to read data
| from outside the physical core (e.g. to communicate with the random
| number generator). In some implementations, this operation is called
| a Special Register Read.
|
| In some implementations, data are staged in a single shared buffer,
| and a full cache line at a time is returned to the core which made the
| Special Register Read. On parts vulnerable to MFBDS or TAA, an
| attacker may be able to access stale data requested by other cores in
| the system.
|
| For more details, see:
| https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00320.html
|
|
| An attacker, which could include a malicious untrusted user process on
| a trusted guest, or an untrusted guest, can sample the contents of
| certain off-core accesses by other cores in the system.
|
| This can include data whose use may depend on the secrecy of the
| value, such as data from the Random Number Generator (e.g.
| RDRAND/RDSEED instructions).

This is yet another CPU hardware bug related to speculative execution.

Only Intel processors are affected. The RDRAND instruction became
available in Intel processors starting with Ivy Bridge (3rd gen Intel
Core). See Intel's advisory for a full list of affected CPUs. (Short
version: Most mobile/desktop CPUs are affected, while most Atoms and
server Xeons are not.)

Impact
=======

An attacker can obtain data returned by RDRAND/RDSEED instructions on
another core on the system (including another VM). In practice, Linux
does use RDRAND/RDSEED to seed its random number generator
(/dev/urandom, getrandom(2) etc.), but RDRAND/RDSEED is not the only
source of entropy. So, as long as other sources of entropy are not
compromised, the overall security of the random number generator is
still preserved. In Qubes OS, the situation is further improved by
seeding the random number generator at VM startup using a random seed
provided from dom0. This means that using Linux's random number
generator is still safe in Qubes.

Aside from the Linux kernel using RDRAND/RDSEED as one of its entropy
sources, userspace applications can also issue RDRAND/RDSEED
instructions on their own. Such software is also affected by the bug
described here. The specific impact on such software depends on what the
application does with the random data obtained in this manner.

Patching
=========

Intel has provided a microcode update that mitigates the issue. Please
note that Ivy Bridge processors are considered retired by Intel and no
longer receive microcode updates. This means that Ivy Bridge processors
will remain vulnerable to this issue. To mitigate the problem, we are

masking out RDRAND availability to VMs on those affected platforms.

The specific packages that resolve the problems discussed in this
bulletin are as follows:

For Qubes 4.0:
- microcode_ctl 2.1-30.qubes1
- qubes-core-dom0 4.0.51 (needed for Ivy Bridge platforms only)

The packages are to be installed in dom0 via the Qubes VM Manager or via
the qubes-dom0-update command as follows:

For updates from the stable repository (not immediately available):
$ sudo qubes-dom0-update

For updates from the security-testing repository:
$ sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing

A system restart will be required afterwards.

These packages will migrate from the security-testing repository to the
current (stable) repository over the next two weeks after being tested
by the community.

If you use Anti Evil Maid, you will need to reseal your secret
passphrase to new PCR values, as PCR18+19 will change due to the new
microcode binaries.

Credits
========

See the original Xen Security Advisory.

References
===========

[1] https://xenbits.xen.org/xsa/advisory-320.html

--
The Qubes Security Team
https://www.qubes-os.org/security/

Qubes Architecture Next Steps: The New Qrexec Policy System
https://www.qubes-os.org/news/2020/06/22/new-qrexec-policy-system/

This is the second article in the “What’s new in Qubes 4.1?” series. You
can find the previous one (about GUI Domains)
here (https://www.qubes-os.org/news/2020/03/18/gui-domain/). While the
introduction of GUI domains is a big, singular feature, the changes to
qrexec are more complex and varied — but also very important.

What is qrexec?

You might have been using Qubes for a while and never encountered the
word “qrexec,” but it is one of the crucial components in the system.
Qubes provides isolation and compartmentalization. Separate qubes are
separate worlds, and what the user does in one qube should not impact
another qube. That is, of course, not realistic. In the real world, we
often need and want to do things like copying and pasting, sending
files, routing internet traffic, and simply synchronizing the time. This
is where qrexec comes in: It is an RPC (remote procedure call) mechanism
that allows one qube to do something inside another qube. Of course,
allowing everything all the time would be extremely dangerous. Thus, a
part of qrexec called “qrexec policy” is also used to enforce who can do
what and where. Furthermore, we want to be able to audit what was done,
and this is provided with the logging capabilities of qrexec. The how
is controlled by qrexec services, which are executed by qrexec and also
must be designed in a secure and resilient way. This post focuses mainly
on qrexec itself, but qrexec services will make a brief appearance.

Overview of changes

Most of this post will be very technical. If you don’t care about
writing your own qrexec policies and services, feel free to just read
this overview.

Before we get into nitty-gritty technical details, here’s a brief, less
technical overview of Qubes 4.1 qrexec changes and what they mean for
users and developers:

A new qrexec policy format. (The old format is still supported, but
the new one is very much superior, allowing for easier-to-read
policies, more qube-centered customization, better auditing, and
more.)
Big performance improvements: bigger data chunk sizes for faster
transfers of large amounts of data, qrexec policy daemon for faster
policy evaluation and call setup, resulting in up to seven-fold
faster qrexec service calls.
Support for socket services: better performance for services that can
use a socket-based implementation with significantly faster setup and
connection times.
Policy notifications that make any abnormal behavior easier to detect
and any problems resulting from incorrect permissions easier to
solve.
There is one other big upcoming change (which is not yet fully
implemented and will arrive after Qubes 4.1): We are working on a qrexec
policy API, that is, a set of qrexec services that will allow for
managing qrexec policies without manually editing policy files. It’s
another step toward separating the user from dom0 and protecting the
vulnerable system internals by isolating them from the outside world to
the greatest extent possible.

New policy format

In Qubes 4.0 and earlier, policies were stored as multiple files, one
for each service. While changing permissions for a single action was
easy, managing permissions for an entire qube was very cumbersome. The
new Qubes 4.1 policy format completely overhauls this approach and
introduces several convenience features to make policy management easier
and more secure.

What if you’ve already spent time carefully crafting your policies in
Qubes 4.0? Don’t worry. The old policy format will still be supported
until at least Qubes 5.0.

You can find details of the development of the new policy format
here (https://github.com/QubesOS/qubes-issues/issues/4370).

Policy files

The biggest difference between the old and new policy formats is that,
under the new format, the entire policy is a single entity. It is not

divided into separate, per-service fragments. While it can be stored in
multiple files located in multiple places, the files are equivalent, and
each can describe policies for multiple services. In other words, we are
moving from a set of tables to one big, flat table.

The policy files, stored previously in /etc/qubes-rpc/policy/, are now
located in /etc/qubes/policy.d/. Furthermore, each file must have a
.policy extension, and any temporary files will no longer cause
issues. Under the old format, there were dozens files:

/etc/qubes-rpc/policy/
├── admin.backup.Cancel
├── admin.backup.Execute
├── admin.backup.Info
├── include
│   ├── admin-local-ro
│   ├── admin-local-rwx
│   ├── admin-global-ro
│   ├── admin-global-rwx
├── …
├── qubes.Gpg
├── qubes.StartApp
├── …
├── whonix.SdwdateStatus


Under the new format, we simply have:

/etc/qubes/policy.d/
├── 35-compat.policy
├── 90-admin-default.policy
├── 90-default.policy
├── include
│   ├── admin-local-ro
│   ├── admin-local-rwx
│   ├── admin-global-ro
│   ├── admin-global-rwx
(and any additional user-defined files)


Here’s an example of an old policy file (qubes.GetDate.policy):

## Note that policy parsing stops at the first match,
## so adding anything below "$anyvm $anyvm action" line will have no effect

## Please use a single # to start your custom comments

$tag:anon-vm $anyvm deny
$anyvm $anyvm allow,target=dom0


Here’s an example of the beginning of a new policy file
(90-default.policy):

## Do not modify this file, create a new policy file with lower number in the
## filename instead. For example `30-user.policy`.

###
### Default qrexec policy
###

## File format:
## service-name|* +argument|* source destination action [options]

## Note that policy parsing stops at the first match.

# policy.RegisterArgument should be allowed only for specific arguments.
policy.RegisterArgument * @anyvm dom0 deny

# WARNING: The qubes.ConnectTCP service is dangerous and allows any
# qube to access any other qube TCP port. It should be restricted
# only to restricted qubes. This is why the default policy is 'deny'

# Example of policy: qubes.ConnectTCP +22 mytcp-client @default allow,target=mytcp-server
qubes.ConnectTCP * @anyvm @anyvm deny

# VM advertise its supported features
qubes.FeaturesRequest * @anyvm dom0 allow

# Windows VM advertise installed Qubes Windows Tools
qubes.NotifyTools * @anyvm dom0 allow

# File copy/move
qubes.Filecopy * @anyvm @anyvm ask

# Get current date/time
qubes.GetDate * @tag:anon-vm @anyvm deny
qubes.GetDate * @anyvm @anyvm allow target=dom0


Under the new format, the policy for a single qube is much easier to
find, parse, and edit. It’s all contained in a single file, and by using
wildcards (see below), it’s much easier to read and understand. For
example, it’s trivial now to forbid all calls for a given qube or forbid
all with a list of exceptions. This allows for a more qube-centric
approach to policies, and while the results are theoretically the same,
there’s a huge difference between a couple of rules, all in one places,
and dozens of rules spread across dozens of files. It’s especially
important for Admin API policies. (The Admin API provides qrexec calls
for querying system state. There are a lot of them, and they are needed
by system qubes such as GUI domains. Under the old policy format, it was
quite arduous to edit them when each call had its own policy file.)

Now that the policy is a single entity, it is parsed as a whole. If
there are any syntax errors, the parser will refuse to load anything (in
order to prevent any unintended permission grants). The system is
designed to “failed closed”: An empty policy results in all qrexec calls
being denied. While this protects users from their own mistakes, users

should still be careful when editing policies so that the system remains
functional. This is similar to the approach that tools such as sudo
take, and we decided that it makes for a safer system on the whole. In
the future, Qubes will also include a Policy API (see below) that will
include calls for modifying the policy in a safe way that prevents
syntax errors.

New column syntax

The full specification can be found
here (https://github.com/QubesOS/qubes-core-qrexec/blob/master/Documentation/multifile-policy.markdown).

Old policy files had three columns: source qube, target qube, and action
(allow/deny/ask with optional arguments). Because the new policy format
no longer includes the service name in the file name, we had to change
this a bit to a five-column format: service name, service argument,
source qube, target qube, and action.

qrexec.Service +ARGUMENT SRCQUBE DSTQUBE {allow|deny|ask} [PARAM=VALUE [PARAM=VALUE ...]]


Under the old format, you could use wildcards only in the source qube
and target qube fields. Under the new format, you can also use wildcards
in the service name and argument fields. For example, to forbid all
calls from the work qube to the personal qube, you could use this
line:

* * work personal deny


You could also deny all calls from work except for calls to dom0:

* * work dom0 allow
* * work * deny


This, along with the new file structure, results in much clearer,
qube-centered policy rules.

A minor change is the replacement of commas with spaces in the parameter
list. For example, a ConnectTCP policy could look like this:

qubes.ConnectTCP * mytcp-client @default allow target=mytcp-server


Security in symbols

The old policy format used the $ character in multiple keywords, such
as $default and $dispvm. Due to a potential issue described in
Qubes Security Bulletin #38 (https://www.qubes-os.org/news/2018/02/20/qsb-38/),
we have been getting rid of $. (In brief, interaction between Bash
shell parameter expansion and $ characters in policy files could
theoretically lead to security problems.) For backward compatibility,
$ is still supported in policy files, but it is being internally
turned into @ before processing, and in the new policy format, we only
use @. In other words, $default in Qubes 4.0 will now be @default,
$dispvm turns into @dispvm, and so on. For example, to update all
TemplateVMs through sys-whonix, you would use:

qubes.UpdatesProxy * @type:TemplateVM @default allow target=sys-whonix


In all client tools, $ will still be automatically translated into
@, so you don’t have to change any existing noscripts. However, we
highly recommend using only @. Legacy support for $ will continue
throughout the Qubes 4.x series and end in Qubes 5.0.

Includes

The old format supported a simple $include directive. In Qubes 4.1,
the inclusion capabilities are extended, and we now have four different
kinds of includes. Due to the aforementioned QSB #38 change, the
keywords no longer start with $, but rather with an exclamation point
(!). The supported include directives are:

!include path_to_file — The simplest command. Includes the entire
contents of the file and parses it according to new policy syntax
rules. The file can contain policy rules for one or more services,
for one or more qubes.
!include-dir path_to_directory — Includes all .policy files
from the directory, parsing them according to new policy syntax
rules.
!include-service service argument path_to_file — Allows for the
inclusion of a policy in a format similar to the old one (without a
service or an argument) by filling in the missing service and
argument fields from the new format with parameters provided to
include-service. Either of those (or both) can be a wildcard (*),
as they can be in all new policy files. (This might seem like a
directive useful only for backward compatibility, but it also has
uses in the Admin API policies used for implementing GUI domains,
among other things.)

!compat-4.0 — An explicit backward compatibility directive that
takes the old policy files from their old locations and converts them
internally (using include-service) to be a part of the new policy.
Backward compatibility

One of the new policy files is 35-compat.policy. It loads the old
policy files and parses them in a way compatible with the new policy
format.

Before the old policy format is completely phased out in Qubes 5.0, we
will provide a conversion tool. (This tool may not be available in Qubes
4.1 on release.) Since there will be legacy support for the old policy
format with 35-compat.policy and the !compat-4.0 include directive,
it is not necessary for users to update their current custom policies
for Qubes 4.1.

Performance improvements

In Qubes 4.1, the max qrexec data chunk size has been increased from 4kB
to 64kB. This makes large data transfers significantly faster, for
example, copying big files or streaming video through qvm-usb from
sys-usb to a qube with an ongoing video call. (Details can be found
here (https://github.com/QubesOS/qubes-issues/issues/4909).)

We have also significantly increased the maximum service and argument
length. In Qubes 4.0, it was just 63 characters for the combined
service+arguments. Now, it is 65,000 characters (a bit less than 64kB,
due to an internal header). The main reason for this change — apart
from sheer convenience — is the qubes.VMShell service. It’s an
extremely dangerous service that gives complete shell access.
Unsurprisingly, it’s not allowed by default. In Qubes 4.0,
qubes.VMShell just provides a shell stdin/stdout, so handling it with
a single command was extremely cumbersome and often required a
prodigious number of quotation marks. Even worse, the command was not
stored in any log file, and qrexec policy did not control what commands
could be executed, opening up a big, unauditable, dangerous space for
exploitation. By increasing the service+argument length (and governing
the argument under qrexec policy, as described above), we are able to
introduce a new, more accountable, safer service. In Qubes 4.1, this new
service is called qubes.VMExec, and the complete command to be
executed, along with its arguments, is logged. This allows for precise
control, as the policy can allow only certain commands, not everything
that can be executed in a shell. Moreover, all the arguments are
explicitly defined and unambiguous, freeing the user from quotation mark
purgatory. (The syntax is described
here (https://www.qubes-os.org/doc/vm-interface/#qubes-rpc).) Other
services will also benefit, such as the U2F implementation that, due to
previous limitations, required some awkward wrangling of the public key
hash. (Details can be found
here (https://github.com/QubesOS/qubes-issues/issues/4850).)

There are also some minor improvements and streamlining coming up: for
example, a new call that allows access to all qube properties at once,
which allows qvm-ls (and similar tools) to work significantly faster.
Instead of making around five Admin API calls per qube, qvm-ls will
now only make one, leading to a five-fold speed increase.

Policy daemon

In Qubes 4.0, performing a qrexec call (with all its assorted policy
checking) was a fairly slow process. Even in the best case (simple
allow, no asking user for input), it consisted of several processes:
loading the whole policy again, loading Python modules required to parse
it, executing the call itself…. The setup alone took about 300 ms (for
a typical system). In the case of a lone operation, such as copying a
file, it’s hardly a problem, but for frequent operations it could be a
disaster. Tunneling a TCP connection via qrexec (the qubes.ConnectTCP
service) would mean a 300 ms lag for establishing the connection — a
complete nightmare for the server! Qubes Clipboard, which also uses
qrexec and is managed by a policy (which allows for blocking copy or
paste for certain qubes), needed 300 ms for each operation, which can be

a bit of a problem for particularly fast typists. The biggest problem
was, however, the Admin API. The whole idea of an Admin API (read more
here (https://www.qubes-os.org/news/2017/06/27/qubes-admin-api/))
requires a lot of qrexec calls. If we want to implement a GUI domain
that manages certain parts of the system instead of having the user
directly access dom0, we need the Admin API to be much, much faster. For
example, without the changes outlined below, starting the Qube Manager
on a default, out-of-the-box Qubes installation with a GUI domain took
37 seconds. This is just unacceptable.

To speed up qrexec calls, Qubes 4.1 introduces a policy daemon. It is a
process that loads the policy into memory and keeps it there (only
reloading when the policy files change), answering qrexec queries about
whether a given operation should be accepted or denied without spawning
new processes or loading more files and Python modules. The results are
quite satisfying. Starting the Qube Manager in a default Qubes
installation with a GUI domain takes less than 5 seconds — a more than
seven-fold improvement.

Socket services

Another problematic bottleneck for qrexec was that each service was a
new process. In many cases, this process just connects to an existing
service. A particularly egregious example is the Admin API. An Admin API
call is just a connection to dom0’s qubesd daemon, but in Qubes 4.0 each
of its calls was a separate process, going through a bunch of shell
noscripts to return a simple chunk of data. For a program like qvm-ls,
which has to access a lot of data from the Admin API, it was a
performance nightmare.

A qrexec service is a file residing in /etc/qubes-rpc/. In Qubes 4.0,
it has to be an executable or a symlink to one. In Qubes 4.1, however,
it can also be a symlink to a unix socket. Via this socket, you can
simply connect to an existing process that will handle your call. With
each socket connection, this running service receives a new connection
with a metadata header (containing information on who wants to do what
and where, a service name just in case, and a terminating 0 byte)
followed by the same client data as before. Thus, even though it’s a
single process that handles multiple calls, it knows where each call
came from and what it asked for.

Performance gains on both speed and memory benchmarks are significant.
For example, we have an icon rendering service, which is responsible for
making sure each of your program icons bears the color of its qube. In
Qubes 4.0, each invocation of this service was a separate per-qube
processes in dom0, each one loading Gtk and other libraries for about
32MB of RAM. In Qubes 4.1, this has been converted into a
single-process, socket-based service. Now, ten running qubes need only
this one socket-based service process, for a single instance of 32MB RAM
usage, instead of ten times that in Qubes 4.0. The Admin API also uses a
socket service, which — combined with the policy daemon described
above — dropped call execution time from 300 ms to about 50 ms.

More information about socket services can be found
here (https://github.com/QubesOS/qubes-issues/issues/3912).

Notifications

Creating a qrexec policy daemon opened another convenient opportunity:
adding notifications for some policy actions. By default, notifications
are shown only when a deny occurs, unless it was due to an ask
action. (If the user was already asked for consent, it is not necessary
to show the notification.) However, the new policy format allows for an
optional notify=no parameter with deny rules. Allow rules support
a notify=yes parameter that will show a notification on accepted
qrexec calls.

For example, this rule will cause notifications to be shown whenever a
qubes.VMExec service call is made from the work qube to the
personal qube:

qubes.VMExec * work personal allow notify=yes


And the above screenshot could be accomplished with:

qubes.Gpg * work work-gpg allow notify=yes
qubes.Filecopy * untrusted * deny


Notifications alert the user that something unexpected might have
happened. They can signal a misconfigured policy (when calls are denied
while the user would prefer them to be allowed) or a misbehaving or
malicious qube (when unexpected calls are being made and denied due to a
correctly configured policy).

The introduction of GUI domains makes the subject of qrexec
notifications a bit more complex. Since there can be more than one GUI
domain, which one should receive notifications? For now, we’ve decided
that the GUI domain serving the source qube (the one making the call)
will show notifications. There are some conceivable setups in which a
different GUI domain would show notifications. While such setups will
not be supported in Qubes 4.1, they may appear in future versions.

More information about notifications can be found
here (https://github.com/QubesOS/qubes-issues/issues/3904).

Policy API (in development)

As we mentioned above, one of our big development goals is separating
the user from the most vulnerable part of the system: dom0. Doing so
improves compartmentalization and security while lowering both the
attack surface and the chance of accidentally committing a compromising
mistake.

In order to completely isolate dom0, however, we would have to provide
qrexec interfaces for everything that the user may need to access and
configure — including the qrexec policy itself. At the moment, we are
working on a broad Policy API that allows for editing the whole policy.
The Policy API will also enforce the correctness of any policy changes,
preventing users from making syntactically invalid policy changes.

We also have some ideas for implementing limited access, for example,
having a deprivileged user who is limited to modifying certain services
or controlling access to certain qubes. The design for this is not yet
final. In its current state, we are thinking about supporting two kinds
of roles: an API administrator with total access, and an operator with
access to only a well-defined subset of the policy. The implementation
of any such ideas will definitely not be a part of Qubes 4.1.

Current work on the Policy API design draft and a proof of concept can
be found here (https://github.com/QubesOS/qubes-policy-control).

Fedora 32 TemplateVMs available
https://www.qubes-os.org/news/2020/06/30/fedora-32-templates-available/

New Fedora 32 TemplateVMs are now available for both Qubes 4.0 and 4.1.

Important: If you wish to use the Qubes Update widget to update a
Fedora 32 template, you must first switch (https://www.qubes-os.org/doc/templates/#switching) the
default-mgmt-dvm qube to a Fedora 32 template. (Alternatively, you
can create a separate management DisposableVM Template based on a
Fedora 32 template for the purpose of updating Fedora 32 templates.)
This does not affect updating internally using dnf.

Instructions are available for upgrading Fedora TemplateVMs (https://www.qubes-os.org/doc/template/fedora/upgrade/). We also
provide fresh Fedora 32 TemplateVM packages through the official Qubes
repositories, which you can get with the following commands (in dom0).

Standard (https://www.qubes-os.org/doc/templates/fedora/) Fedora 32 TemplateVM:

$ sudo qubes-dom0-update qubes-template-fedora-32


Minimal (https://www.qubes-os.org/doc/templates/minimal/) Fedora 32 TemplateVM:

$ sudo qubes-dom0-update qubes-template-fedora-32-minimal


After installing or upgrading a TemplateVM, please remember to update (https://www.qubes-os.org/doc/software-update-domu/)
(see important note above) and switch all qubes that were using the
old template to use the new one (https://www.qubes-os.org/doc/templates/#switching).

QSB #058: Insufficient cache write-back under VT-d (XSA-321)
https://www.qubes-os.org/news/2020/07/07/qsb-058/

We have just published Qubes Security Bulletin (QSB) #058:
Insufficient cache write-back under VT-d (XSA-321).
The text of this QSB is reproduced below. This QSB and its accompanying
signatures will always be available in the Qubes Security Pack (qubes-secpack).

View QSB #058 in the qubes-secpack:

https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-058-2020.txt

Learn about the qubes-secpack, including how to obtain, verify, and read it:

https://www.qubes-os.org/security/pack/

View all past QSBs:

https://www.qubes-os.org/security/bulletins/

View XSA-321 in the XSA Tracker:

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



---===[ Qubes Security Bulletin #58 ]===---

2020-07-07


Insufficient cache write-back under VT-d (XSA-321)


Summary
========

On 2020-07-07, the Xen Security Team published Xen Security Advisory
321 (CVE-2020-15565 / XSA-321) [1] with the following denoscription:

| When page tables are shared between IOMMU and CPU, changes to them
| require flushing of both TLBs. Furthermore, IOMMUs may be non-coherent,
| and hence prior to flushing IOMMU TLBs CPU cached also needs writing
| back to memory after changes were made. Such writing back of cached
| data was missing in particular when splitting large page mappings into
| smaller granularity ones.
|
| A malicious guest may be able to retain read/write DMA access to
| frames returned to Xen's free pool, and later reused for another
| purpose. Host crashes (leading to a Denial of Service) and privilege
| escalation cannot be ruled out.

A malicious HVM qube with a PCI device (such as sys-net or sys-usb in
Qubes' default configuration) can potentially compromise the whole
system.

Only Intel systems are affected. AMD systems are not affected.


Patching
=========

The specific packages that resolve the problems discussed in this
bulletin are as follows:

For Qubes 4.0:
- Xen packages, version 4.8.5-19

The packages are to be installed in dom0 via the Qube Manager or via
the qubes-dom0-update command as follows:

For updates from the stable repository (not immediately available):
$ sudo qubes-dom0-update

For updates from the security-testing repository:
$ sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing

A system restart will be required afterwards.

These packages will migrate from the security-testing repository to the
current (stable) repository over the next two weeks after being tested
by the community.

If you use Anti Evil Maid, you will need to reseal your secret
passphrase to new PCR values, as PCR18+19 will change due to the new
Xen binaries.


Credits
========

See the original Xen Security Advisory.


References
===========

[1] https://xenbits.xen.org/xsa/advisory-321.html

--
The Qubes Security Team
https://www.qubes-os.org/security/

XSAs 317, 319, 327, and 328 do not affect the security of Qubes OS
https://www.qubes-os.org/news/2020/07/07/xsa-317-319-327-328-qubes-not-affected/

The Xen Project has published Xen Security Advisories 317, 319, 327, and
328 (XSA-317, XSA-319, XSA-327, and XSA-328, respectively). These
XSAs do not affect the security of Qubes OS, and no user action is
necessary.

These XSAs have been added to the XSA Tracker (https://www.qubes-os.org/security/xsa/):

https://www.qubes-os.org/security/xsa/#317
https://www.qubes-os.org/security/xsa/#319
https://www.qubes-os.org/security/xsa/#327
https://www.qubes-os.org/security/xsa/#328

XSA-329 does not affect the security of Qubes OS
https://www.qubes-os.org/news/2020/07/16/xsa-329-qubes-not-affected/

The Xen Project has published Xen Security Advisory 329 (XSA-329). This
XSA does not affect the security of Qubes OS, and no user action is
necessary.

This XSA has been added to the XSA Tracker (https://www.qubes-os.org/security/xsa/):

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

Xen Project Hypervisor Version 4.14 brings added security and performance
https://xenproject.org/2020/07/24/xen-project-hypervisor-version-4-14-brings-added-security-and-performance/

New version introduces Linux stubdomains and robust live patching to build on security features. SAN FRANCISCO – July 24, 2020 — The Xen Project, an open source hypervisor hosted at...

HVMI becomes A Xen Project Incubating Project
https://xenproject.org/2020/07/30/hvmi-becomes-a-xen-project-incubating-project/

Today, the Xen Project is thrilled to welcome Hypervisor-based Memory Introspection (HVMI) as an incubating project!  Contributed by Bitdefender, a leading global cybersecurity company protecting over 500 million systems worldwide...

New community forum for Qubes OS users!
https://www.qubes-os.org/news/2020/08/20/new-community-forum-for-qubes-os-users/

We’re pleased to announce the launch of a new forum for Qubes OS users:
https://qubes-os.discourse.group (https://qubes-os.discourse.group/)

This is an official user forum where you can ask questions, get help,
share tips and experiences, and more! For a long time, members of our
community have sought a privacy-respecting forum experience with modern
features that traditional mailing lists do not support. The open-source
Discourse (https://www.discourse.org/) platform fills this need for us, as it does for many other
open-source projects. Thanks to their generous free hosting for open
source projects (https://blog.discourse.org/2018/11/free-hosting-for-open-source-v2/), we’re pleased to be able to create this space for our
community.

Why create a forum now?

Previously, the only option for a forum-like experience was to interact
with our mailing lists via Google Groups, but we understand all too well
that the privacy implications and user experience were unacceptable for
many members of our community, especially with the recent addition of a
sign-in requirement to view threads. Many of you value the lower barrier
to entry, organization, ease-of-use, and modern social features that
today’s forums support. Moreover, Discourse features email integration
for those who still prefer the traditional mailing list format.

How is this different from our mailing lists?

To be clear, this is not a replacement for our mailing lists (https://www.qubes-os.org/support/#mailing-lists) (such
as qubes-users and qubes-devel), which will continue on as they are.
This new forum is simply an additional place for discussion. Certain
types of discussions naturally lend themselves more to mailing lists or
to forums, and different types of users prefer different venues. We’ve
heard from some users who find the mailing lists to be a bit
intimidating or who may feel that their message isn’t important enough
to merit creating a new email that lands in thousands of inboxes. Others
want more selective control over topic notifications. Some users simply
appreciate the ability to add a “reaction” to a message instead of
having to add an entirely new reply. Whatever your reasons, it’s up to
you to decide where and how you want to join the conversation.

Will this split the community?

Many open-source projects (such as Fedora and Debian) have both mailing
lists and forums (and additional discussion venues). In fact, Qubes
already has non-mailing-list discussion venues such as IRC (https://www.qubes-os.org/support/#unofficial-chat-channels) and
Reddit (https://www.reddit.com/r/Qubes/). We believe that this additional venue will foster the
continued growth of community participation and improve everyone’s
experience. In addition, we fully expect that many community members –
especially the most active ones – will choose to participate in both
venues. (Again, for those who still prefer interacting via email,
Discourse supports that too!)

Special thanks to Michael Carbone for spearheading the creation of this
forum and to deeplow who, as our first forum administrator, has done
much of the legwork to help get it looking good and working well!