Hello Michael,
On Sun, Apr 19, 2020 at 10:25:13PM +0200, Michael Kerrisk (man-pages) wrote:
> > **
> >
> > Inconsistent spelling of multithreaded vs. multi-threaded
> >
> > a)
> > "Prior to Linux 2.6.28, SELinux did not allow threads within a multi-threaded "
> > "process to set their security context via this node as it would yield an "
> > "inconsistency among the security contexts of the threads sharing the same "
> > "memory space. Since Linux 2.6.28, SELinux lifted this restriction and began "
> > "supporting \"set\" operations for threads within a multithreaded process if "
> > "the new security context is bounded by the old security context, where the "
> > "bounded relation is defined in policy and guarantees that the new security "
>
> Thanks. Fixed.
>
>
> > b)
> > "In SELinux, this file is used to get the security context of a process. "
> > "Prior to Linux 2.6.11, this file could not be used to set the security "
> > "context (a write was always denied), since SELinux limited process security "
> > "transitions to B<execve>(2) (see the description of I</proc/[pid]/attr/"
> > "exec>, below). Since Linux 2.6.11, SELinux lifted this restriction and "
> > "began supporting \"set\" operations via writes to this node if authorized by "
> > "policy, although use of this operation is only suitable for applications "
> >
>
> What is "b)" about?
Error on my side. Sorry. Please ignore.
Greetings
Helge
--
Dr. Helge Kreutzmann debian@xxxxxxxxxxxxx
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
Attachment:
signature.asc
Description: PGP signature
