October 2014 - Freeradius-Users - lists.freeradius.org

rlm_eap problem after upgrade from 2.1.12 to 2.2.5 via radsecproxy
by Thomas Boettcher 08 Oct '14

08 Oct '14

Hello community, my setup are two boxes with Freeradius and radsecproxy 1.6.5 in an eduroam environment. after upgrading from 2.1.12 to 2.2.5 without any configuration changes I register an enormous (times 31 (562:17678 per day)) amount of error messages: "rlm_eap: No EAP session matching the State variable." The following "Login incorrect:" is mainly from the radsecproxy nas clients. Users from the remote locations brought me to the Problem since they are authenticated OK and just seconds later the above error results in a "Login incorrect". These users are filling my logs with wavelike loglines (OK, incorrect, OK, incorrect). On the other hand not all remote users are affected. The users who stated to have to problem were all within the international eduroam community (not national), but this is just a guess. I do not understand why the eap state variable could be mixed up by a Software Upgrade to a "stable" version, so it looks to me that the problem resides within the freeradius programming. At the moment I do not fully understand all code differences between the two versions. I downgraded to 2.1.12 again to keep my users online, but the problem should be solved. Any ideas to debug the problem are welcome. Does anyone see similar problems with 2.2.5? Thanks for any help, Thomas Böttcher

3 4

checking Packet-Type in post-proxy
by Pshem Kowalczyk 08 Oct '14

08 Oct '14

Hi, I have a setup with a frontend server that proxies all request to a number of backend servers. Depending on the type of the reply packet it supposed to do something extra (like log it into the database and update some aspects of the reply for Access-Accept) I've tried this setup: post-proxy { if (proxy-reply:Packet-Type == Access-Accept ){ .... } but it doesn't seem to trigger: (2) if (proxy-reply:Packet-Type == Access-Accept ) (2) if (proxy-reply:Packet-Type == Access-Accept ) -> FALSE (2) } # post-proxy = noop So I decided to map it to different attribute to see what the value actually is: post-proxy { update control { Filter-Id := "%{proxy-reply:Packet-Type}" } if (proxy-reply:Packet-Type == Access-Accept ){ .... } And this seems to capture the content fine: (2) post-proxy { (2) update control { (2) EXPAND %{proxy-reply:Packet-Type} (2) --> Access-Accept (2) Filter-Id := '"Access-Accept"' (2) } # update control = noop (2) if (proxy-reply:Packet-Type == Access-Accept ) (2) if (proxy-reply:Packet-Type == Access-Accept ) -> FALSE (2) } # post-proxy = noop For now I've settled on this setup: post-proxy { update control { Filter-Id := "%{proxy-reply:Packet-Type}" } if (control:Filter-Id == 'Access-Accept'){ ... } (2) post-proxy { (2) update control { (2) EXPAND %{proxy-reply:Packet-Type} (2) --> Access-Accept (2) Filter-Id := '"Access-Accept"' (2) } # update control = noop (2) if (control:Filter-Id == 'Access-Accept') (2) if (control:Filter-Id == 'Access-Accept') -> TRUE That works fine. I just wonder if there's a simpler way of checking the type of the packet? (Freeradius 3.0.4) kind regards Pshem

3 2

Re: Beginner help (Alan DeKok)
by KAVYA PRABHAKAR 07 Oct '14

07 Oct '14

> > > > Hi, > > > to the TOP of the users file? the same file that the server is > reading...and > restarted > > the server before running the test? > > > > Yes, I have added test Cleartext-Password := "456" as the 1st line (TOP) in users file and restarted the server before running the test. But I encountered same error. (0) WARNING: pap : No "known good" password found for the user. Not setting Auth-Type. (0) WARNING: pap : Authentication will fail unless a "known good" password is available. (0) [pap] = noop (0) } # authorize = ok (0) ERROR: No Auth-Type found: rejecting the user via Post-Auth-Type = Reject (0) Failed to authenticate the user. (0) Using Post-Auth-Type Reject (0) # Executing group from file /usr/local/etc/raddb/sites-enabled/default (0) Post-Auth-Type REJECT { (0) attr_filter.access_reject : EXPAND %{User-Name} (0) attr_filter.access_reject : --> test (0) attr_filter.access_reject : Matched entry DEFAULT at line 11 In debug logs they say "at line 11". I checked the same in users file. That particular line is commented. Thanks, Kavya

2 1

