On Oct 27, 2016, at 10:24 AM, Matthew Newton <mcn4@leicester.ac.uk> wrote:
On Thu, Oct 27, 2016 at 02:01:00PM +0000, Stefan Paetow wrote:
At this point, if you need the features in v3.1., just use the v3.1.x branch. It's stable, and used by many people in production.
There are still regular checkins... This bugs our dev :-)
Sounds like your problem then :)
So if we were to choose a specific Github commit, we should be ok. The blessed release also gives someone paranoid enough about this reassurance that that release is stable enough to go with it.
TBH, I do that with 3.0.x as well anyway.
No software is perfect. "Releases" are just a thing to make people who don't understand think they're getting something more stable. There are still bugs.
I'd just pick a commit and run with it, then you can cherry-pick any future bugfixes if you need them.
I *think* there's still an issue with EAP-TLS on Windows with 3.1? Haven't had time to look at it for a while. Stability is still to be found in 3.0. :)
I think it's only weird ones where you're combining EAP-TLS and PEAP, and I think it's broken in v3.0.x as well. I... I guess you could say "fixed" but it wasn't really broken... Um, changed the fragmentation behaviour back to v3.0.x style in v3.1.x. -Arran