All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Dan Kenigsberg <danken@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] let management expire vnc password
Date: Wed, 30 Sep 2009 09:43:13 -0500	[thread overview]
Message-ID: <4AC36E81.901@codemonkey.ws> (raw)
In-Reply-To: <20090930140312.GB5408@redhat.com>

Dan Kenigsberg wrote:
> On Wed, Sep 30, 2009 at 08:49:28AM -0500, Anthony Liguori wrote:
>   
>> Dan Kenigsberg wrote:
>>     
>>> After a client connects to vnc server, management may wish to expire the
>>> vnc password, so that an attacker has less time to break into the vm.
>>>   
>>>       
>> I don't understand what the use-case for this is.
>>
>> You want to basically lock out any new clients?  Can't you just set the  
>> password to something random?
>>     
>
> Yes, and actually that's what we currently do. But having a random
> password still opens a crack for guessing it.
>   

Is the requirement, prevent future clients from connecting to the vnc 
server?  Essentially, disabling the vnc server?

Could we do something more direct like add a 'vnc off' monitor command?  
The nice thing about this approach is that we could add a flag to 
disconnect all connected clients since someone else wanted that feature 
in the past.

Can you explain the rationale for doing this though in a management 
tool?  I'd like to better understand what sort of policy you're trying 
to enforce.

Regards,

Anthony Liguori

  reply	other threads:[~2009-09-30 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22  8:47 [Qemu-devel] [PATCH] let management expire vnc password Dan Kenigsberg
2009-09-30 13:49 ` Anthony Liguori
2009-09-30 14:03   ` Dan Kenigsberg
2009-09-30 14:43     ` Anthony Liguori [this message]
2009-09-30 16:45       ` Dan Kenigsberg
2009-09-30 21:03         ` Anthony Liguori
2009-10-02  9:58           ` Daniel P. Berrange
2009-10-02 13:44             ` Anthony Liguori
2009-10-02 14:49               ` Jamie Lokier

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=4AC36E81.901@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=danken@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 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.