Re: BUG #14998: XXS vulnerabilities in PostgreSQL 'utf8 4-byte truncation' - Mailing list pgsql-bugs

From Sergei Kornilov
Subject Re: BUG #14998: XXS vulnerabilities in PostgreSQL 'utf8 4-byte truncation'
Date
Msg-id 1246531515060571@web58o.yandex.ru
Whole thread Raw
In response to Fwd: BUG #14998: XXS vulnerabilities in PostgreSQL 'utf8 4-byte truncation'  (Thu Luu <ltthu2810@gmail.com>)
List pgsql-bugs
Hi!
I do not understand what your problem is. UTF8 character may be 4 bytes long by standart. Postgresql can store this
characters.Mysql - for history reasons - treat utf8 as at most 3 byte characters and is not fully unicode compatible.
Inmysql 5.5 was added utf8mb4 charset which is full unicode compatible and can store 4 byte characters (
https://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html). Discarding or correct storing 4-byte symbols is
notvulnerabilities, just historical error in mysql.
 

PS: given link is broken due outdated https cert.


pgsql-bugs by date:

Previous
From: Thu Luu
Date:
Subject: Fwd: BUG #14998: XXS vulnerabilities in PostgreSQL 'utf8 4-byte truncation'
Next
From: PG Bug reporting form
Date:
Subject: BUG #14999: pg_rewind corrupts control file global/pg_control