From: Daniel J Walsh <dwalsh@redhat.com>
To: Chad Sellers <csellers@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Patch to semanage
Date: Wed, 12 Aug 2009 16:26:19 -0400 [thread overview]
Message-ID: <4A83256B.3090806@redhat.com> (raw)
In-Reply-To: <C6A89AF9.A9A88%csellers@tresys.com>
On 08/12/2009 04:14 PM, Chad Sellers wrote:
> On 7/17/09 6:10 AM, "Daniel J Walsh" <dwalsh@redhat.com> wrote:
>
>> Ok lets try the patch again.
>>
>> Added equal patch (spelled correctly.)
>> Beginning to add modules support to consolidate on one management command.
>> Eventually replace semodule/setsebool with semanage command.
>> Some white space fixing in seobject.py
>
> I'm looking at this patch now. There are a couple of changes that I believe
> are not part of the rest, but I wonder if you could verify this (and maybe
> tell me why they're here).
>
>> diff --git a/policycoreutils/semanage/seobject.py
>> b/policycoreutils/semanage/seobject.py
>> index 94bdf7f..5b94a0f 100644
>> --- a/policycoreutils/semanage/seobject.py
>> +++ b/policycoreutils/semanage/seobject.py
>> @@ -21,7 +21,7 @@
>> #
>> #
>>
>> -import pwd, grp, string, selinux, tempfile, os, re, sys
>> +import pwd, grp, string, selinux, tempfile, os, re, sys, stat
>> from semanage import *;
>> PROGNAME = "policycoreutils"
>> import sepolgen.module as module
>> @@ -273,6 +273,7 @@ class setransRecords:
>> (fd, newfilename) = tempfile.mkstemp('', self.filename)
>> os.write(fd, self.out())
>> os.close(fd)
>> + os.chmod(newfilename, os.stat(self.filename)[stat.ST_MODE])
>> os.rename(newfilename, self.filename)
>> os.system("/sbin/service mcstrans reload > /dev/null")
>>
> I'm guessing there was some problem with the permissions on setrans files?
Well the tool was not maintainng the permissions, But I believe we should just remove all handling of setrans records, since this stuff will not work with the latest code. semanage should no longer manage the translatetions.
>
>> @@ -983,7 +1027,7 @@ class portRecords(semanageRecords):
>> proto_str = semanage_port_get_proto_str(proto)
>> low = semanage_port_get_low(port)
>> high = semanage_port_get_high(port)
>> - ddict[(low, high)] = (ctype, proto_str, level)
>> + ddict[(low, high, proto_str)] = (ctype, level)
>> return ddict
>>
>> def get_all_by_type(self, locallist = 0):
>
> Was this just plain wrong before? I'm not familiar with this. Was there not
> a user before (and presumably there is one now)?
>
> Everything else seems to fall into one of your 3 categories above.
>
> Thanks,
> Chad
>
Yes this was a bug.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2009-08-12 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 20:11 Patch to semanage Daniel J Walsh
2009-07-16 17:57 ` Chad Sellers
2009-07-17 10:10 ` Daniel J Walsh
2009-08-12 20:14 ` Chad Sellers
2009-08-12 20:26 ` Daniel J Walsh [this message]
2009-08-12 21:09 ` Chad Sellers
2009-08-17 21:45 ` Chad Sellers
2009-08-18 21:35 ` Daniel J Walsh
2009-08-18 21:41 ` Chad Sellers
2009-08-18 22:09 ` Daniel J Walsh
2009-08-19 13:53 ` Joshua Brindle
2009-08-19 19:20 ` Daniel J Walsh
2009-08-19 19:35 ` Chad Sellers
2009-08-19 20:21 ` Daniel J Walsh
2009-08-27 20:48 ` Chad Sellers
2009-08-27 21:39 ` Daniel J Walsh
2009-08-31 21:24 ` Chad Sellers
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=4A83256B.3090806@redhat.com \
--to=dwalsh@redhat.com \
--cc=csellers@tresys.com \
--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.