On 08/23/2011 04:51 AM, Andres Mejia wrote:
Another question, the only thing I see missing in nettle that libarchive can make use of is RIPEMD-160. In case I want to submit patches, I should submit them here correct? Also, I suppose if I wanted to submit patches, there's no issue in porting code from gcrypt over to nettle correct? I think it would be easier (and faster) to reuse the implementation in gcrypt than to implement the algorithm from scratch.
Btw cryptsetup uses ripemd160 if used in plain mode (iow mode where encryption key is directly hashed password). So despite cryptsetup has already optional Nettle crypto backend support, is cannot provide backward compatibility without ripemd160.
So you have yet another user for these patches ;-)
Thanks, Milan