Re: [qubes-devel] Fedora-26 KDE GUI-actions via service menus broken (fix)

2018-01-07 Thread HawKing 

On Mon, 8 Jan 2018 01:04:14 +0100
Marek Marczykowski-Górecki  wrote:

> I assume this is about Qubes 4, right? Those scripts in 3.2 works...


They were not working on a freshly pulled/installed (not upgraded)
fedora-26 template on 3.2. They did work just fine on F24/25 with
Qubes 3.2. I have not tested at all on 4. 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/9EBB50FA-31E8-4668-9C5F-69275F59D554%40mail.bitmessage.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] Fedora-26 KDE GUI-actions via service menus broken (fix)

2018-01-07 Thread Marek Marczykowski-Górecki 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jan 07, 2018 at 04:51:50PM -0600, hawk...@bitmessage.ch wrote:
> The KDE/dolphin/Konqueror file-move actions are now missing and broken
> in a default Fedora 26 template. They don't show up in Dolphin unless
> put here:
> 
> sudo
> cp /usr/share/kde4/services/qvm-* /usr/share/kservices5/ServiceMenus/
> 
> and the KDE bash scripts are also broken, such that in the following
> scripts

I assume this is about Qubes 4, right? Those scripts in 3.2 works...

> qvm-copy.desktop 
> qvm-move.desktop 
> 
> changing the instance of:
> 
> Exec=/usr/lib/qubes/qvm-copy-to-vm.kde %U
> 
> to 
> 
> Exec=/usr/lib/qubes/qvm-copy-to-vm.gnome %U
> 
> seems to fix the issue for Dolphin and Konqueror.

Thanks, created an issue here:
https://github.com/QubesOS/qubes-issues/issues/3449

> I can't seem to get these to show up in the Krusader action menu
> though... Any ideas?

No idea...

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

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpStX4ACgkQ24/THMrX
1ywK+gf9H5/pFOfXB68oGg0ypc25ab+dKU9aT5MrCG9PXfX8P5G1RhkD5xM7T9AY
aIdN5Klsf5KFhJj2Tn9h52WlMKJJ4jJSD2WA7PN/FnzpbSK2J4Vm6LvJs+9aajys
51ser+/j/szLPh7fGuj6enhYeIPhfQ4FsMqdttHQO5fymVPvDDwU9wQKf9GExfdo
M7ABMDt3OkDhch4TV1lQQyOhpuLfqolmMDEYpPMW6cuDZqjlTL/p2I8H8MMz3s8t
cJN8kanyVhuVGtIJ2tJtLcNUl24SETFuqQuMceYYrMftfp4KVBkmNr0+6Tv5OMKi
Emu+7EfgU5+Sxc4LRM5DhjgI9dS28A==
=R3Yk
-END PGP SIGNATURE-

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

[qubes-devel] Fedora-26 KDE GUI-actions via service menus broken (fix)

2018-01-07 Thread HawKing 
The KDE/dolphin/Konqueror file-move actions are now missing and broken
in a default Fedora 26 template. They don't show up in Dolphin unless
put here:

sudo
cp /usr/share/kde4/services/qvm-* /usr/share/kservices5/ServiceMenus/

and the KDE bash scripts are also broken, such that in the following
scripts

qvm-copy.desktop 
qvm-move.desktop 

changing the instance of:

Exec=/usr/lib/qubes/qvm-copy-to-vm.kde %U

to 

Exec=/usr/lib/qubes/qvm-copy-to-vm.gnome %U

seems to fix the issue for Dolphin and Konqueror.

I can't seem to get these to show up in the Krusader action menu
though... Any ideas?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/2B90FCCD-ED91-4BFA-B275-136117F40432%40mail.bitmessage.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Peter Todd 
On Sun, Jan 07, 2018 at 02:48:29PM -0600, Andrew David Wong wrote:
> This is a known issue:
> 
> https://github.com/QubesOS/qubes-issues/issues/3442
> 
> You can simply use `--best --allow-erasing`.

