> 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
OK, makes kinda sense. The inconsistency was just conf
I guess atomic also must be very helpful.
2016-09-01 20:37 GMT+03:00 Adriano dos Santos Fernandes :
> On 01/09/2016 13:41, Dmitry Yemanov wrote:
>> + nullptr and static_assert, maybe also initializer lists and non-static
>> member initializers.
>>
> And override too, which can be easily defined fo
On 01/09/2016 13:41, Dmitry Yemanov wrote:
> + nullptr and static_assert, maybe also initializer lists and non-static
> member initializers.
>
And override too, which can be easily defined for nothing when not
supported (HP aCC) and is a very good tool specially when refactoring code.
Adriano
01.09.2016 15:46, Adriano dos Santos Fernandes wrote:
>
> I see that before VC++ 2015 Update 3, it accepts everything supported
> without compiler options, right?
Looks so.
> So, I think the plan should be:
>
> - Update Linux prefix files to include -std=c++11
> - Agree on a set of allowed featur
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.
>
>
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_speci
On 09/01/2016 04:54 PM, Jiří Činčura wrote:
> So where the client auth data should be sent? And which tag?
>
client auth data may be sent:
1. In op_connect, in user_id, tag CNCT_specific_data, together with CNCT_login,
CNCT_plugin_name and CNCT_plugin_list (used first time).
2. In DPB, tag isc_dp
So where the client auth data should be sent? And which tag?
--
Mgr. Jiří Činčura
Independent IT Specialist
On Thu, Sep 1, 2016, at 14:57, Alex Peshkoff wrote:
> On 09/01/2016 01:39 PM, Jiří Činčura wrote:
> > Looks like I moved somewhere. In op_connect+op_accept I send as
> > plugin
> > Win_Ssp
On 09/01/2016 01:39 PM, Jiří Činčura wrote:
> Looks like I moved somewhere. In op_connect+op_accept I send as plugin
> Win_Sspi and I send the client token. Then I get back response as
> op_accept_data, there I find the auth data from server and I can use
> there to create client authentication dat
On Thu, Sep 01, 2016 at 03:25:39PM +0300, Dmitry Yemanov wrote:
> 01.09.2016 14:04, Adriano dos Santos Fernandes wrote:
> >
> > MSVC10 supports nothing, and even MSVC12 is also a bit limited in regard
> > to MSVC14 and recent g++ and clang++:
> >
> > https://msdn.microsoft.com/en-us/library/hh56736
On 01/09/2016 09:25, Dmitry Yemanov wrote:
> 01.09.2016 14:04, Adriano dos Santos Fernandes wrote:
>> MSVC10 supports nothing, and even MSVC12 is also a bit limited in regard
>> to MSVC14 and recent g++ and clang++:
>>
>> https://msdn.microsoft.com/en-us/library/hh567368.aspx
> We've agreed on MSVC
Error when "Execute Statement ... on external data source" done under trusted
authentication without "As user ... PASSWORD ... ROLE .." parameters
--
01.09.2016 14:04, Adriano dos Santos Fernandes wrote:
>
> MSVC10 supports nothing, and even MSVC12 is also a bit limited in regard
> to MSVC14 and recent g++ and clang++:
>
> https://msdn.microsoft.com/en-us/library/hh567368.aspx
We've agreed on MSVC13 for FBv4, so we cannot use features from late
On 31/08/2016 04:54, Dmitry Yemanov wrote:
> 31.08.2016 05:14, Adriano dos Santos Fernandes wrote:
>> In the code I'm writing, I had good opportunities to use some features
>> that the compiler flags we're using disallowed, like lambda and default
>> arguments for template parameter.
>>
>> Also we
Looks like I moved somewhere. In op_connect+op_accept I send as plugin
Win_Sspi and I send the client token. Then I get back response as
op_accept_data, there I find the auth data from server and I can use
there to create client authentication data.
In protocol <13 this was sent to server using o
Hi *,
was there any change in FB3 of how the isc_dpb_trusted_auth is handled?
In FB2.5 I get as a response op_trusted_auth with bunch of bytes to
initialize SSPI context. But on FB3 the response is op_cont_auth.
I suppose the isc_dpb_trusted_auth is done differently on FB3. Can
somebody give me s
16 matches
Mail list logo
