Certificate problem between 3.0.11 and 3.1.x

[Arran Cudbard-Bell]

> On 16 Mar 2016, at 16:44, Alan DeKok <aland at deployingradius.com> wrote:
> 
> On Mar 16, 2016, at 10:23 AM, Jonathan Gazeley <Jonathan.Gazeley at bristol.ac.uk> wrote:
>> Well, I wasn't able to get any useful debugging information out of Windows so we have reluctantly taken the decision to revert from bleeding-edge 3.1.x to stable 3.0.11 and work around the problem we were having by avoiding it. We'll revisit this when 3.2.x is released.
> 
>  If you have time... it would help to know when 3.1 stopped working.  You could grab a copy of 3.1 from early 2015, and see if it works.  If so, do a binary search on the commits until you get one which works, and one shortly after that which doesn't.
> 
>  That would at least help us narrow down what changed.  And would likely allow us to fix the problem.

Using current v3.1.x HEAD and running with -Xxx or a debug condition with debug level 3 set would also help.

We could compare the unencrypted tunnel data to what we see with wpa_supplicant and see what's different.

-Arran

Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS development team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 872 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20160316/c24c963c/attachment.sig>