On Thu, Mar 28, 2013 at 12:33 PM, Kohei KaiGai wrote:
> Thanks for your checking.
>
> I doubt of whether security policy module for this regression test is not
> installed on your test environment.
Ah, you are right. Sorry for the noise.
Committed.
--
Robert Haas
EnterpriseDB: http://www.ente
Thanks for your checking.
I doubt of whether security policy module for this regression test is not
installed on your test environment.
Could you try ./test_sepgsql after:
$ make -f /usr/share/selinux/devel/Makefile clean
$ make -f /usr/share/selinux/devel/Makefile
$ sudo semodule -i sepgsql
On Wed, Mar 27, 2013 at 8:41 AM, Robert Haas wrote:
> Based on KaiGai's analysis, it seems to me that there is no serious
> problem here in terms of versioning, and as this patch represents a
> small but useful step forward in our support for SELinux integration,
> I'd like to go ahead and push it
On Fri, Jan 25, 2013 at 10:29 AM, Kohei KaiGai wrote:
> I asked folks of Debian-JP how and when does package maintainer
> pushes new versions. Usually, new versions shall be pushed to
> unstable branch, then testing and stable. But it is now feature freeze
> period thus it is prohibited to push ne
2013/1/25 Kohei KaiGai :
> 2013/1/24 Magnus Hagander :
>> On Thu, Jan 24, 2013 at 10:11 AM, Kohei KaiGai wrote:
>>> 2013/1/24 Tom Lane :
John R Pierce writes:
> On 1/23/2013 8:32 PM, Tom Lane wrote:
>> FWIW, in Fedora-land I see: ...
> I'd be far more interested in what is i
2013/1/24 Magnus Hagander :
> On Thu, Jan 24, 2013 at 10:11 AM, Kohei KaiGai wrote:
>> 2013/1/24 Tom Lane :
>>> John R Pierce writes:
On 1/23/2013 8:32 PM, Tom Lane wrote:
> FWIW, in Fedora-land I see: ...
>>>
I'd be far more interested in what is in RHEL and CentOS.Fedora,
On Thu, Jan 24, 2013 at 10:11 AM, Kohei KaiGai wrote:
> 2013/1/24 Tom Lane :
>> John R Pierce writes:
>>> On 1/23/2013 8:32 PM, Tom Lane wrote:
FWIW, in Fedora-land I see: ...
>>
>>> I'd be far more interested in what is in RHEL and CentOS.Fedora,
>>> with its 6 month obsolescence cycle,
2013/1/24 Tom Lane :
> John R Pierce writes:
>> On 1/23/2013 8:32 PM, Tom Lane wrote:
>>> FWIW, in Fedora-land I see: ...
>
>> I'd be far more interested in what is in RHEL and CentOS.Fedora,
>> with its 6 month obsolescence cycle, is of zero interest to me for
>> deploying database servers.
>
John R Pierce writes:
> On 1/23/2013 8:32 PM, Tom Lane wrote:
>> FWIW, in Fedora-land I see: ...
> I'd be far more interested in what is in RHEL and CentOS.Fedora,
> with its 6 month obsolescence cycle, is of zero interest to me for
> deploying database servers.
But of course Fedora is als
On 1/23/2013 8:32 PM, Tom Lane wrote:
FWIW, in Fedora-land I see:
F16: 2.1.6 (F16 will go out of support next month)
F17: 2.1.10 (F17 has been stable for 6+ months)
F18: 2.1.12 (F18 just went stable)
While requiring 2.1.10 today might be thought a tad leading-edge,
will that still
Heikki Linnakangas writes:
> On 17.01.2013 23:20, Kohei KaiGai wrote:
>> In addition, I forgot to update minimum required version for libselinux;
>> (it also takes change in configure script).
> libselinux1 2.1.10 or newer is a pretty tall order. That's not in debian
> testing yet, for example.
On 17.01.2013 23:20, Kohei KaiGai wrote:
2013/1/16 Robert Haas:
This looks OK on a quick once-over, but should it update the
documentation somehow?
Documentation does not take so much description for type_transition
rules, so I just modified relevant description a bit to mention about
type_tra
2013/1/16 Robert Haas :
> On Tue, Jan 15, 2013 at 3:02 PM, Kohei KaiGai wrote:
>> This patch adds sepgsql the feature of name qualified creation label.
>>
>> Background, on creation of a certain database object, sepgsql assigns
>> a default security label according to the security policy that has
On Tue, Jan 15, 2013 at 3:02 PM, Kohei KaiGai wrote:
> This patch adds sepgsql the feature of name qualified creation label.
>
> Background, on creation of a certain database object, sepgsql assigns
> a default security label according to the security policy that has a set of
> rules to determine
This patch adds sepgsql the feature of name qualified creation label.
Background, on creation of a certain database object, sepgsql assigns
a default security label according to the security policy that has a set of
rules to determine a label of new object.
Usually, a new object inherits its paren
15 matches
Mail list logo
