65b10a4af8
Add additional XChaCha20/Poly1305 test vectors (GH #724 )
...
These test vectors were generated with Botan
2019-02-08 17:08:17 -05:00
b9eea8e842
Add additional ChaCha20/Poly1305 test vectors (GH #724 )
...
These test vectors were generated with Botan
2019-02-08 16:38:23 -05:00
76b47204df
Add IETF XChaCha20Poly1305 (GH #727 , PR #795 )
2019-02-06 04:14:39 -05:00
26c83877ef
Add IETF XChaCha (GH #727 , PR #794 )
2019-02-06 01:03:28 -05:00
dd48a7acef
Fix ChaCha20/Poly1305 when using filters (GH #724 )
2019-01-30 00:55:27 -05:00
e388f2d88d
Add Poly1305TLS algorithm (GH #727 )
...
This is the IETF's rendition of Poly1305 that forgoes AES and the nonce, and uses 16-bytes of the key directly to mac the message
2019-01-27 01:41:53 -05:00
e17f17d8fc
Add tamper comment to Poly1305(AES) tests
2019-01-26 13:12:46 -05:00
69286301e0
Add Poly1305(AES) test vectors
2019-01-26 12:54:47 -05:00
798e4d85b3
Update comments
2019-01-25 05:06:06 -05:00
d7e416d403
Add additional ChaChaTLS test vectors
...
These test vectors were generated from a modified Bernstein reference implementation.
2019-01-25 05:03:27 -05:00
caaaaa7691
Add additional ChaChaTLS test vectors
...
These test vectors were generated from a modified Bernstein reference implementation.
2019-01-25 02:34:44 -05:00
7923a97d24
Enable ChaCha-TLS tests in test vectors
2019-01-25 01:03:22 -05:00
099f870c55
Add additional ChaChaTLS test vectors from RFC 7539
2019-01-24 21:15:48 -05:00
5603661eec
Add ChaChaTLS implementation (GH #265 )
...
We tweaked ChaCha to arrive at the IETF's implementation specified by RFC 7539. We are not sure how to handle block counter wrap. At the moment the caller is responsible for managing it. We were not able to find a reference implementation so we disable SIMD implementations like SSE, AVX, NEON and Power4. We need the wide block tests for corner cases to ensure our implementation is correct.
2019-01-24 09:36:05 -05:00
704762ba2c
Add Test vectors and data to VS project files
2018-12-15 04:24:30 -05:00
8b13c2a8d0
Whitespace check-in
...
Look, we can finally use whitespace to add breaks and make these somewhat readable.
2018-11-05 20:43:11 -05:00
7c0be4ea8f
Add additional Salsa test vectors
2018-11-05 09:00:32 -05:00
5de6545827
Add additional test vectors
2018-11-04 20:05:08 -05:00
d7a3562c0b
Whitespace check-in
2018-11-04 14:36:55 -05:00
87d679bc7e
Add additional ChaCha20 test vectors (GH #732 )
...
The additional tests ensure we cross the 32-bit boundary used by the state counters
2018-11-04 14:34:32 -05:00
40fa6873f9
Add ability to Seek64 in test framework (GH #732 )
...
Also see https://github.com/randombit/botan/pull/1728
2018-11-04 14:21:54 -05:00
916c4484a2
Add ChaCha SSE2 implementation
...
Thanks to Jack Lloyd and Botan for allowing us to use the implementation.
The numbers for SSE2 are very good. When compared with Salsa20 ASM the results are:
* Salsa20 2.55 cpb; ChaCha/20 2.90 cpb
* Salsa20/12 1.61 cpb; ChaCha/12 1.90 cpb
* Salsa20/8 1.34 cpb; ChaCha/8 1.5 cpb
2018-10-23 07:57:59 -04:00
35b874b527
Add additional ChaCha tests
2018-10-23 07:35:41 -04:00
e2be0cdecc
Make ChaCha an Salsa use the same design pattern
2018-08-17 06:19:30 -04:00
2f83777e9b
Backout ChaCha changes to Crypto++ 7.0
...
These changes made it in by accident at Commit b74a6f4445
2018-07-25 16:25:41 -04:00
f065f193c1
Fixed failed ChaCha tests
...
We switched to the pattern used for Salsa but did not update the name in the test vector file
2018-07-06 22:30:11 -04:00
8c871b40ae
Update comments
2018-07-05 22:42:17 -04:00
989bf6dc5e
Add HC-256 stream cipher (GH #680 )
2018-07-05 06:43:04 -04:00
8e430daadf
Add additional HC-128 test vectors (GH #679 )
2018-07-05 00:45:52 -04:00
dd31eb80c0
Add HC-128 stream cipher (GH #679 )
2018-07-05 00:29:07 -04:00
93f46e4302
Update comments
2018-07-04 21:53:08 -04:00
bfe91dc732
Add additional Rabbit test vectors (GH #678 )
2018-07-04 19:34:51 -04:00
d00777e1d7
Add Rabbit stream cipher (GH #678 )
2018-07-04 03:47:28 -04:00
5fd0e98a41
Add additional SIMECK tests (GH #675 )
2018-06-30 09:48:09 -04:00
8b3c472333
Add additional SIMECK tests (GH #675 )
2018-06-30 09:41:38 -04:00
ac036496d3
Add Simeck lightweight block cipher (GH #675 )
...
Add Simeck lightweight block cipher (GH #675 )
2018-06-30 02:43:12 -04:00
b613522794
Fix copy/paste error
2018-06-25 15:38:50 -04:00
2f5b110b52
Add HIGHT lightweight block cipher (GH #672 )
2018-06-24 00:54:16 -04:00
3af3b8019b
Add additional LEA test vectors (GH #669 )
2018-06-23 17:58:12 -04:00
72d5d42746
Add additional LEA test vectors (GH #669 )
2018-06-23 17:38:07 -04:00
34dcb0d4cd
Add additional CHAM test vectors (PR #670 )
...
This is in preparation for SSE and large block processing. CTR mode is used because AdvancedProcessBlocks128_4x1_SSE
2018-06-19 17:09:43 -04:00
54d5100344
Add CHAM lightweight block cipher (PR #670 )
...
Add CHAM lightweight block cipher
2018-06-17 23:24:47 -04:00
1f06c512c4
Add LEA lightweight block cipher (GH #669 )
2018-06-17 22:36:41 -04:00
32abab75f2
Add KeyDerivationFunction interface (GH #610 , PR #611 )
2018-03-29 20:18:27 -04:00
48033dac0a
Updated source comment
2018-02-20 00:01:23 -05:00
c6a29e8708
Add Simon and Speck test vectors to All group (GH #585 )
2018-02-19 18:03:17 -05:00
e5b9fa6485
Use random IV's for Simon and Speck test vectors
2018-02-18 12:10:51 -05:00
3efef479d1
Re-add Simon and Speck test vectors (GH #585 )
...
Of the 200+ test vectors only 10 are semi-authentic. The ten are from the Simon and Speck paper but they had permutations applied to them so they worked with the algorithms described in the paper. The remaining 200 or so were generated with Crypto++ using straight C++ code. The library generated the test vectors because we don't have a reference implementation
2018-02-18 11:19:26 -05:00
2a367627f0
Finish removing Simon and Speck (GH #585 )
2018-02-15 06:17:35 -05:00
15b14cc618
Remove Simon and Speck ciphers (GH #585 )
...
We recently learned our Simon and Speck implementation was wrong. The removal will stop harm until we can loop back and fix the issue.
The issue is, the paper, the test vectors and the ref-impl do not align. Each produces slightly different result. We followed the test vectors but they turned out to be wrong for the ciphers.
We have one kernel test vector but we don't have a working implementation to observe it to fix our implementation. Ugh...
2018-02-14 04:06:16 -05:00
Jeffrey Walton