Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Andrey Rakhmatullin Newsgroups: linux.debian.maint.python Subject: Re: hashlib and sha384 Date: Sun, 31 May 2026 11:40:02 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun May 31 09:31:20 2026 Old-Return-Path: X-Amavis-Spam-Status: No, score=-8.5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, SUBENDNUM=2] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -3.5 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="H1j8grxXb7QeVWFq" Content-Disposition: inline X-Mailing-List: archive/latest/23795 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/ahv_0Hbt1rgyU_j1@belkar.wrar.name Approved: robomod@news.nic.it Lines: 67 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 31 May 2026 14:30:56 +0500 X-Original-Message-ID: X-Original-References: <2fed898a-280d-4f88-b6f8-c2bbbdb53e83@debian.org> Xref: csiph.com linux.debian.maint.python:17511 --H1j8grxXb7QeVWFq Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 31, 2026 at 11:07:08AM +0200, Rene Engelhard wrote: >>>=C2=A0File "/usr/lib/python3/dist-packages/hypothesis/internal/conjectur= e/utils.py", line 35, in calc_label_from_name >>>=C2=A0=C2=A0 hashed =3D hashlib.sha384(name.encode()).digest() >>>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ~~~~~= ~~~~~~~~~^^^^^^^^^^^^^^^ >>>_hashlib.UnsupportedDigestmodError: unsupported hash type sha384 >>> >>>happens. (for both 3.13 and 3.14) >>> >>>From what I read in https://docs.python.org/3/library/hashlib.html sha38= 4 should have been supported in python anyways and >>>xmlsec1s build has >>>checking for SHA384 support... yes >>>(if it even matters, python3s _hashlib doesn't use xmlsec..) >> >>Considering that sha384(b'').digest() works for me in sid Python you may = want to describe your environment better. E.g. do you have anything from ex= perimental installed (like the aforementioned openssl 4)? Is it a clean chr= oot? 1: >all kinds of build-depends of LO (and other packages) as in my standard sy= stemd-nspawn "working sid machine". > >(and yes, xmlsec1 from experimental, since that is the point of this test.= ,.. No, no openssl 4 yet.) 2: >Indeed it works in a clean deboostrap unstable + apt build-dep python-xmls= ec + add experimental=C2=A0 to s.l. + apt -t experimental libxmlsec1-dev ch= root... Are the only differences between 1 and 2 that 1 has some more build-deps=20 installed? That's weird. --=20 WBR, wRAR --H1j8grxXb7QeVWFq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJhBAABCgBLFiEEtf6ieDcfC1EgtGkao+OWn23e7IYFAmob/9AtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEKPjlp9t3uyG SB0P/Amd9jdyZgOmVSR7sOH4iOgunpajWnM3gUJNwmxxOq6CJ1OlawJ3S2A5oNk3 s7WLxXyZTanAiVvjkC9Hk6k5ShAoSoRzX8+dsI89fxd09XO5QeSdAGtpks/OLhWj BxyhP7sLkAWgQsisRRfjMsz8GPfQgZjE+QXgYp0mvGIYi54xzGcHVmTptumya1jh NwI+1WscEtVESs4t3vkvCfWGpFBB0Krymu6ayFcn/TJ3hTmlWnE7JJWbhQL4fAjY 7NMnanzRivQZLyKJ1aVAo7GV81X0ZSiwASI6ZbxBAiFKPONCG5j1KQ6OICw/QmSQ 06bWgIyRdhACkMb4eaHhVVqOsxXeNdK2wxT2FY803/rMGLBO4ossbb9IOLfhbJsc JIxFOLYgAYAW1DZ31dTEKorZgQ8D8ngfwR4NuIKNnMYsbaRvoQIeGg3YHaydQJce SYvD6mrdLdXHrZSPGoFZedqmK0o+etLV/1j4yZnMqVM0A2cOoMLl15FDsSb9z0Lj OdtCbb02YUGP3qhhcnMSCY8Mc2yXh3+15D+vPEdUirJnHh7yTRhE+yC483Kgv3Y+ P23PFgf9osH3OTpwVECdiew1ZO5SPe1Mzu6DVPJHs2hExAtUzAmsO+9Wom186t5b lK+cGfto2o+Ss4OIUILzLPoQ0v9AOtPbyGzM0J/m1xqMxDsJ =EPPF -----END PGP SIGNATURE----- --H1j8grxXb7QeVWFq--