On Tue, 03 Nov 2020 10:24:17 +0100,
Justus Winter wrote:
> "Neal H. Walfield" writes:
>
> > I'm not that familiar with Nettle's API, so I don't know if the
> > following is sufficiently idiomatic.
> >
> > That said, we could do the fo
Hi Niels,
On Mon, 02 Nov 2020 18:49:39 +0100,
Niels Möller wrote:
>
> "Neal H. Walfield" writes:
>
> > So we could add:
> >
> > void sha1_collision_detection_init(...);
> > void sha1_collision_detection_update (struct sha1_ctx *c
Hi Simo,
On Mon, 02 Nov 2020 14:31:34 +0100,
Simo Sorce wrote:
> On Mon, 2020-11-02 at 12:53 +0100, Neal H. Walfield wrote:
> This change would have to be conditional as it will break compatibility
> for the very use case you mention, data at rest saved moons ago.
I see two ways forwa
Hi,
It's well known that SHA-1 is broken. I don't want to save it. But,
particularly when dealing with data at rest, there are cases where one
has to use SHA-1. It would be nice if Nettle integrated SHA-1
collision detection to make that a tiny bit safer:
https://github.com/cr-marcstevens/sh
