gh-109396: Fix test_socket.test_hmac_sha1() in FIPS mode

[vstinner]

Use a longer key: FIPS mode requires at least of at least 112 bits. The previous key was only 32 bits.

• Issue: test_socket.LinuxKernelCryptoAPI.test_hmac_sha1() fails on "AMD64 RHEL8 FIPS Only Blake2 Builtin Hash 3.x" buildbot #109396

[vstinner]

I tested manually that the change fix test_socket on the affected RHEL8 FIPS buildbot:

[vstinner@python-builder-rhel8-fips cpython]$ cat /proc/sys/crypto/fips_enabled
1

[vstinner@python-builder-rhel8-fips cpython]$ ./python -m test test_socket -v -m test_hmac_sha1
== CPython 3.13.0a0 (heads/main:d7dc3d9, Sep 14 2023, 16:42:17) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)]
== Linux-4.18.0-477.21.1.el8_8.x86_64-x86_64-with-glibc2.28 little-endian
(...)
Total tests: run=1 (filtered)
Total test files: run=1/1 (filtered)
Result: SUCCESS

[vstinner]

By the way, this buildbot is running:

[vstinner@python-builder-rhel8-fips cpython]$ uname -r
4.18.0-477.21.1.el8_8.x86_64

[vstinner@python-builder-rhel8-fips cpython]$ cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.8 (Ootpa)

[miss-islington]

Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖

[bedevere-app]

GH-109426 is a backport of this pull request to the 3.12 branch.

[bedevere-app]

GH-109427 is a backport of this pull request to the 3.11 branch.

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL7 LTO 3.x has failed when building commit e091b9f.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/402/builds/5396) and take a look at the build logs.
4. Check if the failure is related to this commit (e091b9f) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/402/builds/5396

Failed tests:

• test.test_asyncio.test_subprocess

Failed subtests:

• test_subprocess_consistent_callbacks - test.test_asyncio.test_subprocess.SubprocessThreadedWatcherTests.test_subprocess_consistent_callbacks

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/test/test_asyncio/test_subprocess.py", line 788, in test_subprocess_consistent_callbacks
    self.loop.run_until_complete(main())
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/asyncio/base_events.py", line 664, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/test/test_asyncio/test_subprocess.py", line 780, in main
    self.assertEqual(events, [
AssertionError: Lists differ: ['process_exited', ('pipe_data_received', 1, b'stdout')] != [('pipe_data_received', 1, b'stdout'), ('p[95 chars]ted']

[vstinner]

The affected buildbot turned green (success): https://buildbot.python.org/all/#/builders/469/builds/6002 :-) It is the first time that it becomes green for a long time. It was failing for at least 3 weeks, but it's likely that it was never green.