Thanks! That worked.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

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


signature.asc
Description: Digital signature

Re: [qubes-devel] Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Andrew David Wong 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-01-07 14:28, Peter Todd wrote:
> On Sat, Jan 06, 2018 at 06:15:21PM -0600, Andrew David Wong wrote:
>> Dear Qubes Community,
>>
>> Fedora 25 reached EOL ([end-of-life]) on 2017-12-12. We sincerely
>> apologize for our failure to provide timely notice of this event. It
>> is strongly recommend that all Qubes users upgrade their Fedora 25
>> TemplateVMs and StandaloneVMs to Fedora 26 immediately. We provide
>> step-by-step [upgrade instructions] for upgrading your existing
>> TemplateVMs and StandaloneVMs in-place on both Qubes 3.2 and Qubes
>> 4.0. For a complete list of TemplateVM versions supported for your
>> specific version of Qubes, see [Supported TemplateVM Versions].
>>
>> We also provide fresh Fedora 26 TemplateVM packages through the
>> official Qubes repositories, which you can get with the following
>> commands (in dom0).
>>
>> Standard Fedora 26 TemplateVM:
>>
>> $ sudo qubes-dom0-update qubes-template-fedora-26
> 
> This template seems to be broken out of the box. After installation, yum
> upgrade gives the following:
> 
> [user@fedora-26 ~]$ sudo yum upgrade
> Last metadata expiration check: 0:26:15 ago on Sun 07 Jan 2018 03:00:32 
> PM EST.
> Dependencies resolved.
> 
>  Problem 1: package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but 
> none of the providers can be installed
>   - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
> 1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
>   - package dnf-utils-2.1.1-1.fc26.noarch conflicts with yum-utils < 
> 1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
>   - cannot install the best update candidate for package 
> yum-utils-1.1.31-512.fc26.noarch
>   - cannot install the best update candidate for package 
> salt-2016.11.5-3.fc26.noarch
>  Problem 2: problem with installed package 
> yum-utils-1.1.31-512.fc26.noarch
>   - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
> 1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
>   - package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but none of 
> the providers can be installed
>   - package dnf-utils-2.1.1-1.fc26.noarch requires dnf-plugins-core = 
> 2.1.1-1.fc26, but none of the providers can be installed
>   - package salt-ssh-2017.7.2-1.fc26.noarch requires salt = 
> 2017.7.2-1.fc26, but none of the providers can be installed
>   - cannot install both dnf-plugins-core-2.1.1-1.fc26.noarch and 
> dnf-plugins-core-2.1.5-1.fc26.noarch
>   - cannot install the best update candidate for package 
> salt-ssh-2016.11.5-3.fc26.noarch
>   - cannot install the best update candidate for package 
> dnf-plugins-core-2.1.5-1.fc26.noarch
> 
> 
>  PackageArch VersionRepository
>  Size
> 
> 
> Skipping packages with conflicts:
> (add '--best --allowerasing' to command line to force their upgrade):
>  dnf-plugins-core   noarch   2.1.1-1.fc26   fedora
>  49 k
>  dnf-utils  noarch   2.1.1-1.fc26   fedora
>  39 k
>  dnf-utils  noarch   2.1.5-1.fc26   updates   
>  40 k
> Skipping packages with broken dependencies:
>  salt   noarch   2017.7.2-1.fc26updates   
> 7.8 M
>  salt-ssh   noarch   2017.7.2-1.fc26updates   
>  21 k
> 
> Transaction Summary
> 
> 
> Skip  5 Packages
> 
> Nothing to do.
> Complete!
> [user@fedora-26 ~]$ 
> 

This is a known issue:

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

