For dapper i think the best option is to do a -security backport of the package (through proposed if necessary), if that is possible. As the squirrelmail minor-releases is mostly-bugfix i would vote for that. 1. Wait for squirrelmail_1.4.13-2ubuntu1.3 to be in hardy (2. Upload squirrelmail_1.4.13-2ubuntu1.3~dapper1 to dapper-proposed for testing)? 3. If it is approved, upload to dapper-testing and dapper-updates
I've just tested backporting squirrelmail_1.4.13-2ubuntu1.3 and running it under dapper, and it compiles and works. Tested both under php5 and php4. -- Multiple CVEs for Squirrelmail <1.4.17 https://bugs.launchpad.net/bugs/375513 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
