From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Moore <pmoore@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vnc: disable VNC password authentication (security type 2) when in FIPS mode
Date: Thu, 3 May 2012 10:09:37 +0100 [thread overview]
Message-ID: <20120503090937.GI24747@redhat.com> (raw)
In-Reply-To: <4FE1F453-EFDF-4126-8CC2-BD68A36A8053@suse.de>
On Thu, May 03, 2012 at 11:06:18AM +0200, Alexander Graf wrote:
>
> On 03.05.2012, at 11:03, Daniel P. Berrange wrote:
>
> > On Thu, May 03, 2012 at 11:01:29AM +0200, Alexander Graf wrote:
> >>
> >> On 03.05.2012, at 10:57, Daniel P. Berrange wrote:
> >>
> >>> On Thu, May 03, 2012 at 10:51:15AM +0200, Alexander Graf wrote:
> >>>>
> >>>> On 03.05.2012, at 10:29, Daniel P. Berrange wrote:
> >>>>
> >>>>> On Wed, May 02, 2012 at 03:32:56PM -0400, 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.
> >>>>
> >>>> So that means "no password" is more secure according to FIPS than
> >>>> "DES encrypted password"?
> >>>
> >>> No, FIPS is not making statements about the choice of auth methods.
> >>> FIPS is concerned with what encryption algorithms an application uses.
> >>> The requirements about whether authentication is required & what sort,
> >>> is upto other specifications (eg Common Criteria) to decide.
> >>
> >> Hrm, so short-term this fixes things. But long-term, I think the
> >> better solution would be to implement the tight security model and
> >> use a real cipher:
> >
> > That is certainly possible, but shouldn't have any bearing on whether
> > this patch is accepted. Note that QEMU already implements VeNCrypt
> > and SASL extensions both of which provide strong security
>
> Hmm. Isn't the syslog message misleading then? Also, why would the
> whole password parameter be blocked then?
The password parameter is irrelevant for VeNCrypt & SASL authentication
types. They are configured via other parameters.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-05-03 9:09 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 [this message]
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
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=20120503090937.GI24747@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@suse.de \
--cc=pmoore@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).