Resolved it myself. <div>For the record, I just needed that for customers, so I changed the actual MD5 crypt in <br>Kernel/System/CustomerAuth/DB.pm</div><div>and</div><div>Kernel/System/CustomerUser/DB.pm</div><div>(its just one line)</div>
<div>from </div><div>$CryptedPw = unix_md5_crypt( $Pw, $Login );</div><div>to</div><div>$CryptedPw = md5_hex($Pw);</div><div><br></div><div>(also added, use Digest::MD5 qw(md5_hex);).</div><div><br></div><div>If anyone thinks I&#39;ve missed something, let me know.</div>
<div><br></div><div>-sv</div><div><div class="gmail_quote">On Tue, Jan 12, 2010 at 11:37 PM, Sagy Volkov <span dir="ltr">&lt;<a href="mailto:sagyvolkov@gmail.com">sagyvolkov@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<div><br></div><div>I need to get OTRS (2.4.5) to somehow change the method in Frontend::Customer::Auth to support another option, (not just plain,MD5, crypt) but also support Digest:: MD5, i.e.</div><div><br></div><div>

<div>use Digest::MD5 qw(md5_hex);</div><div>my testpass=md5_hex(&quot;password&quot;);</div><div><br></div><div>I know in terms of security its less secured, but because of integration from another system who keeps password (in php) with plain MD5, I need to change the way OTRS save/compare customer passwords.</div>

<div><br></div><div>Have anyone done it in the past? any thoughts?</div><div><br></div><div>Best Regards,</div><div><br></div><font color="#888888"><div>-sv</div></font></div>
</blockquote></div><br></div>