- Freeradius-Users - lists.freeradius.org

Request Authenticator value made available to a Perl module
by Brandon Miller 21 Nov '23

21 Nov '23

Hi Everyone, I am working on a Perl module that requires access to the Request Authenticator value for each Access-Request. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Code | Identifier | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Request Authenticator <----------- I need this value passed to my Perl module | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Attributes ... +-+-+-+-+-+-+-+-+-+-+-+-+- I combed through the docs and found the Request-Authenticator Runtime variable (https://wiki.freeradius.org/config/run_time_variables) I tried to dynamically assign this variable (%V) to a Radius-Request variable in my site definition file, but the server won't start with error: /etc/raddb/sites-enabled/myPerlSite[17]: Failed parsing expanded string: /etc/raddb/sites-enabled/myPerlSite[17]: %V /etc/raddb/sites-enabled/myPerlSite[17]: ^ Invalid variable expansion It seems this variable has been deprecated in v3. Is there any way to get at this variable in another way? I am running v3.0.13. Thanks in advance, Brandon

2 13

Issues with vendor 3375 (F5) and FreeRADIUS
by Coy Hile (BLOOMBERG/ 919 3RD A) 21 Nov '23

21 Nov '23

Good morning, We're running into issues with F5 devices and authorization against FreeRADIUS. Our network team have included the following dictionary (which is loaded via a $INCLUDE directive in /etc/raddb/dictionary): VENDOR f5 3375 BEGIN-VENDOR f5 ATTRIBUTE F5-LTM-User-Role 1 integer ATTRIBUTE F5-LTM-User-Role-Universal 2 integer # enable/disable ATTRIBUTE F5-LTM-User-Partition 3 string ATTRIBUTE F5-LTM-User-Console 4 integer # enable/disable ATTRIBUTE F5-LTM-User-Shell 5 string # supported values are disable and tmsh ATTRIBUTE F5-LTM-User-Context-1 10 integer ATTRIBUTE F5-LTM-User-Context-2 11 integer ATTRIBUTE F5-LTM-User-Info-1 12 string ATTRIBUTE F5-LTM-User-Info-2 13 string ATTRIBUTE F5-LTM-Audit-Msg 14 string # F5OS vendor-specific-attributes ATTRIBUTE F5-F5OS-UID 21 integer ATTRIBUTE F5-F5OS-GID 22 integer ATTRIBUTE F5-F5OS-HOMEDIR 23 string ATTRIBUTE F5-F5OS-SHELL 24 string ATTRIBUTE F5-F5OS-USERINFO 25 string VALUE F5-LTM-User-Role Administrator 0 VALUE F5-LTM-User-Role Resource-Admin 20 VALUE F5-LTM-User-Role User-Manager 40 VALUE F5-LTM-User-Role Auditor 80 VALUE F5-LTM-User-Role Manager 100 VALUE F5-LTM-User-Role App-Editor 300 VALUE F5-LTM-User-Role Advanced-Operator 350 VALUE F5-LTM-User-Role Operator 400 VALUE F5-LTM-User-Role Firewall-Manager 450 VALUE F5-LTM-User-Role Fraud-Protection-Manager 480 VALUE F5-LTM-User-Role Certificate-Manager 500 VALUE F5-LTM-User-Role IRule-Manager 510 VALUE F5-LTM-User-Role Guest 700 VALUE F5-LTM-User-Role Web-Application-Security-Administrator 800 VALUE F5-LTM-User-Role Web-Application-Security-Editor 810 VALUE F5-LTM-User-Role Web-Application-Security-Operation-Administrator 820 VALUE F5-LTM-User-Role Acceleration-Policy-Editor 850 VALUE F5-LTM-User-Role No-Access 900 VALUE F5-LTM-User-Role-Universal Disabled 0 VALUE F5-LTM-User-Role-Universal Enabled 1 VALUE F5-LTM-User-Console Disabled 0 VALUE F5-LTM-User-Console Enabled 1 END-VENDOR f5 Further, Shane has configured the server to return the following VSAs for a superuser: Tue Nov 14 13:51:39 2023 Packet-Type = Access-Accept F5-LTM-User-Role = Administrator F5-F5OS-GID = 9000 F5-F5OS-UID = 1001 Timestamp = 1699987899 However, tcpdump shows the following: radcas-rr-641 /root # tcpdump -i bond0 -n -vvv host 10.91.250.120 tcpdump: listening on bond0, link-type EN10MB (Ethernet), capture size 262144 bytes 13:51:39.232624 IP (tos 0x0, ttl 55, id 19394, offset 0, flags [DF], proto UDP (17), length 115) 10.91.250.120.54996 > 10.124.134.47.radius-new: [udp sum ok] RADIUS, length: 87 Access-Request (1), id: 0x1f, Authenticator: 314fd8be32430e77a584870ba696ba64 User-Name Attribute (1), length: 10, Value: sedelman 0x0000: 7365 6465 6c6d 616e User-Password Attribute (2), length: 18, Value: 0x0000: 612c f40e 6250 6c36 fd6e ca89 0853 028f NAS-IP-Address Attribute (4), length: 6, Value: 100.65.6.2 0x0000: 6441 0602 NAS-Identifier Attribute (32), length: 15, Value: password-auth 0x0000: 7061 7373 776f 7264 2d61 7574 68 NAS-Port Attribute (5), length: 6, Value: 7692 0x0000: 0000 1e0c NAS-Port-Type Attribute (61), length: 6, Value: Virtual 0x0000: 0000 0005 Service-Type Attribute (6), length: 6, Value: Authenticate Only 0x0000: 0000 0008 13:51:39.278923 IP (tos 0x0, ttl 64, id 21787, offset 0, flags [none], proto UDP (17), length 84) 10.124.134.47.radius-new > 10.91.250.120.54996: [bad udp cksum 0x95d0 -> 0x3ad8!] RADIUS, length: 56 Access-Accept (2), id: 0x1f, Authenticator: 61df1ce227ff006987a4d9f0506a2cd9 Vendor-Specific Attribute (26), length: 12, Value: Vendor: Unknown (3375) Vendor Attribute: 1, Length: 4, Value: .... 0x0000: 0000 0d2f 0106 0000 0000 Vendor-Specific Attribute (26), length: 12, Value: Vendor: Unknown (3375) Vendor Attribute: 22, Length: 4, Value: ..#( 0x0000: 0000 0d2f 1606 0000 2328 Vendor-Specific Attribute (26), length: 12, Value: Vendor: Unknown (3375) Vendor Attribute: 21, Length: 4, Value: .... 0x0000: 0000 0d2f 1506 0000 03e9 Why is the vendor showing up as "unknown (3375)" when 3375 is the vendor ID for F5? The attributes that FreeRADIUS says it's sending back actually match the vendor attributes, but they're all jumbled. -c

3 2

authorize with other variable
by Florian Traxler (mieX GmbH) 20 Nov '23

20 Nov '23

Hello! I would like to authenticate with Agent Remote ID instead of using MAC as the user name. Can this be solved with "Based on PIN Code" when creating a new user in FreeRadius. In which file can the variable be adjusted to check the agent remote ID instead of the user name and send access-accept. (0) Received Access-Request Id 42 from xxx.xxx.xxx.xxx:57848 to xxx.xxx.xxx.xxx:1812 length 202 (0) NAS-Port-Type = Ethernet (0) NAS-Port = 2207262241 (0) Calling-Station-Id = "cisco-8c94.8s77.dd97-Et0.34" (0) Called-Station-Id = "dhcp1" (0) User-Name = "8C:94:1F:34:EE:89" (0) User-Password = "" (0) Agent-Remote-Id = 0x393734302d31323434313932357c31344d7c35303530343938347c7c (0) Agent-Circuit-Id = 0x4c493732383730322d5045494c5354454930312065746820312f312f31372f31313a3334 (0) NAS-Identifier = "xxx" (0) NAS-IP-Address = xxx.xxx.xxx.xxx (0) # Executing section authorize from file /etc/freeradius/3.0/sites-enabled/default (0) authorize { Thank you for your help

1 0

TOTP module
by João Miguel Regateiro 16 Nov '23

16 Nov '23

Hello, I was testing my freeRadius server and I found out that a user can authenticate with the same TOTP multiple times within the 30 seconds period. From reading the RFC 6238 I understand that this must not be possible as the One Time Password is for one time use only. Here is my code: authorize { ldap if ((ok || updated)) { if (User-Password !~ /^(.*)([0-9]{6})$/) { reject } update request { User-Password := "%{1}" TOTP-Password := "%{2}" } # gets shared secret from ldap if ( &control:totp_teste =~ /([A-Za-z0-9]+),/ ) { update control { TOTP-Secret := "%{1}" } } totp.authenticate if (!ok) { reject } update control { Auth-Type := ldap } } } authenticate { Auth-Type ldap { ldap } } Could you please provide me some guidance on what I am doing wrong here? Thanks, Miguel

3 3

Auth with Agent Remote ID
by Florian Traxler (mieX GmbH) 16 Nov '23

16 Nov '23

Hello! I use FreeRADIUS version 3.0.20 and would like to allow the user to authenticate using "Agent Remote ID". Is there a way to supplement the configuration according to this parameter "access-accept". Thanks for the support.

2 3

set up tls configuration
by Andrei Katsuk 14 Nov '23

14 Nov '23

Hi, I want to set ca_file in the tls config section to env variable as follows: tls { ca_file = $ENV{LDAP_CERT} } and skip it if $ENV{LDAP_CERT} is empty. If it is empty FreeRADIUS shows next error: =========== Unable to check file "": No such file or directory /etc/raddb/mods-enabled/ldap[488]: Failed parsing configuration item "ca_file" ================ How can I skip it in this case? Andrei

2 1

EAP-TLS with CRLs broken on RHEL 8.8
by Fraser Hess 13 Nov '23

13 Nov '23

We have a working FreeRADIUS implementation. It is configured for EAP-TLS. Our production systems use stock rpms for FreeRADIUS and OpenSSL on CentOS 7.9. Current RPMs: freeradius-3.0.13-15.el7.x86_64 and openssl-1.0.2k-26.el7_9.x86_64 We are moving to Red Hat Enterprise Linux 8.8. We built a test system from scratch, installed our RADIUS config and our tests failed. The RPMs in RHEL 8.8 are: freeradius-3.0.20-14.module+el8.8.0+17558+3f8a93b9.x86_64 and openssl-1.1.1k-9.el8_7.x86_64 The failure occurs in CRL checking. With check_crl = yes and check_all_crl = yes, FreeRADIUS is unable to find our root CA's CRL to validate the intermediate CA. Setting either check_crl or check_all_crl to no resolves the issue. (8) eap_tls: TLS-Cert-Serial := "XXX" (8) eap_tls: TLS-Cert-Expiration := "250901211201Z" (8) eap_tls: TLS-Cert-Subject := "/C=US/O=Organization/CN=Organization Intermediate CA" (8) eap_tls: TLS-Cert-Issuer := "/C=US/O=Organization/CN=Organization Root CA" (8) eap_tls: TLS-Cert-Common-Name := "Organization Intermediate CA" (8) eap_tls: ERROR: SSL says error 3 : unable to get certificate CRL (8) eap_tls: >>> send TLS 1.2 [length 0002] (8) eap_tls: ERROR: TLS Alert write:fatal:unknown CA tls: TLS_accept: Error in error (8) eap_tls: ERROR: Failed in __FUNCTION__ (SSL_read): error:1417C086:SSL routines:tls_process_client_certificate:certificate verify failed (8) eap_tls: ERROR: System call (I/O) error (-1) (8) eap_tls: ERROR: TLS receive handshake failed during operation (8) eap_tls: ERROR: [eaptls process] = fail (8) eap: ERROR: Failed continuing EAP TLS (13) session. EAP sub-module failed Checking the leaf certificate against the intermediate CA appears to work. All of the certificates in /etc/raddb/certs have the correct hashed symlinks. We have tried setting tls_min_version = 1.2 and auto_chain = no, adding the intermediate CA certificate to the certificate_file. The same error results. I can break our production servers in the same manner by removing the hash symlink to the root CA's CRL file. In our test system, it's as if the hash symlink doesn't exist. The permissions on the files are correct - radiusd can read them all. Thank you for any help/suggestions Fraser Hess Workstation Engineer Pinnacol Assurance -- This communication and any attachments are for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer.

2 1

Reg: Freeradius 4.0 TACACS testing support
by shalini arivazhagan 10 Nov '23

10 Nov '23

Hi, I recently downloaded the 4.0 freeradius version to start my TACACS authentication. But I am facing an issue in authentication Added a new client in tacacs file. Add added a user<test> in the /etc/raddb/users file. But authentication is failed, it is giving error "No "known good" password found for user". Kindly help me on the TACACS testing. Where to add users for TACACS authentication in conf file. Thanks, Salini

2 1

Odd behavior on authentication
by Philip Prindeville 10 Nov '23

10 Nov '23

Hi, I had a test client (Ubuntu 22.04) set up, and I was running tcpdump on the server (also Ubuntu, running Freeradius 3.0). I had created a username & password on the Radius server, and if I tried to log into the client with those credentials, it failed. But as soon as I created a "cut out" on the client (same username, but '*' password in the shadow file), I could log in because the server was no longer rejecting the authorization request. I don't get it. How would the server know if there was a local user or not? Nothing in the messages seems to be different, other than the things you'd expect (the message id, and the random seed that the password gets hashed with). All other parts of the message looked to be identical. How was the client conveying to the server that there wasn't a local account present? Also, I've run "pam-auth-update --enable radius" to get pam_radius_auth.so plugged into the PAM stack, but how do I integrate it into /etc/nsswitch.conf as well? This is on Ubuntu so I don't have authconfig/authselect which are RedHat only. Thanks

3 5

deployment with two completely different sets of certificates
by Marek Zarychta 08 Nov '23

08 Nov '23

Dear List, I am considering use case with two completely different sets of certificates (different keys, certificates signed by different CAs). First, original set, will be used for clients without the realm and clients from old.realm. The new set, signed by well-know CA, will be used for TTLS-EAP and PEAP authentications only for the new.realm. If such a scenario requires deploying anther instance of FreeRADIUS, then please let me know, but most likely current instance could be configured to handle it. So far I have extended mods-enabled/eap and have there: eap eap1 { old realm / without realm settings } eap eap2 { new realm settings } eap { old realm / without realm settings } then added to sites-enabled/old.realm: if ((User-Name =~ /new\.realm$/) || ( Inner-Realm-Name =~ /new\.realm$/)) { update control { Auth-Type := eap2 } } but the authentications though successful, are still handled by eap1: (0) suffix: Checking for suffix after "@" (0) suffix: Looking up realm "new.realm" for User-Name = "anonymous(a)new.realm" (0) suffix: Found realm "new.realm" (0) suffix: Adding Stripped-User-Name = "anonymous" (0) suffix: Adding Realm = "new.realm" (0) suffix: Authentication realm is LOCAL (0) [suffix] = ok (0) eap1: Peer sent EAP Response (code 2) ID 130 length 29 (0) eap1: EAP-Identity reply, returning 'ok' so we can short-circuit the rest of authorize (0) [eap1] = ok (0) } # authorize = ok (0) Found Auth-Type = eap2 (0) Found Auth-Type = eap1 (0) ERROR: Warning: Found 2 auth-types on request for user 'anonymous' (0) # Executing group from file /usr/local/etc/raddb/sites-enabled/old.realm (0) authenticate { (0) eap1: Peer sent packet with method EAP Identity (1) (0) eap1: Calling submodule eap_peap to process data (0) eap_peap: (TLS) Initiating new session (0) eap1: Sending EAP Request (code 1) ID 131 length 6 (0) eap1: EAP session adding &reply:State = 0x16f700fc167419f8 (0) [eap1] = handled (0) } # authenticate = handled (0) Using Post-Auth-Type Challenge So I am stuck. Please, any clues helping to proceed this further will be appreciated. Cheers ! -- Marek Zarychta

2 2