After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 666365 - Ability to set SPICE password
Ability to set SPICE password
Status: RESOLVED DUPLICATE of bug 694854
Product: gnome-boxes
Classification: Applications
Component: spice
3.3.x (unsupported)
Other All
: Normal enhancement
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
ui-design
Depends on:
Blocks:
 
 
Reported: 2011-12-16 15:09 UTC by Zeeshan Ali
Modified: 2016-03-31 13:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Zeeshan Ali 2011-12-16 15:09:28 UTC 
We should allow the user to (re)set password for a SPICE box from the properties page.
Comment 1 Marc-Andre Lureau 2012-10-22 14:22:22 UTC 
Imho, it should share the same password as user password or it will be very confusing.

If I understand correctly, today only the password is used for VM creation, and nothing else is done with it.

The Spice VM is not shared / exposed on the network.

The user session isn't logged in / unlocked when Boxes user connects to it.

Instead, I think we should:

- protect the session and Spice connection with user password
- store password in keyring
- when connecting, authenticate to spice and login/unlock with known password
- when the VM is made accessible over the network, it will be protected with same password
- when connecting with Boxes to a remote VM (either shared Box or vnc/rdp etc.), ask and store the user/password
- if the user changes password in Boxes, change both VM and spice password
- if the user changes password in Guest, ignore fail attempt to login/unlock and let the user interact with VM to do so.
Comment 2 Zeeshan Ali 2014-10-20 16:26:01 UTC 
Well we haven't been setting a spice password on VMs for a while now so we want to have this option, IMO it should be done as part of bug#694854.

*** This bug has been marked as a duplicate of bug 694854 ***