Hi, Ahmed!
Thanks for checking this problem.
It is really a bug in Npgsql to convert the bytes value with ASCII encoder.
If we change that line to use the UTF-8 encoder, wouldn't it suffice
to fix this problem?
Also, wouldn't change the AuthenticationSSPI case to use context.Host
instead of Brar's code wouldn't break cases like the one he said in
his last email?
Thanks for feedback.
On Wed, Feb 2, 2011 at 14:11, Francisco Figueiredo Jr.
<francisco@npgsql.org> wrote:
> Thank you very much for your patch!
>
> I'm going to review and apply it.
>
> As soon as it is done, I'll let you know.
>
>
> On Wed, Feb 2, 2011 at 12:52, Ahmed <ahmed.shinwari@gmail.com> wrote:
>>
>> The issue has been addressed and patch has been submitted. Refer to Npgsql
>> mailing thread
>> http://lists.pgfoundry.org/pipermail/npgsql-devel/2011-February/001116.html
>> http://lists.pgfoundry.org/pipermail/npgsql-devel/2011-February/001116.html
>> .
>>
>> --
>> View this message in context:
http://postgresql.1045698.n5.nabble.com/could-not-accept-SSPI-security-context-tp3275102p3367884.html
>> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>
>
>
> --
> Regards,
>
> Francisco Figueiredo Jr.
> Npgsql Lead Developer
> http://www.npgsql.org
> http://fxjr.blogspot.com
> http://twitter.com/franciscojunior
>
--
Regards,
Francisco Figueiredo Jr.
Npgsql Lead Developer
http://www.npgsql.org
http://fxjr.blogspot.com
http://twitter.com/franciscojunior