From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Christopher Baines <mail@cbaines.net>,
36634@debbugs.gnu.org, Chris Marusich <cmmarusich@gmail.com>
Subject: bug#36634: Virtual Machine Manager (virt-manager)
Date: Mon, 23 Sep 2019 06:30:14 +0200 [thread overview]
Message-ID: <87y2yf1vop.fsf@nckx> (raw)
In-Reply-To: <87wodzir88.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Chrisen,
Chris Marusich 写道：
> In the meantime, should we revert to version 5.4.0 in Guix? I'm
> not
> sure if there are any security vulnerabilities between 5.4.0 and
> the
> most recent release, but this bug is currently preventing me
> from
> creating any VMs at all in Guix using virt-manager, which is
> pretty bad.
Yes! (which is why I originally updated this package):
v5.5.0 (2019-07-02)
Security
api: Prevent access to several APIs over read-only
connections
Certain APIs give root-equivalent access to the host,
and as
such should be limited to privileged
users. CVE-2019-10161,
CVE-2019-10166, CVE-2019-10167, CVE-2019-10168.
https://libvirt.org/news.html
It might be easy to backport. I didn't try, and I no longer use
libvirt myself.
What's weird (maybe; I haven't kept up with the thread) is that I
used libvirt 5.5.0 (and yes, it was 5.5.0) for a while without
problems. I don't remember whether I created any *new* VMs,
though.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-09-23 4:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 5:06 bug#36634: Virtual Machine Manager (virt-manager) Raghav Gururajan
2019-07-14 12:42 ` Efraim Flashner
2019-07-14 21:21 ` Raghav Gururajan
2019-07-21 17:23 ` Christopher Baines
2019-07-21 21:42 ` Raghav Gururajan
2019-09-23 4:14 ` Chris Marusich
2019-09-23 4:30 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2019-10-05 5:41 ` Chris Marusich
2019-10-10 8:55 ` Chris Marusich
2019-07-25 9:46 ` bug#36634: ATTENTION REQUIRED Raghav Gururajan
2019-07-25 19:36 ` Tobias Geerinckx-Rice
2019-07-25 20:01 ` Tobias Geerinckx-Rice
2019-07-26 3:51 ` bug#36634: Raghav Gururajan
2019-07-26 3:47 ` bug#36634: Raghav Gururajan
2019-09-08 18:14 ` bug#36634: Virtual Machine Manager (virt-manager) Christopher Baines
2019-10-21 14:46 ` Miguel Arruga Vivas
2019-10-27 9:37 ` Miguel Arruga Vivas
2019-11-07 8:44 ` Chris Marusich
2019-11-08 0:53 ` Miguel Arruga Vivas
2020-03-19 10:06 ` bug#36634: (no subject) Brice Waegeneire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2yf1vop.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=36634@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
--cc=mail@cbaines.net \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).