I've been testing upgrading a server VM from Mageia 1 to Cauldron, using boot.iso to launch the installer from my own local HTTP mirror. During the Summary step I did not click to reconfigure the Security level. I had customizations in the /etc/security/msec/perms.conf and /etc/security/msec/security.conf files which got wiped out. I don't believe the msec package is responsible as those files are marked config(noreplace).
CC: (none) => thierry.vignaud
Different, but minor, bug in the Summary step, it said Proxies - not configured, but they are already configured.
Blocks: (none) => 3342
We do not touch those files. we only call msec in order to set the security level
CC: thierry.vignaud => (none)Source RPM: drakx-installer-stage2-14.1-3.mga2.src.rpm => msec
Component: Installer => RPM Packages
Can you at least tell me *how* you call msec?
checkout http://svnweb.mageia.org/soft/drakx/trunk/perl-install/ grep for security in install/*pm, then look at functions called in security/*pm
Also you should see the msec calls in /root/drakx/*.log
Thierry, in ddebug.log it says "msec -q -f secure" was the command it ran. In the documentation for msec, it says the -f option makes it overwrite the current configuration in /etc/security/msec/*.conf. The installer should not be using the -f option during upgrades. It is fine to use it for an initial installation.
Source RPM: msec => drakx-installer-stage2
Your log says that msec wasn't found, and thus not run. So that's not the issue.
Sorry, was looking at another report. Can you attach yours?
Keywords: (none) => NEEDINFO
Created attachment 1921 [details] ddebug.log.gz
Fixed in git
Status: NEW => RESOLVEDResolution: (none) => FIXED