>A fix for the endian problem went in between 2.5.1p1 and 2.5.2p2, so you >are running the last bad version :) If you upgrade to the just-released >2.5.2p1 then all should be well. Sorry, can you explain in more detail? Where is the endian problem? Is it triggered by a new client simply by a change in the default cipher? Phil