Authentication and Authorization
by Alex Gregory 07 Oct '14

07 Oct '14

Hello- If I have both LDAP and Proxy configured will FreeRadius use both? What I am looking for is the FreeRadius server authorize a user in LDAP and if that passes forward the user to the upstream OTP radius server (via proxy.conf) for authentication. I believe its doing this now with the LDAP module, just authenticating locally, rather than proxied. Is this possible? Thanks, Alex

3 8

Windows 8.1 Wi-Fi client handshake failure
by Martin Rowe 07 Oct '14

07 Oct '14

Hello, I'm having trouble getting a Windows 8.1 laptop to connect to my Wi-Fi which is using only EAP-TLS managed by FreeRADIUS. Before you ask, yes I have included serverAuth/clientAuth in the certificates and the configuration is tested to work with Linux and Android clients, so I don't think there is a problem on the server side. That is as far as Google has been able to help me, so I'm hoping someone here has had the same problem and might know a solution. The specific issue as far as I can troubleshoot is that the client and server can't agree on a shared TLS cipher. I'm seeing these lines in my logs every time I attempt a connection: Info: [tls] TLS_accept: before/accept initialization Info: [tls] <<< TLS 1.0 Handshake [length 0067], ClientHello Info: [tls] >>> TLS 1.0 Alert [length 0002], fatal handshake_failure Error: TLS Alert write:fatal:handshake failure Error: TLS_accept: error in SSLv3 read client hello C Error: rlm_eap: SSL error error:1408A0C1:lib(20):func(138):reason(193) Error: SSL: SSL_read failed in a system call (-1), TLS session fails. >From [1] it looks like the SSL errors mean: lib(20) = ERR_LIB_SSL func(138) = SSL_F_SSL3_GET_CLIENT_HELLO reason(193) = SSL_R_NO_SHARED_CIPHER [1] http://comments.gmane.org/gmane.comp.encryption.openssl.user/9654 But that is as far as I can get. I've tried disabling every option I can in the configs and many variations on the Windows side, but they all stop at the same point. There is no limit I have set on which TLS ciphers can be used (cipher_list in eap{tls{}} is not used, and gave the same error when set to DEFAULT). My only other guess is there is something wrong with the certificates, but I'm not sure what might be wrong. I have copied both my root and my radius intermediate CA certificates onto the Windows client along with the client certificate and key. They are installed and the chain is valid according to the Windows Credential Manager. The server ca.pem has both the root and intermediate certificates concatenated together and that works fine with my other clients. So all I can think of is that Windows is being extra picky about something. Below is the sanitized text certificate for the server and client in the hope that the error is obvious to someone else: openssl x509 -text -in server.crt Certificate: Data: Version: 3 (0x2) Serial Number: * Signature Algorithm: ecdsa-with-SHA512 Issuer: O=CA, OU=radius Validity Not Before: Oct 6 17:01:03 2014 GMT Not After : Oct 6 17:01:03 2015 GMT Subject: O=CA, OU=radius, CN=my.server.fqdn Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (521 bit) pub: * ASN1 OID: secp521r1 X509v3 extensions: X509v3 Basic Constraints: CA:FALSE X509v3 Subject Key Identifier: * X509v3 Authority Key Identifier: keyid:* DirName:/O=CA/OU=root serial:* X509v3 CRL Distribution Points: Full Name: URI:http://my.crl.fqdn/radius.crl Authority Information Access: CA Issuers - URI:http://my.crl.fqdn/radius.pem OCSP - URI:http://my.ocsp.fqdn X509v3 Key Usage: Digital Signature, Key Encipherment X509v3 Extended Key Usage: TLS Web Server Authentication X509v3 Issuer Alternative Name: <EMPTY> X509v3 Subject Alternative Name: DNS:my.server.fqdn Signature Algorithm: ecdsa-with-SHA512 * -----BEGIN CERTIFICATE----- * -----END CERTIFICATE----- openssl x509 -text -in client.crt Certificate: Data: Version: 3 (0x2) Serial Number: * Signature Algorithm: ecdsa-with-SHA512 Issuer: O=CA, OU=radius Validity Not Before: Oct 1 21:49:00 2014 GMT Not After : Oct 1 21:49:00 2015 GMT Subject: O=CA, OU=radius, CN=username Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (521 bit) pub: * ASN1 OID: secp521r1 X509v3 extensions: X509v3 Basic Constraints: CA:FALSE X509v3 Subject Key Identifier: * X509v3 Authority Key Identifier: keyid:* DirName:/O=CA/OU=root serial:* X509v3 CRL Distribution Points: Full Name: URI:http://my.crl.fqdn/radius.crl Authority Information Access: CA Issuers - URI:http://my.crl.fqdn/radius.pem OCSP - URI:http://my.ocsp.fqdn X509v3 Key Usage: Digital Signature X509v3 Extended Key Usage: TLS Web Client Authentication X509v3 Issuer Alternative Name: <EMPTY> Signature Algorithm: ecdsa-with-SHA512 * -----BEGIN CERTIFICATE----- * -----END CERTIFICATE----- And my logs for good measure radiusd -XX Info: radiusd: FreeRADIUS Version 2.2.5, for host mips-openwrt-linux-gnu, built on Sep 28 2014 at 19:17:25 Debug: Server was built with: Debug: accounting Debug: authentication Debug: WITH_DHCP Debug: WITH_VMPS Debug: Server core libs: Debug: ssl: OpenSSL 1.0.1i 6 Aug 2014 Info: Copyright (C) 1999-2013 The FreeRADIUS server project and contributors. Info: There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A Info: PARTICULAR PURPOSE. Info: You may redistribute copies of FreeRADIUS under the terms of the Info: GNU General Public License. Info: For more information about these matters, see the file named COPYRIGHT. Info: Starting - reading configuration files ... Debug: including configuration file /etc/freeradius2/radiusd.conf Debug: including configuration file /etc/freeradius2/clients.conf Debug: including configuration file /etc/freeradius2/eap.conf Debug: including files in directory /etc/freeradius2/sites/ Debug: including configuration file /etc/freeradius2/sites/default Debug: main { Debug: allow_core_dumps = no Debug: } Debug: including dictionary file /etc/freeradius2/dictionary Debug: main { Debug: name = "radiusd" Debug: prefix = "/usr" Debug: localstatedir = "/var" Debug: sbindir = "/usr/sbin" Debug: logdir = "/var/log" Debug: run_dir = "/var/run" Debug: libdir = "/usr/lib/freeradius2" Debug: radacctdir = "/var/db/radacct" Debug: hostname_lookups = no Debug: max_request_time = 30 Debug: cleanup_delay = 5 Debug: max_requests = 2048 Debug: pidfile = "/var/run/radiusd.pid" Debug: checkrad = "/usr/sbin/checkrad" Debug: debug_level = 0 Debug: proxy_requests = yes Debug: log { Debug: stripped_names = no Debug: auth = no Debug: auth_badpass = no Debug: auth_goodpass = no Debug: } Debug: } Debug: radiusd: #### Loading Realms and Home Servers #### Debug: radiusd: #### Loading Clients #### Debug: client localhost { Debug: ipaddr = 127.0.0.1 Debug: require_message_authenticator = yes Debug: secret = "*removed1*" Debug: nastype = "other" Debug: } Debug: radiusd: #### Instantiating modules #### Debug: radiusd: #### Loading Virtual Servers #### Debug: server { # from file ?4?wXj Debug: modules { Debug: Module: Checking authenticate {...} for more modules to load Debug: (Loaded rlm_eap, checking if it's valid) Debug: Module: Linked to module rlm_eap Debug: Module: Instantiating module "eap" from file /etc/freeradius2/eap.conf Debug: eap { Debug: default_eap_type = "tls" Debug: timer_expire = 60 Debug: ignore_unknown_eap_types = no Debug: cisco_accounting_username_bug = no Debug: max_sessions = 2048 Debug: } Debug: Module: Linked to sub-module rlm_eap_tls Debug: Module: Instantiating eap-tls Debug: tls { Debug: rsa_key_exchange = no Debug: dh_key_exchange = yes Debug: rsa_key_length = 512 Debug: dh_key_length = 512 Debug: verify_depth = 0 Debug: pem_file_type = yes Debug: private_key_file = "/etc/freeradius2/certs/server.key" Debug: certificate_file = "/etc/freeradius2/certs/server.crt" Debug: CA_file = "/etc/freeradius2/certs/ca.pem" Debug: dh_file = "/etc/freeradius2/certs/dh" Debug: fragment_size = 1024 Debug: include_length = yes Debug: check_crl = no Debug: ecdh_curve = "prime256v1" Debug: } Debug: Module: Checking authorize {...} for more modules to load Debug: } # modules Debug: } # server Debug: radiusd: #### Opening IP addresses and Ports #### Debug: listen { Debug: type = "auth" Debug: ipaddr = 127.0.0.1 Debug: port = 0 Debug: } Debug: Listening on authentication address 127.0.0.1 port 1812 Debug: Listening on proxy address * port 1104 Info: Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 51343, id=22, length=205 User-Name = "*removed2*" Called-Station-Id = "*removed3*" NAS-Port-Type = Wireless-802.11 NAS-Port = 2 Calling-Station-Id = "*removed4*" Connect-Info = "CONNECT 54Mbps 802.11a" Acct-Session-Id = "542D9EF5-0000004F" Framed-MTU = 1400 EAP-Message = 0x024700110162726f6e7468696e6b706164 Message-Authenticator = 0x7e8c00ff349e844a25b649a660222938 Info: # Executing section authorize from file /etc/freeradius2/sites/default Info: +group authorize { Info: [eap] EAP packet type response id 71 length 17 Info: [eap] No EAP Start, assuming it's an on-going EAP conversation Info: ++[eap] = updated Info: +} # group authorize = updated Info: Found Auth-Type = EAP Info: # Executing group from file /etc/freeradius2/sites/default Info: +group authenticate { Info: [eap] EAP Identity Info: [eap] processing type tls Info: [tls] Requiring client certificate Info: [tls] Initiate Info: [tls] Start returned 1 Info: ++[eap] = handled Info: +} # group authenticate = handled Sending Access-Challenge of id 22 to 127.0.0.1 port 51343 EAP-Message = 0x014800060d20 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xafea1117afa21cb71a84ea873cb44d4b Info: Finished request 0. Debug: Going to the next request Debug: Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 51343, id=23, length=324 User-Name = "*removed2*" Called-Station-Id = "*removed3*" NAS-Port-Type = Wireless-802.11 NAS-Port = 2 Calling-Station-Id = "*removed4*" Connect-Info = "CONNECT 54Mbps 802.11a" Acct-Session-Id = "542D9EF5-0000004F" Framed-MTU = 1400 EAP-Message = 0x024800760d800000006c16030100670100006303015432d337768f888dfe17dc33835f35dd997aa21e12f03cacec5381488ea003f3000018c014c0130035002fc00ac00900380032000a00130005000401000022ff01000100000500050100000000000a0006000400170018000b0002010000230000 State = 0xafea1117afa21cb71a84ea873cb44d4b Message-Authenticator = 0xa8307e6d117840db9b85cd0c44938b91 Info: # Executing section authorize from file /etc/freeradius2/sites/default Info: +group authorize { Info: [eap] EAP packet type response id 72 length 118 Info: [eap] No EAP Start, assuming it's an on-going EAP conversation Info: ++[eap] = updated Info: +} # group authorize = updated Info: Found Auth-Type = EAP Info: # Executing group from file /etc/freeradius2/sites/default Info: +group authenticate { Info: [eap] Request found, released from the list Info: [eap] EAP/tls Info: [eap] processing type tls Info: [tls] Authenticate Info: [tls] processing EAP-TLS Debug: TLS Length 108 Info: [tls] Length Included Info: [tls] eaptls_verify returned 11 Info: [tls] (other): before/accept initialization Info: [tls] TLS_accept: before/accept initialization Info: [tls] <<< TLS 1.0 Handshake [length 0067], ClientHello Info: [tls] >>> TLS 1.0 Alert [length 0002], fatal handshake_failure Error: TLS Alert write:fatal:handshake failure Error: TLS_accept: error in SSLv3 read client hello C Error: rlm_eap: SSL error error:1408A0C1:lib(20):func(138):reason(193) Error: SSL: SSL_read failed in a system call (-1), TLS session fails. Debug: TLS receive handshake failed during operation Info: [tls] eaptls_process returned 4 Info: [eap] Handler failed in EAP/tls Info: [eap] Failed in EAP select Info: ++[eap] = invalid Info: +} # group authenticate = invalid Info: Failed to authenticate the user. Sending Access-Reject of id 23 to 127.0.0.1 port 51343 EAP-Message = 0x04480004 Message-Authenticator = 0x00000000000000000000000000000000 Info: Finished request 1. Debug: Going to the next request Debug: Waking up in 4.9 seconds. Info: Cleaning up request 0 ID 22 with timestamp +40 Info: Cleaning up request 1 ID 23 with timestamp +40 Info: Ready to process requests.

4 8

Problem with Proxy server testing
by Himanshu Pandey 07 Oct '14

07 Oct '14

Hi, I was trying to test the proxy server concept of freeradius so I did this: /* proxy.conf */ I added two proxy servers home_server safeword1 { type = auth+acct ipaddr = 192.168.178.25 port = 1812 secret = letmesafeword require_message_authenticator = no response_window = 20 zombie_period = 40 revive_interval = 120 status_check = status-server check_interval = 30 num_answers_to_alive = 3 } home_server google1 { type = auth+acct ipaddr = 172.16.1.27 port = 1812 secret = letmegoogle require_message_authenticator = no response_window = 20 zombie_period = 40 revive_interval = 120 status_check = status-server check_interval = 30 num_answers_to_alive = 3 } home_server_pool my_safeword_radius_servers { type = fail-over home_server = safeword1 } home_server_pool my_googleotp_radius_servers { type = fail-over home_server = google1 } realm "SAFEWORD" { auth_pool = my_safeword_radius_servers acct_pool = my_safeword_radius_servers } realm "GOOGLE" { auth_pool = my_googleotp_radius_servers acct_pool = my_googleotp_radius_servers } realm "GOOGLE" { # do nothing # this means use the local server } In /*hint*/ I added # GOOGLE #Detect gA at start of username and if so add realm GOOGLE at the end # see http://wiki.freeradius.org/Hints DEFAULT User-Name =~ "^(gA.*)" User-Name := "%{1}@GOOGLE" # SAFEWORD # Detect lowercase "v", 1 or 2 captial letters followed by 6 numbers # at start of username to identify a SAFEWORD token # and if so add realm SAFEWORD at the end # see http://wiki.freeradius.org/Hints DEFAULT User-Name =~ "^(v[A-Z]{1,2}[0-9]{6})" User-Name := "%{1}@SAFEWORD" Now I used radtest with the following command /opt/freeradius/bin/radtest gA123443 592455 192.168.178.25 1812 letmegoogle But it is giving an error. Please help me to resolve the same. Debug log: Listening on command file /opt/freeradius/var/run/radiusd/radiusd.sock Listening on auth address * port 1812 as server default Listening on acct address * port 1813 as server default Listening on auth address :: port 1812 as server default Listening on acct address :: port 1813 as server default Listening on auth address 127.0.0.1 port 18120 as server inner-tunnel Opening new proxy socket 'proxy address * port 0' Listening on proxy address * port 48013 Ready to process requests Received Access-Request Id 69 from 127.0.0.1:42855 to 127.0.0.1:1812 length 78 (0) Received Access-Request packet from host 127.0.0.1 port 42855, id=69, length=78 (0) Dropping packet without response because of error: Received packet from 127.0.0.1 with invalid Message-Authenticator! (Shared secret is incorrect.) Waking up in 0.3 seconds. (0) Cleaning up request packet ID 69 with timestamp +12 Ready to process requests Received Access-Request Id 69 from 127.0.0.1:42855 to 127.0.0.1:1812 length 78 (1) Received Access-Request packet from host 127.0.0.1 port 42855, id=69, length=78 (1) Dropping packet without response because of error: Received packet from 127.0.0.1 with invalid Message-Authenticator! (Shared secret is incorrect.) Waking up in 0.3 seconds. (1) Cleaning up request packet ID 69 with timestamp +17 Ready to process requests Received Access-Request Id 69 from 127.0.0.1:42855 to 127.0.0.1:1812 length 78 (2) Received Access-Request packet from host 127.0.0.1 port 42855, id=69, length=78 (2) Dropping packet without response because of error: Received packet from 127.0.0.1 with invalid Message-Authenticator! (Shared secret is incorrect.) Waking up in 0.3 seconds. (2) Cleaning up request packet ID 69 with timestamp +22 Ready to process requests Regards, Sonu

1 0

Re: Beginner help (Alan DeKok)
by KAVYA PRABHAKAR 07 Oct '14

07 Oct '14

Hi, I am running freeradius version 3 in debug mode. When I send radius request usign following command: radtest test 456 localhost 1812 testing123 I encountered following error: (0) WARNING: pap : No "known good" password found for the user. Not setting Auth-Type. (0) WARNING: pap : Authentication will fail unless a "known good" password is available. (0) [pap] = noop (0) } # authorize = ok (0) ERROR: No Auth-Type found: rejecting the user via Post-Auth-Type = Reject (0) Failed to authenticate the user. (0) Using Post-Auth-Type Reject I have added test Cleartext-Password := "456" in users file. I have not deleted any localhost related data from clients.conf afaik no more changes is required for this request to get accept message from server. I have been looking at this issue and reconfirmed that password which I have given in radius server matches with users file also. Could anybody please tell me where am I going wrong. Thanks, Kavya

