an additional requirement on kdelibs

Brad Hards bradh at frogmouth.net
Tue Mar 6 10:53:42 GMT 2007


On Tuesday 06 March 2007 20:39, Jos van den Oever wrote:
> 2007/3/6, Brad Hards <bradh at frogmouth.net>:
> > On Monday 05 March 2007 22:33, Jos van den Oever wrote:
> > > > Why does it use libssl? In any case we have always avoided a linked-
> > > > in libssl, as you can see from KSSL. That dlopens openssl, which is
> > > > very memory-heavy.
> > >
> > > The only reason is the sha1 routine. We could just include it in the
> > > code. I'm open to suggestions of fast sha1 implementations.
> >
> > Do you even need a cryptographic hash? Are you just looking for something
> > that doesn't suffer too many accidental collisions?
>
> No, you can index sha1 sums so you can look for duplicate files quickly.
A cryptographically secure hash is overkill for this. You should be able to 
find a much faster hashing algorithm (with far fewer bits) than SHA1 for 
this.

Brad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070306/9aaf3e40/attachment.sig>


More information about the kde-core-devel mailing list