mirror of https://github.com/postgres/postgres
Coverity complained about possible buffer overrun in two places added by
commit 1eb6d6527
, and AFAICS it's reasonable to worry: even granting that
the WAL originator properly truncated the commit GID to GIDSIZE, we should
not really bet our lives on that having the same value as it does in the
current build. Hence, use strlcpy() not strcpy(), and adjust the pointer
advancement logic to be sure we skip over the whole source string even if
strlcpy() truncated it.
pull/27/merge
parent
05e85d35af
commit
b01f32c313
Loading…
Reference in new issue