TL;DR
Let's add the custom string, to DispVMs, in order to give user a hint, which
dispvm, came from where.
Maybe also add option, for them NOT TO TURN OFF, when you close all gui apps.
-----
As an idea:
This is a wonderful feature, that is currently is implemented in 4.0
But it missing one little detail, and it is the Final name of DispVM.
Currently it is disp[0-9]{2-3} , and it is okay. It is distinct, but other than
color, it does not tell much about template it was created from.
Say, we can add a feature, for user to add custom string, into generated name.
Something [disp03442_workbrowser:project_sunset=DO NOT LEAVE YOUR BROWSER ALONE
FOR A SECOND LEVEL OF PARANOID=], will do for a working title.
It may contain hints on what we are dealing with:
- [disp0666_coocoo:malware_run]
It may contain instruction:
- [disp8131_SAVE YOUR CHANGES ELSWHERE!!]
All is favor of awareness.
----
Hypothetical:
Here is the situation:
- User created TemplateVM with frozen programs and root.
- User create AppVM with frozen home and preferences
- User creates DispVM, which contains all pre-sets and works in it.
When it may be useful ? Say, when we create AppVM with one, and only one
purpose, and want to negate future changes, do not need to store local data.
Example:
Frozen web-browser, with a single password save, for a single site.
Frozen environment, for build testing.(When your code can destroy itself)
Frozen pen-testing platform. (When you get dirty, and don't want to take
anything home)
-----
Problem:
Buuut if, there more that 5-10 disp vms, having similar name, but different
color, It is hard to say, what DispVM originated, from what template. Only the
user will know, but if he... will ever forget that?
Work-around is:
User will have to customize the looks of the programs within AppVMs. In order
to minimize operational error.
Other option:
Automate you preferences. And you normal AppVMs. Because you are so good.
Or:
You clone your AppVMs, each time. Easy, right??
----
Why you want to have a thing like that?
When you want to be **sure**, and you do not want to change preferences if
someone pwns your DispVM. You just load AppVM, make updates you need, in a
different environment and... Have a little faith.
----
Another problem:
If we take on, such way of working within DispVM, we can forget how fragile
data is inside, and close it in a middle of the work.
Solution:
Add preference NOT to shut down DispVM if all gui programs closed.
----
I just found myself craving for such simple thing, and tired of restoring
browser sessions.
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/f7741d61-b07e-42c8-a8ad-bd13e820dfbf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
