Login not functional under BSD - crypt() issue?

Greetings!
After installing OTRS 2.0.2, I am not able to login with the default
username/password: root@localhost/root.
OTRS 2.0.2 is installed on a server running the following:
FreeBSD 5.4
Perl v5.8.6
Apache 2.0.54_2
MySQL 4.1.13
Login attempts generate the following in /var/log/messages:
Sep 15 12:56:34 hostname OTRS-CGI-10[17421]:
[Notice][Kernel::System::Auth::DB::Auth] The crypt() of your mod_perl(2)
is not working correctly! Update mod_perl!
Sep 15 12:56:34 hostname OTRS-CGI-10[17421]:
[Notice][Kernel::System::Auth::DB::Auth] User: root@localhost
authentication with wrong Pw!!! (REMOTE_ADDR: xxx.xxx.xxx.xxx)
The notice re: "The crypt() of your mod_perl(2) is not working correctly!
Update mod_perl!" comes from this portion of Kernel/System/Auth/DB.pm:
# and do this check only in such case (unfortunately there is a
mod_perl2
# bug on RH8 - check if crypt() is working correctly) :-/
if (($Salt =~ /^\$\d\$/) || (crypt('root', 'root@localhost') eq
'roK20XGbWEsSM')) {
$CryptedPw = crypt($Pw, $Salt);
}
else {
$Self->{LogObject}->Log(
Priority => 'notice',
Message => "The crypt() of your mod_perl(2) is not working
correctly! Update mod_perl!",
);
my $TempSalt = quotemeta($Salt);
my $TempPw = quotemeta($Pw);
my $CMD = "perl -e \"print crypt('$TempPw', '$TempSalt');\"";
open (IO, " $CMD | ") || print STDERR "Can't open $CMD: $!";
while (<IO>) {
$CryptedPw .= $_;
}
close (IO);
chomp $CryptedPw;
As stated above, the machine is not running mod_perl or Redhat Linux.
There is a difference between the crypt() functions on FreeBSD and Linux.
It appears that others have run into this issue in the past:
http://lists.otrs.org/pipermail/otrs/2004-April/004706.html
http://lists.otrs.org/pipermail/otrs-de/2005-August/004319.html
Can someone suggest a fix or work-around for this?
If additional system configuration information would be helpful, I'd be
happy to provide it.
Regards,
Wade Naveja

Did I post this issue to the appropriate list? Is there anyone on this list running OTRS on FreeBSD? If so, what version are you running? On Thu, 15 Sep 2005, Wade Naveja wrote:
Greetings!
After installing OTRS 2.0.2, I am not able to login with the default username/password: root@localhost/root.
OTRS 2.0.2 is installed on a server running the following:
FreeBSD 5.4 Perl v5.8.6 Apache 2.0.54_2 MySQL 4.1.13
Login attempts generate the following in /var/log/messages:
Sep 15 12:56:34 hostname OTRS-CGI-10[17421]: [Notice][Kernel::System::Auth::DB::Auth] The crypt() of your mod_perl(2) is not working correctly! Update mod_perl!
Sep 15 12:56:34 hostname OTRS-CGI-10[17421]: [Notice][Kernel::System::Auth::DB::Auth] User: root@localhost authentication with wrong Pw!!! (REMOTE_ADDR: xxx.xxx.xxx.xxx)
The notice re: "The crypt() of your mod_perl(2) is not working correctly! Update mod_perl!" comes from this portion of Kernel/System/Auth/DB.pm:
# and do this check only in such case (unfortunately there is a mod_perl2 # bug on RH8 - check if crypt() is working correctly) :-/ if (($Salt =~ /^\$\d\$/) || (crypt('root', 'root@localhost') eq 'roK20XGbWEsSM')) { $CryptedPw = crypt($Pw, $Salt); } else { $Self->{LogObject}->Log( Priority => 'notice', Message => "The crypt() of your mod_perl(2) is not working correctly! Update mod_perl!", ); my $TempSalt = quotemeta($Salt); my $TempPw = quotemeta($Pw); my $CMD = "perl -e \"print crypt('$TempPw', '$TempSalt');\""; open (IO, " $CMD | ") || print STDERR "Can't open $CMD: $!"; while (<IO>) { $CryptedPw .= $_; } close (IO); chomp $CryptedPw;
As stated above, the machine is not running mod_perl or Redhat Linux.
There is a difference between the crypt() functions on FreeBSD and Linux.
It appears that others have run into this issue in the past:
http://lists.otrs.org/pipermail/otrs/2004-April/004706.html http://lists.otrs.org/pipermail/otrs-de/2005-August/004319.html
Can someone suggest a fix or work-around for this?
If additional system configuration information would be helpful, I'd be happy to provide it.
Regards,
Wade Naveja
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting f�r Ihr OTRS System? => http://www.otrs.de/

On 9/18/05, Wade Naveja
Did I post this issue to the appropriate list? Is there anyone on this list running OTRS on FreeBSD? If so, what version are you running?
I'm using OTRS on FreeBSD. My versions of software are pretty much the same as yours (except perl 5.8.7), but my database has been upgraded many times with origins back in the 0.5beta days. Heh, my root@localhost OTRS password was last changed 2002-10-12 08:27:07-04. :) OTRS people, have you tested an install from scratch recently on a FreeBSD box? Is it possible that the crypted password in the initial SQL is incompatible for some reason? If all else fails you can always generate a new crypt'ed password and manually insert it into the database in the system_users table. Bryan

On 9/19/05 9:15 PM, "Bryan Fullerton"
On 9/18/05, Wade Naveja
wrote: Did I post this issue to the appropriate list? Is there anyone on this list running OTRS on FreeBSD? If so, what version are you running?
I'm using OTRS on FreeBSD. My versions of software are pretty much the same as yours (except perl 5.8.7), but my database has been upgraded many times with origins back in the 0.5beta days. Heh, my root@localhost OTRS password was last changed 2002-10-12 08:27:07-04. :)
OTRS people, have you tested an install from scratch recently on a FreeBSD box? Is it possible that the crypted password in the initial SQL is incompatible for some reason?
If all else fails you can always generate a new crypt'ed password and manually insert it into the database in the system_users table.
Bryan
I did not see the original post. I, too, am running OTRS under BSD (5.4/release). There should be no problems with crypt() under BSD 5.4. One possibility, though: What version of MySQL are you using? And is there more than one? Likewise with SSL. -- Mark J. Nernberg Director of Technology (412)478-6262 http://www.downtownhelpdesk.com/ Customer Support: support@downtownhelpdesk.com Have you tried our on-demand remote support services? Downtown Help Desk and 1-Fast Computer Service, providing quality technology solutions to the small business since 2003.

Thanks Bryan.
I had previously tried manually inserting a new crypt() generated password
in the database, but that didn't work.
I did get it working, though. My problem turns out to have been of my
own making as opposed to anything wrong or broken with OTRS. It turns out
that this particular FreeBSD server's crypt_default value had been
modified from the default of md5 and des to use the blowfish algorithm.
/etc/auth.conf had been changed from:
# crypt_default = md5 des
to:
crypt_default = blf
Undoing that change allowed me to sign in and carry on with the rest of
the configuration.
So far, I have to say I'm very impressed with OTRS. Apart from this bit
of self-inflicted agony, the install and configuration has been very
simple!
My only request would be to add a comment in the docs or faq about
FreeBSD users being able to shoot themselves in the foot this way. This
probably isn't the right list to make such a request, so I'll do that
elsewhere.
Regards,
Wade Naveja
On 9/18/05, Wade Naveja
wrote: Did I post this issue to the appropriate list? Is there anyone on this list running OTRS on FreeBSD? If so, what version are you running?
I'm using OTRS on FreeBSD. My versions of software are pretty much the same as yours (except perl 5.8.7), but my database has been upgraded many times with origins back in the 0.5beta days. Heh, my root@localhost OTRS password was last changed 2002-10-12 08:27:07-04. :)
OTRS people, have you tested an install from scratch recently on a FreeBSD box? Is it possible that the crypted password in the initial SQL is incompatible for some reason?
If all else fails you can always generate a new crypt'ed password and manually insert it into the database in the system_users table.
Bryan _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System?

On 9/20/05, Wade Naveja
I did get it working, though. My problem turns out to have been of my own making as opposed to anything wrong or broken with OTRS. It turns out that this particular FreeBSD server's crypt_default value had been modified from the default of md5 and des to use the blowfish algorithm.
Ah, yes, that would do it. [snip]
My only request would be to add a comment in the docs or faq about FreeBSD users being able to shoot themselves in the foot this way. This probably isn't the right list to make such a request, so I'll do that elsewhere.
Perhaps just an OS-independant note that DES password support is required in the system's crypt() call for the default root@localhost password to work. Hopefully that'd tweak the memory of anyone who's been changing their system crypt() settings. :) If you're sufficiently interested, you could submit a diff to the docs in a bug on http://bugs.otrs.org/. Bryan
participants (3)
-
Bryan Fullerton
-
Mark Nernberg
-
Wade Naveja