On 2021-02-10 Daiki Ueno wrote:
> ni...@lysator.liu.se (Niels Möller) writes:
[...]
> > Tentative patch below, but I need to extend the tests to get proper test
> > coverage of this case.
> Thank you so much! The patch fixes the issue (tested on gcc cfarm).
Hello,
Just for completeness sake I
Hi, I think the chacha bug is a severe enough regression to warrant a
bugfix release pretty soon. I'll aim to get it out in a week from now.
I think it should be fine to do a 3.7.1 release from the master branch,
rather than cherry-picking selected bugfixes. I've looked through git
history and
Daiki Ueno writes:
> Thank you so much! The patch fixes the issue (tested on gcc cfarm).
Thanks for testing. Pushed to master branch now. BTW, I could test
ppc64el locally on my laptop fairly easily, I used:
# apt-get install -t testing gcc-powerpc64le-linux-gnu
# dpkg --add-architecture
Hello,
ni...@lysator.liu.se (Niels Möller) writes:
> ni...@lysator.liu.se (Niels Möller) writes:
>
>> I would guess that means that we got 209 bytes, including the 16-byte
>> poly1305 authentication tag. Message size is then 209 - 16 = 193 bytes.
>> If the first byte is a TLS packet type, the
Jeffrey Walton writes:
> Or you can use the test vectors from Wei Dai's Crypto++. The project
> already generated test vectors for 1x, 4x and 12x blocks. The test
> vectors include Bernstein's ChaCha and the IETF version. Also see
>
