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

Small GUI app for easy adding new appmenus for VMs #45

Closed
marmarek opened this Issue Mar 8, 2015 · 10 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 8 Jun 2010 12:02 UTC
Generate new app menus for Dom0's start menu whenever the user installs new apps in a template VM.

Migrated-From: https://wiki.qubes-os.org/ticket/45

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 27 Jul 2010 13:32 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 27 Jul 2010 13:32 UTC

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 5 Aug 2010 21:17 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 5 Aug 2010 21:17 UTC

@marmarek marmarek added enhancement and removed bug labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 29 Sep 2010 22:45 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 29 Sep 2010 22:45 UTC

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 24 Jan 2011 12:01 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 24 Jan 2011 12:01 UTC

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 24 Jan 2011 12:06 UTC
Normally (in the case there is only one template in the system) the user fully trusts the template. This means the template's filesystem is not malicious, e.g. it's ok to mount it under Dom0, and the fs metadate will not be trying to exploit some (hypothetical) bug in the Dom0's fs module.

However when the user has more than one template, some templates might not be so trusted as others. In that case it's a security threat to attempt to mount template's fs under Dom0.

This means that if we don't trust the template fully, we cannot automatically update appmenues for this template!

Member

marmarek commented Mar 8, 2015

Comment by joanna on 24 Jan 2011 12:06 UTC
Normally (in the case there is only one template in the system) the user fully trusts the template. This means the template's filesystem is not malicious, e.g. it's ok to mount it under Dom0, and the fs metadate will not be trying to exploit some (hypothetical) bug in the Dom0's fs module.

However when the user has more than one template, some templates might not be so trusted as others. In that case it's a security threat to attempt to mount template's fs under Dom0.

This means that if we don't trust the template fully, we cannot automatically update appmenues for this template!

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 29 Mar 2011 00:12 UTC
I think the best solution would be to have just a few AppMenus for each VM by default (just like we have now, starting from Beta 1), and one more Appmenu -- "Add more shortcuts...". When the user clicks this appmenu, it launches our app that communicates with an agent in the AppVM, who in turn parses the VM's /usr/share/applications directory and sends out the list of appmenus using a very simple (so, safe) protocol over xenstore (or qrexec). Then the user is presented with a list of Appmenus avilable for the VM and can check which one should be added to the menu.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 29 Mar 2011 00:12 UTC
I think the best solution would be to have just a few AppMenus for each VM by default (just like we have now, starting from Beta 1), and one more Appmenu -- "Add more shortcuts...". When the user clicks this appmenu, it launches our app that communicates with an agent in the AppVM, who in turn parses the VM's /usr/share/applications directory and sends out the list of appmenus using a very simple (so, safe) protocol over xenstore (or qrexec). Then the user is presented with a list of Appmenus avilable for the VM and can check which one should be added to the menu.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 11 Apr 2011 12:17 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 11 Apr 2011 12:17 UTC

@marmarek marmarek removed the C: core label Mar 8, 2015

@marmarek marmarek changed the title from Auto-update "start" menu after template VM boot to Small GUI app for easy adding new appmenus for VMs Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 23 May 2011 16:25 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 23 May 2011 16:25 UTC

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 25 May 2011 11:04 UTC
TODO: Trigger apmenus template update on package installation in TemplateVM (some yum trigger?)

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 25 May 2011 11:04 UTC
TODO: Trigger apmenus template update on package installation in TemplateVM (some yum trigger?)

@marmarek marmarek closed this Mar 8, 2015

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