poor wording on SSPI error message - Mailing list pgsql-hackers

From Alvaro Herrera
Subject poor wording on SSPI error message
Date
Msg-id 20090306201607.GA3162@alvh.no-ip.org
Whole thread Raw
Responses Re: poor wording on SSPI error message  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Hi,

This message
   r = (_QuerySecurityContextToken) (sspictx, &token);   if (r != SEC_E_OK)   {       FreeLibrary(secur32);
pg_SSPI_error(ERROR,             gettext_noop("could not get security token from context"), r);   }
 

looks poorly worded.  What "context" is it talking about?  Can we be a
bit more explicit?  Any other thoughts on how to improve it?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: libxml incompatibility
Next
From: Kenneth Marshall
Date:
Subject: Re: libxml incompatibility