old msec from 2009.0 has different configuration files – /var/lib/msec/security.conf, /etc/security/msec/security.conf, /etc/security/msec/level.local, and so on. When migrating from 2009.0, the upgrade procedure attempts to process all those files, and convert their parameters, so you security configuration stays (mostly) the same. But, of course, it is always a nice idea to check the configuration after the upgrade.

For 2009.1 the idea is to use the same procedure.

I didn’t wanted to add all the new options automatically to give some more time to test them throughly. But it will be done automatically when we get closer to 2010.

“If you are using cooker or 2010 alpha, these options will not be added automatically to your /etc/security/msec/security.conf configuration file.”

What about user migration from 2009.1 or 2009.0 to 2010.0 stable ? How will you handle it, in particular for users that didn’t change the default configuration, so that they get the new default configuration ?