October 2009 - Freeradius-Devel - lists.freeradius.org

Missing TLS Change Cipher Spec and TLS Finished in EAP-TLS exchanges
by arno＠natisbad.org 09 Jul '11

09 Jul '11

Hi, I upgraded an internal freeradius server (Linux, Debian unstable, libssl 0.9.8) used for EAP-TLS (802.11 WPA2 access) from 2.0.5 to 2.1.3. With 2.1.3, client authentication fails in the following way (wpasupplicant on Debian unstable, working with 2.0.5): - the TLS exchange is completed from freeradius point of view. It even sends the Access-Accept message to the NAS. - from the clients point of view, the TLS exchange is not over, it expects some more data from the server which are never sent. I took two pcap traces (sent to you privately, Alan), one with 2.0.5, one with 2.1.3. It looks like the TLS Change Cipher and TLS Tinished elements of the TLS exchange are not in the EAP encapsulated TLS packets sent by the server. Compare packet #23 of 2.1.3 trace with packet #27 of 2.0.5 trace. If you use wireshark, you will notice that the SSL layer is dissected; this is because #27 has a small brother: #29. It is not sent by 2.1.3. Alan, if you have an idea or a patch, I can test it on monday. Cheers, a+

5 15

eap2 in freeradius
by Chanthearith HUON 04 Apr '11

04 Apr '11

Hi everyone, I am testing eap2 in freeradius. I run "radiusd -X", I got following error message " radiusd: symbol lookup error: /usr/lib/rlm_eap2-2.1.0.so: undefined symbol: eap_server_register_methods " Anyone, have any idea what might be wrong with the configuration? Thank in advance, Thierry

5 10

make_passwd(), rlm_perl and double quotes in the password
by Niko Tyni 28 Jan '10

28 Jan '10

Hi, we're seeing failed logins when proxying authentication requests through to another RADIUS server if the password contains a double quote ("). I've debugged the issue a bit, and what happens is that when the password does a roundtrip through the rlm_perl module, the value pair structure ends up with extra bytes at the end so that strlen(vp->data.strvalue) > vp->length. These extra bytes are the result of escaping the double quote before entering the Perl code and then unescaping it afterwards. For instance, the password abcdef" is passed as abcdef\" to the Perl code, and afterwards it becomes abcdef"" with length 7 (so the extra byte is not supposed to hurt AIUI.) Unfortunately make_passwd() rounds 'inlen' up to a multiple of 16 before copying the input string, so the extra bytes end up in the message authenticator of the proxied request. It seems to me that the escaping and unescaping done in rlm_perl via perl_store_vps() -> vp_prints_value() -> librad_safeprint() and get_hv_content() -> pairadd_sv() -> pairmake() -> pairparsevalue() is a bit unnecessary, and that the unescaping could zero out the extra bytes, but the main bug is in make_passwd() IMO. I have reproduced this with a Debian 2.0.4 freeradius package, a Fedora 2.1.3 package, and a current git.freeradius.org checkout (commit ef2a7db5e). I'm attaching a proposed patch to make_passwd(). Please let me know if you need more information, I can easily produce stack traces and the like. Thanks for your work on FreeRADIUS, -- Niko Tyni ntyni(a)cc.helsinki.fi

3 5

Re: vmps request: long attribute VQP-Ethernet-Frame
by Hermann Lauer 05 Jan '10

05 Jan '10

Alan DeKok wrote: > > 0x0c05 is VQP-Ethernet-Frame, which can of course be longer than 253 bytes, > > so there is a design issue here. One idea would be to cut the attribute to > > 253 bytes in vqp_recv(). Could this be done there without memory issues ? > > Yes, if you're not interested in the rest of the data. appended is a patch which implemeted the cutting. Seems to work. Please tell me if anybody sees any pitfall in it. Otherwise it should be cleaned up, which I probably will do in a week or so. Thanks, Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224 Email: Hermann.Lauer(a)iwr.uni-heidelberg.de

2 5

PATCH: allow detail listeners to write to other files
by John Morrissey 06 Dec '09

06 Dec '09

I noticed[1] that detail listeners refuse to write detail entries to files, even if the destination filename is different from the source filename. The attached patch fixes that. It also centralizes the listen_detail_t definition, removing the 'stub' definition in src/main/event.c. john [1] https://lists.freeradius.org/pipermail/freeradius-users/2009-October/msg001… -- John Morrissey _o /\ ---- __o jwm(a)horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__

2 6

Setting Client-IP-Address in rlm_preprocess
by John Morrissey 04 Dec '09

04 Dec '09

Client-IP-Address is dynamically set by xlat_packet(). AFAICT, there's no way to trigger this in rlm_perl, so Client-IP-Address is never available in rlm_perl handlers. This leads to some interesting unlang to set Client-IP-Address in the request so rlm_perl can access it: authorize { update request { Client-IP-Address := "%{Client-IP-Address}" } } rlm_preprocess sets NAS-IP-Address if it's not set. Alan, would you accept a patch to add similar behavior for Client-IP-Address? john -- John Morrissey _o /\ ---- __o jwm(a)horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__

3 7

FreeRadius + EAP-AKA support
by Kumar, Sunil 26 Nov '09

26 Nov '09

