Opened 3 years ago
Closed 2 years ago
#45 closed enhancement (implemented)
Small GUI app for easy adding new appmenus for VMs
| Reported by: | joanna | Owned by: | marmarek |
|---|---|---|---|
| Priority: | major | Milestone: | Release 1 Beta 2 |
| Component: | Dom0 Window Manager | Keywords: | |
| Cc: |
Description
Generate new app menus for Dom0's start menu whenever the user installs new apps in a template VM.
Change History (10)
comment:1 Changed 3 years ago by joanna
- Milestone changed from Release 1 Beta 1 to Release 1 Alpha 3
comment:2 Changed 3 years ago by joanna
- Type changed from defect to enhancement
comment:3 Changed 3 years ago by joanna
- Milestone changed from Release 1 Alpha 3 to Release 1 Beta 1
comment:4 Changed 2 years ago by joanna
- Milestone changed from Release 1 Beta 1 to Release 1 Beta 2
comment:5 Changed 2 years ago by joanna
comment:6 Changed 2 years ago by joanna
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.
comment:7 Changed 2 years ago by joanna
- Component changed from core to kde-dom0
- Summary changed from Auto-update "start" menu after template VM boot to Small GUI app for easy adding new appmenus for VMs
comment:8 Changed 2 years ago by marmarek
- Owner changed from joanna to marmarek
- Status changed from new to accepted
comment:9 Changed 2 years ago by marmarek
TODO: Trigger apmenus template update on package installation in TemplateVM (some yum trigger?)
comment:10 Changed 2 years ago by marmarek
- Resolution set to implemented
- Status changed from accepted to closed

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!