Agreed, but it would be good to use all sensible means available to
communicate this - it is not one or the other, there's no mutual
exclusivity.
I just feel that it would be useful to try and step in to prevent this
from becoming a problem when iOS 9 and OS X El Capitan come out of
beta and
Hi,
Not tested, but I suspect that we will find that 1.53 is the version
at which this starts to work and, if so, it should become the minimum
version that should be used.
based on other changes etc I would say just go for the current latest
release - 1.70 - why opt for something older?
On 07/30/2015 08:57 PM, Nick Lowe wrote:
Agreed: Added support for SSL_export_keying_material where present
(ie in OpenSSL 1.0.1 and later).
Support for this Net::SSLeay function was added in Radiator 4.11
patches. In other words, Radiator 4.12 and later will use it if it's
available.
Hi,
Installing and running Radiator 4.15 under CentOS 7 with SELinux in enforced
mode worked out of the box. However, we don't use any databases. Our
environment is pretty typical for eduroam-installations: local users are
authenticated against a Windows-AD (using winbind) and non-local users
1.46 doesn't work.
Nick
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
On 7/24/2015 3:17 PM, David Zych wrote:
so I installed the latest Net::SSLeay 1.70 from cpan and successfully
got rid of the warnings.
After I deployed these changes to production, we were pleasantly
astonished to discover that El Capitan and iOS 9 clients were suddenly
able to connect with
Agreed: Added support for SSL_export_keying_material where present
(ie in OpenSSL 1.0.1 and later).
Not tested, but I suspect that we will find that 1.53 is the version
at which this starts to work and, if so, it should become the minimum
version that should be used.
Regards,
Nick
On Thu, Jul
Hi David,
I definitely agree with your suggestion. Now that we all know that
this is an issue, we can take steps to raise awareness and inform. For
Eduroam in particular, I feel that notices should be put out to
participating institutions.
I replied to Heikki before, forgetting to copy to the
Hi,
I definitely agree with your suggestion. Now that we all know that
this is an issue, we can take steps to raise awareness and inform. For
Eduroam in particular, I feel that notices should be put out to
participating institutions.
actually, as a specific vendor problem, I would hope that
