July 2013 - Freeradius-Users - lists.freeradius.org

maintaining reSIProcate compatibility with FreeRADIUS
by Daniel Pocock 11 Jul '13

11 Jul '13

Hi, A few years ago, I adapted the RADIUS client code from SER to work in reSIProcate and specifically the SIP proxy, repro I'm now reviewing the code to work out how to extend it for reTurn, the TURN server and to see if any other changes are necessary. Things have changed slightly since reSIProcate originally adopted RADIUS support. The original implementation is based on http://tools.ietf.org/html/draft-sterman-aaa-sip-04 and that works with FreeRADIUS (or it did work at the time) although the draft is now expired. Since that time, RFC 5090 has emerged I notice various differences in the RFC, e.g. the RADIUS server must provide nonces: http://tools.ietf.org/html/rfc5090#section-2.1.5 and may also provide other values. reSIProcate currently generates it's own nonces and passes all the auth parameters to FreeRADIUS for verification. This brings me to some questions: Is anybody already working on migrating FreeRADIUS to the RFC variation of DIGEST support? If so, will older clients stop working? How to handle STUN/TURN? I notice STUN only uses "nonce" and not "qop" or any of the other values, yet RFC 5090 suggests that a RADIUS server can demand that the challenge uses those attributes. I'm also not sure just what value for "method" would be used with STUN. However, it would seem desirable to support STUN/TURN from a single RADIUS server. STUN auth (inherited by TURN) is described here: http://tools.ietf.org/html/rfc5389#section-10.2 This all leaves me feeling that STUN/TURN may need it's now module in FreeRADIUS. Regards, Daniel

1 0

PEAP using different CA?
by Fernando Hammerli 11 Jul '13

11 Jul '13

Hi, Currently we have 1000´s of users self-signed certificates (EAP-TLS), and we´re planning to move our main authentication method to PEAP, but keeping the certificates in use while valid. To avoid the need of installing our CA certificate on every Windows machine, we´ll buy the server certificate from a public CA. Can Freeradius allow me to have both methods at the same time, ie, the PEAP with the public CA and certificate users with our 'self-signed' CA? Thanks in advance, Fernando Hämmerli Pontifícia Universidade Católica do Rio de Janeiro

6 9

Changing proxy server for a specific user
by Angel L. Mateo 11 Jul '13

11 Jul '13

Hello, I have defined a DEFAULT realm proxying requests to a remote radius server (for eduroam). Now I want to create another virtual server using this DEFAULT realm, but proxying requests to another radius server. Is there any way to do this? Maybe modifying some attribute in the request with an entry in the user's file? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 1

Reject a specific realm from a client
by David Aldwinckle 11 Jul '13

11 Jul '13

Hello, I have two clients that proxy access requests to me. The realm varies, but the format is always userid(a)realm.whatever Is there a way that I can deny a specific realm when an access request is received from a specific client? I tried adding something to policy.conf but I couldn't get the syntax right: #Prevent secretrealm from logging in off-campus remote_secret_reject if ("%{Realm}" == "secretrealm.ca") && ((Client-Shortname == "proxy-client1") || (Client-Shortname == "proxy-client2"))) { reject } Is there a different way that I should be doing this? Thanks, Dave Dave Aldwinckle Network Support Specialist Information Systems and Technology Phone: (519)-888-4567 ext. 31145 E-Mail: daldwinc(a)uwaterloo.ca<mailto:daldwinc@uwaterloo.ca>

1 0

Indexing multi-valued attrbutes (was RE: 3.0)
by Brian Julin 11 Jul '13

11 Jul '13

