The point is valid on the random passwords in a secured environment.<br>However that being said the randomly generated password does make it a pain when interacting with HTML5 based clients (SPICE or VNC) or any standalone client for that matter.<br>
<br>At the very least can this to be made to be configurable? The default can be as is but at the very least allow for configurable VNC or SPICE passwords if so desired..<br><br>Curiously I know that the Web UI does not allow for this now but is it possible to change the password policies via any existing engine or vdsm configurations/parameters?<br>
EG:<br>- default 120 second password re-generation, can this be altered?<br>- fixed vs randomly generated password?<br><br>A side note are there any plans of the horizon for integrating support or allowing for interaction with HTML5 based clients mostly VNC but with new SPICE HTML5 client?<br>
<br>- DHC<br><br><div class="gmail_quote">On Fri, Oct 12, 2012 at 9:42 AM, David Jaša <span dir="ltr"><<a href="mailto:djasa@redhat.com" target="_blank">djasa@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Dead Horse píše v Čt 11. 10. 2012 v 12:00 -0500:<br>
<div class="im">> Would like to make a couple of small feature requests.<br>
><br>
> 1) Allow for the SPICE or VNC password to be set in the UI by admin's<br>
> or power users.<br>
> Benefit: (Assumes spice SSL has been disabled) allows user or admin to<br>
> set a password for access by a standalone remote session via vncviewer<br>
> or remote-viewer or the spice html5 implementation which is WIP, or<br>
> standalone HW thin client<br>
> - This may also assume that vdsm is running with SSL disabled as well<br>
> to have had vdsm make the neccesary changes to the qemu spice<br>
> configuration<br>
<br>
</div>Drawback: users can choose repetitive and/or weak passwords. Generating<br>
a new random password for each connection is the best thing from<br>
security POV in my opinion.<br>
<div class="im"><br>
><br>
> 2) Display currently configured OR generated password and IP/Port for<br>
> either VNC or SPICE console of the VM within the PUP and Admin UI<br>
> Benefit: At the very least a standalone remote client can be used to<br>
> connect once the password and IP/PORT is known for spice or VNC<br>
> - Currently VNC will display a dialog that shows the this info but it<br>
> would be more useful to have it displayed in the UI given proper<br>
> privilege<br>
<br>
</div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=843397" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=843397</a><br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=843410" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=843410</a><br>
<div class="im"><br>
><br>
> 3) Display the UUID of a VM in the Admin UI (similar to the how the<br>
> disks tab breaks down and shows DISK UUID mappings)<br>
> - Benefit: Easier for administrators to map UUID to VM config file<br>
> data in the data stores or export domains<br>
<br>
</div>IMO full uuid should be displayed in General subtab only because it's<br>
too long to have it as a column.<br>
<br>
It would be nice to see it in a column though in some shortened form<br>
because it could probably enable relaxing of<br>
unique-name-of-VM-in-whole-setup restriction.<br>
<br>
David<br>
<br>
><br>
> - DHC<br>
><br>
> _______________________________________________<br>
> Engine-devel mailing list<br>
> <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
<br>
David Jaša, RHCE<br>
<br>
SPICE QE based in Brno<br>
GPG Key: 22C33E24<br>
Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24<br>
<br>
<br>
<br>
</font></span></blockquote></div><br>