From: cpebenito@tresys.com (Christopher J. PeBenito) Date: Wed, 16 Feb 2011 11:27:53 -0500 Subject: [refpolicy] [ access_vectors patch 2/2] These are not deprecated as far as i can see. In-Reply-To: <20110214204602.GA9446@localhost.localdomain> References: <20110214204602.GA9446@localhost.localdomain> Message-ID: <4D5BFB09.80003@tresys.com> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com On 02/14/11 15:46, Dominick Grift wrote: > These seem to not be deprecated. Atleast, when i commented them out i got complaints when loading policy. No, they are deprecated. You can't just comment out the permissions in kernel object classes. They're still in the kernel, but not used. In the future, if we need new packet permissions, these could be reclaimed if necessary. > Signed-off-by: Dominick Grift > --- > :100644 100644 1966443... 3257105... M policy/flask/access_vectors > policy/flask/access_vectors | 4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/policy/flask/access_vectors b/policy/flask/access_vectors > index 1966443..3257105 100644 > --- a/policy/flask/access_vectors > +++ b/policy/flask/access_vectors > @@ -687,8 +687,8 @@ class packet > send > recv > relabelto > - flow_in # deprecated > - flow_out # deprecated > + flow_in > + flow_out > forward_in > forward_out > } > > > > _______________________________________________ > refpolicy mailing list > refpolicy at oss.tresys.com > http://oss.tresys.com/mailman/listinfo/refpolicy -- Chris PeBenito Tresys Technology, LLC www.tresys.com | oss.tresys.com