| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allow building trusted languages without the untrusted versions |
| Date: | 2022-05-27 12:03:21 |
| Message-ID: | 849661f1-85a3-2833-5477-059a9b58e70f@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24.05.22 22:58, Nathan Bossart wrote:
> FWIW this was my original thinking. I can choose to build/install
> extensions separately, but when it comes to PL/Tcl and PL/Perl, you've
> got to build the trusted and untrusted stuff at the same time, and the
> untrusted symbols remain even if you remove the control file and
> installation scripts. Of course, this isn't a complete solution for
> removing the ability to do any sort of random file system access, though.
This only makes sense to me if you install directly from the source tree
to your production installation. Presumably, there is usually a
packaging step in between. And you can decide at that point which files
to install or not to install.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2022-05-27 12:22:34 | Re: doc: CREATE FOREIGN TABLE .. PARTITION OF .. DEFAULT |
| Previous Message | Laurenz Albe | 2022-05-27 12:02:24 | Re: Prevent writes on large objects in read-only transactions |