Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Combine Configurator and Chooser #83

Open
DonatJR opened this issue Jul 25, 2018 · 2 comments
Open

Combine Configurator and Chooser #83

DonatJR opened this issue Jul 25, 2018 · 2 comments

Comments

@DonatJR
Copy link
Contributor

DonatJR commented Jul 25, 2018

@bencikpeter
Copy link
Contributor

According to #85 , the access rights of the confing files are admin only... however apps on secure desktop are launched with logged on user security context, therefore if user is not an administrator of computer, he would not be able to use configurator (or chooser)... and if he was an admin, the configurator/chooser would need to prompt UAC dialogue to run elevated.. is that desirable? Isn´t that a design flaw a bit? Wouldn´t digital signatures of config files be a better solution? Since we will already have a logic to verify signatures to avoid binary spoofing, why not reuse it?

@DonatJR
Copy link
Contributor Author

DonatJR commented Jul 31, 2018

@bencikpeter
The Chooser is usable by any user, but you are right that the Configurator must be run with admin rights (and it only starts elevated since just after it was created).
Having the configurations only be modifiable by admins was professor langwegs idea and was decided very early in (team) project. Because of this the image token presented to the user is embedded in the configuration and could be read by third-party applications if not secured by the current access rights.

Your idea using signatures might be worth pursuing if we find an adequate solution for the image token but I'm afraid it probably has to wait until after the team project has ended (20th of August). We want to have a working project to present and this has too much potential for errors in my opinion. 😅

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants