Ticket #601 (new defect)
MySQL privileges aren't updated on package reconfiguration
| Reported by: | lunar | Owned by: | anonymous |
|---|---|---|---|
| Priority: | high | Milestone: | alternc-futur |
| Component: | Autres | Version: | alternc-0.9.4 |
| Severity: | crash | Keywords: | |
| Cc: |
Description
When alternc package is reconfigured, the value for MYSQL_CLIENT can be modified. In this case, database users don't work anymore: the allowed host should be updated.
Change History
comment:2 Changed 6 years ago by anarcat
I had to deal with this problem when we migrated our database service to a dedicated server. So I'd also like to fix this. I think an UPDATE on the host and user tables is necessary...
comment:3 Changed 5 years ago by anarcat
(In [2117]) Major redesign of the MySQL backend interface to fix a security issue. See: #318.
As of now, the MySQL configuration used everywhere by AlternC is not stored in the main configuration file (/etc/alternc/local.sh) but in a MySQL configuration file in /etc/alternc/my.cnf, which enables us to call mysql without exposing the password on the commandline.
The changes here are quite invasive but will allow us to factor out the MySQL configuration better. See #364.
This includes a partial rewrite of the mysql.sh logic, which is now ran from the postinst script (and not alternc.install) which will allow us to actually change the MySQL root user properly. See #601.
This commit was tested like this:
- clean install on etch (working)
- upgrade from a clean 0.9.7 (working)
