- Freeradius-Devel - lists.freeradius.org

cert bootstrap script change: no more MD5?
by Stefan Winter 18 Oct '11

18 Oct '11

Hi, the bootstrap script uses ca.cnf, server.cnf and client.cnf for the generated certificates. All of these set the default_md = md5. iOS 5 is the first OS to condemn certificates which are signed by MD5. So, the default certificates generated by this script will not be compatible with recent iOS. Does anything speak against up'ing the default_md to sha1? Otherwise I can see questions on -user coming up saying EAP doesn't work - and this time with a particularly difficult to diagnose issue. Greetings, Stefan Winter

5 7

current GIT of FR 3.0 doesnt compile
by Alan Buxey 17 Oct '11

17 Oct '11

hi, fails in the mysql: sql_mysql.c: In function 'sql_init_socket': sql_mysql.c:80: error: 'SQLSOCK' has no member named 'id' gmake[10]: *** [sql_mysql.lo] Error 1 gmake[9]: *** [rlm_sql_mysql] Error 2 gmake[8]: *** [all] Error 2 gmake[7]: *** [drivers] Error 2 gmake[6]: *** [build-module] Error 2 gmake[5]: *** [rlm_sql] Error 2 gmake[4]: *** [all] Error 2 gmake[3]: *** [modules] Error 2 gmake[2]: *** [all] Error 2 gmake[1]: *** [src] Error 2 make: *** [all] Error 2 alan

2 2

new rlm_sql connection pool logic
by Arran Cudbard-Bell 17 Oct '11

17 Oct '11

Hi All, Alan mercilessly ripped out all the connection pool logic in rlm_sql and replaced it with calls to the generic connection pool API which is new in 3.0. In anyone's running an SQL DB and wants to test it'd be much appreciated. New code is in Master@HEAD. WARNING: This change breaks compatibility with V2.0 configs, you will need an empty pool { } stanza in each instance of rlm_sql configuration or the server will fail to load. See here https://github.com/alandekok/freeradius-server/blob/master/raddb/modules/sql for the full pool configuration sub-section. The following configuration items no longer have any effect: num_sql_socks, connect_failure_retry_delay, lifetime, max_queries. Their equivalents are, (start, mix, max, spare), *none* , lifetime, uses. DEVELOPERS NOTE: From this point onwards any new modules which use a pool of connections, or would benefit from a pool of connections but doesn't use the connection API, will not be accepted. Code for connection pool is here: https://github.com/alandekok/freeradius-server/blob/master/src/main/connect… #include <freeradius-devel/connection.h> -Arran Arran Cudbard-Bell a.cudbardb(a)freeradius.org Betelwiki, Betelwiki, Betelwiki.... http://wiki.freeradius.org/ !

5 18

EAP Testing - Newbie
by Sergio NNX 16 Oct '11

16 Oct '11

