Sorry to keep bugging this list,
can anyone tell me why I can't set the password in MySQL with the UPDATE
statement below? I have upgraded from 3.8.4 to 4.0.14 and run the
password updater. MySQL was at 5.1 so I didn't need to do the MySQL
update stuff as far as my reading shows.
Is there something wrong with my query or is there something that RT is
doing such that the passwords are perhaps hashed differently?
I'd so love to get past this final hurdle and be able to make tickets
again...
Is there perhaps some further info that I should supply that I have not
to help understand this?
Regards
Paul O'Rorke
Tracker Software Products Canada Limited
[email protected] <mailto:[email protected]>
tracker-software.com <http://tracker-software.com>
On 07/30/2013 03:17 PM, Paul O'Rorke wrote:
Thanks for that Kevin,
not the first time - a silly little mistake had me scratching my
head. I had in my Apache config a rewrite rule for /rt and had the
wrong value in RT_Siteconfig for Set($WebPath, '');
So I now get my logon screen but cannot log in.
I did run the password updater:
root@rt4:/opt/rt4# perl /opt/rt4/etc/upgrade/vulnerable-passwords
--fix
Upgrading 16 users...
Done.
I am assuming that I can't just UPDATE the passwords in MySQL because
of the hashing? I tried without success:
mysql> UPDATE rtdb.Users SET Password=PASSWORD('xxxx') WHERE
Name='jamie';
Query OK, 1 row affected, 1 warning (0.01 sec)
Rows matched: 1 Changed: 1 Warnings: 1
I guess I have missed something in these upgrade README files. I do
appreciate your help. Now that I've the Apache thing sorted I'm
feeling like on the home stretch - if only I can sort these passwords
out. Is there another related script I missed perhaps?
Sincerely
Paul O'Rorke
Tracker Software Products Canada Limited
[email protected] <mailto:[email protected]>
tracker-software.com <http://tracker-software.com>
Tel: +1 (250) 324 1621
Fax: +1 (250) 324 1623
