Re:Qubes – Secure Desktop OS Using Security by Compartmental...
by Touche on Thursday October 09, 2014 @12:55AM
(#8430885)
I know of no such models. Perhaps someone smarter than me has thought of them, that's why I asked the question initially.
[ Parent
| on HN ]
Re:Qubes – Secure Desktop OS Using Security by Compartmental...
by pjmlp on Thursday October 09, 2014 @07:26AM
(#8431706)
Sandboxing, where each process is only allowed to use a precise set of system resources.
Any attempt to use anything else leads to termination.
Re:Qubes – Secure Desktop OS Using Security by Compartmental...
by Touche on Thursday October 09, 2014 @09:42AM
(#8432259)
Which resources are they allowed to use? What defines which resources they are given?
Re:Qubes – Secure Desktop OS Using Security by Compartmental...
by pjmlp on Friday October 10, 2014 @02:46AM
(#8436551)
> Which resources are they allowed to use?
The system administrator at installation time.
> What defines which resources they are given?
Applications just have a request list of what they require.
If the administrator doesn't allow them for the given application modules (executable, dynamic library, function call,...), bad luck.
Re:Qubes – Secure Desktop OS Using Security by Compartmental...
by SamReidHughes on Thursday October 09, 2014 @01:38AM
(#8430971)
Sandboxing. It's present on OS X.
Re:Qubes – Secure Desktop OS Using Security by Compartmental...
by Touche on Thursday October 09, 2014 @09:44AM
(#8432265)
I'm confused. The original person I responded to said that no desktop OSes had good security models. On OSX I can write a script that, when run as a user, has access to everything the user has access to. So what exactly are you talking about?
Re:Qubes – Secure Desktop OS Using Security by Compartmental...
by SamReidHughes on Thursday October 09, 2014 @12:02PM
(#8433201)
I'm talking about OS X sandboxing. The hypothetical PDF reader doesn't have access to the email.