From: Gerd Hoffmann <kraxel@redhat.com>
To: bancfc@openmailbox.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU soundcards vulnerable to jack retasking?
Date: Mon, 28 Nov 2016 11:30:14 +0100 [thread overview]
Message-ID: <1480329014.20061.57.camel@redhat.com> (raw)
In-Reply-To: <290015b23a9ec5033ee65209882dcbc0@openmailbox.org>
On Fr, 2016-11-25 at 21:25 +0100, bancfc@openmailbox.org wrote:
> Recent security research shows that soundcards support surreptitiously
> switching line-out jacks into line-in by modifying the software stack.
> The way modern speakers and headphones are designed makes them readily
> usable as microphones. The Intel High Definition (HD) Audio standards
> which all modern consumer soundcards are based mandates this stupidity.
>
> https://arxiv.org/ftp/arxiv/papers/1611/1611.07350.pdf
>
> Does anyone know if QEMU's emulated sound devices follow this standard?
No. Output line is output only and input line is input only, period.
There are three qemu hda codecs available:
hda-output
only playback (line-out). No way the guest can record anything.
hda-duplex
record (line-in) and playback (line-out). Use that if you need
sound recording in the guest.
hda-micro
record (micro) and playback (speaker). Same as hda-duplex, except
that the record and playback channels are tagged differently. Use
that if your guests app is picky and refuses to record from line-in.
Where the data for the record channel comes from is subject to host
configuration. On a typical linux system it'll probably being
pulseaudio, either directly or indirectly (via spice).
cheers,
Gerd
prev parent reply other threads:[~2016-11-28 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 20:25 [Qemu-devel] QEMU soundcards vulnerable to jack retasking? bancfc
2016-11-28 10:19 ` Dr. David Alan Gilbert
2016-11-28 10:38 ` Daniel P. Berrange
2016-11-28 10:30 ` Gerd Hoffmann [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=1480329014.20061.57.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=bancfc@openmailbox.org \
--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).