Univention Bugzilla – Bug 31068
Don't run server password change at the same date on all systems
Last modified: 2013-11-19 06:44:26 CET
Server password change runs at the same date on all systems (if "$(date +%j | sed -e 's|^0*||') % $(ucr get server/password/interval) == 0"). This schould be changed to something like "every $(ucr get server/password/interval) days starting at installation date" so that bugs/problems within the server password change do not hit every customer at the same time.
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2. As such, this bug is moved to the new target milestone.
The rotation of machine passwords is now performed after amount of days in server/password/change since the last password change.
OK: svn41293,41294 but there's no need to convert it into a bash-only script: @@ -1,1 +1,1 @@ -#!/bin/bash +#!/bin/sh @@ -75,q +75,1 @@ -if (("$server_password_interval" > "$days_last_change")); then +if [ "$server_password_interval" -gt "$days_last_change" ]; then FAIL→OK: Changelog svn41295→43124 re-worded to The rotation of machine passwords is performed in intervals of days configurable through the &ucsUCRV; <envar>server/password/change</envar>. The date is now calculated relative to the date of the last password change instead of being relative to the start of the current year (<ulink url="&ucsbug;31068">Bug 31068</ulink>).
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".