GNOME Bugzilla – Bug 693391
Remember product keys
Last modified: 2016-03-31 13:58:23 UTC
It gets pretty frustrating to having to enter product keys all the time, even if copy&pasted from some file. It would be nice to cache the product key first time user enters it and automatically set it into the product key text entry for the user on subsequent runs. Ideally, we should keep separate cache for each ISO but having just one key cached at a time won't be a bad start either.
Different Windows editions need different keys (winxp home VS winxp pro), so this per-ISO would work better than just one key (ideally this would be per OS version, but libosinfo does not have such a concept yet).
(In reply to comment #1) > Different Windows editions need different keys (winxp home VS winxp pro), so > this per-ISO would work better than just one key (ideally this would be per OS > version, but libosinfo does not have such a concept yet). ack
The per-ISO means that having a different ISO for the same OS does not recognize it? I would think of a list containing the last used keys with its respective OS and version. On installation process, maybe filtering them by publisher would be useful (i.e. do not display Mac keys when installing Windows)
(In reply to comment #3) > The per-ISO means that having a different ISO for the same OS does not > recognize it? I don't think people typically keep multiple duplicate ISOs and when they do, I don't think it would be a big deal if they have to type the key twice rather than once. > I would think of a list containing the last used keys with its respective OS > and version. On installation process, maybe filtering them by publisher would > be useful (i.e. do not display Mac keys when installing Windows) I don't see the need to go that far. The point is to making users life easier and not make them having to write the key each time they create a VM against a particular installer.
Created attachment 298050 [details] [review] unattended-setup-box: Take media as constructor arg Instead of passing different parts of the InstallerMedia instance, lets pass the instance itself to constructor and let it take what it needs from it.
Created attachment 298051 [details] [review] unattended-setup-box: Cache setup data Cache express install toggle, username, password and product key for every media. No need to keep product keys in a separate file and having to paste them each time you create a windows VM anymore. \o/
Where does this data get stored, and will users know how to clear it ?
(In reply to Matthias Clasen from comment #7) > Where does this data get stored, ~/.cache/gnome-boxes/unattended/setup-data.conf > and will users know how to clear it ? I wouldn't know how to expose such an option nicely. I think its ok for now if they currently have to remove that hidden file.
(In reply to Zeeshan Ali (Khattak) from comment #8) > > and will users know how to clear it ? > > I wouldn't know how to expose such an option nicely. I think its ok for now > if they currently have to remove that hidden file. Is that a common action? = Should it be covered in docs?
(In reply to André Klapper from comment #9) > (In reply to Zeeshan Ali (Khattak) from comment #8) > > > and will users know how to clear it ? > > > > I wouldn't know how to expose such an option nicely. I think its ok for now > > if they currently have to remove that hidden file. > > Is that a common action? = Should it be covered in docs? I seriously doubt so.
sorry, didn't mean to derail this. having it stored in ~/.cache is fine
Attachment 298050 [details] pushed as d806ef5 - unattended-setup-box: Take media as constructor arg Attachment 298051 [details] pushed as ae21e56 - unattended-setup-box: Cache setup data