You can simply use `--best --allow-erasing`.

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpSh5sACgkQ203TvDlQ
MDA/cxAAlpHOvQ055n+PN8JQoQy6mPuUN6lkV712E/bmGm/29RwEZV0QPU3Y2EdD
0GVqNC9hHz3VLzcPnXY0MfTDAeZEgASzTXsWFUNYxz1iTPnsSm13Nf6UTWXSMRkE
lz754rPrYaUXDNJSuw+O6Agyiek8Q4yYy+61rNFGoJrKNZ3cFUuTfedc1KtQXbl8
OtSWOnl4vqvntWHEibduB5F0Jvyaj0fafrzSiBUD1AIlwP1zfdkNjkbUc+0vMrIn
Rael/qWLxoMe9xckkYVYt1RAWDLgV8YCs8Ve5e9K1p67dGgynqu50QFrk3L9+C8l
EksfYwhYRI14TygBFG/guaMah4nHj4ho8qQvtB2vXYIT6WE0oTyfB3+twbs6U8hi
uxhPymZPfC9rzJPOYt9jqwY7hnZ/5bEh+lIJhLVW9bwYkoh8yZ2oofZFDEsq795e
NYCtcURE4G/Dm/A6YEDJcHDq0QYfvqaFFrBVi8XTNsbj1IlVz5RHDa2W4OWVUbHb
UFROOgxUVQFjH4rnVXzjFb+uhFEug+yILewcjPBWHCacgf16C4JhFBrfKVo11rtn
GIiOmwCEtJOo0toB2cJ6padcrcyp5FiukHL5eh/tZ3D2VPUqoqF5/Qo7cGiVeuJ9
9FKjr02qQmhT5HFCwZI5UkN7Q5X6FQtFjQzNlHN0CRA1yp7WszI=
=hIky
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel"

Re: [qubes-devel] Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Peter Todd 
On Sat, Jan 06, 2018 at 06:15:21PM -0600, Andrew David Wong wrote:
> Dear Qubes Community,
> 
> Fedora 25 reached EOL ([end-of-life]) on 2017-12-12. We sincerely
> apologize for our failure to provide timely notice of this event. It
> is strongly recommend that all Qubes users upgrade their Fedora 25
> TemplateVMs and StandaloneVMs to Fedora 26 immediately. We provide
> step-by-step [upgrade instructions] for upgrading your existing
> TemplateVMs and StandaloneVMs in-place on both Qubes 3.2 and Qubes
> 4.0. For a complete list of TemplateVM versions supported for your
> specific version of Qubes, see [Supported TemplateVM Versions].
> 
> We also provide fresh Fedora 26 TemplateVM packages through the
> official Qubes repositories, which you can get with the following
> commands (in dom0).
> 
> Standard Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26

This template seems to be broken out of the box. After installation, yum
upgrade gives the following:

[user@fedora-26 ~]$ sudo yum upgrade
Last metadata expiration check: 0:26:15 ago on Sun 07 Jan 2018 03:00:32 PM 
EST.
Dependencies resolved.

 Problem 1: package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but 
none of the providers can be installed
  - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
  - package dnf-utils-2.1.1-1.fc26.noarch conflicts with yum-utils < 
1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
  - cannot install the best update candidate for package 
yum-utils-1.1.31-512.fc26.noarch
  - cannot install the best update candidate for package 
salt-2016.11.5-3.fc26.noarch
 Problem 2: problem with installed package yum-utils-1.1.31-512.fc26.noarch
  - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
  - package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but none of the 
providers can be installed
  - package dnf-utils-2.1.1-1.fc26.noarch requires dnf-plugins-core = 
2.1.1-1.fc26, but none of the providers can be installed
  - package salt-ssh-2017.7.2-1.fc26.noarch requires salt = 
2017.7.2-1.fc26, but none of the providers can be installed
  - cannot install both dnf-plugins-core-2.1.1-1.fc26.noarch and 
dnf-plugins-core-2.1.5-1.fc26.noarch
  - cannot install the best update candidate for package 
salt-ssh-2016.11.5-3.fc26.noarch
  - cannot install the best update candidate for package 
dnf-plugins-core-2.1.5-1.fc26.noarch


 PackageArch VersionRepository 
