Re: Proposal: Remove MD5 / SHA1 support from veriexec

[Sevan Janiyan <venture37%geeklan.co.uk@localhost>]

On 08/23/17 21:29, Taylor R Campbell wrote:
> Sounds good to me.  Maybe also start to get rid of RIPEMD160 since
> even if it's not specifically broken like MD5 and SHA1 are, the cost
> of a generic collision attack on a 160-bit hash function is nearing
> the realm of possibility.

Updated patches which also removes RMD160.

http://www.netbsd.org/~sevan/patch-veriexecgen-mk2.txt

http://www.netbsd.org/~sevan/patch-veriexec-nomd5-sha1-mk2.txt


Sevan