Transfering postnuke users to cpg users

[greentin]

Hi, I've searched the board but I've not found any answers...
I want to transfer postnuke user to cpg and after that desinstall postnuke and just use the coppermine gallery as a standalone script...
So I've installed pnCPG to transfer my users to my CPG 1.3.0... and after that I've done an update to 1.3.2...
My users can't login now... I've check in my mysql database in the cpg130_users table and all the password are encrypted (like 28ne827fk) and my admin password isn't...

So what did I do wrongly? Is it normal that my password isn't encrypted? Is it not an security issue?
Sorry for my ugly english, I speak french...
Happy Holidays and thanks for futur help!

greentin

[kegobeer]

Coppermine doesn't encrypt passwords, so your users will have to log in with the encrypted password (you'll have to give them the encrypted password).  Or you can have them contact you and supply a new password that you can use to replace the encrypted password.

[casNuy]

When you transferred your PN users to Coppermine, pnCPG assigns a random password to your users. these are not encrypted.(opposite PN which does encrypt the password hence the reason why I cannot use the same password).
Your users should logon with this password and change it as they like.

Cas

[kegobeer]

Thanks for the explanation, Cas.  I wasn't aware of how PN handled the passwords.

[cutandpaste01]

I've checked the button to "Update Coppermine users from Postnuke" in the PN CPG 2.5 module admin section and clicked on the Update button.

g) Update Coppermine users from Postnuke  [ ]
Mass update of all Postnuke users into Coppermine on demand(This option will be unchecked as soon as soon as you hit the update button)

However my PN users don't get moved over into the Coppermine Users table.

Is there any combination of settings in the Coppermine/PN CPG 2.5 settings screens that could cause a conflict if I've got them set wrong?

Any ideas?

Thanks,

Simon

[casNuy]

If you dont know which pill you took, i wonder if you can answer the following question, but let's try.
Did you fill correctly the users table of Postnuke and of Coppermine ?
I assume there was no error message ?

Cas

[jami]

When you transferred your PN users to Coppermine, pnCPG assigns a random password to your users. these are not encrypted.(opposite PN which does encrypt the password hence the reason why I cannot use the same password).
Your users should logon with this password and change it as they like.

this doesn't make much sense ... at this point one can take pn_uname and pn_email and insert them by hand in the cpg_users table with a fake password, tell the user to login with this password and then change it ...
if the advantage is that a user should not register again in coppermine, but the admin must comunicate him a new password every time, where is the deal with pncpg?
maybe pncpg can insert the postnuke encrypted password in the db and one can modify the control /cpg133/login.php, line 34 :

Code Select Expand

    $results = db_query("SELECT user_id, user_name, user_password FROM {$CONFIG['TABLE_USERS']} WHERE user_name = '" . addslashes($HTTP_POST_VARS['username']) . "' AND BINARY user_password = '" . addslashes($HTTP_POST_VARS['password']) . "' AND user_active = 'YES'");
so that $HTTP_POST_VARS['password'] is encrypted in the same manner as postnuke.
but i can be wrong ... i really don't have looked coppermine code so much ...

sorry for the english...

[casNuy]

This could be possible but since Coppermine does not use encryption and I try to avoid standard scripts, this is not there.
The trick here is that only you have access to the db so you would be the only one who could do that.
cas

[jami]

i've already done it ( with .760rc4b and pncpg 2.6 ) and everything works fine.
there are 2 lines of code in login.php to change ( password control and cookie generation ), and three in pncpg ( to store the pn_users encrypted password, in place of the random generated pass ).
I understand that a thing like this would cause an eventual problem when upgrading the standalone application, or a little confusion with non-so-informed cpg users, but since one will do by himself, this hack is really simple and really useful.

keep up the good work at nuy.info
bye