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

(GUI enhancement) Policy question readability #3381

Closed
svenssonaxel opened this Issue Dec 9, 2017 · 2 comments

Comments

Projects
None yet
4 participants
@svenssonaxel

Qubes OS version: R3.2

Some questions, e.g. about shutting down a VM, have the VM name in bold. This makes them easy and quick to read, especially for experienced users that recognize the question and only want to check that the VM names are correct.

Policy questions do not have this feature, but maybe they should?
I propose changing the policy question that currently reads for example:

Do you allow domain "vm1" to execute qubes.Filecopy operation on the domain "vm2"?
"Yes to All" option will automatically allow this operation in the future.

to be change to the more readable:

Do you allow this RPC operation?
Operation: qubes.Filecopy
Executed by: vm1
Target domain: vm2

"Yes to All" option will automatically allow this operation in the future.

@mirrorway

This comment has been minimized.

Show comment
Hide comment
@mirrorway

mirrorway Dec 10, 2017

Even better I think would be to drop the "Yes to all..." explanation and simply make the button text self-explanatory. Make the window look like:

Titlebar: [Dom0] RPC.request

vm1 wants to run qubes.Filecopy on vm2.

[Deny] [Allow once] [Allow forever]

It seems much easier to parse.

mirrorway commented Dec 10, 2017

Even better I think would be to drop the "Yes to all..." explanation and simply make the button text self-explanatory. Make the window look like:

Titlebar: [Dom0] RPC.request

vm1 wants to run qubes.Filecopy on vm2.

[Deny] [Allow once] [Allow forever]

It seems much easier to parse.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 28, 2018

Member

Done in policy dialog in 4.0

Member

marmarek commented Jan 28, 2018

Done in policy dialog in 4.0

@marmarek marmarek closed this Jan 28, 2018

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