Ciao all, First of all, I'm new to this project so I may ask 'dumb' questions and I may be slow to understand. Be patient! I'm in the process of testing FreeRADIUS 2.1.11, just basic/standard setup. I've been following the following user guide: http://deployingradius.com/documents/configuration/pap.html. Very useful, by the way. PAP, MSCHAP and MSCHAPv2 work ok, but I'm unable to get any EAP tests to pass. I've tries almost everything, including: http://deployingradius.com/documents/configuration/eap-problems.html I need some help! Thanks in advance. Sergio. Test output ------------- radtest -t eap-md5 ....... (it works ok) (Client side) Sending Access-Request packet to host 127.0.0.1 port 1812, id=229, length=0 User-Name = "testuser" User-Password = "testpw" NAS-IP-Address = 127.0.0.1 NAS-Port = 1812 EAP-Code = Response EAP-Type-Identity = "testuser" Message-Authenticator = 0x00 EAP-Message = 0x02e4000d017465737475736572 Received Access-Challenge packet from host 127.0.0.1 port 1812, id=229, length=97 Reply-Message = "Hello, testuser" EAP-Message = 0x01e5001604103823185ef840cc37ad7436a904db9605 Message-Authenticator = 0xf5a2da42e33cfe56a80104afb9931946 State = 0x3dcf853c3d2a813191ce5fb05bf39134 EAP-Id = 229 EAP-Code = Request EAP-Type-MD5 = 0x103823185ef840cc37ad7436a904db9605 Sending Access-Request packet to host 127.0.0.1 port 1812, id=230, length=93 User-Name = "testuser" User-Password = "testpw" NAS-IP-Address = 127.0.0.1 NAS-Port = 1812 EAP-Code = Response Message-Authenticator = 0x00000000000000000000000000000000 EAP-Type-MD5 = 0x105a160cce9524d55843b32d1fcbaedb6b EAP-Id = 229 State = 0x3dcf853c3d2a813191ce5fb05bf39134 EAP-Message = 0x02e5001604105a160cce9524d55843b32d1fcbaedb6b Received Access-Accept packet from host 127.0.0.1 port 1812, id=230, length=71 Reply-Message = "Hello, testuser" EAP-Message = 0x03e50004 Message-Authenticator = 0xa9e17bcb7d0b8e0ad062f9b3c5d0399c User-Name = "testuser" EAP-Id = 229 EAP-Code = Success Total approved auths: 1 Total denied auths: 0 (Server side) Ready to process requests. # Executing section authorize from file ..\etc\raddb/radiusd.conf +- entering group authorize {...} [auth_log] ../var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d.log expands to ../var/log/radius/radacct/127.0.0.1/auth-detail-20111016.log ++[auth_log] returns ok [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop ++[mschap] returns noop [files] users: Matched entry testuser at line 29 ++[files] returns ok [eap] EAP packet type response id 228 length 13 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated Found Auth-Type = EAP # Executing group from file ..\etc\raddb/radiusd.conf +- entering group authenticate {...} [eap] EAP Identity [eap] processing type md5 ++[eap] returns handled Finished request 0. Going to the next request Waking up in 4.9 seconds. # Executing section authorize from file ..\etc\raddb/radiusd.conf +- entering group authorize {...} [auth_log] ../var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d.log expands to ../var/log/radius/radacct/127.0.0.1/auth-detail-20111016.log ++[auth_log] returns ok [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop ++[mschap] returns noop [files] users: Matched entry testuser at line 29 ++[files] returns ok [eap] EAP packet type response id 229 length 22 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated Found Auth-Type = EAP # Executing group from file ..\etc\raddb/radiusd.conf +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/md5 [eap] processing type md5 [eap] Freeing handler ++[eap] returns ok WARNING: Empty post-auth section. Using default return values. Finished request 1. Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 229 with timestamp +14 Cleaning up request 1 ID 230 with timestamp +14 Ready to process requests. --------- EAP-MD5 test --------- http://deployingradius.com/scripts/eapol_test/ eapol_test.exe -c md5.conf -s testing123 ( it doesn't work!) Output: Reading configuration file 'md5.conf' Line: 1 - start of a new network block ssid - hexdump_ascii(len=7): 45 78 61 6d 70 6c 65 Example eap methods - hexdump(len=16): 00 00 00 00 15 00 00 00 00 00 00 00 00 00 00 00 eapol_flags=0 (0x0) key_mgmt: 0x1 identity - hexdump_ascii(len=8): 74 65 73 74 75 73 65 72 testuser password - hexdump_ascii(len=6): 74 65 73 74 70 77 testpw ca_cert - hexdump_ascii(len=40): 63 3a 2f 46 72 65 65 52 41 44 49 55 53 2f 65 74 c:/FreeRADIUS/et 63 2f 72 61 64 64 62 2f 63 65 72 74 73 2f 52 6f c/raddb/certs/Ro 6f 74 43 41 2e 70 65 6d otCA.pem phase2 - hexdump_ascii(len=8): 61 75 74 68 3d 4d 44 35 auth=MD5 anonymous_identity - hexdump_ascii(len=9): 61 6e 6f 6e 79 6d 6f 75 73 anonymous Priority group 0 id=0 ssid='Example' Authentication server 127.0.0.1:1812 EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portValid=0 EAPOL: External notification - portEnabled=1 EAPOL: SUPP_PAE entering state CONNECTING EAPOL: SUPP_BE entering state IDLE EAP: EAP entering state INITIALIZE EAP: EAP entering state IDLE Sending fake EAP-Request-Identity EAPOL: Received EAP-Packet frame EAPOL: SUPP_PAE entering state RESTART EAP: EAP entering state INITIALIZE EAP: EAP entering state IDLE EAPOL: SUPP_PAE entering state AUTHENTICATING EAPOL: SUPP_BE entering state REQUEST EAPOL: getSuppRsp EAP: EAP entering state RECEIVED EAP: Received EAP-Request id=0 method=1 vendor=0 vendorMethod=0 EAP: EAP entering state IDENTITY CTRL-EVENT-EAP-STARTED EAP authentication started EAP: EAP-Request Identity data - hexdump_ascii(len=0): EAP: using anonymous identity - hexdump_ascii(len=9): 61 6e 6f 6e 79 6d 6f 75 73 anonymous EAP: EAP entering state SEND_RESPONSE EAP: EAP entering state IDLE EAPOL: SUPP_BE entering state RESPONSE EAPOL: txSuppRsp WPA: eapol_test_eapol_send(type=0 len=14) TX EAP -> RADIUS - hexdump(len=14): 02 00 00 0e 01 61 6e 6f 6e 79 6d 6f 75 73 Encapsulating EAP message into a RADIUS packet Learned identity from EAP-Response-Identity - hexdump(len=9): 61 6e 6f 6e 79 6d 6f 75 73 Sending RADIUS message to authentication server RADIUS message: code=1 (Access-Request) identifier=0 length=126 Attribute 1 (User-Name) length=11 Value: 'anonymous' Attribute 4 (NAS-IP-Address) length=6 Value: 127.0.0.1 Attribute 31 (Calling-Station-Id) length=19 Value: '02-00-00-00-00-01' Attribute 12 (Framed-MTU) length=6 Value: 1400 Attribute 61 (NAS-Port-Type) length=6 Value: 19 Attribute 77 (Connect-Info) length=24 Value: 'CONNECT 11Mbps 802.11b' Attribute 79 (EAP-Message) length=16 Value: 02 00 00 0e 01 61 6e 6f 6e 79 6d 6f 75 73 Attribute 80 (Message-Authenticator) length=18 Value: 8a 2a d9 3f 9a 16 02 d3 9e be 52 a3 cc a2 a0 b6 Next RADIUS client retransmit in 3 seconds EAPOL: SUPP_BE entering state RECEIVE Received 80 bytes from RADIUS server Received RADIUS message RADIUS message: code=11 (Access-Challenge) identifier=0 length=80 Attribute 79 (EAP-Message) length=24 Value: 01 01 00 16 04 10 2d 5a 5e ca fd 46 31 37 33 67 ef 5f ec 14 64 c3 Attribute 80 (Message-Authenticator) length=18 Value: 37 83 06 12 9c 7b 2d 98 9a e8 6b 81 79 03 ce 63 Attribute 24 (State) length=18 Value: cb 7a ce 96 cb 7b ca 0b 07 a3 2c 75 4a 0c c4 c6 STA 02:00:00:00:00:01: Received RADIUS packet matched with a pending request, round trip time 0.00 sec RADIUS packet matching with station decapsulated EAP packet (code=1 id=1 len=22) from RADIUS server: EAP-Request-MD5 (4) EAPOL: Received EAP-Packet frame EAPOL: SUPP_BE entering state REQUEST EAPOL: getSuppRsp EAP: EAP entering state RECEIVED EAP: Received EAP-Request id=1 method=4 vendor=0 vendorMethod=0 EAP: EAP entering state GET_METHOD EAP: configuration does not allow: vendor 0 method 4 EAP: vendor 0 method 4 not allowed CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=4 -> NAK EAP: Building EAP-Nak (requested type 4 vendor=0 method=0 not allowed) EAP: allowed methods - hexdump(len=1): 15 EAP: EAP entering state SEND_RESPONSE EAP: EAP entering state IDLE EAPOL: SUPP_BE entering state RESPONSE EAPOL: txSuppRsp WPA: eapol_test_eapol_send(type=0 len=6) TX EAP -> RADIUS - hexdump(len=6): 02 01 00 06 03 15 Encapsulating EAP message into a RADIUS packet Copied RADIUS State Attribute Sending RADIUS message to authentication server RADIUS message: code=1 (Access-Request) identifier=1 length=136 Attribute 1 (User-Name) length=11 Value: 'anonymous' Attribute 4 (NAS-IP-Address) length=6 Value: 127.0.0.1 Attribute 31 (Calling-Station-Id) length=19 Value: '02-00-00-00-00-01' Attribute 12 (Framed-MTU) length=6 Value: 1400 Attribute 61 (NAS-Port-Type) length=6 Value: 19 Attribute 77 (Connect-Info) length=24 Value: 'CONNECT 11Mbps 802.11b' Attribute 79 (EAP-Message) length=8 Value: 02 01 00 06 03 15 Attribute 24 (State) length=18 Value: cb 7a ce 96 cb 7b ca 0b 07 a3 2c 75 4a 0c c4 c6 Attribute 80 (Message-Authenticator) length=18 Value: 6b 08 01 29 89 bc 34 13 49 53 aa 7a 8d 43 4d f4 Next RADIUS client retransmit in 3 seconds EAPOL: SUPP_BE entering state RECEIVE EAPOL: startWhen --> 0 STA 02:00:00:00:00:01: Resending RADIUS message (id=1) Next RADIUS client retransmit in 6 seconds STA 02:00:00:00:00:01: Resending RADIUS message (id=1) Next RADIUS client retransmit in 12 seconds STA 02:00:00:00:00:01: Resending RADIUS message (id=1) Next RADIUS client retransmit in 24 seconds EAPOL test timed out EAPOL: EAP key not available MPPE keys OK: 0 mismatch: 1 FAILURE The server shows: rad_recv: Access-Request packet .... then Sending Access-Challenge of id 0 to 127.0.0.1 then .... nothing at all!

