Add TLS version to logs with linelog in FreeRADIUS 3.2.4
Hi guys A few weeks back, I used FreeRADIUS 3.0.26 on Ubuntu 22.04.4 LTS before upgrading to FreeRADIUS 3.2.4 (NetworkRADIUS packages). Everything works great so far, except two attributes are missing in our logs since then: TLS-Session-Version and TLS-Session-Cipher-Suite. My /etc/freeradius/mods-available/linelog configuration looked like this on FreeRADIUS 3.0.x: sp { Access-Accept = "%t : AuthZ: (%I) Access-Accept: [%{%{reply:User-Name}:-%{User-Name}}] TLS-Version=%{%{session-state:TLS-Session-Version}:-NULL} TLS-Ciphers=%{%{session-state:TLS-Session-Cipher-Suite}:-NULL} SSID=%{%{request:Called-Station-SSID}:-NULL} Calling-Station-Id=%{%{request:Calling-Station-Id}:-Unknown} Called-Station-Id=%{%{request:Called-Station-Id}:-Unknown} Filter-ID=%{%{reply:Filter-Id}:-NULL} VLAN=%{%{reply:Tunnel-Private-Group-Id}:-NULL} Class=%{%{reply:Class}:-NULL} (from client %{Client-Shortname} port %{%{request:Nas-Port}:-0} cli %{%{request:Calling-Station-Id}:-Unknown})" } When I start the debugging (see full output below), I can see the following attributes, which I could use / log now: (10) eap_peap: TLS-Session-Cipher-Suite = "ECDHE-RSA-AES256-GCM-SHA384" (10) eap_peap: TLS-Session-Version = "TLS 1.2" When I try to “access” them in the linelog configuration like this… sp { Access-Accept = "%t : AuthZ: (%I) Access-Accept: [%{%{reply:User-Name}:-%{User-Name}}] TLS-Test=%{%{eap_peap:TLS-Session-Version}:-NULL} TLS-Version=%{%{session-state:TLS-Session-Version}:-NULL} TLS-Ciphers=%{%{session-state:TLS-Session-Cipher-Suite}:-NULL} SSID=%{%{request:Called-Station-SSID}:-NULL} Calling-Station-Id=%{%{request:Calling-Station-Id}:-Unknown} Called-Station-Id=%{%{request:Called-Station-Id}:-Unknown} Filter-ID=%{%{reply:Filter-Id}:-NULL} VLAN=%{%{reply:Tunnel-Private-Group-Id}:-NULL} Class=%{%{reply:Class}:-NULL} (from client %{Client-Shortname} port %{%{request:Nas-Port}:-0} cli %{%{request:Calling-Station-Id}:-Unknown})" } } …I get the following error in the debug output: (21) 802.1x_authz_log: ERROR: %t : AuthZ: (%I) Access-Accept: [%{%{reply:User-Name}:-%{User-Name}}] TLS-Test=%{%{eap_peap:TLS-Session-Version}:-NULL} TLS-Version=%{%{session-state:TLS-Session-Version}:-NULL} TLS-Ciphers=%{%{session-state:TLS-Session-Cipher-Suite}:-NULL} SSID=%{%{request:Called-Station-SSID}:-NULL} Calling-Station-Id=%{%{request:Calling-Station-Id}:-Unknown} Called-Station-Id=%{%{request:Called-Station-Id}:-Unknown} Filter-ID=%{%{reply:Filter-Id}:-NULL} VLAN=%{%{reply:Tunnel-Private-Group-Id}:-NULL} Class=%{%{reply:Class}:-NULL} (from client %{Client-Shortname} port %{%{request:Nas-Port}:-0} cli %{%{request:Calling-Station-Id}:-Unknown}) (21) 802.1x_authz_log: ERROR: ^ Unknown module Any hint, how I can “access” those two attributes in FreeRADIUS 3.2.4 correctly? (10) eap_peap: TLS-Session-Cipher-Suite = "ECDHE-RSA-AES256-GCM-SHA384" (10) eap_peap: TLS-Session-Version = "TLS 1.2" Thanks in advance and best regards Dominic *** Full debug output: root@id-radiustest1:~# freeradius -X FreeRADIUS Version 3.2.4 Copyright (C) 1999-2023 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 For more information about these matters, see the file named COPYRIGHT Starting - reading configuration files ... including dictionary file /usr/share/freeradius/dictionary including dictionary file /usr/share/freeradius/dictionary.dhcp including dictionary file /usr/share/freeradius/dictionary.vqp including dictionary file /etc/freeradius/dictionary 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/mods-enabled/ including configuration file /etc/freeradius/mods-enabled/preprocess including configuration file /etc/freeradius/mods-enabled/utf8 including configuration file /etc/freeradius/mods-enabled/expr including configuration file /etc/freeradius/mods-enabled/expiration including configuration file /etc/freeradius/mods-enabled/passwd including configuration file /etc/freeradius/mods-enabled/sradutmp including configuration file /etc/freeradius/mods-enabled/dynamic_clients including configuration file /etc/freeradius/mods-enabled/digest including configuration file /etc/freeradius/mods-enabled/chap including configuration file /etc/freeradius/mods-enabled/unix including configuration file /etc/freeradius/mods-enabled/always including configuration file /etc/freeradius/mods-enabled/linelog including configuration file /etc/freeradius/mods-enabled/soh including configuration file /etc/freeradius/mods-enabled/date including configuration file /etc/freeradius/mods-enabled/pap including configuration file /etc/freeradius/mods-enabled/totp including configuration file /etc/freeradius/mods-enabled/files including configuration file /etc/freeradius/mods-enabled/echo including configuration file /etc/freeradius/mods-enabled/cache_eap including configuration file /etc/freeradius/mods-enabled/replicate including configuration file /etc/freeradius/mods-enabled/exec including configuration file /etc/freeradius/mods-enabled/eap including configuration file /etc/freeradius/mods-enabled/ntlm_auth including configuration file /etc/freeradius/mods-enabled/radutmp including configuration file /etc/freeradius/mods-enabled/attr_filter including configuration file /etc/freeradius/mods-enabled/mschap including configuration file /etc/freeradius/mods-enabled/logintime including configuration file /etc/freeradius/mods-enabled/realm including configuration file /etc/freeradius/mods-enabled/detail including configuration file /etc/freeradius/mods-enabled/unpack including configuration file /etc/freeradius/mods-enabled/detail.log including files in directory /etc/freeradius/policy.d/ including configuration file /etc/freeradius/policy.d/operator-name including configuration file /etc/freeradius/policy.d/debug including configuration file /etc/freeradius/policy.d/filter including configuration file /etc/freeradius/policy.d/accounting including configuration file /etc/freeradius/policy.d/canonicalization including configuration file /etc/freeradius/policy.d/abfab-tr including configuration file /etc/freeradius/policy.d/moonshot-targeted-ids including configuration file /etc/freeradius/policy.d/rfc7542 including configuration file /etc/freeradius/policy.d/cui including configuration file /etc/freeradius/policy.d/eap including configuration file /etc/freeradius/policy.d/dhcp including configuration file /etc/freeradius/policy.d/control including files in directory /etc/freeradius/sites-enabled/ including configuration file /etc/freeradius/sites-enabled/inner-tunnel including configuration file /etc/freeradius/sites-enabled/default including configuration file /etc/freeradius/sites-enabled/proxy-inner-tunnel including configuration file /etc/freeradius/sites-enabled/control-socket main { security { user = "freerad" group = "freerad" allow_core_dumps = no } name = "freeradius" prefix = "/usr" localstatedir = "/var" logdir = "/var/log/freeradius" run_dir = "/var/run/freeradius" } main { name = "freeradius" prefix = "/usr" localstatedir = "/var" sbindir = "/usr/sbin" logdir = "/var/log/freeradius" run_dir = "/var/run/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" hostname_lookups = no max_request_time = 30 proxy_dedup_window = 1 cleanup_delay = 5 max_requests = 16384 max_fds = 512 postauth_client_lost = no pidfile = "/var/run/freeradius/freeradius.pid" checkrad = "/usr/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = yes auth_badpass = no auth_goodpass = no colourise = yes msg_denied = "You are already logged in - access denied" } resources { } security { max_attributes = 200 reject_delay = 1.000000 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 } ... } Debugger not attached systemd watchdog is disabled # Creating Auth-Type = mschap # Creating Auth-Type = eap radiusd: #### Instantiating modules #### modules { # Loaded module rlm_preprocess # Loading module "preprocess" from file /etc/freeradius/mods-enabled/preprocess preprocess { huntgroups = "/etc/freeradius/mods-config/preprocess/huntgroups" hints = "/etc/freeradius/mods-config/preprocess/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 } # Loaded module rlm_utf8 # Loading module "utf8" from file /etc/freeradius/mods-enabled/utf8 # Loaded module rlm_expr # Loading module "expr" from file /etc/freeradius/mods-enabled/expr expr { safe_characters = "@abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789.-_: /äéöüàâæçèéêëîïôœùûüaÿÄÉÖÜßÀÂÆÇÈÉÊËÎÏÔŒÙÛÜŸ" } # Loaded module rlm_expiration # Loading module "expiration" from file /etc/freeradius/mods-enabled/expiration # Loaded module rlm_passwd # Loading module "etc_passwd" from file /etc/freeradius/mods-enabled/passwd passwd etc_passwd { filename = "/etc/passwd" format = "*User-Name:Crypt-Password:" delimiter = ":" ignore_nislike = no ignore_empty = yes allow_multiple_keys = no hash_size = 100 } # Loaded module rlm_radutmp # Loading module "sradutmp" from file /etc/freeradius/mods-enabled/sradutmp radutmp sradutmp { filename = "/var/log/freeradius/sradutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes permissions = 420 caller_id = no } # Loaded module rlm_dynamic_clients # Loading module "dynamic_clients" from file /etc/freeradius/mods-enabled/dynamic_clients # Loaded module rlm_digest # Loading module "digest" from file /etc/freeradius/mods-enabled/digest # Loaded module rlm_chap # Loading module "chap" from file /etc/freeradius/mods-enabled/chap # Loaded module rlm_unix # Loading module "unix" from file /etc/freeradius/mods-enabled/unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Creating attribute Unix-Group # Loaded module rlm_always # Loading module "reject" from file /etc/freeradius/mods-enabled/always always reject { rcode = "reject" simulcount = 0 mpp = no } # Loading module "fail" from file /etc/freeradius/mods-enabled/always always fail { rcode = "fail" simulcount = 0 mpp = no } # Loading module "ok" from file /etc/freeradius/mods-enabled/always always ok { rcode = "ok" simulcount = 0 mpp = no } # Loading module "handled" from file /etc/freeradius/mods-enabled/always always handled { rcode = "handled" simulcount = 0 mpp = no } # Loading module "invalid" from file /etc/freeradius/mods-enabled/always always invalid { rcode = "invalid" simulcount = 0 mpp = no } # Loading module "userlock" from file /etc/freeradius/mods-enabled/always always userlock { rcode = "userlock" simulcount = 0 mpp = no } # Loading module "notfound" from file /etc/freeradius/mods-enabled/always always notfound { rcode = "notfound" simulcount = 0 mpp = no } # Loading module "noop" from file /etc/freeradius/mods-enabled/always always noop { rcode = "noop" simulcount = 0 mpp = no } # Loading module "updated" from file /etc/freeradius/mods-enabled/always always updated { rcode = "updated" simulcount = 0 mpp = no } # Loaded module rlm_linelog # Loading module "802.1x_authz_log" from file /etc/freeradius/mods-enabled/linelog linelog 802.1x_authz_log { filename = "/var/log/freeradius/authz.log" escape_filenames = no syslog_severity = "info" permissions = 384 reference = "sp.%{%{reply:Packet-Type}:-format}" } # Loading module "acct_log" from file /etc/freeradius/mods-enabled/linelog linelog acct_log { filename = "/var/log/freeradius/acct.log" escape_filenames = no syslog_severity = "info" permissions = 384 reference = "Accounting-Request.%{%{Acct-Status-Type}:-unknown}" } # Loaded module rlm_soh # Loading module "soh" from file /etc/freeradius/mods-enabled/soh soh { dhcp = yes } # Loaded module rlm_date # Loading module "date" from file /etc/freeradius/mods-enabled/date date { format = "%b %e %Y %H:%M:%S %Z" utc = no } # Loading module "wispr2date" from file /etc/freeradius/mods-enabled/date date wispr2date { format = "%Y-%m-%dT%H:%M:%S" utc = no } # Loaded module rlm_pap # Loading module "pap" from file /etc/freeradius/mods-enabled/pap pap { normalise = yes } # Loaded module rlm_totp # Loading module "totp" from file /etc/freeradius/mods-enabled/totp totp { time_step = 30 otp_length = 6 lookback_steps = 1 lookback_interval = 30 lookforward_steps = 0 } # Loaded module rlm_files # Loading module "files" from file /etc/freeradius/mods-enabled/files files { filename = "/etc/freeradius/mods-config/files/authorize" acctusersfile = "/etc/freeradius/mods-config/files/accounting" preproxy_usersfile = "/etc/freeradius/mods-config/files/pre-proxy" } # Loaded module rlm_exec # Loading module "echo" from file /etc/freeradius/mods-enabled/echo exec echo { wait = yes program = "/bin/echo %{User-Name}" input_pairs = "request" output_pairs = "reply" shell_escape = yes } # Loaded module rlm_cache # Loading module "cache_eap" from file /etc/freeradius/mods-enabled/cache_eap cache cache_eap { driver = "rlm_cache_rbtree" key = "%{%{control:State}:-%{%{reply:State}:-%{State}}}" ttl = 15 max_entries = 0 epoch = 0 add_stats = no } # Loaded module rlm_replicate # Loading module "replicate" from file /etc/freeradius/mods-enabled/replicate # Loading module "exec" from file /etc/freeradius/mods-enabled/exec exec { wait = no input_pairs = "request" shell_escape = yes timeout = 10 } # Loaded module rlm_eap # Loading module "eap" from file /etc/freeradius/mods-enabled/eap eap { default_eap_type = "PEAP" timer_expire = 60 max_eap_type = 52 ignore_unknown_eap_types = yes cisco_accounting_username_bug = no max_sessions = 8192 dedup_key = "" } # Loading module "ntlm_auth" from file /etc/freeradius/mods-enabled/ntlm_auth exec ntlm_auth { wait = yes program = "/path/to/ntlm_auth --request-nt-key --domain=MYDOMAIN --username=%{mschap:User-Name} --password=%{User-Password}" shell_escape = yes } # Loading module "radutmp" from file /etc/freeradius/mods-enabled/radutmp radutmp { filename = "/var/log/freeradius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes permissions = 384 caller_id = yes } # Loaded module rlm_attr_filter # Loading module "attr_filter.post-proxy" from file /etc/freeradius/mods-enabled/attr_filter attr_filter attr_filter.post-proxy { filename = "/etc/freeradius/mods-config/attr_filter/post-proxy" key = "%{Realm}" relaxed = no } # Loading module "attr_filter.pre-proxy" from file /etc/freeradius/mods-enabled/attr_filter attr_filter attr_filter.pre-proxy { filename = "/etc/freeradius/mods-config/attr_filter/pre-proxy" key = "%{Realm}" relaxed = no } # Loading module "attr_filter.access_reject" from file /etc/freeradius/mods-enabled/attr_filter attr_filter attr_filter.access_reject { filename = "/etc/freeradius/mods-config/attr_filter/access_reject" key = "%{User-Name}" relaxed = no } # Loading module "attr_filter.access_challenge" from file /etc/freeradius/mods-enabled/attr_filter attr_filter attr_filter.access_challenge { filename = "/etc/freeradius/mods-config/attr_filter/access_challenge" key = "%{User-Name}" relaxed = no } # Loading module "attr_filter.accounting_response" from file /etc/freeradius/mods-enabled/attr_filter attr_filter attr_filter.accounting_response { filename = "/etc/freeradius/mods-config/attr_filter/accounting_response" key = "%{User-Name}" relaxed = no } # Loading module "attr_filter.coa" from file /etc/freeradius/mods-enabled/attr_filter attr_filter attr_filter.coa { filename = "/etc/freeradius/mods-config/attr_filter/coa" key = "%{User-Name}" relaxed = no } # Loaded module rlm_mschap # Loading module "mschap" from file /etc/freeradius/mods-enabled/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = yes passchange { } allow_retry = yes winbind_retry_with_normalised_username = no } # Loaded module rlm_logintime # Loading module "logintime" from file /etc/freeradius/mods-enabled/logintime logintime { minimum_timeout = 60 } # Loaded module rlm_realm # Loading module "IPASS" from file /etc/freeradius/mods-enabled/realm realm IPASS { format = "prefix" delimiter = "/" ignore_default = no ignore_null = no } # Loading module "suffix" from file /etc/freeradius/mods-enabled/realm realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } # Loading module "bangpath" from file /etc/freeradius/mods-enabled/realm realm bangpath { format = "prefix" delimiter = "!" ignore_default = no ignore_null = no } # Loading module "realmpercent" from file /etc/freeradius/mods-enabled/realm realm realmpercent { format = "suffix" delimiter = "%" ignore_default = no ignore_null = no } # Loading module "ntdomain" from file /etc/freeradius/mods-enabled/realm realm ntdomain { format = "prefix" delimiter = "\" ignore_default = no ignore_null = no } # Loaded module rlm_detail # Loading module "detail" from file /etc/freeradius/mods-enabled/detail detail { filename = "/var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d" header = "%t" permissions = 384 locking = no dates_as_integer = no escape_filenames = no log_packet_header = no } # Loaded module rlm_unpack # Loading module "unpack" from file /etc/freeradius/mods-enabled/unpack # Loading module "auth_log" from file /etc/freeradius/mods-enabled/detail.log detail auth_log { filename = "/var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/auth-detail-%Y%m%d" header = "%t" permissions = 384 locking = no dates_as_integer = no escape_filenames = no log_packet_header = no } # Loading module "reply_log" from file /etc/freeradius/mods-enabled/detail.log detail reply_log { filename = "/var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/reply-detail-%Y%m%d" header = "%t" permissions = 384 locking = no dates_as_integer = no escape_filenames = no log_packet_header = no } # Loading module "pre_proxy_log" from file /etc/freeradius/mods-enabled/detail.log detail pre_proxy_log { filename = "/var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/pre-proxy-detail-%Y%m%d" header = "%t" permissions = 384 locking = no dates_as_integer = no escape_filenames = no log_packet_header = no } # Loading module "post_proxy_log" from file /etc/freeradius/mods-enabled/detail.log detail post_proxy_log { filename = "/var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/post-proxy-detail-%Y%m%d" header = "%t" permissions = 384 locking = no dates_as_integer = no escape_filenames = no log_packet_header = no } instantiate { } # Instantiating module "preprocess" from file /etc/freeradius/mods-enabled/preprocess reading pairlist file /etc/freeradius/mods-config/preprocess/huntgroups reading pairlist file /etc/freeradius/mods-config/preprocess/hints # Instantiating module "expiration" from file /etc/freeradius/mods-enabled/expiration # Instantiating module "etc_passwd" from file /etc/freeradius/mods-enabled/passwd rlm_passwd: nfields: 3 keyfield 0(User-Name) listable: no # Instantiating module "reject" from file /etc/freeradius/mods-enabled/always # Instantiating module "fail" from file /etc/freeradius/mods-enabled/always # Instantiating module "ok" from file /etc/freeradius/mods-enabled/always # Instantiating module "handled" from file /etc/freeradius/mods-enabled/always # Instantiating module "invalid" from file /etc/freeradius/mods-enabled/always # Instantiating module "userlock" from file /etc/freeradius/mods-enabled/always # Instantiating module "notfound" from file /etc/freeradius/mods-enabled/always # Instantiating module "noop" from file /etc/freeradius/mods-enabled/always # Instantiating module "updated" from file /etc/freeradius/mods-enabled/always # Instantiating module "802.1x_authz_log" from file /etc/freeradius/mods-enabled/linelog # Instantiating module "acct_log" from file /etc/freeradius/mods-enabled/linelog # Instantiating module "pap" from file /etc/freeradius/mods-enabled/pap # Instantiating module "totp" from file /etc/freeradius/mods-enabled/totp # Instantiating module "files" from file /etc/freeradius/mods-enabled/files reading pairlist file /etc/freeradius/mods-config/files/authorize reading pairlist file /etc/freeradius/mods-config/files/accounting reading pairlist file /etc/freeradius/mods-config/files/pre-proxy # Instantiating module "cache_eap" from file /etc/freeradius/mods-enabled/cache_eap rlm_cache (cache_eap): Driver rlm_cache_rbtree (module rlm_cache_rbtree) loaded and linked # Instantiating module "eap" from file /etc/freeradius/mods-enabled/eap # Linked to sub-module rlm_eap_peap peap { tls = "tls-common" default_eap_type = "mschapv2" copy_request_to_tunnel = yes use_tunneled_reply = yes proxy_tunneled_request_as_eap = yes virtual_server = "proxy-inner-tunnel" soh = no require_client_cert = no } tls-config tls-common { 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.crt" fragment_size = 1024 include_length = yes auto_chain = yes check_crl = no check_all_crl = no ca_path_reload_interval = 0 cipher_list = "ECDHE-RSA-AES128-SHA ECDHE-RSA-AES256-SHA ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-CHACHA20-POLY1305 TLS_AES_256_GCM_SHA384" reject_unknown_intermediate_ca = no ecdh_curve = "prime256v1" tls_max_version = "1.3" tls_min_version = "1.0" cache { enable = no lifetime = 12 name = "EAP module" max_entries = 0 persist_dir = "/var/log/freeradius/tlscache" } verify { skip_if_ocsp_ok = no } ocsp { enable = no override_cert_url = no use_nonce = yes timeout = 0 softfail = no } } tls: In order to use TLS 1.0 and/or TLS 1.1, you likely need to set: cipher_list = "DEFAULT@SECLEVEL=0" # Linked to sub-module rlm_eap_mschapv2 mschapv2 { with_ntdomain_hack = no send_error = no } # Instantiating module "attr_filter.post-proxy" from file /etc/freeradius/mods-enabled/attr_filter reading pairlist file /etc/freeradius/mods-config/attr_filter/post-proxy # Instantiating module "attr_filter.pre-proxy" from file /etc/freeradius/mods-enabled/attr_filter reading pairlist file /etc/freeradius/mods-config/attr_filter/pre-proxy # Instantiating module "attr_filter.access_reject" from file /etc/freeradius/mods-enabled/attr_filter reading pairlist file /etc/freeradius/mods-config/attr_filter/access_reject # Instantiating module "attr_filter.access_challenge" from file /etc/freeradius/mods-enabled/attr_filter reading pairlist file /etc/freeradius/mods-config/attr_filter/access_challenge # Instantiating module "attr_filter.accounting_response" from file /etc/freeradius/mods-enabled/attr_filter reading pairlist file /etc/freeradius/mods-config/attr_filter/accounting_response # Instantiating module "attr_filter.coa" from file /etc/freeradius/mods-enabled/attr_filter reading pairlist file /etc/freeradius/mods-config/attr_filter/coa # Instantiating module "mschap" from file /etc/freeradius/mods-enabled/mschap rlm_mschap (mschap): using internal authentication # Instantiating module "logintime" from file /etc/freeradius/mods-enabled/logintime # Instantiating module "IPASS" from file /etc/freeradius/mods-enabled/realm # Instantiating module "suffix" from file /etc/freeradius/mods-enabled/realm # Instantiating module "bangpath" from file /etc/freeradius/mods-enabled/realm # Instantiating module "realmpercent" from file /etc/freeradius/mods-enabled/realm # Instantiating module "ntdomain" from file /etc/freeradius/mods-enabled/realm # Instantiating module "detail" from file /etc/freeradius/mods-enabled/detail # Instantiating module "auth_log" from file /etc/freeradius/mods-enabled/detail.log rlm_detail (auth_log): 'User-Password' suppressed, will not appear in detail output # Instantiating module "reply_log" from file /etc/freeradius/mods-enabled/detail.log # Instantiating module "pre_proxy_log" from file /etc/freeradius/mods-enabled/detail.log # Instantiating module "post_proxy_log" from file /etc/freeradius/mods-enabled/detail.log } # modules radiusd: #### Loading Virtual Servers #### server { # from file /etc/freeradius/radiusd.conf } # server server inner-tunnel { # from file /etc/freeradius/sites-enabled/inner-tunnel # Loading authenticate {...} # Loading authorize {...} Ignoring "sql" (see raddb/mods-available/README.rst) Ignoring "ldap" (see raddb/mods-available/README.rst) # Loading session {...} # Loading post-proxy {...} # Loading post-auth {...} # Skipping contents of 'if' as it is always 'false' -- /etc/freeradius/sites-enabled/inner-tunnel:336 Compiling Post-Auth-Type REJECT for attr Post-Auth-Type } # server inner-tunnel server default { # from file /etc/freeradius/sites-enabled/default # Loading authenticate {...} Compiling Auth-Type eap for attr Auth-Type # Loading authorize {...} # Loading preacct {...} # Loading accounting {...} # Loading pre-proxy {...} # Loading post-proxy {...} # Loading post-auth {...} Compiling Post-Auth-Type REJECT for attr Post-Auth-Type } # server default server proxy-inner-tunnel { # from file /etc/freeradius/sites-enabled/proxy-inner-tunnel # Loading authenticate {...} Compiling Auth-Type mschap for attr Auth-Type # Loading authorize {...} } # server proxy-inner-tunnel radiusd: #### Opening IP addresses and Ports #### listen { type = "control" listen { socket = "/var/run/freeradius/control/freeradius.sock" uid = "freerad" gid = "freerad" mode = "rw" peercred = no } } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } listen { type = "auth" ipaddr = * port = 1812 } listen { type = "acct" ipaddr = * port = 1813 } Listening on command file /var/run/freeradius/control/freeradius.sock Listening on auth address 127.0.0.1 port 18120 bound to server inner-tunnel Listening on auth address * port 1812 bound to server default Listening on acct address * port 1813 bound to server default Listening on proxy address * port 44695 Ready to process requests
On Jun 14, 2024, at 7:10 AM, dominic.stalder@unibe.ch wrote:
When I start the debugging (see full output below), I can see the following attributes, which I could use / log now:
(10) eap_peap: TLS-Session-Cipher-Suite = "ECDHE-RSA-AES256-GCM-SHA384" (10) eap_peap: TLS-Session-Version = "TLS 1.2"
When I try to “access” them in the linelog configuration like this…
The "eap_peap" text is just debugging information that tells you which module is being run. It's not part of the attribute name.
sp { Access-Accept = "%t : AuthZ: (%I) Access-Accept: [%{%{reply:User-Name}:-%{User-Name}}] TLS-Test=%{%{eap_peap:TLS-Session-Version}:-NULL}
You can't use "%{eap_peap:TLS-Session-Version}". No documentation says that it will work.
TLS-Version=%{%{session-state:TLS-Session-Version}:-NULL}
Why are you using "session-state" in one place, and "eap_peap" in another? If the reference in session-state works, just use that.
Any hint, how I can “access” those two attributes in FreeRADIUS 3.2.4 correctly?
Use the correct reference.
Full debug output:
Which doesn't actually include the server receiving any packets... It helps to read documentation. Alan DeKok.
Hi Alan
Why are you using "session-state" in one place, and "eap_peap" in another? If the reference in session-state works, just use that. The use of "session-state" was working in FreeRADIUS 3.0.26, but does not anymore in 3.2.4, that's why I am asking.
Use the correct reference. That's why I am asking, because I do not know the correct reference.
Which doesn't actually include the server receiving any packets... Also true, because my email was bigger than 500 KB and was rejected by the email list admins...
Regards Dominic Am 14.06.24, 13:21 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: On Jun 14, 2024, at 7:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> wrote:
When I start the debugging (see full output below), I can see the following attributes, which I could use / log now:
(10) eap_peap: TLS-Session-Cipher-Suite = "ECDHE-RSA-AES256-GCM-SHA384" (10) eap_peap: TLS-Session-Version = "TLS 1.2"
When I try to “access” them in the linelog configuration like this…
The "eap_peap" text is just debugging information that tells you which module is being run. It's not part of the attribute name.
sp { Access-Accept = "%t : AuthZ: (%I) Access-Accept: [%{%{reply:User-Name}:-%{User-Name}}] TLS-Test=%{%{eap_peap:TLS-Session-Version}:-NULL}
You can't use "%{eap_peap:TLS-Session-Version}". No documentation says that it will work.
TLS-Version=%{%{session-state:TLS-Session-Version}:-NULL}
Why are you using "session-state" in one place, and "eap_peap" in another? If the reference in session-state works, just use that.
Any hint, how I can “access” those two attributes in FreeRADIUS 3.2.4 correctly?
Use the correct reference.
Full debug output:
Which doesn't actually include the server receiving any packets... It helps to read documentation. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
On Jun 14, 2024, at 7:24 AM, <dominic.stalder@unibe.ch> <dominic.stalder@unibe.ch> wrote:
Why are you using "session-state" in one place, and "eap_peap" in another? If the reference in session-state works, just use that. The use of "session-state" was working in FreeRADIUS 3.0.26, but does not anymore in 3.2.4, that's why I am asking.
It should work, I'll go look at that.
Use the correct reference. That's why I am asking, because I do not know the correct reference.
It should be session-state. If you want to see what is in each list, you can read raddb/policy.d/debug. That file has various policies which you can add to the virtual server. They will print out the contents of the various lists. i.e. .... eap debug_control debug_request debug_session_state ... You can then read the debug output to see exactly what's in each list.
Which doesn't actually include the server receiving any packets... Also true, because my email was bigger than 500 KB and was rejected by the email list admins...
It should be possible to send text email, and enough logs to show the issue. Your post was larger than 1M, which means there was about 10,000 lines of text in it. There's just no need to send that much. Alan DeKok.
Hi Alan
It should work, I'll go look at that. Thanks, would appreciate any help on this __
It should be session-state. I thought the same and tried to find the information in the RADIUS answer in the debug output (freeradius -X). But I do not have the debug output for version 3.0.26 anymore, so I am not able to compare the debug outputs.
If you want to see what is in each list, you can read raddb/policy.d/debug. That file has various policies which you can add to the virtual server. They will print out the contents of the various lists. Thanks for this hint, tried to find some attribute lists online.
It should be possible to send text email, and enough logs to show the issue. Your post was larger than 1M, which means there was about 10,000 lines of text in it. There's just no need to send that much. Will be more "careful" the next time with the length of the "full debug output".
Regards Dominic Am 14.06.24, 13:31 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: On Jun 14, 2024, at 7:24 AM, <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>> <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>> wrote:
Why are you using "session-state" in one place, and "eap_peap" in another? If the reference in session-state works, just use that. The use of "session-state" was working in FreeRADIUS 3.0.26, but does not anymore in 3.2.4, that's why I am asking.
It should work, I'll go look at that.
Use the correct reference. That's why I am asking, because I do not know the correct reference.
It should be session-state. If you want to see what is in each list, you can read raddb/policy.d/debug. That file has various policies which you can add to the virtual server. They will print out the contents of the various lists. i.e. .... eap debug_control debug_request debug_session_state ... You can then read the debug output to see exactly what's in each list.
Which doesn't actually include the server receiving any packets... Also true, because my email was bigger than 500 KB and was rejected by the email list admins...
It should be possible to send text email, and enough logs to show the issue. Your post was larger than 1M, which means there was about 10,000 lines of text in it. There's just no need to send that much. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
Hi Alan
It should work, I'll go look at that. Have you been able to check on this or reproduce it?
Thanks and regards Dominic Am 14.06.24, 13:34 schrieb "Stalder, Dominic (ID)" <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>: Hi Alan
It should work, I'll go look at that. Thanks, would appreciate any help on this __
It should be session-state. I thought the same and tried to find the information in the RADIUS answer in the debug output (freeradius -X). But I do not have the debug output for version 3.0.26 anymore, so I am not able to compare the debug outputs.
If you want to see what is in each list, you can read raddb/policy.d/debug. That file has various policies which you can add to the virtual server. They will print out the contents of the various lists. Thanks for this hint, tried to find some attribute lists online.
It should be possible to send text email, and enough logs to show the issue. Your post was larger than 1M, which means there was about 10,000 lines of text in it. There's just no need to send that much. Will be more "careful" the next time with the length of the "full debug output".
Regards Dominic Am 14.06.24, 13:31 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> <mailto:unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org>> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com> <mailto:aland@deployingradius.com <mailto:aland@deployingradius.com>>>: On Jun 14, 2024, at 7:24 AM, <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>> <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>> wrote:
Why are you using "session-state" in one place, and "eap_peap" in another? If the reference in session-state works, just use that. The use of "session-state" was working in FreeRADIUS 3.0.26, but does not anymore in 3.2.4, that's why I am asking.
It should work, I'll go look at that.
Use the correct reference. That's why I am asking, because I do not know the correct reference.
It should be session-state. If you want to see what is in each list, you can read raddb/policy.d/debug. That file has various policies which you can add to the virtual server. They will print out the contents of the various lists. i.e. .... eap debug_control debug_request debug_session_state ... You can then read the debug output to see exactly what's in each list.
Which doesn't actually include the server receiving any packets... Also true, because my email was bigger than 500 KB and was rejected by the email list admins...
It should be possible to send text email, and enough logs to show the issue. Your post was larger than 1M, which means there was about 10,000 lines of text in it. There's just no need to send that much. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html;>
Hi Alan Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x? Thanks and best regards Dominic Am 14.06.24, 13:34 schrieb "Stalder, Dominic (ID)" <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>: Hi Alan
It should work, I'll go look at that. Thanks, would appreciate any help on this __
It should be session-state. I thought the same and tried to find the information in the RADIUS answer in the debug output (freeradius -X). But I do not have the debug output for version 3.0.26 anymore, so I am not able to compare the debug outputs.
If you want to see what is in each list, you can read raddb/policy.d/debug. That file has various policies which you can add to the virtual server. They will print out the contents of the various lists. Thanks for this hint, tried to find some attribute lists online.
It should be possible to send text email, and enough logs to show the issue. Your post was larger than 1M, which means there was about 10,000 lines of text in it. There's just no need to send that much. Will be more "careful" the next time with the length of the "full debug output".
Regards Dominic Am 14.06.24, 13:31 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> <mailto:unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org>> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com> <mailto:aland@deployingradius.com <mailto:aland@deployingradius.com>>>: On Jun 14, 2024, at 7:24 AM, <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>> <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>> wrote:
Why are you using "session-state" in one place, and "eap_peap" in another? If the reference in session-state works, just use that. The use of "session-state" was working in FreeRADIUS 3.0.26, but does not anymore in 3.2.4, that's why I am asking.
It should work, I'll go look at that.
Use the correct reference. That's why I am asking, because I do not know the correct reference.
It should be session-state. If you want to see what is in each list, you can read raddb/policy.d/debug. That file has various policies which you can add to the virtual server. They will print out the contents of the various lists. i.e. .... eap debug_control debug_request debug_session_state ... You can then read the debug output to see exactly what's in each list.
Which doesn't actually include the server receiving any packets... Also true, because my email was bigger than 500 KB and was rejected by the email list admins...
It should be possible to send text email, and enough logs to show the issue. Your post was larger than 1M, which means there was about 10,000 lines of text in it. There's just no need to send that much. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html;>
On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week. Alan DeKok.
Hi Alan Thanks a lot! Regards Dominic Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
Hi Dominic, Not sure if it helps, or if I make a mistake in my thinking, but I’m logging the TLS version with %{reply:TLS-Session-Version} in a linelog, with I believe a reasonably unmodified default configuration otherwise. Regards, Paul From: Freeradius-Users <freeradius-users-bounces+paul.dekkers=surf.nl@lists.freeradius.org> on behalf of dominic.stalder@unibe.ch <dominic.stalder@unibe.ch> Date: Wednesday, 3 July 2024 at 15:37 To: freeradius-users@lists.freeradius.org <freeradius-users@lists.freeradius.org> Subject: Re: Add TLS version to logs with linelog in FreeRADIUS 3.2.4 Hi Alan Thanks a lot! Regards Dominic Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Paul Thanks for your response, but even when I replace the configuration in /etc/freeradius/mods-enabled/linelog with TLS-Version=%{%{reply:TLS-Session-Version}:-NULL}, it does log NULL for TLS Version and TLS Cipher-Suite. Regards Dominic Von: Paul Dekkers <paul.dekkers@surf.nl> Datum: Donnerstag, 26. September 2024 um 13:36 An: "Stalder, Dominic (ID)" <dominic.stalder@unibe.ch> Cc: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Betreff: Re: Add TLS version to logs with linelog in FreeRADIUS 3.2.4 You don't often get email from paul.dekkers@surf.nl. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Dominic, Not sure if it helps, or if I make a mistake in my thinking, but I’m logging the TLS version with %{reply:TLS-Session-Version} in a linelog, with I believe a reasonably unmodified default configuration otherwise. Regards, Paul From: Freeradius-Users <freeradius-users-bounces+paul.dekkers=surf.nl@lists.freeradius.org> on behalf of dominic.stalder@unibe.ch <dominic.stalder@unibe.ch> Date: Wednesday, 3 July 2024 at 15:37 To: freeradius-users@lists.freeradius.org <freeradius-users@lists.freeradius.org> Subject: Re: Add TLS version to logs with linelog in FreeRADIUS 3.2.4 Hi Alan Thanks a lot! Regards Dominic Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi, Ok, you made me try it on a clean config 😉 because I know I use this with success. And… it works for me (used v3.2.x branch); the %{reply:TLS-Session-Version} works if I put the linelog after this section in post-auth: update { &reply: += &session-state: } But if I put linelog at the start of post-auth, just adding the TLS-Version with the session-state also works: Access-Accept = "Accepted user: %{User-Name} TLS-Version=%{%{session-state:TLS-Session-Version}:-NULL}" So, back to your original question I guess there’s nothing wrong with %{session-state:…}? Paul From: dominic.stalder@unibe.ch <dominic.stalder@unibe.ch> Date: Thursday, 26 September 2024 at 15:26 To: Paul Dekkers <paul.dekkers@surf.nl> Cc: freeradius-users@lists.freeradius.org <freeradius-users@lists.freeradius.org> Subject: Re: Add TLS version to logs with linelog in FreeRADIUS 3.2.4 Hi Paul Thanks for your response, but even when I replace the configuration in /etc/freeradius/mods-enabled/linelog with TLS-Version=%{%{reply:TLS-Session-Version}:-NULL}, it does log NULL for TLS Version and TLS Cipher-Suite. Regards Dominic Von: Paul Dekkers <paul.dekkers@surf.nl> Datum: Donnerstag, 26. September 2024 um 13:36 An: "Stalder, Dominic (ID)" <dominic.stalder@unibe.ch> Cc: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Betreff: Re: Add TLS version to logs with linelog in FreeRADIUS 3.2.4 You don't often get email from paul.dekkers@surf.nl. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Dominic, Not sure if it helps, or if I make a mistake in my thinking, but I’m logging the TLS version with %{reply:TLS-Session-Version} in a linelog, with I believe a reasonably unmodified default configuration otherwise. Regards, Paul From: Freeradius-Users <freeradius-users-bounces+paul.dekkers=surf.nl@lists.freeradius.org> on behalf of dominic.stalder@unibe.ch <dominic.stalder@unibe.ch> Date: Wednesday, 3 July 2024 at 15:37 To: freeradius-users@lists.freeradius.org <freeradius-users@lists.freeradius.org> Subject: Re: Add TLS version to logs with linelog in FreeRADIUS 3.2.4 Hi Alan Thanks a lot! Regards Dominic Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Alan Just wanted to check about the following logging options in FreeRadius > 3.2.4; have you or your team been able to have a look at it in the meantime? Best regards Dominic Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
Hi Alan Sorry for asking again, but any news on this topic? Regards Dominic Am 28.08.24, 10:21 schrieb "Stalder, Dominic (ID)" <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>: Hi Alan Just wanted to check about the following logging options in FreeRadius > 3.2.4; have you or your team been able to have a look at it in the meantime? Best regards Dominic Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> <mailto:unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org>> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com> <mailto:aland@deployingradius.com <mailto:aland@deployingradius.com>>>: On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html;>
Not yet, sorry.
On Sep 12, 2024, at 11:48 AM, dominic.stalder@unibe.ch wrote:
Hi Alan
Sorry for asking again, but any news on this topic?
Regards Dominic
Am 28.08.24, 10:21 schrieb "Stalder, Dominic (ID)" <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>:
Hi Alan
Just wanted to check about the following logging options in FreeRadius > 3.2.4; have you or your team been able to have a look at it in the meantime?
Best regards Dominic
Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> <mailto:unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org>> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com> <mailto:aland@deployingradius.com <mailto:aland@deployingradius.com>>>:
On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html;>
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Alan Thanks any way for the feedback; could you please let me know, when you or your team was able to investigate. Regards Dominic Am 20.09.24, 16:46 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com>>: Not yet, sorry.
On Sep 12, 2024, at 11:48 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> wrote:
Hi Alan
Sorry for asking again, but any news on this topic?
Regards Dominic
Am 28.08.24, 10:21 schrieb "Stalder, Dominic (ID)" <dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>>:
Hi Alan
Just wanted to check about the following logging options in FreeRadius > 3.2.4; have you or your team been able to have a look at it in the meantime?
Best regards Dominic
Am 03.07.24, 15:17 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> <mailto:unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org>> <mailto:unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org> <mailto:unibe.ch@lists.freeradius.org <mailto:unibe.ch@lists.freeradius.org>>> im Auftrag von aland@deployingradius.com <mailto:aland@deployingradius.com> <mailto:aland@deployingradius.com <mailto:aland@deployingradius.com>> <mailto:aland@deployingradius.com <mailto:aland@deployingradius.com> <mailto:aland@deployingradius.com <mailto:aland@deployingradius.com>>>>:
On Jul 3, 2024, at 8:10 AM, dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch> <mailto:dominic.stalder@unibe.ch <mailto:dominic.stalder@unibe.ch>>> wrote:
Sorry for asking, but have you been able to have a look at the session-state attributes (session-state:TLS-Session-Version and session-state:TLS-Session-Cipher-Suite) in FreeRADIUS version 3.2.x?
Some from the team should have time to look at this late next week.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html;> <http://www.freeradius.org/list/users.html> <http://www.freeradius.org/list/users.html;> <http://www.freeradius.org/list/users.html;> <http://www.freeradius.org/list/users.html;>
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
participants (3)
-
Alan DeKok -
dominic.stalder@unibe.ch -
Paul Dekkers