Commitb28a064

committed

revert "warn of SECURITY DEFINER schemas for non-sql_body funcs"

doc revert of commit1703726. Change was applied to irrelevantbranches, and was not detailed enough to be helpful in relevantbranches.Reported-by: Peter Eisentraut, Noah MischDiscussion:https://postgr.es/m/a2dc9de4-24fc-3222-87d3-0def8057d7d8@enterprisedb.comBackpatch-through: 10

1 parentc0c2a9b commitb28a064Copy full SHA for b28a064

File tree

-4

lines changed

-4

lines changed

Lines changed: 1 addition & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -753,10 +753,7 @@ SELECT * FROM dup(42);`
`753`	`753`	`<para>`
`754`	`754`	`Because a <literal>SECURITY DEFINER</literal> function is executed`
`755`	`755`	`with the privileges of the user that owns it, care is needed to`
`756`		`- ensure that the function cannot be misused. This is particularly`
`757`		`- important for non-<replaceable>sql_body</replaceable> functions because`
`758`		`- their function bodies are evaluated at run-time, not creation time.`
`759`		`- For security,`
	`756`	`+ ensure that the function cannot be misused. For security,`
`760`	`757`	`<xref linkend="guc-search-path"> should be set to exclude any schemas`
`761`	`758`	`writable by untrusted users. This prevents`
`762`	`759`	`malicious users from creating objects (e.g., tables, functions, and`

Comments

(0)