1 0

freeradius config problems
by Kambey Kisambu 07 Oct '11

07 Oct '11

Hi guys, I was installing freeradius and after complete successfull installation and some configuration , while testing by running freeradius -X i was getting some errors as below: /etc/freeradius/sql.conf[22]: Instantiation failed for module "sql" /etc/freeradius/sites-enabled/default[159]: Failed to find module "sql". /etc/freeradius/sites-enabled/default[62]: Errors parsing authorize section. I have tried fix without any luck. Can some one help on this? -- Thanks Kambey

4 6

[libfreeradius-client] Send request to non-standard ports
by Kevin Lemonnier 05 Oct '11

05 Oct '11

Hi, I'm trying to send radius auth request to the 11812 port. So i've placed 11812 as second parameter of the rc_auth function. On my server's log, I can see that the NAS-PORT is set, in the request, to 11812. But the request itself is sent to the standard 1812 port .. How can I change that ? I need to send some request to 1812 and some others to 11812 (two radius servers are running). I've looked at the example code but they are just using the port parameter of rc_auth, so I can't find a way to make it work. (I'll need to do the same with accounting too) Thanks

4 12

Re: rlm_ldap patch for access_attr_deny_value
by Arran Cudbard-Bell 03 Oct '11

03 Oct '11

Your patch is all mangled. Please resubmit it via GitHub. http://wiki.freeradius.org/GitHub -Arran Arran Cudbard-Bell a.cudbardb(a)freeradius.org Betelwiki, Betelwiki, Betelwiki.... http://wiki.freeradius.org/ !

