aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-01-13 18:06:45 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-01-13 18:06:45 +0000
commit1564e92cea27a22ace7da635fe73fc23f96f8d4e (patch)
treec3cc191a5dd42f56c7b56e4405e98ebafa5d488d /src/backend/access/gist/gistget.c
parent4b3252c4b8533bacfe6b14d866d2cdae79574b1c (diff)
downloadpostgresql-1564e92cea27a22ace7da635fe73fc23f96f8d4e.tar.gz
postgresql-1564e92cea27a22ace7da635fe73fc23f96f8d4e.zip
Require the issuer of CREATE TYPE to own the functions mentioned in the
type definition. Because use of a type's I/O conversion functions isn't access-checked, CREATE TYPE amounts to granting public execute permissions on the functions, and so allowing it to anybody means that someone could theoretically gain access to a function he's not supposed to be able to execute. The parameter-type restrictions already enforced by CREATE TYPE make it fairly unlikely that this oversight is meaningful in practice, but still it seems like a good idea to plug the hole going forward. Also, document the implicit grant just in case anybody gets the idea of building I/O functions that might need security restrictions.
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions