Skip to content

Commit bd029bc

Browse files
committed
From: Tom Lane <tgl@sss.pgh.pa.us> The attached patches respond to discussion that was on pgsql-hackers around the beginning of June (see thread "libpgtcl bug (and symptomatic treatment)"). The changes are: 1. Remove code in connectDB that throws away the password after making a connection. This doesn't really add much security IMHO --- a bad guy with access to your client's address space can likely extract the password anyway, to say nothing of what he might do directly. And there's the serious shortcoming that it prevents PQreset() from working if the database requires a password. 2. Fix coredump problem: fe_sendauth did not guard against being handed a NULL password pointer. (This is the proximate cause of the coredump- during-PQreset problem that Magosanyi Arpad complained of last month.) 3. Remove highly questionable "error recovery" logic in libpgtcl's pg_exec statement. I believe the consensus of the discussion last month was in favor of #1 and #3, but I'm just now getting around to making the change. I realized that #2 was a bug in process of looking at the change.
1 parent ce81267 commit bd029bc

File tree

3 files changed

+10
-32
lines changed

3 files changed

+10
-32
lines changed

src/interfaces/libpgtcl/pgtclCmds.c

Lines changed: 2 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
*
88
*
99
* IDENTIFICATION
10-
* $Header: /cvsroot/pgsql/src/interfaces/libpgtcl/Attic/pgtclCmds.c,v 1.27 1998/06/16 06:53:27 momjian Exp $
10+
* $Header: /cvsroot/pgsql/src/interfaces/libpgtcl/Attic/pgtclCmds.c,v 1.28 1998/07/09 03:32:09 scrappy Exp $
1111
*
1212
*-------------------------------------------------------------------------
1313
*/
@@ -441,24 +441,7 @@ Pg_exec(ClientData cData, Tcl_Interp *interp, int argc, char* argv[])
441441
}
442442
else {
443443
/* error occurred during the query */
444-
Tcl_SetResult(interp, conn->errorMessage, TCL_STATIC);
445-
if (connStatus != CONNECTION_OK) {
446-
/* Is this REALLY a good idea? I don't think so! */
447-
PQreset(conn);
448-
if (conn->status == CONNECTION_OK) {
449-
result = PQexec(conn, argv[2]);
450-
PgNotifyTransferEvents(connid);
451-
if (result) {
452-
int rId = PgSetResultId(interp, argv[1], result);
453-
if (result->resultStatus == PGRES_COPY_IN ||
454-
result->resultStatus == PGRES_COPY_OUT) {
455-
connid->res_copyStatus = RES_COPY_INPROGRESS;
456-
connid->res_copy = rId;
457-
}
458-
return TCL_OK;
459-
}
460-
}
461-
}
444+
Tcl_SetResult(interp, conn->errorMessage, TCL_VOLATILE);
462445
return TCL_ERROR;
463446
}
464447
}

src/interfaces/libpq/fe-auth.c

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
*
88
*
99
* IDENTIFICATION
10-
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-auth.c,v 1.18 1998/07/03 04:24:11 momjian Exp $
10+
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-auth.c,v 1.19 1998/07/09 03:32:09 scrappy Exp $
1111
*
1212
*-------------------------------------------------------------------------
1313
*/
@@ -522,6 +522,12 @@ fe_sendauth(AuthRequest areq, PGconn *conn, const char *hostname,
522522

523523
case AUTH_REQ_PASSWORD:
524524
case AUTH_REQ_CRYPT:
525+
if (password == NULL || *password == '\0')
526+
{
527+
(void) sprintf(PQerrormsg,
528+
"fe_sendauth: no password supplied\n");
529+
return (STATUS_ERROR);
530+
}
525531
if (pg_password_sendauth(conn, password, areq) != STATUS_OK)
526532
{
527533
(void) sprintf(PQerrormsg,

src/interfaces/libpq/fe-connect.c

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
*
88
*
99
* IDENTIFICATION
10-
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-connect.c,v 1.73 1998/07/09 03:29:07 scrappy Exp $
10+
* $Header: /cvsroot/pgsql/src/interfaces/libpq/fe-connect.c,v 1.74 1998/07/09 03:32:10 scrappy Exp $
1111
*
1212
*-------------------------------------------------------------------------
1313
*/
@@ -768,17 +768,6 @@ connectDB(PGconn *conn)
768768

769769
PQsetenv(conn);
770770

771-
/* Free the password so it's not hanging out in memory forever */
772-
/* XXX Is this *really* a good idea? The security gain is marginal
773-
* if not totally illusory, and it breaks PQreset() for databases
774-
* that use passwords.
775-
*/
776-
if (conn->pgpass != NULL)
777-
{
778-
free(conn->pgpass);
779-
conn->pgpass = NULL;
780-
}
781-
782771
return CONNECTION_OK;
783772

784773
connect_errReturn:

0 commit comments

Comments
 (0)