]> granicus.if.org Git - postgresql/commit
Use explicit_bzero
authorPeter Eisentraut <peter@eisentraut.org>
Thu, 5 Sep 2019 06:15:58 +0000 (08:15 +0200)
committerPeter Eisentraut <peter@eisentraut.org>
Thu, 5 Sep 2019 06:30:42 +0000 (08:30 +0200)
commit74a308cf5221f491776fcdb4dc36eb61678dbc6f
treec2e9a146616d9b40dcd606db4030abcd1b1fe25b
parentae060a52b2881ea842f596fa78b8d09f9a91b149
Use explicit_bzero

Use the explicit_bzero() function in places where it is important that
security information such as passwords is cleared from memory.  There
might be other places where it could be useful; this is just an
initial collection.

For platforms that don't have explicit_bzero(), provide various
fallback implementations.  (explicit_bzero() itself isn't standard,
but as Linux/glibc, FreeBSD, and OpenBSD have it, it's the most common
spelling, so it makes sense to make that the invocation point.)

Discussion: https://www.postgresql.org/message-id/flat/42d26bde-5d5b-c90d-87ae-6cab875f73be%402ndquadrant.com
configure
configure.in
src/backend/libpq/be-secure-common.c
src/include/pg_config.h.in
src/include/pg_config.h.win32
src/include/port.h
src/interfaces/libpq/fe-connect.c
src/port/explicit_bzero.c [new file with mode: 0644]
src/tools/msvc/Mkvcbuild.pm