Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

32-bit MinGW self test failures #768

Closed
noloader opened this issue Dec 27, 2018 · 1 comment
Closed

32-bit MinGW self test failures #768

noloader opened this issue Dec 27, 2018 · 1 comment
Labels

Comments

@noloader
Copy link
Collaborator

noloader commented Dec 27, 2018

It looks like 32-bit MinGW is failing self tests for LEA, SIMON, SPECK and SM4.

An example of a failure is shown below.

Testing SymmetricCipher algorithm SM4/ECB.
.....................
Testing SymmetricCipher algorithm SM4/CBC.
.......................
incorrectly encrypted: 9B195C61B03B3DF17F0A5C36C332A1A8EF265A6EB555E140D3BBF04EA
41B0FF3F333DB0EB42671ED22AF0000371DAA94B1ACD4BB7D5E362BE83A0A75253B529D70FE88FC3
1E4A2E25C525EFFD54AC8CF4F1346C2D68D77F3E7F7DE1575E30B4AEE95D4F9505FACC40925B642C
09160931FB3B5E062DD438DECFBEB005F7BFA6B
AlgorithmType: SymmetricCipher
Ciphertext: 7A97307CB8E9EACD703E6F9B518772AB2C7A0FA3F9FF61FBE8CE0896F10DA287E0CA
E7C276EC9E6713A692908284EEA0420CAC3B35C6D43594605CA637C7520CB6B7759FBE7660167C4C
08B337C4451B85890C3B354382C5721A555777474CDA0E0A82E623FEC9C0645CECD7A7FE7E5F499E
71E49DB83A1540448FC1B84BC06C
Comment: SM4-128(128)
IV: B09B187F7CCE25E94F534F06D8442796
Key: 5458876D02C39DB8458372E89CB3EF27
Name: SM4/CBC
Plaintext: 751579F1BB15910733507A4CC04CF00EAEFC3577EAD165F77F2CDF037B445CA4390B5
6EDF0F3832889828B613A785CA924D3259AD7E664186D2C88C01615B637D0796246AEBBA584AA374
6E10EEF436E73792CFEA40290260AE9BE1CABA919919F5AF3A2F7A2CE67912FD3464A564BF4D4374
895F0CE6AB91851F35A1CB197B9
Source: Botan 2.3 generated
Test: Encrypt

Test FAILED.
Skipping to next test.
......
Tests complete. Total tests = 51. Failed tests = 1.
@noloader noloader added the Bug label Dec 28, 2018
@noloader
Copy link
Collaborator Author

A retest this week on the same machine did not witness the problem.

I'm beginning to wonder if wires are getting crossed/wrong DLL's being used because I have this many environments:

  • Git Bash
  • MinGW-32
  • MinGW-64
  • Cygwin-32
  • Cygwin-64

I often see weird failures with Git Bash, like "resource unavailable" when performing a git pull. If I reboot the problem seems to clear itself. The problem seems to get worse when I try to run two or three of the terminals at once.

noloader added a commit that referenced this issue Jan 16, 2019
I also suspect this has something to do with GH #768 and several others
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant