https://proxy2.de/forum/posts/list/3.php JForum - http://www.jforum.net
are there any news about the login problem ???

is it possible, that the problem is a sql problem?

my isp changed the sql version. since this day i can not administrad my guestbooks.

best regards

bernd]]> https://proxy2.de/forum/posts/preList/4076/12898.php https://proxy2.de/forum/posts/preList/4076/12898.php GMT
Could you email me the link so I can see your page?]]> https://proxy2.de/forum/posts/preList/4076/12899.php https://proxy2.de/forum/posts/preList/4076/12899.php GMT https://proxy2.de/forum/posts/preList/4076/12906.php https://proxy2.de/forum/posts/preList/4076/12906.php GMT
There is some information at MySQL about changes to the password exchange system in MySQL 4.1, perhaps we're falling into that issue? Specifically the "password handling changes" section at the bottom of http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.0.html ?]]> https://proxy2.de/forum/posts/preList/4076/12919.php https://proxy2.de/forum/posts/preList/4076/12919.php GMT
Before doing anything, dump your database to have a baseline to restore back to before doing any of the following, your milage may vary, all the rest of the usual disclaimers apply to my suggestion below:

It appears that MySQL 4.1+ might treat "password" by itself as a field name as a magic field, automatically applying the new password encryption rules on the data in a field with that name.

To fix this on my site I went into phpMyAdmin and clicked on the book_auth table, then clicked browse to pull up the data inside that table, and then on the pencil to edit the admin I wanted to fix. From there, I put in "value" the *PLAINTEXT* password that I wanted to use, and in the 'function' pulldown selected PASSWORD. Upon clicking "go" there was now a new encrypted password in the field and viola, logins to the guestbook admin function now work again.

I believe you can un-do just the attempt at password change in phpMyAdmin by saving the data from password field in notepad, doing the above change, and if it doesn't work just pasting the original data back into the field without selecting a function. Or just restore the dump you made of the entire database before attempting the change Course, if your password doesn't work before or after this change, it shouldn't really matter what the data in that field is, but I digress.

Luck.
P]]> https://proxy2.de/forum/posts/preList/4076/12920.php https://proxy2.de/forum/posts/preList/4076/12920.php GMT https://proxy2.de/forum/posts/preList/4076/12926.php https://proxy2.de/forum/posts/preList/4076/12926.php GMT https://proxy2.de/forum/posts/preList/4076/12931.php https://proxy2.de/forum/posts/preList/4076/12931.php GMT I do know that 123 in the 'new' 4.1 system is encoded in the database as *23AE809DDACAF96AF0FD78ED04B6A265E05AA257 rather than 773359240eb9a1d9. On my system, using the string starting with 773 does not allow login with 4.1 server, the one starting with *23A does, which is what lead me to belive that it's a storage/encoding magic action rather than a handshake. I would think the standard PHP call would be the same, with the handshake taken care of by the library (which I also recompiled to PHP-5.0.3 at the same time I updated MySQL, pointing at the new /usr/local/mysql source tree).]]> https://proxy2.de/forum/posts/preList/4076/12936.php https://proxy2.de/forum/posts/preList/4076/12936.php GMT https://proxy2.de/forum/posts/preList/4076/12937.php https://proxy2.de/forum/posts/preList/4076/12937.php GMT
I changed session.class.php lines 41 54 to read "SET password=OLD_PASSWORD" instead of "SET password=PASSWORD" and changed the database entry back to 773359240eb9a1d9 and 123 works again, so it looks like even though they changed the function, they did leave a backward compatibility path for now.

admin.php line 177 also needs to be changed to allow changing the password without locking yourself out of the site

Anyway, hopefully this was of some help to ya.
Take care,
P]]> https://proxy2.de/forum/posts/preList/4076/12938.php https://proxy2.de/forum/posts/preList/4076/12938.php GMT https://proxy2.de/forum/posts/preList/4076/12939.php https://proxy2.de/forum/posts/preList/4076/12939.php GMT https://proxy2.de/forum/posts/preList/4076/12941.php https://proxy2.de/forum/posts/preList/4076/12941.php GMT ]]> https://proxy2.de/forum/posts/preList/4076/12943.php https://proxy2.de/forum/posts/preList/4076/12943.php GMT
thank you very much.


best regards

bernd]]> https://proxy2.de/forum/posts/preList/4076/12977.php https://proxy2.de/forum/posts/preList/4076/12977.php GMT