From: Tom Lane Date: Sat, 6 Mar 2010 00:46:18 +0000 (+0000) Subject: When reading pg_hba.conf and similar files, do not treat @file as an inclusion X-Git-Tag: REL8_0_24~6 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=cc2f4e091839dd937b9d5483ca7739bf2d9fb7f7;p=thirdparty%2Fpostgresql.git When reading pg_hba.conf and similar files, do not treat @file as an inclusion unless (1) the @ isn't quoted and (2) the filename isn't empty. This guards against unexpectedly treating usernames or other strings in "flat files" as inclusion requests, as seen in a recent trouble report from Ed L. The empty-filename case would be guaranteed to misbehave anyway, because our subsequent path-munging behavior results in trying to read the directory containing the current input file. I think this might finally explain the report at http://archives.postgresql.org/pgsql-bugs/2004-05/msg00132.php of a crash after printing "authentication file token too long, skipping", since I was able to duplicate that message (though not a crash) on a platform where stdio doesn't refuse to read directories. We never got far in investigating that problem, but now I'm suspicious that the trigger condition was an @ in the flat password file. Back-patch to all active branches since the problem can be demonstrated in all branches except HEAD. The test case, creating a user named "@", doesn't cause a problem in HEAD since we got rid of the flat password file. Nonetheless it seems like a good idea to not consider quoted @ as a file inclusion spec, so I changed HEAD too. --- diff --git a/src/backend/libpq/hba.c b/src/backend/libpq/hba.c index 0c5c0e5bcfe..34a9c1c916a 100644 --- a/src/backend/libpq/hba.c +++ b/src/backend/libpq/hba.c @@ -10,7 +10,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/libpq/hba.c,v 1.136.4.2 2010/03/03 20:31:41 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/libpq/hba.c,v 1.136.4.3 2010/03/06 00:46:18 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -111,7 +111,7 @@ pg_isblank(const char c) * database names specially, by appending a newline to them. */ static void -next_token(FILE *fp, char *buf, int bufsz) +next_token(FILE *fp, char *buf, int bufsz, bool *initial_quote) { int c; char *start_buf = buf; @@ -120,8 +120,11 @@ next_token(FILE *fp, char *buf, int bufsz) bool was_quote = false; bool saw_quote = false; + /* end_buf reserves two bytes to ensure we can append \n and \0 */ Assert(end_buf > start_buf); + *initial_quote = false; + /* Move over initial whitespace and commas */ while ((c = getc(fp)) != EOF && (pg_isblank(c) || c == ',')) ; @@ -180,6 +183,8 @@ next_token(FILE *fp, char *buf, int bufsz) { in_quote = !in_quote; saw_quote = true; + if (buf == start_buf) + *initial_quote = true; } c = getc(fp); @@ -219,12 +224,13 @@ next_token_expand(const char *filename, FILE *file) char buf[MAX_TOKEN]; char *comma_str = pstrdup(""); bool trailing_comma; + bool initial_quote; char *incbuf; int needed; do { - next_token(file, buf, sizeof(buf)); + next_token(file, buf, sizeof(buf), &initial_quote); if (!buf[0]) break; @@ -237,7 +243,7 @@ next_token_expand(const char *filename, FILE *file) trailing_comma = false; /* Is this referencing a file? */ - if (buf[0] == '@') + if (!initial_quote && buf[0] == '@' && buf[1] != '\0') incbuf = tokenize_inc_file(filename, buf + 1); else incbuf = pstrdup(buf);