Bug #18628 mysqld: security problem
| Submitted: | 29 Mar 2006 20:16 | Modified: | 1 Jun 2007 14:00 |
|---|---|---|---|
| Reporter: | Paul DuBois | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
| Version: | 5.0 | OS: | Linux (Linux) |
| Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
[29 Mar 2006 20:16]
Paul DuBois
[3 Aug 2006 9:32]
Magnus Blåudd
A --secure-file-priv command should be implemented to get this approved.
[14 Feb 2007 13:46]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/19868 ChangeSet@1.2395, 2007-02-14 14:44:34+01:00, msvensson@pilot.mysql.com +17 -0 Bug#18628 mysql-test-run: security problem(part1) - Implement --secure-file-priv=<dir> option that limits "load_file", "LOAD DATA" and "SELECT .. INTO OUTFILE" to work with files in specified dir. - Use above option for mysqld in mysql-test-run.pl
[8 Mar 2007 22:15]
Timothy Smith
pushed to 5.0.38, 5.1.17
[13 Mar 2007 18:50]
Paul DuBois
Noted in 5.0.38, 5.1.17 changelogs, and in the mysqltest manual.
[1 Jun 2007 14:00]
Paul DuBois
--secure-file-priv is an option for mysqld, not mysqltest. I removed the description from the mysqltest manual to the reference manual. There is also an associated secure_file_priv system variable.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.071 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.