Hi,
I've had kind of strange week last week. Three days of working mostly on
other projects, followed by two days of being ill and staying home..
So, I didn't do a lot of DBMail related work last week.
Aaron Stone wrote:
Ilja,
Have you checked out my patch since 2.0rc2 on SourceForge? I'd like to see
this patch be the impetus for the 2.0rc3 release, as it adds much robustness
that will need a few weeks of user testing to ensure that it is real-world
ready.
I'll check it out today :)
Also, I got my Alpha out of storage and have found that the MD5 code does not
segfault. Amusingly, the last time I compiled DBMail on this machine was
1.0rc3, when I wrote the authldap code :-) I have not yet tried a memory
debugger to confirm that it isn't just working by mistake, though.
OK. So it might be some strange Opteron-only problem. Still, it's a
matter that should be solved somehow, to make sure DBMail also runs well
on Opteron machines (I keep reading reports on big hardware vendors
adding Opteron-based machines to their lists, so we need to support them).
Please let us know if you're waiting on 2.0rc3 until the MD5 issue is
resolved; I'm sure that more people would suddenly be eager to learn MD5
hashing if a new or fixed implementation is what we need to continue towards a
2.0 release ;-)
I guess your solution, using the RSA-code would be best. I'll have a
look at all the licenses involved.
Ilja
