/var/tmp/mysql-buildtests was intended to be the location for mysql to read from, but still use --tmpdir /var/tmp/mysql. Based on your comment, this isn't going to work anyway because of the permissions on /var/tmp/mysql and running as non-mysql. Additionally, in discussing this with mdeslaur, I've come to the conclusion that adjusting the profile for the testsuite is the wrong approach anyway since it does cover the chained attack of sql injection -> file -> include in php, but does not cover the other way around. Therefore, I don't see any other option than to use a mysqld not confined by AppArmor for these private build tests.
This said, it is vitally important that the QRT test-mysql.py is run before upload. -- MySQL must not use /tmp https://bugs.launchpad.net/bugs/375371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
