Hi,

we see exactly the same issue. Going back to 4.2.23-1 fixed the issue for now, but as already stated this opens the security hole again.

Thanks for fixing,

Christopher

--
======================================================
    Dipl.-Ing. Christopher Odenbach
    Zentrum fuer Informations- und Medientechnologien
    Universitaet Paderborn
    Raum N5.308
    odenb...@uni-paderborn.de
    Tel.: +49 5251 60 5315
======================================================

Reply via email to