http://qa.mandrakesoft.com/show_bug.cgi?id=2411
------- Additional Comments From [EMAIL PROTECTED] 2003-02-25 23:51 ------- It's not so simple. sasldbconverter-2 must be running manually (it prompts for confirmation), and only after reading the documentation and understanding all the implications. The short story is that sasl v1 isn't developed anymore, and sasl v2 uses a different format for the databases (the change wasn't made gratuitously btw, it was necessary). After the conversion there's no means to keep both databases in sync, so either all apps use sasl v2 or you have to keep both databases in sync yourself (of course this all applies if you're using the sasldb, if you're using other authentication sources, sasl v1 and sasl v2 applications can happily coexist -- that's what I do). ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: I updated from cyrus v1 to cyrus v2. During the ugrade, the existing sasl.db hasn't been upgraded to v2 with dbconverter-2 and it has been renamed to /var/lib/sasl.db.rpmsave. I'd expect the upgrade to also upgrade an existing sasl.db. As said, dbconverter-2 needs to be run. But that's impossible because of bug #2410.
