On 09/01/2016 05:40 PM, Jiří Činčura wrote: > Nice, nailed it. > > Another question. For Srp I send the auth data as a HEX string in UTF8 > bytes (and that works), while in Sspi the auth data is sent (at least > only that works) as bytes directly. In both cases in > isc_dpb_specific_auth_data. > > Srp: byte[] -> HEX string -> UTF8 byte[] -> isc_dpb_specific_auth_data > Sspi: byte[] -> isc_dpb_specific_auth_data > > That doesn't seem right to me.
SSPI is used for windows only, and the data sent is exactly what windows recommends. With Srp I've chosen hex form due to the following reason. (BTW I can't imagine difference for hex string between utf8 and plain ascii). Tommath library keeps bigintegers in some internal form not known to outer world. It may be exported/imported in text string using various radix (from 2 to 50) or in internal binary form. That binary form is definitely more compact - but what happens with it on machines with different endianess? Or what will happen if another biginteger implementation will be used instead tommath in some client? On the other hand text with radix representation does not depend upon both issues and radix == 16 is expected to be supported by any reasonable big integer packet. Returning to SSPI - it's not expected to have different endianess (windows runs on intels) and moreover different implementations. Therefore no such problems with it. > But it's the combination that works. Am I > doing it right? > Yes. ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
