The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Woops, too bad, I missed your previous posts.


Starting Sympa 5.4, we changed the way passwords are store. We no longer use the cookie parameter but now store a MD5 fingerprint of the password. We still need the cookie parameter for the upgrade because we need to uncrypt password before creating the MD5.

The advantage of this new storage method is that the value stored in database can not be used to guess the actual password value, only to make sure that the value given by the user is right. Also, it allows to get rid of this cookie parameter which was a pain for listmasters on each upgrade.

You need to run sympa.pl --md5_encode_password to change the value stored in database. Please take care that this operation cannot be reverted, so backup your database before doing it.

P.S. : I spotted an FAQ explaining it (it says what I just wrote): https://www.sympa.org/faq/password_problem_updating_to_version6

Regards,

David

Le 01/07/2010 17:17, Allen, Pat a écrit :

Good morning,

 

So I restored my VM yesterday to the working 5.3.4 version and verified that the cookie in /etc/sympa.conf matched the cookie on my original system. I saved a copy of sympa.conf to /tmp so that I could have a reference copy along the way. I then went through the upgrade process. Along the way I made sure that the value of the cookie had not changed. And yet, after I started the sympa processes with the new 6.0.3 installation, my passwords weren’t accepted. I could tell that it could see the accounts since, if I put in the wrong email address, I got a different error message.

 

So, has anyone seen this problem before? Is there any way around it? I really don’t want to have to tell all my subscribers that they have to change their passwords.

 

Thanks!

Pat

 

From: address@concealed [mailto:address@concealed] On Behalf Of Allen, Pat
Sent: Wednesday, June 30, 2010 6:32 AM
To: address@concealed
Subject: [sympa-users] upgrade problem / question

Good morning,

I am having a problem upgrading from version 5.3.4 to version 6.0.3.

Here’s my situation:

·         I have a production installation running on “server1” (version 5.3.4).

·         I’ve created a VMware virtual machine named “server2” and installed version 5.3.4 on it. I’ve followed the instructions in the documentation on moving to a new server. It’s running with a temporary, dedicated DNS server so that it thinks that it’s the proper server name.

·         I’ve tested the new 5.3.4 installation and am happy that it’s working OK. (I then take a VMware snapshot so that I can easily roll back to this spot.)

·         I unpack the 6.0.3 tar ball and do the configure, make, and make install.

·         I then update my perl modules using sympa_wizard.pl –check

·         I then run sympa.pl –upgrade. The upgrade doesn’t report any errors.

·         I started the sympa processes.

Sounds great so far. It’s just that I can’t login with any of my user accounts.  I get a message saying the password you submitted is incorrect. It allows me to request a new password and I can change my password which then allows me to login. After that everything appears to work OK. But I can’t make all my subscribers change their passwords. Why is the upgrade breaking my passwords?

Thanks!

Pat

 

--------------
Pat Allen (address@concealed & http://www.mbari.org/staff/pat)

Monterey Bay Aquarium Research Institute (MBARI)
7700 Sandholdt Rd, Moss Landing, CA 95039
(voice) 831-775-1724; (fax) 831-775-1620

 

 

--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the mails.
So if you want your bug reports or feature requests for Sympa to be processed, please post them to the Sympa tracker