From: KaiGai Kohei <kaigai@kaigai.gr.jp>
To: busybox@busybox.net, selinux@tycho.nsa.gov
Cc: rob@landley.net, dwalsh@redhat.com, russell@coker.com.au,
busybox@kaigai.gr.jp
Subject: [PATCH 2/8] busybox -- libselinux utilities applets
Date: Thu, 25 Jan 2007 23:44:02 +0900 [thread overview]
Message-ID: <45B8C232.8030001@kaigai.gr.jp> (raw)
In-Reply-To: <45B8C039.10907@kaigai.gr.jp>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
[2/8] busybox-libselinux-02-getenforce.patch
getenforce - get the current mode of SELinux.
SELinux has two mode. 'Enforcing' is the one, it enables
mandatory access control based on the security policy.
The other is 'Permissive' mode. It enables to evaluate
security policy and output audit messages, if violated.
But mandatory access control was not done. It was used
to debug policy.
Signed-off-by: Hiroshi Shinji <shiroshi@my.email.ne.jp>
Signed-off-by: KaiGai Kohei <kaigai@kaigai.gr.jp>
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
[-- Attachment #2: busybox-libselinux-02-getenforce.patch --]
[-- Type: text/x-patch, Size: 847 bytes --]
Index: selinux/getenforce.c
===================================================================
--- selinux/getenforce.c (revision 0)
+++ selinux/getenforce.c (revision 0)
@@ -0,0 +1,40 @@
+/*
+ * getenforce
+ *
+ * Based on libselinux 1.33.1
+ * Port to BusyBox Hiroshi Shinji <shiroshi@my.email.ne.jp>
+ *
+ */
+
+#include "busybox.h"
+#include <unistd.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <selinux/selinux.h>
+
+int getenforce_main(int argc, char **argv)
+{
+ int rc;
+
+ rc = is_selinux_enabled();
+ if (rc < 0) {
+ bb_error_msg("is_selinux_enabled() failed");
+ return 2;
+ }
+ if (rc == 1) {
+ rc = security_getenforce();
+ if (rc < 0) {
+ bb_error_msg("getenforce() failed");
+ return 2;
+ }
+
+ if (rc)
+ puts("Enforcing");
+ else
+ puts("Permissive");
+ } else {
+ puts("Disabled");
+ }
+
+ return 0;
+}
next prev parent reply other threads:[~2007-01-25 14:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 14:35 [PATCH 0/8] busybox -- libselinux utilities applets KaiGai Kohei
2007-01-25 14:44 ` KaiGai Kohei [this message]
[not found] ` <200701270054.34561.vda.linux@googlemail.com>
2007-01-29 13:47 ` [PATCH 2/8] " KaiGai Kohei
2007-01-25 14:44 ` [PATCH 3/8] " KaiGai Kohei
2007-01-25 14:44 ` [PATCH 4/8] " KaiGai Kohei
[not found] ` <200701270059.34996.vda.linux@googlemail.com>
2007-01-29 14:06 ` KaiGai Kohei
[not found] ` <20070130092817.GA32212@aon.at>
2007-01-31 12:13 ` [busybox:00323] " KaiGai Kohei
2007-01-25 14:44 ` [PATCH 5/8] " KaiGai Kohei
2007-01-26 20:10 ` Christopher J. PeBenito
2007-01-29 12:28 ` Russell Coker
2007-01-29 14:44 ` KaiGai Kohei
2007-01-25 14:44 ` [PATCH 6/8] " KaiGai Kohei
2007-01-25 14:45 ` [PATCH 7/8] " KaiGai Kohei
[not found] ` <200701270050.27149.vda.linux@googlemail.com>
2007-01-29 13:43 ` KaiGai Kohei
2007-01-25 14:45 ` [PATCH 8/8] " KaiGai Kohei
2007-01-26 15:29 ` [PATCH 0/8] " KaiGai Kohei
2007-01-29 17:38 ` James Carter
2007-01-26 19:36 ` Christopher J. PeBenito
2007-01-29 13:31 ` KaiGai Kohei
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=45B8C232.8030001@kaigai.gr.jp \
--to=kaigai@kaigai.gr.jp \
--cc=busybox@busybox.net \
--cc=busybox@kaigai.gr.jp \
--cc=dwalsh@redhat.com \
--cc=rob@landley.net \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/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.