
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?