Discussion:
[freetds] NTLM buffer length insufficient
samuel.ferencik
2013-12-09 10:02:58 UTC
Permalink
Hi,

The default NTLM buffer length, as defined in tds/sspi.c (NTLMBUF_LEN = 4096) is insufficient in my environment. The token returned is 7566 bytes long. As a result, the call to InitializeSecurityContext() in tds_sspi_get_auth() returns SEC_E_INSUFFICIENT_MEMORY.

I have recompiled with a larger buffer size (16384) and tds_sspi_get_auth() now works.

I wonder if this is the right way to fix this - should people adjust the buffer length as needed and rebuild? Or should the default be increased in the trunk?

Thanks,
Sam

_______________________________________________

This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.

For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.

_______________________________________________
Frediano Ziglio
2013-12-16 14:25:16 UTC
Permalink
Post by samuel.ferencik
Hi,
The default NTLM buffer length, as defined in tds/sspi.c (NTLMBUF_LEN = 4096) is insufficient in my environment. The token returned is 7566 bytes long. As a result, the call to InitializeSecurityContext() in tds_sspi_get_auth() returns SEC_E_INSUFFICIENT_MEMORY.
I have recompiled with a larger buffer size (16384) and tds_sspi_get_auth() now works.
I wonder if this is the right way to fix this - should people adjust the buffer length as needed and rebuild? Or should the default be increased in the trunk?
Thanks,
Sam
I don't see any problem with the patch. Perhaps we could use a
parameter to let InitializeSecurityContext allocate memory for you but
I have to test it.

Frediano

Loading...