5 ms·
Putting a file into "that dir" also requires elevated permissions. (e.g. C:\Program Files\VSTPlugins )
by radiowave 3y ago
Putting a file into "that dir" also requires elevated permissions.
(e.g. C:\Program Files\VSTPlugins )
- throwaway290 3y agoOf course but the point is I do that myself. Installer just asks for permissions and does who knows what.
- prmoustache 3y agoThen the binary does who knows what so in any case you are kind of bound to your trust in the vendor.
- throwaway290 3y agoPlugins themselves never require admin access to run, the installer does.
- prmoustache 3y agoUnless you are running your plugins in a sandbox or have different profiles for different usages, this doesn't make any difference as what is more important, your personal data is accessible from your main user. Anyone producing music from qubesOS?
- throwaway290 3y agoAre you saying it makes no difference whether process runs as root or normal user in whatever OS you're on?
- prmoustache 3y agoI am saying it depends of the attack scenario. Privilege escalation is a big issue for servers and mutualized systems. On a personal computer this is the least of your concerns as your personnal data is more valuable than some binaries in your root filesystem. People are ready to get their precious data pwned or ransomwared but are afraid some process would get root access, this is backwards thinking.
- throwaway290 3y agoIn many systems today an app is sandboxed and doesn't get full disk access unless it's granted. But installer gets full access, since it can plug the password into su/sudo and do whatever.