New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the default colors for the Whonix VMs and templates #1633

Closed
rootkovska opened this Issue Jan 15, 2016 · 7 comments

Comments

Projects
None yet
5 participants
@rootkovska
Member

rootkovska commented Jan 15, 2016

By default we use the black color to signalize VMs whose integrity is critical to the user's safety (e.g. templates installed by default), while red to signalize the VMs where the user should remember not to feel too safe. To be consistent with this approach I thus suggest to change the default Whonix coloring (now created by firstboot) to the following:

  • black for all the templates
  • black for the whonix-gw (protection of the user's identity depends on this being non-compromised)
  • ref for the default whonix AppVM based on the whonix-ws template (to warn user not to feel "too safe" while using it).
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Jan 15, 2016

Member

Implementing this would be up to @marmarek, I suppose. (I would just
have to update the screenshots in the user documentation accordingly.)

Joanna Rutkowska:

  • black for all the templates

Yes, templates always black sounds like a plan.

  • black for the whonix-gw (protection of the user's identity depends on this being non-compromised)

I guess you meant black for the whonix-gw based ProxyVM. "Overloading" /
re-using the color black for anything other than templates may not be
great. Not a strong opinion. @bnvk what do you think?

  • ref for the default whonix AppVM based on the whonix-ws template (to warn user not to feel "too safe" while using it).

I guess 'ref' is a typo and you meant 'red'. Sounds okay.

Member

adrelanos commented Jan 15, 2016

Implementing this would be up to @marmarek, I suppose. (I would just
have to update the screenshots in the user documentation accordingly.)

Joanna Rutkowska:

  • black for all the templates

Yes, templates always black sounds like a plan.

  • black for the whonix-gw (protection of the user's identity depends on this being non-compromised)

I guess you meant black for the whonix-gw based ProxyVM. "Overloading" /
re-using the color black for anything other than templates may not be
great. Not a strong opinion. @bnvk what do you think?

  • ref for the default whonix AppVM based on the whonix-ws template (to warn user not to feel "too safe" while using it).

I guess 'ref' is a typo and you meant 'red'. Sounds okay.

@ideologysec

This comment has been minimized.

Show comment
Hide comment
@ideologysec

ideologysec Feb 1, 2016

Speaking as a user, the proposed changes make sense to me. I wasn't aware that there was a guideline for color use (documentation opportunity, perhaps?), but thinking of black as "if compromised then screwed" and red as "trust nothing," making the proposed changes to the Whonix VMs sounds good.

Also, y'all need a "Welcome to Qubes here's what things mean!" intro. I realize that this is sort of a specialized OS and most of the people picking it up will have a good sense for Linux distros (hopefully!), but having a high level abstract overview/welcome splash would be great.

Speaking as a user, the proposed changes make sense to me. I wasn't aware that there was a guideline for color use (documentation opportunity, perhaps?), but thinking of black as "if compromised then screwed" and red as "trust nothing," making the proposed changes to the Whonix VMs sounds good.

Also, y'all need a "Welcome to Qubes here's what things mean!" intro. I realize that this is sort of a specialized OS and most of the people picking it up will have a good sense for Linux distros (hopefully!), but having a high level abstract overview/welcome splash would be great.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 2, 2016

Member

@Aktariel, is this what you're looking for?
https://www.qubes-os.org/getting-started/

Member

andrewdavidwong commented Feb 2, 2016

@Aktariel, is this what you're looking for?
https://www.qubes-os.org/getting-started/

@marmarek marmarek self-assigned this Feb 5, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 7, 2016

Member

What about using gray for sys-whonix Whonix-Gateway ProxyVM? It doesn't overload black templates, but is also some dark color.

Member

marmarek commented Feb 7, 2016

What about using gray for sys-whonix Whonix-Gateway ProxyVM? It doesn't overload black templates, but is also some dark color.

@rootkovska

This comment has been minimized.

Show comment
Hide comment
@rootkovska

rootkovska Feb 9, 2016

Member

I'd still vote for the black label for the Tor proxyVM -- after all it's a very critical VM and the black color should be saying: "stay away from tinkering with it, deal user!". Like in case of the default templates.

Member

rootkovska commented Feb 9, 2016

I'd still vote for the black label for the Tor proxyVM -- after all it's a very critical VM and the black color should be saying: "stay away from tinkering with it, deal user!". Like in case of the default templates.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 11, 2016

Member

Automated announcement from builder-github

The package qubes-mgmt-salt-dom0-virtual-machines-3.1.1-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

Member

marmarek commented Feb 11, 2016

Automated announcement from builder-github

The package qubes-mgmt-salt-dom0-virtual-machines-3.1.1-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 22, 2016

Member

Automated announcement from builder-github

The package qubes-mgmt-salt-dom0-virtual-machines-3.1.1-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Member

marmarek commented Feb 22, 2016

Automated announcement from builder-github

The package qubes-mgmt-salt-dom0-virtual-machines-3.1.1-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment