[RADIATOR] What is the best way to get Net::LDAP on REdHat 8 ?

Ehlers, Y.W. (Ydo) y.ehlers at ru.nl
Fri Feb 21 15:12:30 UTC 2020


Heikki,


Thank you for your  input.
I have decided on the EPEL repo as well.

It turned out to be already provisioned by our automation tool (puppet) on RedHat 8, just not enabled by default.
Being also in line with our generic setup for RedHat8 hosts, it is really a no-brainer to choose the Epel route.

Thanks,


--
Ydo Ehlers | IT Beheerder | ICT Service Center | Radboud Universiteit | Postbus 9102, 6500 HC Nijmegen | (024) 361 78 94 | www.ru.nl/isc

Dit bericht en elke eventuele bijlage is uitsluitend bestemd voor de geadresseerde(n) en kan vertrouwelijke informatie bevatten. Indien u niet de geadresseerde bent mag u dit bericht en de bijlage niet kopiëren of aan derden ter inzage geven of verspreiden. 
U wordt verzocht de afzender hiervan onmiddellijk op de hoogte te stellen en het bericht te vernietigen.


> -----Original Message-----
> From: radiator <radiator-bounces at lists.open.com.au> On Behalf Of Heikki
> Vatiainen
> Sent: Friday, February 21, 2020 1:01 PM
> To: radiator at lists.open.com.au
> Subject: Re: [RADIATOR] What is the best way to get Net::LDAP on REdHat 8 ?
> 
> On 21.2.2020 10.28, Ehlers, Y.W. (Ydo) wrote:
> 
> > As I was saying, CPAN versus EPEL.
> > Are there any pro’s and con’s when using Radiator?
> 
> Looks like the version in EPEL is the current released version CPAN offers. Both
> are fine with Radiator so for me it seems a matter of local preference.
> 
> > I have no personal favourite, I would like to choose the most
> > futureproof and robust solution.
> 
> In terms of features Radiator can use either one, especially because they are now
> exactly the same version. We currently use EPEL version with automatic tests that
> run in el8 environment. However, the LDAP features Radiator uses are not
> complicated so an older versions work fine and newer version should work fine as
> well.
> 
> > So I hope someone else has already gone through the same struggles and
> > came up with the ultimate answer….
> 
> What we have seen is that this often comes to local preference: some organisations
> like to use pre-packaged modules while some prefer CPAN.
> 
> Comments would be welcome of course.
> 
> Thanks,
> Heikki
> 
> --
> Heikki Vatiainen <hvn at open.com.au>
> 
> Radiator: the most portable, flexible and configurable RADIUS server anywhere.
> SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory, EAP, TLS,
> TTLS, PEAP, WiMAX, RSA, Vasco, Yubikey, HOTP, TOTP, DIAMETER etc. Full
> source on Unix, Windows, MacOSX, Solaris, VMS, etc.
> _______________________________________________
> radiator mailing list
> radiator at lists.open.com.au
> https://lists.open.com.au/mailman/listinfo/radiator


More information about the radiator mailing list