2 1

Radmin Provides Per Proxy Server Statistics
by Himanshu Pandey 07 Oct '14

07 Oct '14

Hi friends, Using Radmin you can view the following statistics of a proxy server. The command for this is: radmin> stats home_server [auth/acct] OR <ipaddr> <port> e.g. stats home_server 127.0.0.1 1812 requests 0 responses 0 accepts 0 rejects 0 challenges 0 dup 0 invalid 0 malformed 0 bad_authenticator 0 dropped 0 unknown_types 0 timeouts 0 last_packet 0 elapsed.1us 0 elapsed.10us 0 elapsed.100us 0 elapsed.1ms 0 elapsed.10ms 0 elapsed.100ms 0 elapsed.1s 0 elapsed.10s 0 outstanding 0 Regards, Sonu From: "Himanshu Pandey" <pandey_himanshu80(a)rediffmail.com> Sent: Mon, 06 Oct 2014 10:56:53 To: "freeradius-users(a)lists.freeradius.org" <freeradius-users(a)lists.freeradius.org> Subject: Re: Per Proxy Server Statistics Hi, I want to track proxy server statistics like minimum response time, maximum response time, Average response time, Mean response time. I don't think the freeradius currently provides these statistics. Now, since I want these statistics, can somebody guide & help me to achieve these statistics using freeradius. Regards, Sonu From: Alan DeKok <aland(a)deployingradius.com> Sent: Tue, 30 Sep 2014 18:36:31 To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Subject: Re: Per Proxy Server Statistics Himanshu Pandey wrote: > Do radius server support Per Proxy Server Statistics like minimum > response time, maximum response time, Average response time, Mean > response time?  All of the statistics the server tracks can be queried with the "radmin" command.  If a statistics is missing, it's not tracked.  Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Get your own FREE website, FREE domain & FREE mobile app with Company email.  Know More > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

