* Gregory Stark (stark@enterprisedb.com) wrote:
> "Joe Conway" <mail@joeconway.com> writes:
> > 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.
Agreed, and regardless of the sysadmin doing x, y, or z, or what some
other package might be doing with untrusted languages, what matters here
is what we're doing and the functions we're providing. Best practice is
to disable functions by default which aren't safe & secure for users to
have access to.
If you know of any others in anything we're distributing, please point
them out. If there are some in related projects, point those out and
ask those projects to be careful with them and encourage them to disable
them by default.
Thanks,
Stephen