PostgreSQL PITR & SELinux

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/18/2012 06:03 PM, Dmitry Makovey wrote:
> Hi Dominick,
> 
> thanks for your reply, see responses below:
> 
> On September 18, 2012 22:31:02 Dominick Grift wrote:
>> On Tue, 2012-09-18 at 13:32 -0600, Dmitry Makovey wrote:
>>> What I really wander about is - above I've opened up quite a few
>>> things that are very specific to this mode of operation, however I
>>> can't believe I'm in a situation nobody else have been before and there
>>> are no booleans/tunables for most of things outlined above. So is there
>>> a way to make above utilize existing hooks or is it "as good as it
>>> gets"?
>> 
>> Hi
>> 
>> This actually looks pretty good in this case and well suited for a 
>> boolean in the postgresql policy in my opinion.
> 
> good to know it's not just me who thinks that way :)
> 
>> Currently this is indeed not supported by the policy it seems.
>> 
>> Why not file a bugzilla report as a feature request?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=858406
> 

How about this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBaGAcACgkQrlYvE4MpobORjACdEDRLaAvGyDiJzoVqYgA2BF7J
fMwAni+1cQty4eNSDR0r1UtdHO6dw5VQ
=aiRn
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postgresql_replication.patch
Type: text/x-patch
Size: 1003 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/selinux/attachments/20120919/3916a2ea/attachment.bin>