<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in files.securelevel</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6887492c261e6d27ac6fa6294fb8552ffcfd0c49 - Make securelevel a &quot;secmodel&quot; of its own.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/secmodel/securelevel/files.securelevel#6887492c261e6d27ac6fa6294fb8552ffcfd0c49</link>
        <description>Make securelevel a &quot;secmodel&quot; of its own.While it&apos;s true that it&apos;s part of the traditional 4.4BSD security model,there may come a time where a different &quot;primary&quot; security model used forfine-grained privileges (ie., splitting root&apos;s responsibilities to variousprivileges that can be assigned) may want to still have a securelevelsetting.Idea from Daniel Carosone:  http://mail-index.netbsd.org/tech-security/2006/08/25/0001.htmlThe location of the removed files, for reference, was:  src/secmodel/bsd44/secmodel_bsd44_securelevel.c  src/secmodel/bsd44/securelevel.h

            List of files:
            /netbsd-src/sys/secmodel/securelevel/files.securelevel</description>
        <pubDate>Wed, 21 Nov 2007 22:49:05 +0000</pubDate>
        <dc:creator>elad &lt;elad@NetBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
