Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1whQOq-000DGg-03 for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Jul 2026 11:25:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1whQOn-006sXv-1f for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Jul 2026 11:25:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1whQOn-006sXl-0g for pgsql-hackers@lists.postgresql.org; Wed, 08 Jul 2026 11:25:05 +0000 Received: from ma03-relay.lansolnet.com ([176.95.46.36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1whQOl-000000008zc-2G9t for pgsql-hackers@postgresql.org; Wed, 08 Jul 2026 11:25:04 +0000 ARC-Authentication-Results: i=1; ma03.lansolnet.com 1; spf=pass reason=mailfrom (ip=194.126.198.214, headerfrom=nidsa.net) smtp.mailfrom=nidsa.net smtp.helo=mail.cloud4partner.com; ARC-Message-Signature: a=rsa-sha256; bh=CC+u1+nDawOK+apla/tmt36642+AFX3+B2tPaldr2pY=; c=relaxed/relaxed; d=hornetsecurity.com; h=from:to:date:subject:mime-version:; i=1; s=hse1; t=1783509898; b=hTz9IsSSh6Ix4guV7KLvFzkO8sZEsagbsW22PeRQFdAEFwnMky1no4V/xk2QMlNkDzH/M9ZU CxD12nBq1tKNoqDWT5U5KVZuoyoyvtKKbRHHaJCWob7LlmxE+mrPidon40LYZCFGQxv8Zh6uOjB 9CsoeAfmS8OgAfXNa6YiS5CjrhjzIdETCc6gNgzpGgtBc83V2CUtCffHOaw2YW7OzmSErt1XegD MXbauyxLuk8U8I1w++ZdJNzchQSjCmwrz+25cPi6f7iYXVszDIXJOJj/a9CrYgbsuqROlyzh+xJ gKBCnCW0gqiEWF+hpF4sRkH9Xn+VlE+i9uHKlSUmNTddQ== ARC-Seal: a=rsa-sha256; cv=none; d=hornetsecurity.com; i=1; s=hse1; t=1783509898; b=Goa8Qoy2yxaAfPeRkZzVSsiP3zOKHNOewCd/wrKplOvcBW/zSwMUOIbB1Xgsli1QLP94BDe3 mFbcv612+fujZFlIllO/Kud9SZgQ8Dtg4cP9qw5S2HV/G/REnF/h1Qgy1O69MAe3Kx2X/37dbGs Yc3hGahGrcwKZvDw5Bbpm2vO9M2jc90FQkYZLQ4vY3c49JSR9Xw27TOvxRyXo6u6U/h7NS38QlJ /iQYvOJPQ/9Qx5iZCSsEyJizBaoZJYxrJ1GO2m6BmBAWBJT8w2KYO5XIyPHOw1rBznhdAUqWdJH 4Zpt4KEwUUMKX04X9GpravhItRbToSRxhxz0RNGX+N3yA== Received: from unknown ([194.126.198.214]) by ma03; Wed, 08 Jul 2026 13:24:58 +0200 Received: from MBX200E.cloud4partner.com (192.168.8.234) by MBX200A.cloud4partner.com (192.168.8.230) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.2507.44; Wed, 8 Jul 2026 13:24:55 +0200 Received: from MBX200E.cloud4partner.com ([fe80::e4a1:818c:c1f9:8e28]) by MBX200E.cloud4partner.com ([fe80::e4a1:818c:c1f9:8e28%15]) with mapi id 15.01.2507.044; Wed, 8 Jul 2026 13:24:55 +0200 From: Hans Buschmann To: Matthias van de Meent CC: Peter Eisentraut , "pgsql-hackers@postgresql.org" Subject: AW: Increased SECURITY RISCS from omitting some compikler options when building PG with meson; e.g. -fcf-protection=full Thread-Topic: Increased SECURITY RISCS from omitting some compikler options when building PG with meson; e.g. -fcf-protection=full Thread-Index: AQHdDgvEBR5VR+6/dkmCjQqZoZnn3rZjX8sO///zlwCAACW3qA== Date: Wed, 8 Jul 2026 11:24:55 +0000 Message-ID: References: <01e60576b689490a9388b3d840f23cd8@nidsa.net> <9412859e22d74f218562a535a7271a40@nidsa.net>, In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.8.240] Content-Type: multipart/alternative; boundary="_000_f2761ed18e744f1993935c0e05aca2eenidsanet_" MIME-Version: 1.0 X-cloud-security-sender: buschmann@nidsa.net X-cloud-security-recipient: pgsql-hackers@postgresql.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on ma03 with D44BD1981F11 X-cloud-security-connect: unknown[194.126.198.214], TLS=1, IP=194.126.198.214 X-cloud-security: scantime:.5095 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_f2761ed18e744f1993935c0e05aca2eenidsanet_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello Matthias, Thank you for pointing me to the pg_config options. I didn't know and will = take a look. > If the normal user cannot handle compiler options, then should they > really be self-compiling PostgreSQL with custom compiler options, for > a platform that already has pre-compiled binary distributions? As already mentioned in my original post, there are some cases a "normal" u= ser (in my terminology it is a db responsible not experienced with C progra= mming practice) may use a manual recompile: - blocksize change - emergency patch: see current planet postgres: - test on beta versions of the OS - etc... https://www.credativ.de/blog/postgresql/replikations-deadlock-fehler-in-akt= uellen-postgres-versionen-14-16/ The user should be able to recompile the package (which is really very easy= with meson after some setup of developer packages) without deeper knowledg= e of C programming with the original configuration of the distribution. In production I use the binary distribution from PGDG and additionally comp= ile the latest/beta versions for a compatibility check. Best regards Hans Buschmann --_000_f2761ed18e744f1993935c0e05aca2eenidsanet_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello Matthias,


Thank you for pointing me to the pg_config options. I didn't know and wi= ll take a look.



> If the normal user cannot handle compile= r options, then should they
> really be self-compiling PostgreSQL with custom compiler options,= for
> a platform that already has pre-compiled binary distributions?
As already mentioned in my original post, there are some cases a "norm= al" user (in my terminology it is a db responsible not experienced wit= h C programming practice) may use a manual recompile:

- blocksize change
- emergency patch: see current planet postgres:
- test on beta versions of the OS
- etc...


The user should be able to recompile the package (= which is really very easy with meson after some setup of developer packages= ) without deeper knowledge of C programming with the original configuration= of the distribution.

In production I use the binary distribution from P= GDG and additionally compile the latest/beta versions for a compatibility c= heck.

Best regards

Hans Buschmann

--_000_f2761ed18e744f1993935c0e05aca2eenidsanet_--