On 08/20/2013 07:49 PM, Thomas Raschbacher wrote:
>> Mhash is dead, as in un-maintained and abandoned. I think you should
>> take it up with the packager. For Debian it was fixed in-distro a long
>> time ago.
>>
> that doesn't sound good. isn't there some alternative then?
Mhash is used for two purposes:
- encryption of the passwords in the database. Mhash has a rich set of
algorhythms, and I'm not aware of an alternative - short of including
implementations in-tree. I may end up doing that with mash.
- check-sums for the blobs in the database. We use cryptographic
checksums (sha1, md5, tiger, etc as per dbmail.conf) for indexing the
single-instance blob-storage of mime-parts and header values. For this
we could rely on the checksum implementations available in GLib.
But it's mainly the first reason that mhash is still around. It's solid
code, and work reliably. It's just the packaging that is crap.
> @Paul:
> Do you intend to put one of those choices into the next release? Because
> if you do I will just ignore this for now since it doesn't really do
> much harm except confuse an admin /user maybe ;)
I've already pushed it to the master branch. I use a separate DM_VERSION
variable internally, rather than the generic VERSION.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
