[Dbconfig-common-devel] Read only access for all users to database

[Paul Gevers]

Hi

On 14-04-16 23:32, Kip Warner wrote:
> On Thu, 2016-04-14 at 22:34 +0200, Paul Gevers wrote:
>> dbconfig-common doesn't handle that, nor do I believe you should do 
>> that for any package in Debian. The database you are looking into may 
>> be on a different host and other system users of that system may have 
>> no business in the package database.
> 
> I should have clarified. The package in question is not the client
> application of the database, but actually hosts the database itself
> (depends on postgresql). It is responsible for providing the schema,
> teardown, etc. So we can assume that when the package is installed, it
> is done so on the same machine that is hosting it.

May I ask which features of dbconfig-common you are using than? And how
do you prevent dbconfig-common to do the wrong thing (installing on a
different host)? Aren't you better of handling this yourself (without
dbconfig-common)? I'll keep thinking about it.

> However, in the case of the client application, you are correct. The
> database could be anywhere. 
> 
> I am asking about how to give all system users on the machine hosting
> the database read access to it.

I'll think about it (not an PostgreSQL expert myself).

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20160415/48fcb7c8/attachment.sig>