|
From: | Gerd Hoffmann |
Subject: | Re: [Qemu-devel] [PATCH 2/3] vnc: support password expire |
Date: | Wed, 17 Nov 2010 11:23:11 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100827 Red Hat/3.1.3-1.el6 Thunderbird/3.1.3 |
Hi,
Having an expiration policy builtin to QEMU (as opposed to libvirt) seems like the wrong place.IMHO it doesn't build policy into qemu. It is still up to libvirt (or the management app building on top of libvirt) to decide if and when the password will expire.Except if you want to cancel the expiration because the expiration policy changes. You'd have to set the password without an expiration time and you may not have ready access to the password.
Point.
set-password $protocol $secret [ let $time pass ] expire-password $protocol I fail to see why this is better though. The former is more robust and easier to implement in the management. The amount of code needed in qemu is probably quite similar ...But the later let's a management tool implement arbitrarily complex expiration policies.
Hmm, we could do this: set-password $protocol $secret expire-password $protocol [ now | never | $seconds ] Comments? cheers, Gerd
[Prev in Thread] | Current Thread | [Next in Thread] |