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.94.2) (envelope-from ) id 1vBjDB-0048ho-JQ for pgsql-bugs@arkaria.postgresql.org; Thu, 23 Oct 2025 00:29:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vBjDA-002PYu-FI for pgsql-bugs@arkaria.postgresql.org; Thu, 23 Oct 2025 00:29:47 +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.94.2) (envelope-from ) id 1vBjDA-002PYg-0K for pgsql-bugs@lists.postgresql.org; Thu, 23 Oct 2025 00:29:47 +0000 Received: from fhigh-b4-smtp.messagingengine.com ([202.12.124.155]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vBjD7-003Ffm-0w for pgsql-bugs@lists.postgresql.org; Thu, 23 Oct 2025 00:29:46 +0000 Received: from phl-compute-08.internal (phl-compute-08.internal [10.202.2.48]) by mailfhigh.stl.internal (Postfix) with ESMTP id 6B8CE7A0103; Wed, 22 Oct 2025 20:29:44 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-08.internal (MEProxy); Wed, 22 Oct 2025 20:29:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1761179384; x=1761265784; bh=TSQ9pRXDGK ZY8elgFrNc8IC8Q+BuFuP+iqC0wevofbQ=; b=pGNbjJPj4H9kRsq9TO3ptBZDUn 4E6gM59jxdggToZQjFDLWDIEEqnOunbf1wZ5sTC5W1UnNc+QaGSwZcAXMoYqm7G3 KOHYzQ6KB+uneKjGQXQ9q4qap2wTz127hrIulbWTyI6VV8BnyFw7iTSvRUEJjG6+ C3rLw2Jt6qIsxch2I6Tkarjetb9hbR22crxPz5TGfdyRgg493au+RL+EG8vGUcuV j/kBlj9CCNDJsonaSxZ9E99AxtbobE7LxttwYU7i1rHJ5+rF1v/J6C/WlpPVsjer NuTknYvwCULXjZDl2PWClevEMDdZcbo7M4nEZSMCMY7k4RjTp+9REoPMG5Aw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1761179384; x=1761265784; bh=TSQ9pRXDGKZY8elgFrNc8IC8Q+BuFuP+iqC 0wevofbQ=; b=mwnt5RB34qCdGn1jgSupNAUQzpzJ77CvVD2zk04VbD4i6uF3zM1 pkhDws9TfwO/7VINwd1FElzpRTToimynbYCUw5dX3RRoTL8KmFVTL5Lfi6O7owTn NHZHW37dEo/8M765NZ3Odrpj7Mc1p06kKGcFOQH8sJVrHfN37ZbMvVCPKATmHkfb jynJG9/d79MGtpv0pLehbzNKxmp+eGLRkt7wqaLKx1v2rGQdVgxQPj7jNgMhFiRa f+4cjPHOpMx46BMXN4lS4q+u1OOpvzg4LCfaAWKM0hOuntjx8FtzJTL/GUTdxC5x fzGiGd0gyexTEq4PIcw+gVHpbClDQoVh0hw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddugeehtdefucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegfrh hlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeggeeg fffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihiidp nhgspghrtghpthhtohepgedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepthhglh esshhsshdrphhghhdrphgrrdhushdprhgtphhtthhopegurghnihgvlheshigvshhqlhdr shgvpdhrtghpthhtohepudefleehvdekjeekjeelleesudeifedrtghomhdprhgtphhtth hopehpghhsqhhlqdgsuhhgsheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Oct 2025 20:29:42 -0400 (EDT) Date: Thu, 23 Oct 2025 09:29:19 +0900 From: Michael Paquier To: Tom Lane Cc: Daniel Gustafsson , 13952878799@163.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech Message-ID: References: <19092-b06adfd70ddcd2ab@postgresql.org> <64F1394B-E765-4291-91CF-E6CFE019D195@yesql.se> <494078.1761059179@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FknIUppCDToqiW0G" Content-Disposition: inline In-Reply-To: <494078.1761059179@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --FknIUppCDToqiW0G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Oct 21, 2025 at 11:06:19AM -0400, Tom Lane wrote: > We'd really need to see a concrete example to decide whether this is > a PG bug or user error. I think the SASL stuff is sufficiently poorly > tested that it could be a previously-unknown PG bug, but it's not clear. [ .. double-checking the code .. ] FWIW, I doubt that this is something we need to worry about and I suspect that there is no action item here. dblink and WAL receivers do their stuff so as the main backend code does not link with libpq, and I doubt that we'd ever want to enter in the territory where FRONTEND becomes a thing in libpq. Of course, I may prove wrong. > So: test case, please. Yes. -- Michael --FknIUppCDToqiW0G Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmj5dt8ACgkQnvQgOdby QH1+Yg//ZR6apGkntUof9VxQ7+8X7M0Spv1AinC8dG/Wd5EuE4E7EwVzDpmab5+D qXnkhyIUlT0VSfaCo3tdHDaalVBaEGK3b2+QrzzEqd1q2H4rM0lEmsb37OhoXMz+ diIcnzEzmRDS/eKZukUNiWEUzkoD/nv2Uuf8ko0P5GyLb3Zy2Bc9KGtw8C8nphyu oGC+c0wbFBF9+V9o6uTMq0z0/quAYlJCWyoCu//RcGLMKMC8JJjxLlMe+76F2WzT HYBQ/Pp+SeHD3DPExiHmXPhVQ9gMsr/MSfWr9gjbd+M0FDR7mZgFe+xZtk2qYBUR O1pzyF0Fy+ZiUkNJy3FDao0HWCCAUp0ARjRNAd8ru3G/ipkVbwLZ7UNQrS7ftU5f PF46pyvk2BiddD1k6KjeWAVYl0Wbw/vHoZAXp5oWHV3E6/5SvTBWTTNAaCkAo8WU riKqqNgAfSPnGoMDabEi9zn96ikfLH62Vqp5D8RJ05U4BpbSunvMqnlaghO8s5bw ZfnJKvvtS+3BqGOBMvLi4oDWLTAV+HKv6pC27rp0Cb41lDntPyvinmcRPuO3jKfw eul0p4GMJCC/NFuSbFPfsOPVCwOTuiiWJhXNAygJRw5AFYoU846jW9BRkU7hw2J3 uENHCiykhF+sj/5zEPKKrQkLtWc8KhvuoDTJzj3EmupSBg+B3Ts= =rgc8 -----END PGP SIGNATURE----- --FknIUppCDToqiW0G--