Hi, We are trying to use FreeRadius1.1.4 as authentication server for EAP-AKA implementation with our product toolkit. As per the RFC 4187 AT_RES The value field of this attribute begins with the 2-byte RES Length, which identifies the exact length of the RES in bits. The RES length is followed by the AKA RES parameter. According to [TS33.105], the length of the AKA RES can vary between 32 and 128 bits. Because the length of the AT_RES attribute must be a multiple of 4 bytes, the sender pads the RES with zero bits where necessary. In the freeradius1.1.4 implementation, for EAP-AKA the value of RES length is always considered as constant EAPSIM_RES_SIZE (16). It doesn't take care of the values other than 16 bytes. We in our toolkit needs to support all the variable length of RES values from 32 bits (4 bytes) to 128 bits (16 bytes). So I have modified the FreeRadius implementation for the same support. The intention of writing such mail is to get the information that if somebody has already noticed and fixed this issue in the latest releases, so please share that information as well. In case it's not been fixed as yet, then may be I could contribute my patch for freeradius 1.1.4 version to support all variable length RES value varying from 32 bits to 128 bits. Thanks. Warm regards. Sunil Kumar The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.

4 5

EAP proxing with client-balance
by Alexander Clouter 18 Nov '09

18 Nov '09

Hi, Being part of the 'eduroam' clan we have a lot of EAP traffic proxying about the place, even more so being part of the 'University Triangle' in London so those peskey students and staff mooch where ever they can. My setup is generally: ---- home_server_pool eduroam { #type = fail-over <-- works #type = client-balance <-- grumbles #type = client-port-balance <-- grumbles type = keyed-balance <-- grumbles home_server = jrs.0 home_server = jrs.1 home_server = jrs.2 } ---- The proxy topology in eduroam (incase you do not know) is: [us x 2] ---------- [ .ja.net proxies x 3 ] ---------- [them x 2] <ramble> I used 'keyed-balance' as 'client-balance'/'client-port-balance' load balance terribly when your NAS's use the same source port and most of our traffic comes from the same IP (the single infernal WLC 4400 we have). This however is not important, as I only started to use 'keyed-balance' about an hour ago. I noticed after the summer FreeRADIUS overhaul I am finishing off that a number of proxied requests to particular realms failed for no reason. Speaking to my counterparts at the other universities they could see nothing wrong in their *FreeRADIUS* installations. Because I have a general knowledge of whats going on in the nearby universities I know there are some filthy MS IAS installations about and pretty quickly noticed queries to these places were working fine whilst request to my FreeRADIUS buddies did not. </ramble> Looking closer at the detail logs I saw that mid-EAP conversation the packets started to get proxied to different national proxies which resulted (expectedly) with a Access-Reject; also explaining why my counterparts never saw an inner authentication. Looks like MS IAS does not really care where the proxied packets come from, it only key's on Proxy-State (I'm guessing here); FreeRADIUS being a lot more picky...which is just what I like :) With this in mind I moved to 'fail-over' and everything started working. Alas I cannot leave it on 'fail-over' otherwise Alan Buxey gets grumbly. <ramble> I figured out how to enable super verbosity to get at those RDEBUG3's in realms.c:home_server_ldb() and saw (when using anything other than 'fail-over'): ---- [first packet] PROXY jrs 2.0 jrs 0.0 PROXY jrs 2.0 jrs 1.0 [a latter EAP packet had something like] PROXY jrs 2.0 jrs 0.0 PROXY jrs 1.0 jrs 0.0 ---- I think this was a red herring for me, but it got me to look more closer at the realms.c code. </ramble> The conclusion, we should not be paying any attention to 'currently_outstanding' or 'fr_rand()' when there is EAP traffic; I decided to add the clause !HOME_POOL_LOAD_BALANCE; things now work. What do you think of the following patch, I think there is sound reasoning behind it, however of course I am just a network monkey? Cheers -- Alexander Clouter .sigmonster says: There is no grief which time does not lessen and soften. diff --git a/src/main/realms.c b/src/main/realms.c index a0cb796..71640d0 100644 --- a/src/main/realms.c +++ b/src/main/realms.c @@ -1938,8 +1938,12 @@ home_server *home_server_ldb(const char *realmname, /* * We've found the first "live" one. Use that. + * The !HOME_POOL_LOAD_BALANCE clause is for the EAP + * case when we want to do CLIENT/KEY based balancing + * and avoid inconsistent proxying */ - if (pool->type == HOME_POOL_FAIL_OVER) { + if (pool->type == HOME_POOL_FAIL_OVER + || pool->type != HOME_POOL_LOAD_BALANCE) { found = home; break; }

4 14

GIT Log for 2009-10-29 00:33 GMT
by aland＠deployingradius.com 29 Oct '09

29 Oct '09

commit 9dbc8974fdd2300a70293eda9c62bce20a3c9165 Author: Alan T. DeKok <aland(a)freeradius.org> Date: Wed Oct 28 09:44:38 2009 -0400 errormsg may be NULL .../drivers/rlm_sql_postgresql/sql_postgresql.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-)

1 0

raddebug(8) man page typo
by John Morrissey 26 Oct '09

26 Oct '09

Small typo in raddebug(8) man page: diff --git a/man/man8/raddebug.8 b/man/man8/raddebug.8 index f145a00..d9c2d7d 100644 --- a/man/man8/raddebug.8 +++ b/man/man8/raddebug.8 @@ -72,7 +72,7 @@ option is equivalent to using: The radius configuration directory, usually /etc/raddb. See the \fIradmin\fP manual page for more description of this option. .IP \-I\ \fIipv6-address\fP -Show debug output for the client having the given IPv4 address. This +Show debug output for the client having the given IPv6 address. This option is equivalent to using: .br .in +0.3i -- John Morrissey _o /\ ---- __o jwm(a)horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__

1 0