password handling: has it changed? password handling: has it changed?
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

password handling: has it changed?

Started by sleepmonsta, March 21, 2006, 05:47:04 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

sleepmonsta

I have been using 135 with a membership script called amember which integrates with coppermine via a plugin.

I have just upgraded to 144 and have noticed that passwords are now encrypted in the sql table whereas in 135 they were plain text.

This has rendered the amember script unusable as it passes login information to the cpg sql tables. Is there any way to change the password handling in cpg or should I just stick with an older version?

What is the most recent coppermine version that doesnt use encrypted passwords in the database?

thanks in advance for any help/suggestions

Tranz

If you had done an upgrade, the passwords would have remained plaintext until you changed the Config to encrypt passwords.

sleepmonsta

can you tell me how to change it back to plaintext? thanks

Joachim Müller

you can change this by modifiying coppermine's config table, however your user's passwords won't revert back to being unencrypted - this is a one-way road.

sleepmonsta

thanks for the info. could you tell me step by step how to change it back to plaintext? I appreciate your help with this. Dave

Nibbler

You can't. Either modify the 3rd party script or restore your gallery to the state it was in using a backup.