Groups > linux.debian.maint.python > #17513

Re: hashlib and sha384

Path	csiph.com!weretis.net!feeder8.news.weretis.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From	Andrey Rakhmatullin <wrar@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: hashlib and sha384
Date	Sun, 31 May 2026 16:40:01 +0200
Message-ID	<N0Pux-9hHl-3@gated-at.bofh.it> (permalink)
References	<N0JS9-9dZ8-1@gated-at.bofh.it> <N0K1P-9e2F-3@gated-at.bofh.it> <N0Klc-9eqb-7@gated-at.bofh.it> <N0KOe-9eAb-7@gated-at.bofh.it> <N0MwF-9fLu-5@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Sun May 31 14:35:39 2026
Old-Return-Path	<wrar@debian.org>
X-Amavis-Spam-Status	No, score=-10 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, 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="bodDKlNHat2NDfU1"
Content-Disposition	inline
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/23797
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/ahxHKXn4OfbG_L2P@belkar.wrar.name
Approved	robomod@news.nic.it
Lines	56
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Sun, 31 May 2026 19:35:21 +0500
X-Original-Message-ID	<ahxHKXn4OfbG_L2P@belkar.wrar.name>
X-Original-References	<d09fc8cb-18d6-4148-b5dd-bd0834893db2@debian.org> <ahv0HIVleOvoYTa6@belkar.wrar.name> <2fed898a-280d-4f88-b6f8-c2bbbdb53e83@debian.org> <ahv_0Hbt1rgyU_j1@belkar.wrar.name> <fb19f303-14f0-4610-a2d9-cd297de9ebdd@debian.org>
Xref	csiph.com linux.debian.maint.python:17513

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

I can now repdocue and somewhat minimize it but I didn't find the reason.

How to reproduce it: 
1. Get python-xmlsec 1.3.17-2 (currently in incoming).
2. Add B-D: libxmlsec1-dev (= 1.3.11-1) (currently in experimental, so 
adjust your build command accordingly).
3. Add B-D: python3-pytest-arraydiff.
4. Build.

None of python3-pytest-arraydiff is actually needed for this, you can 
replace all of /usr/lib/python3/dist-packages/pytest_arraydiff/plugin.py 
with "import hashlib".

And the failing test is test_init_shutdown_module in tests/test_xmlsec.py 
which does "xmlsec.init(); xmlsec.shutdown()" which (especially the 
comment in it) sounds like it *could* be problematic, whatever that 
actually does, if you want to use OpenSSL after it.

So it looks like three things are required: libxmlsec1-dev from experimental,
importing hashlib early enough, and running that test. This doesn't answer 
what to do though.

-- 
WBR, wRAR

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

hashlib and sha384 Rene Engelhard <rene@debian.org> - 2026-05-31 10:40 +0200
  Re: hashlib and sha384 Andrey Rakhmatullin <wrar@debian.org> - 2026-05-31 10:50 +0200
    Re: hashlib and sha384 Rene Engelhard <rene@debian.org> - 2026-05-31 11:10 +0200
      Re: hashlib and sha384 Andrey Rakhmatullin <wrar@debian.org> - 2026-05-31 11:40 +0200
        Re: hashlib and sha384 Rene Engelhard <rene@debian.org> - 2026-05-31 13:30 +0200
          Re: hashlib and sha384 Andrey Rakhmatullin <wrar@debian.org> - 2026-05-31 16:40 +0200

csiph-web