Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nuYgq-0002fN-U7 for pgsql-hackers@arkaria.postgresql.org; Fri, 27 May 2022 12:03:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nuYgp-0002jg-RR for pgsql-hackers@arkaria.postgresql.org; Fri, 27 May 2022 12:03:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nuYgp-0002jX-I3 for pgsql-hackers@lists.postgresql.org; Fri, 27 May 2022 12:03:35 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nuYgg-0003SC-TV for pgsql-hackers@postgresql.org; Fri, 27 May 2022 12:03:35 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 5708B5C0162; Fri, 27 May 2022 08:03:24 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 27 May 2022 08:03:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1653653004; x= 1653739404; bh=2RiJkv4fX5MunZ5V0XpXbuvPaIXveNHHdOAgGnW5gOU=; b=i 2nLalFwXaRJ+SKjtmJJZ4ndgcdlR9mTIieGYr/oVNKLO77qVur1sf4jyukjl1blo kjJNIsK7PWtCOpGqb5FaupOY9/Oac11YQDfOllZdLdJAzaiPN0DALlLPM89QmDEH 90xd1MS4UeNGkLRYmFQY6UEf6eAqXeoavI5Xcf44bbbZ5TjJ0y3fF32sOh9BUQVz 5UrTQWHlTR4EQUaHj3lcW+9i5p1CWfhwh/970BdADyrQiBvzNODVv9D5Scd7/5la oJnaZqRxKSljuNcS4raYScPw+g0nVbf6ElHnF+Un5OV3m4nCCGB+nfGv6qjQw0mm 08c/LIanEXGzAgwLb9ZiQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeelgdegjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheelffeggedujeetiefh leetuddvieffhfffvdejvdffgeejkeduleduheduieefnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 27 May 2022 08:03:22 -0400 (EDT) Message-ID: <849661f1-85a3-2833-5477-059a9b58e70f@enterprisedb.com> Date: Fri, 27 May 2022 14:03:21 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: allow building trusted languages without the untrusted versions Content-Language: en-US To: Nathan Bossart , Robert Haas Cc: Tom Lane , "pgsql-hackers@postgresql.org" References: <571753.1653092411@sss.pgh.pa.us> <20220523165403.GC938919@nathanxps13> <1290329.1653326228@sss.pgh.pa.us> <1333860.1653338790@sss.pgh.pa.us> <1354561.1653345768@sss.pgh.pa.us> <20220524172851.GA1191690@nathanxps13> <20220524205841.GA1254661@nathanxps13> From: Peter Eisentraut In-Reply-To: <20220524205841.GA1254661@nathanxps13> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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.