1 0

RADIUS Disconnect scenarios
by vikraman.p36＠wipro.com 29 Sep '11

29 Sep '11

Hi , Please provide me the solution for the following , What are the scenarios/conditions cause the RADIUS server to send RADIUS Disconnect Request to RADIUS client (NAS) ? Thanks, Vikram Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

3 2

rlm_sim_files pairadd only ? Is there any need to pairdelete ?
by Ming-Ching Tiew 24 Sep '11

24 Sep '11

I am fairly new to writing modules for freeradius. While reading the sources for rlm_sim_files, in the authorize section the code adds the needed attributes by using pairadd(...). I am just wondering if the authorize section keeps adding things into the memory by using pairadd(), at some point in time ( say after authentication ) these values will have to be removed from the memory, otherwise after many times of invocations, that will constitute a memory leak. How is the housekeeping been carried out ?

2 1

radtest should always send Message-Authenticator
by John Dennis 22 Sep '11

22 Sep '11

Here is a small 1-line patch for radtest. This was originally filed as a bug by the NSA (https://bugzilla.redhat.com/show_bug.cgi?id=630072) It would be nice if this could be applied to 2.1.12 before it's released. The patch is attached in git format and can be applied with either "git am" or "git apply <attachement>" if you save the attachment. I wrote up the justification for the change: ------------------------------------------------------------------ Originally Message-Authenticator was introduced to provide message integrity for EAP messages and originally the Message-Authenticator attribute was only required for EAP messages. But then RFC 5080 came along and suggested Message-Authenticator always be sent as best practice. Any Access-Request packet that performs authorization checks, including Call Check, SHOULD contain a Message-Authenticator attribute. RFC 5080 then goes on to say: ... server implementations may be configured to require the presence of a Message-Authenticator attribute in Access-Request packets. Requests not containing a Message-Authenticator attribute MAY then be silently discarded. The raddb/clients.conf has this configuration option to satisfy the above suggestion in RFC 5080: require_message_authenticator = no|yes If require_message_authenticator == yes then non-EAP auth-requests generated by radtest will fail because currently radtest only supplies the Message-Authenticator if EAP is being performed. With modern Radius servers (e.g. FreeRADIUS) there is no harm in providing the Message-Authenticator attribute for non-EAP packets, in fact it's actually recommended in RFC 5080. Therefore radtest should ALWAYS send the Message-Authenticator attribute. If it's EAP or if the server is configured with require_message_authenticator it must be present. If those conditions do not hold it's benign. However if require_message_authenticator is configured radtest will fail for non-EAP. -- John Dennis <jdennis(a)redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/

5 6