[Bug 249522] Review Request: sepostgresql - Security-Enhanced PostgreSQL

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request:  sepostgresql - Security-Enhanced PostgreSQL


https://bugzilla.redhat.com/show_bug.cgi?id=249522





------- Additional Comments From kaigai at kaigai.gr.jp  2007-08-29 01:49 EST -------
(In reply to comment #58)
> I wonder if it'd be feasible to hide the sepostgres add-on data into
> the t_hoff padding, the way OIDs have been handled the last few releases?
> It's a bit of a long shot, but otherwise we're going to have a real hard 
> time with binary dependencies.

In SE-PostgreSQL, all tuples have a its security attribute without any 
exception,
and I made a decision it's not necessary this field with flexible length.
It is the reason why I didn't use t_hoff padding to store security attribtue.

Your suggestion seems to me fine enough. However, I hesitate to apply it onto
the 8.2.x based SE-PostgreSQL now, because this change affects so wide range.
I want this change to be queued for 8.3.x based SE-PostgreSQL.

In the current version, I believe that installing se- version module into
"/usr/lib/sepgsql" is the best way to enhance its functionality.

Thanks,

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.