From: Paul Moore <pmoore@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>,
Roman Drahtmueller <draht@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] vnc: disable VNC password authentication (security type 2) when in FIPS mode
Date: Thu, 03 May 2012 16:54:48 -0400 [thread overview]
Message-ID: <4548305.DtX99stsJu@sifl> (raw)
In-Reply-To: <07DE940E-13C2-47D9-86C7-AA5FD8346C86@suse.de>
On Thursday, May 03, 2012 04:54:42 PM Alexander Graf wrote:
> On 02.05.2012, at 21:32, Paul Moore wrote:
> > FIPS 140-2 requires disabling certain ciphers, including DES, which is
> > used
> > by VNC to obscure passwords when they are sent over the network. The
> > solution for FIPS users is to disable the use of VNC password auth when
> > the
> > host system is operating in FIPS mode.
> >
> > This patch causes qemu to emit a syslog entry indicating that VNC password
> > auth is disabled when it detects the host is running in FIPS mode, and
> > unless a VNC password was specified on the command line it continues
> > normally. However, if a VNC password was given on the command line, qemu
> > fails with an error message to stderr explaining that VNC password auth is
> > not allowed in FIPS mode.
>
> I just talked to Roman about this one and he had some comments :)
I'm sure he did :)
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2012-05-03 20:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 19:32 [Qemu-devel] [PATCH v2] vnc: disable VNC password authentication (security type 2) when in FIPS mode Paul Moore
2012-05-03 8:29 ` Daniel P. Berrange
2012-05-03 8:51 ` Alexander Graf
2012-05-03 8:57 ` Daniel P. Berrange
2012-05-03 9:01 ` Alexander Graf
2012-05-03 9:03 ` Daniel P. Berrange
2012-05-03 9:06 ` Alexander Graf
2012-05-03 9:09 ` Daniel P. Berrange
2012-05-03 9:11 ` Alexander Graf
2012-05-03 20:58 ` Paul Moore
2012-05-03 9:04 ` Alexander Graf
2012-05-03 20:51 ` Paul Moore
2012-05-03 14:54 ` Alexander Graf
2012-05-03 20:54 ` Paul Moore [this message]
2012-05-04 2:01 ` Roman Drahtmueller
2012-05-04 12:39 ` Paul Moore
2012-05-04 12:42 ` Daniel P. Berrange
2012-06-03 0:55 ` Anthony Liguori
2012-06-04 18:16 ` Paul Moore
2012-06-04 23:11 ` Anthony Liguori
2012-06-04 23:17 ` Alexander Graf
2012-06-04 23:54 ` Anthony Liguori
2012-06-05 0:55 ` Alexander Graf
2012-06-05 1:03 ` Anthony Liguori
2012-06-05 1:08 ` Alexander Graf
2012-06-05 1:23 ` Anthony Liguori
2012-06-05 1:29 ` Alexander Graf
2012-06-05 7:23 ` Gerd Hoffmann
2012-06-05 21:45 ` Paul Moore
2012-06-05 21:51 ` Alexander Graf
2012-06-05 22:06 ` Paul Moore
2012-06-05 23:07 ` Anthony Liguori
2012-06-05 23:56 ` Alexander Graf
2012-06-06 22:56 ` Paul Moore
2012-06-07 3:10 ` Anthony Liguori
2012-06-07 10:31 ` Alexander Graf
2012-06-07 13:21 ` Paul Moore
2012-06-08 21:37 ` Paul Moore
2012-06-11 13:33 ` Roman Drahtmueller
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=4548305.DtX99stsJu@sifl \
--to=pmoore@redhat.com \
--cc=agraf@suse.de \
--cc=draht@suse.de \
--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).