I'm about to port the changes over to that today. The way I look at it
I'm either screwing up the block count or I have some idiotic fencepost
issue. Mostly I'm trying to maximize throughput by parallelizing some
aspect of the encipherment process for chacha. I probably need to just
focus on the cipher itself but I wanted to try a different approach first.
Anyway, thanks for taking a look. If anything interesting comes up I'll
let people know.
Chris
On 4/21/21 10:02 PM, Damien Miller wrote:
On Wed, 21 Apr 2021, rapier wrote:
For various reasons I'd like to be able to understand how the block
counter is handled cipher-chacha-libcrypto.c (mostly to test something
that will probably go nowhere).
I don't have any insight into the problem you're seeing except to note
that you don't seem to be doing anything obviously wrong.
As a suggestion, maybe try your experiment in the included portable
implementation of the cipher (i.e. cipher-chachapoly.c) - there's
less magic behind the scenes there compared to libcrypto and it's easier
to insert a bunch of printf()s to see what is actually being supplied to
the chacha20 primitive.
-d
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
