From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: David Vossel <dvossel@redhat.com>
Cc: qemu-devel@nongnu.org, Michal Privoznik <mprivozn@redhat.com>,
Fabian Deutsch <fdeutsch@redhat.com>
Subject: Re: guest agent public ssh key add/remove support?
Date: Wed, 19 Aug 2020 16:17:30 +0200 [thread overview]
Message-ID: <63919092.VjiBKyA9Op@silver> (raw)
In-Reply-To: <CAPjOJFsr2_0Kdp03jbSUZ2vpde41uHrS6ki_Wax4pZ-d8RTDvQ@mail.gmail.com>
On Mittwoch, 19. August 2020 15:49:50 CEST David Vossel wrote:
> > There are two pass-through file systems in QEMU: 9pfs and virtiofs. Don't
> > you
> > think they would be sufficient for the use case?
>
> probably not entirely.
>
> Understand this isn't an either/or scenario. Our api has been designed to
> support multiple "propagation" methods for the ssh keys. We've converged on
> the qemu guest agent for some other features and the agent appears to have
> the potential to provide us the greatest flexibility when it comes to how
> we want this pub ssh key use case to work. This isn't to say something
> like virtiofs won't make sense either in certain scenarios, but for the
> purposes of this discussion we're hoping to explore how the qemu guest
> agent could be used.
>
> I don't want to go too deep into the shared filesystem approach. I'll
> provide some context on the challenges there though.
Expected response, but I could not resist. ;-)
> - virtiofs requires guest kernel >= 5.4. We aren't considering 9p due to
> security/performance concerns.
Hey, there had been no security issue for quite a while with 9pfs. :)
And I am working on the performance issues actually.
Best regards,
Christian Schoenebeck
prev parent reply other threads:[~2020-08-19 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 13:25 guest agent public ssh key add/remove support? David Vossel
2020-08-18 18:35 ` Christian Schoenebeck
2020-08-19 13:49 ` David Vossel
2020-08-19 14:17 ` Christian Schoenebeck [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=63919092.VjiBKyA9Op@silver \
--to=qemu_oss@crudebyte.com \
--cc=dvossel@redhat.com \
--cc=fdeutsch@redhat.com \
--cc=mprivozn@redhat.com \
--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 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 NNTP newsgroup(s).