1 0

Re: Beginner help (Alan DeKok)
by KAVYA PRABHAKAR 06 Oct '14

06 Oct '14

> > > I have installed Freeradius version 3 and get openssl error as my > openssl version was in range 1.0.1 - 1.0.1f*. * > Now I removed my older openssl version and installed* *openssl 1.0.1g. > Edited radiusd.conf file as well. > > |allow_vulnerable_openssl = 'CVE-2014-0160'| > > When I start freeradius server ( ./radiusd -X for debug mode), it will > refuse to start with libssl version which is currently installed on your > server. Root cause for this is ?Security advisory CVE-2014-0160 > (Heartbleed)? > > > Then you're not editing the file which the server is reading. > > > Alan DeKok. > > > Thanks Alan. I corrected my mistake. Thanks, Kavya > >

1 0

Re:Re: Beginner help (Alan DeKok)
by KAVYA PRABHAKAR 06 Oct '14

06 Oct '14

> > > > Message: 1 > Date: Mon, 06 Oct 2014 07:58:34 -0400 > From: Alan DeKok <aland(a)deployingradius.com> > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Subject: Re: Beginner help > Message-ID: <543283EA.1060900(a)deployingradius.com> > Content-Type: text/plain; charset=UTF-8 > > KAVYA PRABHAKAR wrote: > > I have installed Freeradius version 3 and get openssl error as my > > openssl version was in range 1.0.1 - 1.0.1f*. * > > Now I removed my older openssl version and installed* *openssl 1.0.1g. > > Edited radiusd.conf file as well. > > > > |allow_vulnerable_openssl = 'CVE-2014-0160'| > > > > When I start freeradius server ( ./radiusd -X for debug mode), it will > > refuse to start with libssl version which is currently installed on your > > server. Root cause for this is ?Security advisory CVE-2014-0160 > > (Heartbleed)? > > Then you're not editing the file which the server is reading. > > > Ok. I will check it out. But I have only one freeradius 3.0.3 directory and I am editing raddb\radiusd.config file in the respective directory. Let me know if the path where I am editing the file is wrong. Thanks, Kavya

1 0