> ChangeLog.byversion updated. Is it ok?

Perfect.

Apart from the bug I found (see reports), everything should be fine.

Once the remaining bugs get fixed, it should be ok for a merge, although I was not able to evaluate the impact of bug #1957 on a system working with real ssh key prefix.

I notice also that in some case, the ssh keys of some users always get updated. But their keys are ok and it's only 10 users. I'd like that thing to be clarified but it is not critical in any way.

Hello Sylvain. It is important the you update the ChangeLog.byversion file. This will save lot of time for the next release.

Ok, I managed to spam savane-dev-i18n - I didn't know it existed; I wish I could set the category to none :/

Current sum up:
Done:

• add a SSH prefix/regexp -> config var: $sys_authorized_keys_prefix

change in User.pm (GetUserSSHRealKey, UserAddSSHKey) and sv_users (way to compare ssh keys in the system and in the database re:newlines).

• add MySQL option for Perl -> config var: $sys_dbparams

change in DB.pm

• add MakeCvsAttic-like procedures that actually takes the frontend params into account for the CVS repository

-> new kind of download area (MakeCvsAttic-like) at project creation

Remaining:

• Create chroot'd /etc/passwd and /etc/group -> separate cron job

Does copy /etc/group and /etc/passwd in each cvs root, provided /etc/ is more recent that in the first cvs root.

• sv_gatekpr -> separate cron_job

recreates all keyrings, provided /etc/ is more recent that the current keyring.

• Add documentation for the new variables

• See what to do with gnueval.php and send_registration_notification.php

• Remove the reference to 'fingerprint' in "Edit GPG key".

• Add code to manage GPG keys; even if it is not useful atm, it is wanted

• Add exclusion lists to sv_backup so as not to include private and big synced projects

Also check https://mail.gna.org/public/savane-dev/2004-09/msg00237.html