From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Ted Toth <txtoth@gmail.com>, SELinux <selinux@tycho.nsa.gov>,
refpolicy <refpolicy@oss.tresys.com>
Subject: Re: refpolicywarn usage
Date: Mon, 8 Jun 2015 09:11:22 -0400 [thread overview]
Message-ID: <5575947A.3070005@tresys.com> (raw)
In-Reply-To: <CAFPpqQEKBu2SsRN=GJj2SMvNLDW+Hj91MUTkU_L_-3DbKaW1Xg@mail.gmail.com>
On 6/5/2015 4:28 PM, Ted Toth wrote:
> I tried to use "refpolicywarn(`$0($*) has been deprecated.')" in a
> deprecated interface removing all of the previously defined policy.
> However the interface is used in an 'optional' which then causes the
> policy compilation to fail. What is the right way to handle this
> situation?
This should go to the refpolicy list.
Refpolicywarn is an m4 macro, so it doesn't result in any policy. If
you have an optional block with only one call to an interface that only
has a refpolicywarn in its implementation, it will result in an optional
with no rules inside.
We handle this in refpolicy by calling the new interface, e.g. if
interface X is being replaced by interface Y, in the implementation of X
we put a refpolicywarn message and call Y. If there is no new
interface, you could put safe placeholder rules, such as a call to
dev_rw_null().
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
WARNING: multiple messages have this Message-ID (diff)
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] refpolicywarn usage
Date: Mon, 8 Jun 2015 09:11:22 -0400 [thread overview]
Message-ID: <5575947A.3070005@tresys.com> (raw)
In-Reply-To: <CAFPpqQEKBu2SsRN=GJj2SMvNLDW+Hj91MUTkU_L_-3DbKaW1Xg@mail.gmail.com>
On 6/5/2015 4:28 PM, Ted Toth wrote:
> I tried to use "refpolicywarn(`$0($*) has been deprecated.')" in a
> deprecated interface removing all of the previously defined policy.
> However the interface is used in an 'optional' which then causes the
> policy compilation to fail. What is the right way to handle this
> situation?
This should go to the refpolicy list.
Refpolicywarn is an m4 macro, so it doesn't result in any policy. If
you have an optional block with only one call to an interface that only
has a refpolicywarn in its implementation, it will result in an optional
with no rules inside.
We handle this in refpolicy by calling the new interface, e.g. if
interface X is being replaced by interface Y, in the implementation of X
we put a refpolicywarn message and call Y. If there is no new
interface, you could put safe placeholder rules, such as a call to
dev_rw_null().
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2015-06-08 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 20:28 refpolicywarn usage Ted Toth
2015-06-08 13:11 ` Christopher J. PeBenito [this message]
2015-06-08 13:11 ` [refpolicy] " Christopher J. PeBenito
2015-06-08 14:42 ` Ted Toth
2015-06-08 14:42 ` [refpolicy] " Ted Toth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5575947A.3070005@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
--cc=selinux@tycho.nsa.gov \
--cc=txtoth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.