Size


Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 dnf-plugins-core   noarch   2.1.1-1.fc26   fedora 
49 k
 dnf-utils  noarch   2.1.1-1.fc26   fedora 
39 k
 dnf-utils  noarch   2.1.5-1.fc26   updates
40 k
Skipping packages with broken dependencies:
 salt   noarch   2017.7.2-1.fc26updates   
7.8 M
 salt-ssh   noarch   2017.7.2-1.fc26updates
21 k

Transaction Summary


Skip  5 Packages

Nothing to do.
Complete!
[user@fedora-26 ~]$ 

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

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


signature.asc
Description: Digital signature

[qubes-devel] Re: Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Andrew David Wong 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-01-06 18:15, Andrew David Wong wrote:
> Dear Qubes Community,
> 
> Fedora 25 reached EOL ([end-of-life]) on 2017-12-12. We sincerely
> apologize for our failure to provide timely notice of this event. It
> is strongly recommend that all Qubes users upgrade their Fedora 25
> TemplateVMs and StandaloneVMs to Fedora 26 immediately. We provide
> step-by-step [upgrade instructions] for upgrading your existing
> TemplateVMs and StandaloneVMs in-place on both Qubes 3.2 and Qubes
> 4.0. For a complete list of TemplateVM versions supported for your
> specific version of Qubes, see [Supported TemplateVM Versions].
> 
> We also provide fresh Fedora 26 TemplateVM packages through the
> official Qubes repositories, which you can get with the following
> commands (in dom0).
> 
> Standard Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26
> 
> [Minimal] Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26-minimal
> 
> After upgrading to a Fedora 26 TemplateVM, please remember to set all
> qubes that were using the old template to use the new one. The
> instructions to do this can be found in the [upgrade instructions]
> for your specific version.
> 
> Please note that no user action is required regarding the OS version
> in dom0. If you're using Qubes 3.2 or 4.0, there is no dom0 OS
> upgrade available, since none is currently required. For details,
> please see our [Note on dom0 and EOL].
> 
> If you're using an older version of Qubes than 3.2, we strongly
> recommend that you upgrade to 3.2, as older versions are no longer
> supported.
> 
> 
> [end-of-life]: 
> https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule

Here are the reference links with complete URLs:

[upgrade instructions]: 
https://www.qubes-os.org/doc/template/fedora/upgrade-25-to-26/
[Supported TemplateVM Versions]: 
https://www.qubes-os.org/doc/supported-versions/#templatevms
[Minimal]: https://www.qubes-os.org/doc/templates/fedora-minimal/
[Note on dom0 and EOL]: 
https://www.qubes-os.org/doc/supported-versions/#note-on-dom0-and-eol

> 
> This announcement is also available on the Qubes website:
> https://www.qubes-os.org/news/2018/01/06/fedora-26-upgrade/
> 

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpSgbUACgkQ203TvDlQ
MDDuehAAr4D9wYq8Z+YeCPrOtQUMsHrW20cHCVd1Vxint2fSh2BlwvwElhVr8XKb
UYpnGNNwIZNIVL/PzLJzAXgtyu7tmHOHWqP9jV6d/YzJ+vcCH69X2WG3k9uclNJc
RorgK7YbHOq/LSZfyDgYoNnPfhfywcf9nVuFvaYvlFwwBC6njK0PAhvr16hbbEF+
U7jXIspcqr5THcVS5jYpl7r4fnXtC3UB5PlwlN33G65C7kc7SaDl03G1R/loJNkJ
PSTV9vba7R16e7rfGaN0VVu42xrj4XG+eqU3/RGaTyZxHKdexOsNrjuQouv+AinM
M4JklLQTYpgcClvwMkkgYklr4RPlhg9gJXYeLdArxRNAedCufgc+mUwS3qeBbPeo
tIhh46w3feZr1q0OG2O0s4IejZiq6Eqt8WdZfOVuyhtbEMSJR/iMEkjRgUgZx3A3
g1p5XEh2ofZ7HAYbsJGXKWAwDqgrVpjqtPYULaVMtmOl+q1g2+6vSUD8sJI0VRwE
U/ieNm+pKUd7bYyFaicMaskFT1yZHsArmrVoAAkBTwpM+MWTu4CntMAuXLp+sH/0
iLJgP1yvJEsgOzZcYr2urCqmZEMu892Q42f5Xyvw0sRFaL/GWpsyoNC9L9Fu583F
2ogsn68cc90N5IhOQ0OOA/HmZW3pS1qsvZ5Sy+I1fYlRgab471Q=
=wCzE
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/6d3e3b1e-067e-fbe7-7a49-c829b6303621%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-devel] Qubes 4.0 rc4 delay because of Meltdown and Spectre attacks

