qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Dan Kenigsberg <danken@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] let management expire vnc password
Date: Fri, 02 Oct 2009 08:44:09 -0500	[thread overview]
Message-ID: <4AC603A9.1050208@codemonkey.ws> (raw)
In-Reply-To: <20091002095837.GB21416@redhat.com>

Daniel P. Berrange wrote:
> I think it is a pretty valid use case, though I don't like the proposed
> implementation. In essence it is implementing one-time-passwords instead
> of multi-use passwords and both of those are reasonable concepts. Having
> to implement one-time passwords using multi-use passwords + iptables is
> a really bad, over complicated hack, particularly considering how trivial
> this is todo in QEMU.
>
> In terms of impl though, rather than having separate a 'expire_password'
> command, I think  it would be preferrable to have alternative syntax for
> setting initial credentials 
>
>     change vnc passwd     (for multi-use passwords)
>     change vnc otp        (for single-use passwords)
>
> Or, extend the existing 'change vnc passwd' command to allow optional
> flags as a 4th argument.
>
>      change vnc passwd otp
>   

A one time password does make a bit more sense to me but I wonder if 
that still satisfies the use case.

Regards,

Anthony Liguori

  reply	other threads:[~2009-10-02 13:44 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
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 [this message]
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=4AC603A9.1050208@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=berrange@redhat.com \
    --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 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).