Arran Cudbard-Bell wrote: > > Soon. We've gone into official feature freeze. Still finding bugs though, it'd be helpful if people could test. Just to make sure it was understood during the "foreach" fixup patch I sent on github, I mentioned that indexed attribute accesses were broken. None of var[#] var[2] or var[*] work in xlats, unless that's been fixed recently. -- Brian

3 2

freeradius seeing anonymous identity as username
by sebastian buettrich 11 Jul '13

11 Jul '13

hello all, not really a problem, just a question out of interest: i m reconfiguring a freeradius server for eduroam and extended use of rlm_perl for all kinds of fun stuff, and when testing, i notice that all requests containing an anonymous identity @mydomain.org (regardless of where they come from, a real AP or local eapol_test) appear to freeradius as User-Name, i.e. freeradius does not make a difference (?) between anon identity and username is this expected behaviour, the way anonymous identities are implemented, or a sign of some misconfiguration, e.g. someone trying to take care of something that really should just be passed on? it seems to happen before any site configurations are being processed - see debug output and log below. it doesnt do any damage .. just wondering. thanks everybody on the list for sharing, cheers, sebastian ====================================================================== output of radiusd -Xx -------------------------------- Thu Jul 11 10:23:40 2013 : Info: Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 39508, id=0, length=125 User-Name = "@mydomain.org" NAS-IP-Address = 127.0.0.1 Calling-Station-Id = "CA-FF-EE-00-00" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 ... Thu Jul 11 10:23:43 2013 : Info: # Executing section authorize from file /etc/raddb/sites-enabled/default Thu Jul 11 10:23:43 2013 : Info: +- entering group authorize {...} Thu Jul 11 10:23:43 2013 : Info: ++[preprocess] returns ok log file: -------------------------------- Thu Jul 11 10:28:37 2013 : Auth: Login OK: [username/<via Auth-Type = EAP>] (from client local port 0 via TLS tunnel) Thu Jul 11 10:28:37 2013 : Auth: Login OK: [@mydomain.org/<via Auth-Type = EAP>] (from client local port 0 cli CA-FF-EE-00-00)

2 1

Dictionary type problem
by Muhammad Nadeem 11 Jul '13

11 Jul '13

hi everybody I am adding some new attributes to dictionary.motorola. but when i run freeradius , it gives the follwoing error. including dictionary file /usr/local/etc/raddb/dictionary Errors reading dictionary: dict_init: /usr/local/share/freeradius/dictionary.motorola[78]: invalid type "hexdecimal" it clearly indicates that it doesnot support hexadecimal type. Could anyone please tell me , whts the alternative of this. Thanks in advance -- Best Regards Muhammad Nadeem Muhammad Ali Jinnah University

3 3

Update sections
by Arran Cudbard-Bell 10 Jul '13

10 Jul '13

Update sections in 3.0 are considerably more powerful than 2.x.x In addition to being able to override lists on an attribute by attribute basis, e.g: update { request:foo = 'bar' } You can also perform full list copies: update { request: += &reply: } Filtered list copies (all instance of attribute in a list) update { request: += &reply:foo } Reference attributes: update { request:foo += &reply:foo } and perform both types of program execution: update { request:foo := `<my program>` # foo is assigned the output of my program } update { request: := `<my program>` # any VALUE_PAIRs returned by my program are added to the request list } Update sections may now also return fail. (0) update { (0) Executing: "/tmp/foo %{User-Name}" (0) expand: "%{User-Name}" -> 'foo' (0) Program returned code (2): Failed to execute "/tmp/foo": No such file or directory (0) ERROR: Failed to execute "/tmp/foo": No such file or directory (0) } # update = fail In which case subsequent statements are not executed. As with modules failure this can be checked with if (fail). Update sections are no longer atomic as a whole. But individual statements are. That is if a statement fails, all VALUE_PAIRs created up to the point of the failure are discarded. We may be able to restore atomicity of update sections once sets and lists are implemented in 3.1. If you absolutely require it in 3.0 you can wrap each statement in it's own update section and check for failure. -Arran Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> FreeRADIUS Development Team

2 3

Re: PEAP using different CA?
by Alan Buxey 10 Jul '13

10 Jul '13

User a deployment tool as then things like CN checks are done alan

1 0

freeradius using linux user passwd
by Julian Macassey 10 Jul '13

10 Jul '13

I have a Netgear WiFi router set up for WPA2 Enterprise. It is pointed at a freeradius server. I am trying to use the username and password of that server to authenticate. It fails consistenty with: [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Failed to authenticate the user. ---------- FreeRADIUS Version 2.1.10, for host x86_64-pc-linux-gnu, built on Sep 24 2012 at 17:58:57 Copyright (C) 1999-2009 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License v2. Starting - reading configuration files ... including configuration file /etc/freeradius/radiusd.conf including configuration file /etc/freeradius/proxy.conf including configuration file /etc/freeradius/clients.conf including files in directory /etc/freeradius/modules/ including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/wimax including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/detail.example.com including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/dynamic_clients including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/policy including configuration file /etc/freeradius/modules/perl including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/modules/opendirectory including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/modules/otp including configuration file /etc/freeradius/modules/sql_log including configuration file /etc/freeradius/modules/smsotp including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login including configuration file /etc/freeradius/modules/ntlm_auth including configuration file /etc/freeradius/modules/cui including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/eap.conf including configuration file /etc/freeradius/policy.conf including files in directory /etc/freeradius/sites-enabled/ including configuration file /etc/freeradius/sites-enabled/default including configuration file /etc/freeradius/sites-enabled/inner-tunnel main { user = "freerad" group = "freerad" allow_core_dumps = no } including dictionary file /etc/freeradius/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/var/run/plumgrid-radius1/plumgrid-radius1.pid" checkrad = "/usr/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = no auth_badpass = no auth_goodpass = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "d1sc0verplum" response_window = 20 max_outstanding = 65536 require_message_authenticator = yes zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "d1sc0verplum" nastype = "other" } client 10.1.1.211 { ipaddr = 10.1.1.211 require_message_authenticator = no secret = "d1sc0verplum" shortname = "wifi" nastype = "other" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating module "exec" from file /etc/freeradius/modules/exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating module "expr" from file /etc/freeradius/modules/expr Module: Linked to module rlm_expiration Module: Instantiating module "expiration" from file /etc/freeradius/modules/expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating module "logintime" from file /etc/freeradius/modules/logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { # from file /etc/freeradius/sites-enabled/inner-tunnel modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating module "pap" from file /etc/freeradius/modules/pap pap { encryption_scheme = "auto" auto_header = yes } Module: Linked to module rlm_chap Module: Instantiating module "chap" from file /etc/freeradius/modules/chap Module: Linked to module rlm_mschap Module: Instantiating module "mschap" from file /etc/freeradius/modules/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating module "unix" from file /etc/freeradius/modules/unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating module "eap" from file /etc/freeradius/eap.conf eap { default_eap_type = "md5" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no max_sessions = 4096 } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 CA_path = "/etc/freeradius/certs" pem_file_type = yes private_key_file = "/etc/freeradius/certs/server.key" certificate_file = "/etc/freeradius/certs/server.pem" CA_file = "/etc/freeradius/certs/ca.pem" private_key_password = "whatever" dh_file = "/etc/freeradius/certs/dh" random_file = "/dev/urandom" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/etc/freeradius/certs/bootstrap" cache { enable = no lifetime = 24 max_entries = 255 } verify { } } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "md5" copy_request_to_tunnel = no use_tunneled_reply = no virtual_server = "inner-tunnel" include_length = yes } Module: Linked to sub-module rlm_eap_peap Module: Instantiating eap-peap peap { default_eap_type = "mschapv2" copy_request_to_tunnel = no use_tunneled_reply = no proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_realm Module: Instantiating module "suffix" from file /etc/freeradius/modules/realm realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating module "files" from file /etc/freeradius/modules/files files { usersfile = "/etc/freeradius/users" acctusersfile = "/etc/freeradius/acct_users" preproxy_usersfile = "/etc/freeradius/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating module "radutmp" from file /etc/freeradius/modules/radutmp radutmp { filename = "/var/log/freeradius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Linked to module rlm_attr_filter Module: Instantiating module "attr_filter.access_reject" from file /etc/freeradius/modules/attr_filter attr_filter attr_filter.access_reject { attrsfile = "/etc/freeradius/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { # from file /etc/freeradius/radiusd.conf modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_digest Module: Instantiating module "digest" from file /etc/freeradius/modules/digest Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating module "preprocess" from file /etc/freeradius/modules/preprocess preprocess { huntgroups = "/etc/freeradius/huntgroups" hints = "/etc/freeradius/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating module "acct_unique" from file /etc/freeradius/modules/acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating module "detail" from file /etc/freeradius/modules/detail detail { detailfile = "/var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Instantiating module "attr_filter.accounting_response" from file /etc/freeradius/modules/attr_filter attr_filter attr_filter.accounting_response { attrsfile = "/etc/freeradius/attrs.accounting_response" key = "%{User-Name}" } Module: Checking session {...} for more modules to load Module: Checking post-auth {...} for more modules to load } # modules } # server radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 10.1.1.211 port 35032, id=73, length=162 User-Name = "evergreen" NAS-IP-Address = 192.168.1.1 NAS-Port = 0 Called-Station-Id = "28-C6-8E-A4-2B-6A:plum-radius" Calling-Station-Id = "00-1F-5B-C1-AB-24" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 0Mbps 802.11b" EAP-Message = 0x02b1000e0165766572677265656e Message-Authenticator = 0x6f0e884ab22ca3b623c88cb2a8bab823 # Executing section authorize from file /etc/freeradius/sites-enabled/default +- entering group authorize {...} ++[preprocess] returns ok ++[digest] returns noop [suffix] No '@' in User-Name = "evergreen", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop ++[unix] returns notfound ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Failed to authenticate the user. Using Post-Auth-Type Reject # Executing group from file /etc/freeradius/sites-enabled/default +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> evergreen attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 0 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 0 Sending Access-Reject of id 73 to 10.1.1.211 port 35032 Waking up in 4.9 seconds. --

3 10