2018-01-07 Thread Marek Marczykowski-Górecki 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Jan 05, 2018 at 12:14:43PM +, Marco Giglio wrote:
> By reading that advisory and information posted here (
> https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/),
> it seems that there are 2 possible short-term mitigations against
> Meltdown for QubesOS 3.2 users.
> -  Move PV VMs to HVM.

This option require VT-x support in the hardware. Something that wasn't
required by 3.2 before.

> -  Move PV VMs to use 32-bit kernels. It should prevent to use
> Meltdown/SP3 against the hypervisor, but it won't prevent it against the
> kernel itself.  Then update when newer 32-bit kernel with KPIT are
> available.

This option require replacing both VM kernel _and_ templates. Especially
painful for heavily customized templates.

> Qubes 4 users shouldn't be affected by SP3/Meltdown, but should be
> affected from SP1/SP2/Spectre.

Yes, that's correct.

We're still evaluating available options. For example there are three
alternative workarounds for SP3 developed in parallel on xen-devel, each
having own good and bad sides. And patches to mitigate SP1/SP2 are also
not ready yet.

For this reason, we're delaying Qubes OS rc4 (originally scheduled to be
released tomorrow), until we come up with final plan what to do about
those hardware issues.

> On 01/04/2018 10:53 PM, Chris Drake wrote:
> > It is very clear: https://xenbits.xen.org/xsa/advisory-254.html
> >
> > IMPACT
> > ==
> >
> > Xen guests may be able to infer the contents of arbitrary host memory,
> > including memory assigned to other guests.
> >
> > VULNERABLE SYSTEMS
> > ==
> >
> > Systems running all versions of Xen are affected.
> >
> > MITIGATION
> > ==
> >
> > There is no mitigation for SP1 and SP2.
> >
> > RESOLUTION
> > ==
> >
> > There is no available resolution for SP1 or SP3.
> >
> >
> > For those unaware - this is a hardware fault.  CPUs make use of speculative 
> > execution (Spectre) or Pipelines (Meltdown) - both of which can be used to 
> > attempt to access illegal memory.  The access fails, however, it's possible 
> > to use the "stolen" memory before the access-fail is enforced in a way that 
> > makes it available on a side-channel (cache in these exploits, but could be 
> > anything else like ports/dma) to any non-privileged process.
> >
> 

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

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpSZD0ACgkQ24/THMrX
1yyK9Qf/T5jG7zHPjwCmF4ztD2FRJoo0qJzWmtjgNz67V+tK1K/hQsTph3CMor5N
UCKSKqSXxRZVjTfgv4CW4SJqUfDk++aIs/lvdsAABOt25LU2nVOy9BwPSWVYZDs7
KqsERFSAaorNEzq0CftHVIDyvzOOtWRD/eGL4P5TlfTvCvv2HN2/Br9esItxF3CM
vzT/qGCnNpkhn9TIlVxK/JTeZ9t/krC1Z2/vaiU5h+noxv6LFvL4pZ5zILjNgcGu
BeeqymA1VrWijoRA2W+qdI3s3moCOQfWNvXxYujc/sAr/axVjqfdC4+qsL2h4pH2
OykhrEfRubAVSqyW4c/vYunT7ARY7A==
=00Sg
-END PGP SIGNATURE-

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