From: Thomas Huth <676934@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 676934] Re: Ability to use -net socket with unix sockets
Date: Thu, 17 Jun 2021 07:38:28 -0000 [thread overview]
Message-ID: <162391550829.13571.1865475702478122249.malone@wampee.canonical.com> (raw)
In-Reply-To: 20101118110340.18016.73281.malonedeb@palladium.canonical.com
*** This bug is a duplicate of bug 1903470 ***
https://bugs.launchpad.net/bugs/1903470
This is an automated cleanup. This bug report got closed because it
is a duplicate.
** Changed in: qemu
Importance: Wishlist => Undecided
** Changed in: qemu
Status: New => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/676934
Title:
Ability to use -net socket with unix sockets
Status in QEMU:
Expired
Bug description:
It would be a nice feature (simplifying access control for example) to
be able to do something like:
qemu -net socket,listen=unix:/tmp/qemunet
qemu -net socket,connect=unix:/tmp/qemunet
For now one has to use TCP connections even for guests running on the
same host, which involves setting up iptables to restrict access.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/676934/+subscriptions
prev parent reply other threads:[~2021-06-17 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 11:03 [Qemu-devel] [Bug 676934] [NEW] Ability to use -net socket with unix sockets Tefnet Developers
2017-01-10 9:17 ` [Qemu-devel] [Bug 676934] " Thomas Huth
2019-05-17 14:07 ` Alex Bennée
2019-05-17 14:30 ` Daniel Berrange
2020-11-18 10:33 ` Thomas Huth
2021-06-17 7:38 ` Thomas Huth [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162391550829.13571.1865475702478122249.malone@wampee.canonical.com \
--to=676934@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.