The mailing list for listmasters using Sympa

[Johan Loubser <address@concealed>]

On Thu, Apr 26, 2007 at 09:45:04AM +0200, Olivier Salaün - CRU wrote:
>  Hi Johan,
> 
>  You should ta care to have the same value for the sympa.conf "cookie" 
>  parameter on both servers. This parameter usages includes passwords 
>  encryption/decryption. It needs to be the same value if both Sympa servers 
>  share the same password database.
> 
>  See 
>  
> http://www.sympa.org/wiki/manual/upgrading?s=cookie#moving_to_another_server
> 
>     ...
>     the directory |/etc/sympa.conf| and |wwsympa.conf|. Sympa new
>     installation creates a file |/etc/sympa.conf| (see sympa.conf
>     parameters <http://www.sympa.org/wiki/manual/conf-parameters/index>)
>     and randomly initializes the cookie parameter. Changing this
>     parameter will break all passwords. When upgrading Sympa on a new
>     server, take care that you start with the same value of this
>     parameter, otherwise you might have problems!
> 
> 
>  Johan Loubser wrote:
> > I have an old sympa installation on debian woody (sympa 3.3.3)
> >
> > I am in proses of building a backup server(clone) with same version sympa 
> > to keep the proses going while
> > we do a dubble upgrade on the mail server.
> > And migrade to the latest version of sympa.
> >
> > My problem at the moment on the clone server is that the  passwd is not
> > decrypted as should when login is attemted, same is hapening if the
> > passwd is requested through mail. The data is in a postgres database.
> >   

After alot of searching i found that wwsympa is writeing the passwd back
to the data base in clear text.
Thus there must be a setting that i am missing that set the passwd
writing to md5

My cookie  setting is the same as on the stable running server. 
My key_passwd setting is also the same.



-- 
Johan Loubser
(021) 8084036
Informasie Tegnologie
University of Stellenbosch