Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAM message. - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAM message.
Date
Msg-id CAB7nPqQrU1QyagF0i0MVw5_Cxy+YF+kJj5m8X5+qnNawn_UJuQ@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAMmessage.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAMmessage.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
On Mon, May 29, 2017 at 2:06 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> These messages look all wrong to me.

So your complain would be to do the following for each error message
that uses parenthesis to include details? Like that I suppose:
--- a/src/backend/libpq/auth-scram.c
+++ b/src/backend/libpq/auth-scram.c
@@ -283,11 +283,13 @@ pg_be_scram_exchange(void *opaq, char *input,
int inputlen,   if (inputlen == 0)       ereport(ERROR,               (errcode(ERRCODE_PROTOCOL_VIOLATION),
-                (errmsg("malformed SCRAM message (empty message)"))));
+                errmsg("malformed SCRAM message"),
+                errdetail("Empty message.")));   if (inputlen != strlen(input))       ereport(ERROR,
(errcode(ERRCODE_PROTOCOL_VIOLATION),
-                (errmsg("malformed SCRAM message (length mismatch)"))));
+                errmsg("malformed SCRAM message"),
+                errdetail("Length mismatch.")));
-- 
Michael


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAM message.
Next
From: Alvaro Herrera
Date:
Subject: Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAMmessage.