|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Stop making mediocre tutorials.The best tutorials are video! Camtasia Studio makes it easy to create engaging, buzz-building screen videos at any size, in any popular format. Download the free trial!
|
|
#16
|
||||
|
||||
|
Ok, I've done some googling, and it looks like phpBB has trouble with php5. The solutions are to a) use php 4 or b) to install this patch/mod
--Simon
__________________
|
|
#17
|
||||
|
||||
|
Thanks Simon
I did try the mod but found that this would also require mysqli to be installed with mysql from the start (or so it seemed) Being that that I'm not sure if the enviroment I'm going to be deploying to had this, I decided that going the route of switching to php4 was the better answer, seeing as the production enviroment was using 4.3.10. I just like to be running the latest and greatest if I can, guess I just couldn't have it all this time, (well could have, just decided to let it go and move on) In any case, it's up and running thanks to your help. |
|
#18
|
||||
|
||||
|
blockcipher told me that:
Downloading a new version from CPAN I don't think will help unless you actually compile it against version 4.1 or newer client libraries. I'll let someone else walk you through this because I had to do it once with the Cygwin version of Perl using GCC and that involved recompiling both the client libraries and dbd::mysql. If you're using the Activestate version of Perl, you probably didn't get the CPAN version of dbd::mysql, you got the Activestate version which is pre-compiled and, the last time I checked, a couple minor versions behind the CPAN version. You'll probably want to ask for more help in the Perl forums. but i dont know exactly what to do: Actually yes i do have ActiveState's Perl version and i c:\> ppm install dbd::mysql exit to download the mysql DataBase Driver. What exactly i must do now to get mysql 5 to work?
__________________
What is now proved was once only imagined! |
|
#19
|
||||
|
||||
|
ok,
I'm confused because it seems like it should be working, as things always do whenever we have a problem...but that's neither here nor there, my problem is that I cannot seem to get mysqld.exe to run with --old-passwords ![]() each time I try to do that from my command prompt I get a: [ERROR] mysqld: unknown variable 'Server=C:/dir/path/bin/mysqld-nt.exe' I've made sure that mysql is shut down before trying to execute the code and I've tried editing the registry entry for the server, but I can't figure it out and don't know what to do next. I also tried adding "old_passwords" to the my.ini file as sombody suggested, but that didn't fix my authentication problem either. Any suggestions?
__________________
"So I hired the best Feng-Shui artist to come down here and get my yin and yang in order, cause I...FRICK'N...LOVE...HARMONY!!!" - Captain Murphey, Sealab 2021 |
|
#20
|
||||
|
||||
|
ok,
well what I ended up doing to fix my problem was using Code:
mysql> UPDATE mysql.user SET Password = OLD_PASSWORD('newpwd')
-> WHERE Host = 'some_host' AND User = 'some_user';
mysql> FLUSH PRIVILEGES;
while this worked, it is by no means ideal since it is on a per-user basis...fortunately, the db I'm working on is dev only and when the project goes live, it will be running on an earlier version and won't have to deal with this problem. |
|
#21
|
|||
|
|||
|
Quote:
That's not entirely correct. The problem is that many programs use an old libmysql.dll (MySQL Client Library) which doesn't support the new password hashing. In most programs where the mysql client is dynamically linked (DLL) you can simply replace the dll with a newer one.. you can find the dll in mysql servers in "\lib\opt\libmysql.dll" which is the same version as the mysql server. So if your server is 5.0.15, that DLL would be also version 5.0.15. But there's an alternative workaround, which is posted in this thread hundred times.. SET PASSWORD FOR user@host = OLD_PASSWORD('password'); |
|
#22
|
||||
|
||||
|
Hmm, I have enabled the old passwords flag in mysql administrator and restarted mysql and apache and I still get the client does not support.... error.
I can log into a console though using this: mysql -u root -p password any ideas? |
|
#23
|
|||
|
|||
|
I have a little problem. I'm using a share server. I set the command : SET PASSWORD = OLD_PASSWORD( 'pass' ), but no resoults..
|
|
#24
|
|||
|
|||
|
After I do this..the password was changed..and now I don't have acces even to myphpadmin
, but my scripts also don't work. |
|
#25
|
|||
|
|||
|
i running in a newer MySQL 4.1.7 when i'm connecting i get
DBI connect('andregaron1:localhost','agaron',...) failed: Client does not support authentication protocol requested by server; conside based on this thread i'm trying to fix my code but now i'm getting: syntax error at login.pl line 15, near "FOR 'agaron'" Bad name after newpwd' at login.pl line 15. #!/usr/bin/perl -wT use strict; use CGI qw/:standard/; use CGI::Carp "fatalsToBrowser"; use DBI; print "Content-type: text/html\n\n"; SET PASSWORD = OLD_PASSWORD('secret'); SET PASSWORD FOR 'agaron'@'localhost' = OLD_PASSWORD('newpwd'); my $host = "localhost"; my $db = "andregaron1"; my $user = "agaron"; my $pass = "********"; my $dbh = DBI->connect ("DBI:mysql:$db:$host",$user,$pass,{ RaiseError => 1, AutoCommit => 1}) or die "info.pl: can't open database: $!\n";
__________________
_____________________________ www.tim0.net |
|
#26
|
||||
|
||||
|
You'll need to run that query directly in MySQL, or send it as a query to the server via DBI
|
|
#27
|
|||
|
|||
|
Quote:
can i keep the old password? |
|
#28
|
||||
|
||||
|
Yes, it's just changing the stored hash of it -
Code:
mysql> select PASSWORD( 'secret' ), OLD_PASSWORD( 'secret' ); +-------------------------------------------+--------------------------+ | PASSWORD( 'secret' ) | OLD_PASSWORD( 'secret' ) | +-------------------------------------------+--------------------------+ | *14E65567ABDB5135D0CFD9A70B3032C179A49EE7 | 428567f408994404 | +-------------------------------------------+--------------------------+ 1 row in set (0.00 sec) Both passwords are "secret", but the hash is different. --Simon |
|
#29
|
|||
|
|||
|
YEEAAA it worked
thank you so much |