Microsoft ODBC bug
a.cudbardb at freeradius.org
Thu Jul 4 20:21:18 CEST 2019
> On 4 Jul 2019, at 11:10, Dom Latter <freeradius-users at latter.org> wrote:
> On 03/07/2019 07:53, Alan DeKok wrote:
>> On Jul 2, 2019, at 6:21 PM, Dom Latter <freeradius-users at latter.org> wrote:
>>>> That's all well and good, but what should *we* be doing differently?
>>> Well, if I knew that...
>> That is the problem.
>> As background, the unfortunate thing is that the FreeRADIUS core team is pretty darn small (less than 5, by a lot.) And we're expected to be experts in:
>> * RADIUS
> Yes, it's a lot of stuff.
> Anyway, I have run ltrace to grab calls to the MS ODBC driver, from both
> freeradius and a small python test script (which doesn't exhibit this
> weird bug).
> These are the calls (sorted alphabetically) that are used by Freeradius:
> And these are the ones used by Python:
Could we get the calls listed chronologically.
Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
More information about the Freeradius-Users