Computer Enthusiastic writes:
> I have tried to build the putty_0.81-3 package using pbuilder.
[...]
> The build failed (the buildlog is attached as xz compressed file) with
> the following error runnning the ./test/cryptsuite.py python script:
[...]
> PUTTY_TESTCRYPT=./debian/build/testcrypt python3 ./test/cryptsuite.py
> /build/putty-0.81/test/testcrypt.py:311: SyntaxWarning: invalid escape
> sequence '\('
> '\(',
> /build/putty-0.81/test/testcrypt.py:312: SyntaxWarning: invalid escape
> sequence '\)'
> '\)',
> .....Segmentation fault (core dumped)
> EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
> ======================================================================
> ERROR: testAESGCMBlockBoundaries (__main__.crypt.testAESGCMBlockBoundaries)
> (aes_impl='sw', gcm_impl='clmul')
I suspect I know what this is.
This fault is in a cryptography self-test (testcrypt/cryptsuite).
The past few upstream releases of PuTTY, including 0.81, have had a
couple of bugs where if these crypto tests are run on a machine whose
processor doesn't support certain types of hardware crypto acceleration,
there can be a segfault
https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=a1d80e41ddc9fc7e280a9d7167533d33aee7cdae
and spurious test failures (the 'EEEEE' bit)
https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=5ced517428f57275c47a5b99b18fbdbba2105bb8
These bugs will be fixed in the next upstream release.
(This test is not strictly necessary to build PuTTY. I don't know enough
about pbuilder to know if there's a way to invoke it that bypasses this
test.)
(I think the SyntaxWarnings are unrelated, and probably fixed by
https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=22f8122b13e6c856aad9c8a76ace72d1f783dc2f
which will also be in the next release.)
