All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] policycoreutils: setfiles: do not restrict checks against a binary policy
@ 2020-07-07 14:35 Antoine Tenart
  2020-07-07 15:43 ` Stephen Smalley
  0 siblings, 1 reply; 3+ messages in thread
From: Antoine Tenart @ 2020-07-07 14:35 UTC (permalink / raw)
  To: selinux
  Cc: Antoine Tenart, stephen.smalley.work, matthew.weber, thomas.petazzoni

The -c option allows to check the validity of contexts against a
specified binary policy. Its use is restricted: no pathname can be used
when a binary policy is given to setfiles. It's not clear if this is
intentional as the built-in help and the man page are not stating the
same thing about this (the man page document -c as a normal option,
while the built-in help shows it is restricted).

When generating full system images later used with SELinux in enforcing
mode, the extended attributed of files have to be set by the build
machine. The issue is setfiles always checks the contexts against a
policy (ctx_validate = 1) and using an external binary policy is not
currently possible when using a pathname. This ends up in setfiles
failing early as the contexts of the target image are not always
compatible with the ones of the build machine.

This patch reworks a check on optind only made when -c is used, that
enforced the use of a single argument to allow 1+ arguments, allowing to
use setfiles with an external binary policy and pathnames. The following
command is then allowed, as already documented in the man page:

  $ setfiles -m -r target/ -c policy.32 file_contexts target/

Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
---

Since v1:
  - Updated the number of 'name' arguments to reflect the format string
    change.

 policycoreutils/setfiles/setfiles.c | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/policycoreutils/setfiles/setfiles.c b/policycoreutils/setfiles/setfiles.c
index ed67b5f12245..422c3767b845 100644
--- a/policycoreutils/setfiles/setfiles.c
+++ b/policycoreutils/setfiles/setfiles.c
@@ -48,11 +48,10 @@ static __attribute__((__noreturn__)) void usage(const char *const name)
 			name, name);
 	} else {
 		fprintf(stderr,
-			"usage:  %s [-diIDlmnpqvEFW] [-e excludedir] [-r alt_root_path] spec_file pathname...\n"
-			"usage:  %s [-diIDlmnpqvEFW] [-e excludedir] [-r alt_root_path] spec_file -f filename\n"
-			"usage:  %s -s [-diIDlmnpqvFW] spec_file\n"
-			"usage:  %s -c policyfile spec_file\n",
-			name, name, name, name);
+			"usage:  %s [-diIDlmnpqvEFW] [-e excludedir] [-r alt_root_path] [-c policyfile] spec_file pathname...\n"
+			"usage:  %s [-diIDlmnpqvEFW] [-e excludedir] [-r alt_root_path] [-c policyfile] spec_file -f filename\n"
+			"usage:  %s -s [-diIDlmnpqvFW] spec_file\n",
+			name, name, name);
 	}
 	exit(-1);
 }
@@ -409,7 +408,7 @@ int main(int argc, char **argv)
 
 	if (!iamrestorecon) {
 		if (policyfile) {
-			if (optind != (argc - 1))
+			if (optind > (argc - 1))
 				usage(argv[0]);
 		} else if (use_input_file) {
 			if (optind != (argc - 1)) {
-- 
2.26.2


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] policycoreutils: setfiles: do not restrict checks against a binary policy
  2020-07-07 14:35 [PATCH v2] policycoreutils: setfiles: do not restrict checks against a binary policy Antoine Tenart
@ 2020-07-07 15:43 ` Stephen Smalley
  2020-07-10 13:42   ` Petr Lautrbach
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Smalley @ 2020-07-07 15:43 UTC (permalink / raw)
  To: Antoine Tenart; +Cc: SElinux list, matthew.weber, thomas.petazzoni

On Tue, Jul 7, 2020 at 10:35 AM Antoine Tenart
<antoine.tenart@bootlin.com> wrote:
>
> The -c option allows to check the validity of contexts against a
> specified binary policy. Its use is restricted: no pathname can be used
> when a binary policy is given to setfiles. It's not clear if this is
> intentional as the built-in help and the man page are not stating the
> same thing about this (the man page document -c as a normal option,
> while the built-in help shows it is restricted).
>
> When generating full system images later used with SELinux in enforcing
> mode, the extended attributed of files have to be set by the build
> machine. The issue is setfiles always checks the contexts against a
> policy (ctx_validate = 1) and using an external binary policy is not
> currently possible when using a pathname. This ends up in setfiles
> failing early as the contexts of the target image are not always
> compatible with the ones of the build machine.
>
> This patch reworks a check on optind only made when -c is used, that
> enforced the use of a single argument to allow 1+ arguments, allowing to
> use setfiles with an external binary policy and pathnames. The following
> command is then allowed, as already documented in the man page:
>
>   $ setfiles -m -r target/ -c policy.32 file_contexts target/
>
> Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>

Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] policycoreutils: setfiles: do not restrict checks against a binary policy
  2020-07-07 15:43 ` Stephen Smalley
@ 2020-07-10 13:42   ` Petr Lautrbach
  0 siblings, 0 replies; 3+ messages in thread
From: Petr Lautrbach @ 2020-07-10 13:42 UTC (permalink / raw)
  To: SElinux list
  Cc: Antoine Tenart, Stephen Smalley, matthew.weber, thomas.petazzoni

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

On Tue, Jul 07, 2020 at 11:43:24AM -0400, Stephen Smalley wrote:
> On Tue, Jul 7, 2020 at 10:35 AM Antoine Tenart
> <antoine.tenart@bootlin.com> wrote:
> >
> > The -c option allows to check the validity of contexts against a
> > specified binary policy. Its use is restricted: no pathname can be used
> > when a binary policy is given to setfiles. It's not clear if this is
> > intentional as the built-in help and the man page are not stating the
> > same thing about this (the man page document -c as a normal option,
> > while the built-in help shows it is restricted).
> >
> > When generating full system images later used with SELinux in enforcing
> > mode, the extended attributed of files have to be set by the build
> > machine. The issue is setfiles always checks the contexts against a
> > policy (ctx_validate = 1) and using an external binary policy is not
> > currently possible when using a pathname. This ends up in setfiles
> > failing early as the contexts of the target image are not always
> > compatible with the ones of the build machine.
> >
> > This patch reworks a check on optind only made when -c is used, that
> > enforced the use of a single argument to allow 1+ arguments, allowing to
> > use setfiles with an external binary policy and pathnames. The following
> > command is then allowed, as already documented in the man page:
> >
> >   $ setfiles -m -r target/ -c policy.32 file_contexts target/
> >
> > Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
> 
> Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>
> 

Applied. Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-07-10 13:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-07 14:35 [PATCH v2] policycoreutils: setfiles: do not restrict checks against a binary policy Antoine Tenart
2020-07-07 15:43 ` Stephen Smalley
2020-07-10 13:42   ` Petr Lautrbach

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.