From: | "Klaus Reger" <K(dot)Reger(at)twc(dot)de> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: import/export of large objects on server-side |
Date: | 2001-11-02 09:40:11 |
Message-ID: | 64124.193.158.34.193.1004694011.squirrel@emailbox24.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Klaus Reger <K(dot)Reger(at)twc(dot)de> writes:
>> at the moment import/export of large objects on server-side only can
>> be activated for all users by editing config.h due to security
>> reasons. My idea is, to enable in for everyone, when using s apecial
>> directory (e.g. /tmp). What do you think about this?
>
> It'd still be a security hole, and not significantly smaller (consider
> symlinks).
>
> Use the client-side LO import/export functions, instead.
ok, i've read the config.h and the sources. I agree that this can be a
security hole. But for our application we need lo-access from
PL/PGSQL-Procedures (explicitly on the server). We have to check out
documents, work with them and then check the next version in.
Whats about an configuration-file entry, in the matter
LO_DIR=/directory or none (which is the default).
For our product we want to be compatible with the original sources of Pg,
avoiding own patches in every new version.
What do you think about this idea? Do you have any other suggestions for
serverside lo-ing, without granting every user superuser-privileges?
Regards, Klaus
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-11-02 12:47:25 | Re: compiler warnings in ODBC |
Previous Message | Philip Warner | 2001-11-02 09:16:24 | Re: Another planner/optimizer question... |