Re: glob support in extension_control_path/dynamic_library_path? - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: glob support in extension_control_path/dynamic_library_path?
Date
Msg-id CAN4CZFMsqRGZ=P-axY_LeeLyRNvj9R6GPF1skL=SjEtB=bJyhQ@mail.gmail.com
Whole thread
In response to Re: glob support in extension_control_path/dynamic_library_path?  ("David E. Wheeler" <david@justatheory.com>)
List pgsql-hackers
> What’s the disadvantage, exactly? Sure, an attacker could stick a new directory in the wild-carded path and it will
suddenlybe available, but they can also just stick a dynamic library in any directory in a dynamic_library_path and
it’llbe available. How is a wild carded directory worse than the current wildcarding, essentially, of DSOs and control
files?

My main concern is observability: if you have a single directory, or a
list of directories, it is clearly visible, it is relatively easy to
argue about who can create files where. When we start adding wildcards
anywhere on the path, and we can also have symlinks anywhere, it gets
more difficult.

Providing admins a way to see the currently active paths, and also
possibly making it fixed between config reloads could mitigate most of
that.



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Small patch to improve safety of utf8_to_unicode().
Next
From: Sami Imseih
Date:
Subject: Re: [PATCH] COPY TO FORMAT json: respect column list order