[MDEV-8357] Ability to disable creation of MyISAM tables Created: 2015-06-23 Updated: 2015-06-23 Resolved: 2015-06-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Cloud Foundry Core Services team | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
We use MariaDB exclusively in Galera clusters. We do not enable MyISAM replication because it is not recommended. We wish there were a way to prevent users from creating MyISAM tables, since there is no way to raise a warning that such tables are not replicated. This is especially useful given that we've found a way for users to crash MariaDB if they have the ability to create/access MyISAM tables. This is the result of our investigation into CVE-2015-3210. This is evidently possible, since there is a community provided plugin. We do not plan to use this plugin, as it is not intended for MariaDB. |
| Comments |
| Comment by Elena Stepanova [ 2015-06-23 ] |
|
It has already been implemented in MariaDB 10.1, see enforce_storage_engine option. |
| Comment by Elena Stepanova [ 2015-06-23 ] |
|
Duplicate of |
| Comment by Cloud Foundry Core Services team [ 2015-06-23 ] |
|
D'oh! Thanks Elena. I never would have thought to search for "enforce storage engine." We'll be looking forward for the 10.1 series to go GA! |