| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
The strategy of "cleanup under-aligned buffers" is not scaling well. Corner cases are still turing up. The library has some corner-case breaks, like old 32-bit Intels. And it still has not solved the AltiVec and Power8 alignment problems.
For now we are backing out the changes and investigating other strategies
|
| |
|
|
|
|
| |
These tests are effectively performed in MDC, SEAL and OldRandomPool
|
|
|
|
| |
Currently the CRYPTOPP_BOOL_XXX macros set the macro value to 0 or 1. If we remove setting the 0 value (the #else part of the expression), then the self tests speed up by about 0.3 seconds. I can't explain it, but I have observed it repeatedly.
This check-in prepares for the removal in Upstream master
|
|
|
|
|
|
|
|
|
|
| |
(ClCompile target) ->
validat1.cpp(1081): warning C4800: 'CryptoPP::word32' : forcing value to bool
'true' or 'false' (performance warning) [c:\Users\cryptopp\cryptest.vcxproj]
validat1.cpp(1090): warning C4800: 'CryptoPP::word32' : forcing value to bool
'true' or 'false' (performance warning) [c:\Users\cryptopp\cryptest.vcxproj]
validat1.cpp(1099): warning C4800: 'CryptoPP::word32' : forcing value to bool
'true' or 'false' (performance warning) [c:\Users\cryptopp\cryptest.vcxproj]
|
|
|
|
| |
The are configurations tests as recommended by Cryptography Research, Inc in their 2003 audit report
|
| |
|
| |
|
|
|
|
|
| |
#461)
Split source files to support Base Implementation + SIMD implementation
|
|
|
|
| |
Enums don't take up space in class objects. Its should result in smaller objects and faster code
|
| |
|
|
|
|
| |
This should tickle endianness issues
|
| |
|
|
|
|
| |
Users of OldRandomPool must use the new interface. All that means is they must call IncorporateEntropy instead of Put, and GenerateBlock instead of Get
|
|
|
|
|
|
|
|
| |
The existing interface still exists. The new interface is routed into the old methods. Without the new interface, using OldRandPool could result in:
$ ./cryptest.exe v
terminate called after throwing an instance of CryptoPP::NotImplemented
what(): RandomNumberGenerator: IncorporateEntropy not implemented
Aborted (core dumped)
|
|
|
|
| |
We still need to get the test result cross-validated
|
|
|
|
| |
This reverts commit c3871aec948013c1a4d5613050c659520f59e2e4.
|
|
|
|
| |
This reverts commit eb3b27a6a543. The change broke GCC 4.8 and unknown version of Clang on OS X. UB reported the OS X break, and JW found duplicated the break on a ARM CubieTruck with GCC 4.8.
|
| |
|
|
|
|
|
| |
They seemed to produce a hang when running self tests in AppVeyor.
Also use IsDebuggerPresent() to determine when we should call DebugBreak(). The OS killed our debug build when fuzzing caused an assert to fail
|
|
|
|
| |
Windows Phone
|
| |
|
|
|
|
| |
We have not been able to determine a reliable way to detect cpu's and platforms with Cmake. We are side stepping the Cmake problem by building rdrand.cpp all the time. If its not avilable for a cpu or platform, then RDRAND or RDSEED throw an exception.
|
|
|
|
| |
Whitespace check-in
|
| |
|
|
|
|
| |
The improved validation and excpetion clears the Address Sanitizer and Undefined Behavior Sanitizer findings
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Whitespace check-in
|
| |
|
|
|
|
| |
Fix Carmichael pseudo-prime tests
|
| |
|
| |
|
|
|
|
| |
Whitespace check-in
|
| |
|
| |
|
|
|
|
| |
The tests now include the first 10 elements of the sequence to ensure a properly implemented algorithm and endianess correctness.
|
| |
|
|
|
|
| |
CRYPTOPP_COVERAGE was added at 9614307ab7f4a4a4 to increase code coverage support. This commit enables additional validation routines when CRYPTOPP_COVERAGE is in effect.
|
|
|
|
|
|
| |
This is the reference implementation, test data and test vectors from the ARIA.zip package on the KISA website. The website is located at http://seed.kisa.or.kr/iwt/ko/bbs/EgovReferenceList.do?bbsId=BBSMSTR_000000000002.
We have optimized routines that improve Key Setup and Bulk Encryption performance, but they are not being checked-in at the moment. The ARIA team is updating its implementation for contemporary hardware and we would like to use it as a starting point before we wander too far away from the KISA implementation.
|
|
|
|
| |
Previous testing occurred with Visual Studio 2005 SP 1, and it lacks some of the Safe C++/security enhanced functions.
|
| |
|
| |
|
| |
|
| |
|
| |
|