mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2025-01-06 15:24:56 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add configurable option controlling security checks in LO functions.

Browse Source
This commit is contained in:
Tom Lane 1999-06-04 21:13:38 +00:00
parent 1c3c080534
commit 4cd4a54c80
2 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/backend/libpq/be-fsstubs.c
View File

@ -7,7 +7,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/libpq/be-fsstubs.c,v 1.34 1999/05/31 22:53:57 tgl Exp $
* $Header: /cvsroot/pgsql/src/backend/libpq/be-fsstubs.c,v 1.35 1999/06/04 21:13:38 tgl Exp $
*
* NOTES
* This should be moved to a more appropriate place. It is here
@ -334,10 +334,12 @@ lo_import(text *filename)
LargeObjectDesc *lobj;
Oid lobjOid;
#ifndef ALLOW_DANGEROUS_LO_FUNCTIONS
if (!superuser())
elog(ERROR, "You must have Postgres superuser privilege to use "
"server-side lo_import().\n\tAnyone can use the "
"client-side lo_import() provided by libpq.");
#endif
/*
* open the file to be read in
@ -405,10 +407,12 @@ lo_export(Oid lobjId, text *filename)
LargeObjectDesc *lobj;
mode_t oumask;
#ifndef ALLOW_DANGEROUS_LO_FUNCTIONS
if (!superuser())
elog(ERROR, "You must have Postgres superuser privilege to use "
"server-side lo_export().\n\tAnyone can use the "
"client-side lo_export() provided by libpq.");
#endif
/*
* open the inversion "object"

12
src/include/config.h.in
View File

@ -342,7 +342,7 @@ extern void srandom(unsigned int seed);
#undef USE_POSIX_SIGNALS
/*
* Code below this point should not require changes
* Pull in OS-specific declarations (using link created by configure)
*/
#include "os.h"
@ -494,6 +494,16 @@ extern void srandom(unsigned int seed);
*/
/* #define PSQL_ALWAYS_GET_PASSWORDS */
/*
* Define this if you want to allow the lo_import and lo_export SQL functions
* to be executed by ordinary users. By default these functions are only
* available to the Postgres superuser. CAUTION: these functions are
* SECURITY HOLES since they can read and write any file that the Postgres
* backend has permission to access. If you turn this on, don't say we
* didn't warn you.
*/
/* #define ALLOW_DANGEROUS_LO_FUNCTIONS */
/*
* Use btree bulkload code:
* this code is moderately slow (~10% slower) compared to the regular