3 ms·
> The problem is every executable can impersonate the user, Um, what? What do you mean by "impersonate" here? What does a process that does not impersonate th
by Karellen 4y ago
> The problem is every executable can impersonate the user,
Um, what?
What do you mean by "impersonate" here? What does a process that does not impersonate the user look like? Do you just mean "executables that run as the user"?
When you log in, and a shell is started that runs as you, is that shell impersonating the user?
When you execute commands, as yourself, those commands run with your credentials. Because you ran them. Isn't that, like, the point?
- dllthomas 4y agoTypically, any program I run has the totality of my (regular user) authority, which may let it do things I did not intend. Related: https://en.wikipedia.org/wiki/Ambient_authority https://en.wikipedia.org/wiki/Ambient_authority https://en.wikipedia.org/wiki/Confused_deputy_problem https://en.wikipedia.org/wiki/Confused_deputy_problem https://en.wikipedia.org/wiki/Object-capability_model https://en.wikipedia.org/wiki/Object-capability_model
- derefr 4y ago> What does a process that does not impersonate the user look like? A command running inside a virtual machine, maybe?
- eru 4y agoOr check out how iOS and Android use permissions.