> this was resolved a long time ago ... why is it coming up now?
Not sure why. The MD5 was clearly broken (I got an update in several days fixing that), but apart from that, it was a clean install with all up-to-date fixes.
> this was resolved a long time ago ... why is it coming up now?
Not sure why. The MD5 was clearly broken (I got an update in several days fixing that), but apart from that, it was a clean install with all up-to-date fixes.