All of lore.kernel.org
 help / color / mirror / Atom feed
From: mgrepl@redhat.com (Miroslav Grepl)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] New database object classes
Date: Tue, 18 Jan 2011 15:36:01 +0000	[thread overview]
Message-ID: <4D35B361.70109@redhat.com> (raw)
In-Reply-To: <4D35A20A.1020400@redhat.com>

On 01/18/2011 02:22 PM, Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/18/2011 01:03 AM, KaiGai Kohei wrote:
>> (2011/01/18 0:20), Daniel J Walsh wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 01/15/2011 07:48 AM, Kohei KaiGai wrote:
>>>>>> How about getting inclusion of this patch?
>>>>>>
>>>>>> These new object classes and corresponding rules are necessary
>>>>>> to run SE-PostgreSQL based on the upcoming v9.1.
>>>>>>
>>>>    :
>>>>> KaiGai, I believe we have your patches in Fedora and RHEL6, If not
>>>>> please ping me to add them.
>>>> I'm not certain about the latest RHEL6 policy, because I don't know
>>>> the way to reference its repository.
>>>> However, these new object classes are not included within the latest
>>>> Fedora policy right now. I checked it using "fedpkg co selinux-policy".
>>>> Do I see the same tree with you, don't I?
>>>>
>>>> Thanks,
>>> Please send me your latest patch.
>>>
>> The attached two are for RHEL6 and Fedora. These patches are made up
>> based on selinux-policy-3.7.19-29.el6 and  selinux-policy-3.9.12-7.fc15.
>>
>> Don't forget to add the following line in %fileList macro of the specfile
>>    %config %{_sysconfdir}/selinux/%1/contexts/sepgsql_contexts \
>>
>> Thanks,
> It looks like your stuff is now in
> selinux-policy-3.9.13-2.fc15
Yes, it should be there.

Regards,
Miroslav
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk01ogoACgkQrlYvE4MpobNSjACgmPqSmScrwalpoWA/zTtQiB8n
> /JIAoJQFKt9X/06JBWHQz/MPGFXhpJnV
> =qfaA
> -----END PGP SIGNATURE-----
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy

  reply	other threads:[~2011-01-18 15:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10  9:49 [PATCH] New database object classes KaiGai Kohei
2010-12-10  9:49 ` [refpolicy] " KaiGai Kohei
2010-12-10 12:18 ` Andy Warner
2010-12-10 12:18   ` Andy Warner
2010-12-10 12:59   ` KaiGai Kohei
2010-12-10 12:59     ` KaiGai Kohei
2011-01-14  6:19 ` KaiGai Kohei
2011-01-14  6:19   ` KaiGai Kohei
2011-01-14 14:03   ` Daniel J Walsh
2011-01-14 14:03     ` Daniel J Walsh
2011-01-15 12:48     ` Kohei KaiGai
2011-01-15 12:48       ` Kohei KaiGai
2011-01-17 15:20       ` Daniel J Walsh
2011-01-17 15:20         ` Daniel J Walsh
2011-01-18  6:03         ` KaiGai Kohei
2011-01-18  6:03           ` KaiGai Kohei
2011-01-18 14:22           ` Daniel J Walsh
2011-01-18 14:22             ` Daniel J Walsh
2011-01-18 15:36             ` Miroslav Grepl [this message]
2011-01-18 14:40               ` Kohei KaiGai
2011-01-18 14:40                 ` Kohei KaiGai
2011-01-18 16:00                 ` Daniel J Walsh
2011-01-18 16:00                   ` Daniel J Walsh
2011-01-14 15:41 ` Christopher J. PeBenito
2011-01-14 15:41   ` Christopher J. PeBenito

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=4D35B361.70109@redhat.com \
    --to=mgrepl@redhat.com \
    --cc=refpolicy@oss.tresys.com \
    /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.