All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	"Christopher J. PeBenito" <cpebenito@tresys.com>,
	SE Linux <selinux@tycho.nsa.gov>
Subject: Re: More  small fixes to policycoreutils
Date: Mon, 20 Nov 2006 15:14:07 -0500	[thread overview]
Message-ID: <45620C8F.2040002@mentalrootkit.com> (raw)
In-Reply-To: <4561F3EA.8020603@tresys.com>

Joshua Brindle wrote:
> Daniel J Walsh wrote:
>> audit2allow was not generating reference policy correctly.  This 
>> patches fixes this and uses /usr/share/sleinux/devel/Makefile to 
>> create policy packages.
>>
> 
> This is distro specific, audit2allow should be using /etc/selinux/config 
> to find the interface directory to use. Further, why is this needed at all?
> 

Not certain that /usr/share/selinux/targeted/include is any more general 
in reality. There is nothing stopping a distro from installing headers 
in different locations.

>  > run_init needs to call pam_acct_mgmt, so that pam_tally will work
>  > correctly.
>  >
> 
> What is pam_tally and what does the call to pam_acct_mgmt do, and how 
> does it affect run_init?
> 
>  > Also after modifying translations the mcstrans needs to be signaled.
>  >
>  > (I think it is time we break the mcstrans code out into a separate
>  > script, maybe executed by semanage, which would allow us to write
>  > tighter policy around this object and semanage.)
> 
> Its interesting that semanage manages something that is redhat specific 
> and not part of the upstream utilities at all.. IMO this should never 
> have been merged in the first place, semanage manages libsemanage 
> abstractions, if translations were a part of libsemanage it'd be a 
> different story.
> 

Why isn't setrans upstream?

>> Lastly are you going to merge the translations?
>> http://people.redhat.com/dwalsh/SELinux/pocicycoreutils-po.patch
>>
>>
> 
> It can be merged when a revised patchset does.
> 
> p.s. please please inline patches and make them apply from the top of 
> the tree with -p1 or -p0 :)
> 
>> @@ -204,7 +206,8 @@
>>          os.write(fd, self.out())
>>          os.close(fd)
>>          os.rename(newfilename, self.filename)
>> -
>> +                os.system("/sbin/service mcstrans reload > /dev/null")
>> +                
> 
> This is very distro specific and totally inappropriate IMO.
> 

Agreed - what is the solution, though?

Karl


--
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.

  reply	other threads:[~2006-11-20 20:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 15:06 Multiple small fixes to policycoreutils Daniel J Walsh
2006-11-14 16:13 ` Christopher J. PeBenito
2006-11-14 16:18   ` Daniel J Walsh
2006-11-14 19:19     ` Christopher J. PeBenito
2006-11-14 20:09       ` Daniel J Walsh
2006-11-15 18:34         ` Karl MacMillan
2006-11-15 19:38           ` Joshua Brindle
2006-11-15 20:16             ` Daniel J Walsh
2006-11-15 20:18               ` Joshua Brindle
2006-11-15 22:01               ` Karl MacMillan
2006-11-16  0:05                 ` Joshua Brindle
2006-11-16 22:15                   ` Karl MacMillan
2006-11-17  0:50                     ` Joshua Brindle
2006-11-17 12:02                     ` Daniel J Walsh
2006-11-20 17:10                       ` Karl MacMillan
2006-11-20 17:36                         ` More " Daniel J Walsh
2006-11-20 18:28                           ` Joshua Brindle
2006-11-20 20:14                             ` Karl MacMillan [this message]
2006-11-20 20:25                               ` Stephen Smalley
2006-11-21  3:54                                 ` Joshua Brindle
2006-11-21 14:35                                   ` Karl MacMillan
2006-11-21 14:37                                 ` Karl MacMillan
2006-11-20 21:58                             ` Daniel J Walsh
2006-11-21 13:53                               ` Stephen Smalley
2006-11-22 19:16                                 ` Daniel J Walsh
2006-11-22 19:22                                   ` Joshua Brindle
2006-11-22 20:05                                     ` Daniel J Walsh
2006-11-22 20:31                                       ` Joshua Brindle
2006-11-22 21:21                                         ` Daniel J Walsh
2006-11-28 19:37                                           ` Joshua Brindle
2006-11-29 21:18                                           ` Joshua Brindle
2006-11-22 20:06                                     ` Daniel J Walsh
2006-11-22 20:34                                       ` Joshua Brindle
2006-11-22 21:10                                         ` Daniel J Walsh
2006-11-22 20:07                                     ` Daniel J Walsh
2006-11-22 20:35                                       ` Joshua Brindle
2006-11-22 20:08                                     ` Daniel J Walsh
2006-11-22 20:36                                       ` Joshua Brindle
2006-11-22 20:10                                     ` Daniel J Walsh
2006-11-22 20:36                                       ` Joshua Brindle
2006-11-22 21:07                                         ` Daniel J Walsh
2006-11-27 13:39                                           ` Joshua Brindle
2006-11-21 21:13                           ` Stephen Smalley
2006-11-15 16:13 ` Multiple " 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=45620C8F.2040002@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.com \
    --cc=cpebenito@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.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.