Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Polyinstantiation
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Operating system security == In [[Operating system#Security|Operating system security]], polyinstantiation is the concept of creating a user or process specific view of a shared resource. I.e. Process '''A''' cannot affect process '''B''' by writing malicious code to a shared resource, such as [[UNIX]] directory '''/tmp'''.<ref>{{cite web | url=http://www.ibm.com/developerworks/linux/library/l-polyinstantiation/ | title=Improve security with polyinstantiation: Using a Pluggable Authentication Module to protect private data | author-link=Robb R. Romans | first= Robb R | last= Romans | date=2008-03-26 | publisher=IBM DeveloperWorks}}</ref><ref>{{cite web | url=http://www.coker.com.au/selinux/talks/sage-2006/PolyInstantiatedDirectories.html | title=Polyinstantiation of directories in an SE Linux system | author-link=Russell Coker | first= Russell | last= Coker | date=2007-01-04 | work=[[SAGE-AU|Sage 2006]]}}</ref> Polyinstantiation of shared resources have similar goals as [[process isolation]], an application of [[virtual memory]], where processes are assigned their own isolated [[virtual address space]] to prevent process '''A''' writing into the memory space of process '''B'''.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)