"Joe Conway" <[EMAIL PROTECTED]> writes: > See my last email... > > Consider a scenario like "package <x> uses <arbitrary function y in an > untrusted language z>". Exact same concerns arise.
Well arbitrary function may or may not actually do anything that needs to be restricted. If it does then yes the same concerns arise and the same conclusion reached. That users should be granted permission to execute it based on local policies. Certainly granting execute permission to public by default is a bad start in that regard. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
