On Wed, Nov 12, 2014 at 10:57:22AM +0100, Giorgio Pioda wrote:
> > This seems to work getting an upgraded Wheezy main-server working again 
> > (no need to generate a new gosa.conf):
> > 
> > (1) cat /dev/null > /etc/gosa/gosa.secrets
> > (2) take the random cleartext password from gosa.conf.orig and put it
> >     instead of the encrypted long one into gosa.conf (actually twice: 
> >     adminPassword and snapshotAdminPassword)
> > (3) restart apache2
> > 
> > From a security point of view it's probably more than dubious...
> > Maybe gosa-encrypt-passwords has to be adjusted. 
> 
> I confirm that this approach fixes the issue.
> 
> Thanks Wolfgang !
> 
> I'm also pretty dubious about security, but this file is going
> to be used only locally. I hope to see a GOsa package update with
> a better, cleaner reset.

Now that gosa 2.7.4-4.3~deb7u2 is available (since point release 7.8),
you can re-enable encryption.
Make sure, gosa 2.7.4-4.3~deb7u2 is installed. Then execute:

rm /etc/gosa/gosa.secrets 
gosa-encrypt-passwords 
service apache2 restart


Wolfgang

Attachment: signature.asc
Description: Digital signature

Reply via email to