On 19 Apr 2016, at 08:29, Matthew Newton <mcn4@leicester.ac.uk> wrote:
On Sat, Apr 02, 2016 at 09:39:20PM -0400, Arran Cudbard-Bell wrote:
On 1 Apr 2016, at 14:01, Matthew Newton <mcn4@leicester.ac.uk> wrote:
On Fri, Apr 01, 2016 at 10:34:51AM -0600, Arran Cudbard-Bell wrote:
There's now support for OpenSSL 1.1.0-pre4 in v3.1.x.
Nice.
Our basic EAP test suite passes, but it would be useful if those who rely heavily on TLS could test this out in their lab environment.
I'll try and check it out here in the next couple of weeks if I get a spare 10 minutes.
Thanks Alan B/Matthew!
Took a while, sorry. Recommendation is to not get ill... :(
openssl 1.1.0-pre5-dev (34da11b39d24) freeradius v3.1.x (dc43c5913064)
The clients are Windows 7, and use PEAP/EAP-TLS. (Which I guess is fairly unusual in itself.) PEAP seems to come up fine, and SoH data is retrieved. Then inner-tunnel does EAP-TLS which looks like it's all there, but the client then goes silent on an Access-Challenge.
Yeah that's pre-existing. I think Win 7 might actually produce useful output though... If you can get a trace that'd help. I found the same issue with v3.0.x with OpenSSL 1.0.1 on Win 10. Assumed it was Win 10 though... Seems something more fundamental is broken. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2