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 1tSDWq-00EwFz-E0 for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Dec 2024 11:01:45 +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 1tSDVq-00BaNF-Oj for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Dec 2024 11:00:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tSDVq-00BaLz-Aq for pgsql-hackers@lists.postgresql.org; Mon, 30 Dec 2024 11:00:42 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tSDVn-002Kpi-Ic for pgsql-hackers@lists.postgresql.org; Mon, 30 Dec 2024 11:00:41 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 4B8FB1BA4D3 for ; Mon, 30 Dec 2024 12:00:38 +0100 (CET) Received: from s979.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 3C4731BA8E7; Mon, 30 Dec 2024 12:00:38 +0100 (CET) Received: from s473.loopia.se (unknown [172.22.191.5]) by s979.loopia.se (Postfix) with ESMTP id 3A20710BC4B1; Mon, 30 Dec 2024 12:00:38 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s473.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s934.loopia.se ([172.22.191.5]) by s473.loopia.se (s473.loopia.se [172.22.190.13]) (amavisd-new, port 10024) with LMTP id E7KlLgyFp-FL; Mon, 30 Dec 2024 12:00:37 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s934.loopia.se (Postfix) with ESMTPSA id 99F517CEAA6; Mon, 30 Dec 2024 12:00:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1735556437; bh=tbKMd4AQ4oA7m1qpFGL1iRiHY6krPFCwGZBL9jiaHH8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=MirM9WMQBQ9X5lMlQUqF5LQANoZj7qhT4fYiukhyIT+3s55K+bss4bAmDbhcbg54w ScjxT0j2TuiKYhnq2vwlIOtTGtwo8GWSshXxKzlN4WwX6rL1tYjpbZeMaqjaFx/e0a El7ILnjQMrmOeTxbk9fQ7gfOkSRBPpehGdZKDWlmtyAcbkTP7Tl8NqfJzNh8xtzQ6E ehwgdtWgDRA/lY9Vv8H9S35F9h5y4b2eMAFKacDM9fyKKW+sXS3SPt2Q5PhYMFiHBy ICKv97PH1sr9PbQQdZgyfKKNmFmdmtMoB4brFuphBh3Nv2rEiyIeOB0I4s7fbZeLMM H2AX8FkP6oxZg== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) Subject: Re: Remove support for OpenSSL *eay32 libs on Windows From: Daniel Gustafsson In-Reply-To: Date: Mon, 30 Dec 2024 12:00:26 +0100 Cc: PostgreSQL Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <8BBBBAC0-1F1B-4CFC-8D5C-31B8D7EDBD4D@yesql.se> References: <3C445F8E-D43E-4970-9CD9-A54882197714@yesql.se> To: Michael Paquier X-Mailer: Apple Mail (2.3776.700.51.11.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 30 Dec 2024, at 02:24, Michael Paquier wrote: >=20 > On Fri, Dec 27, 2024 at 03:09:48PM +0100, Daniel Gustafsson wrote: >> The thread in [0] which adds Meson support for *eay32 OpenSSL library = names on >> Windows reminded me that we should remove these from master since we = no longer >> support OpenSSL 1.0.2 (which was the final version with those names). = Attached >> is a small (as of yet untested on Windows/autoconf) diff removing = these names >> from the Makefiles. >>=20 >> [0] = CAHrt6656W9OnFomQTHBGYDcM5CKZ7hcgzFt8L+N0ezBZfcN3zA@mail.gmail.com >=20 > Good idea, looks rather sane to me. Thanks for looking. > I don't have a clear idea about > the WIN32/autoconf combination (sorry!), but I can't really believe > that packagers of OpenSSL on Windows would want the same library name > compatibility, patching upstream to be able to achieve the old naming. I've never heard of anyone doing that, and it would only be additive = leaving the proper named files in place. > fairywren, hamerkop and drongo use meson. Lorikeet relies on > ./configure and builds with OpenSSL 3.0.12, so even there I would hope > that we are in the clear. All animals building HEAD would have to be well past the renaming since = we don't support version 1.0.2 there, so they should already be using the = new names. > Not something I'm planning to care about, just noting that from the > top of OpenSSL master branch (0958f5a5bc47 as of today): > $ git grep eay32 > .gitignore:/ms/libeay32.def > .gitignore:/ms/ssleay32.def Nice catch, they should indeed not be needed anymore. I can submit a PR = for it if you don't want to deal with setting up a CLA. -- Daniel Gustafsson