diff options
| author | Robert Adam <dev@robert-adam.de> | 2020-05-30 10:23:08 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-30 10:23:08 +0300 |
| commit | 7156a2b06af597ca5e6cdb4e2cb17ac82ad5efd8 (patch) | |
| tree | 8083b4c4134bd61e5296d7a67b8ce5cef96a3767 /SECURITY.md | |
| parent | 50aea07d6ae7887994b35a190607a34382f3608a (diff) | |
| parent | 9768cc70d4dbd323c837afb6f29a3c6f9e24309e (diff) | |
Merge pull request #4220: Fix database encoding
In #4213 it was reported that connecting to a server with a unicode
character (Emoji) in the name can crash the server (provided the user
name passes validation which is only possible if the server uses a
special rule for the username config) when using MySQL as the backend.
This is because we have been using "utf8" for MySQL which - as it turns
out - isn't actual utf8 (https://mathiasbynens.be/notes/mysql-utf8mb4).
Therefore this commit changes this behavior by setting the proper utf8
encoding for MySQL databases. For SQLite and PostgreSQL the encoding is
checked and if it is not utf8 (or utf16), the server will refuse to
start. This is because there is no way to set the encoding for existing
databases for these backends.
Fixes #4213
Changelog
| Fixed: Character encoding issues with MySQL which could lead to crash
Diffstat (limited to 'SECURITY.md')
0 files changed, 0 insertions, 0 deletions