From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, SE Linux <selinux@tycho.nsa.gov>
Subject: Fix semodule option handling
Date: Thu, 11 Oct 2007 16:03:18 -0400 [thread overview]
Message-ID: <470E8186.2050307@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
semodule -B lksjdlj
will blow up.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHDoGGrlYvE4MpobMRAnWHAKCWIP/cHhbcwOjyc19RSqcvW2zAkACgscin
BYK2/vMCU9tpuZH2RB3NrJ4=
=lkqh
-----END PGP SIGNATURE-----
[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 972 bytes --]
diff --exclude-from=exclude --exclude=sepolgen-1.0.10 --exclude=gui --exclude=po -N -u -r nsapolicycoreutils/semodule/semodule.c policycoreutils-2.0.29/semodule/semodule.c
--- nsapolicycoreutils/semodule/semodule.c 2007-09-26 19:37:44.000000000 -0400
+++ policycoreutils-2.0.29/semodule/semodule.c 2007-10-11 15:59:39.000000000 -0400
@@ -249,11 +249,12 @@
* arguments as args. Will allow 'semodule -i *.pp' to
* work as expected.
*/
- if (commands[num_commands - 1].mode == INSTALL_M) {
+
+ if (commands && commands[num_commands - 1].mode == INSTALL_M) {
mode = INSTALL_M;
- } else if (commands[num_commands - 1].mode == UPGRADE_M) {
+ } else if (commands && commands[num_commands - 1].mode == UPGRADE_M) {
mode = UPGRADE_M;
- } else if (commands[num_commands - 1].mode == REMOVE_M) {
+ } else if (commands && commands[num_commands - 1].mode == REMOVE_M) {
mode = REMOVE_M;
} else {
fprintf(stderr, "unknown additional arguments:\n");
[-- Attachment #3: diff.sig --]
[-- Type: application/octet-stream, Size: 65 bytes --]
next reply other threads:[~2007-10-11 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 20:03 Daniel J Walsh [this message]
2007-10-12 3:16 ` Fix semodule option handling Joshua Brindle
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=470E8186.2050307@redhat.com \
--to=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.