search for: private_key_fil

...ass looks like the best for what we need to do but I am not sure how to generate the key. The docs say: This is a shortcut for using an asymmetrical algorithm with a private/ public key file. To use this, generate a public and private key with Sentry::AsymmetricalSentry.save_random_rsa_key (private_key_file, public_key_file). If you want to encrypt the private key file with a symmetrical algorithm, pass a secret key (neither the key nor the decrypted value will be stored). Sentry::AsymmetricSentry.save_random_rsa_key(private_key_file, public_key_file, :key => ''secret_password'...

...certs/service.radius.crt chmod 640 /etc/freeradius/3.0/certs/service.radius.* chown freerad:freerad /etc/freeradius/3.0/certs/service.radius.* ``` - configure eap module to use peap per default ``` # /etc/freeradius/3.0/mods-available/eap default_eap_type = peap #private_key_password = whatever private_key_file = ${certdir}/service.radius.key certificate_file = ${certdir}/service.radius.crt tls_min_version = "1.2" cache: enable = yes cache: name = ?<somename>.radius" cache: persist_dir = "${logdir}/tlscache" peap: copy_request_to_tunnel = yes ``` ### 4.5 Configure Clien...

...3.0/certs/service.radius.* > chown freerad:freerad /etc/freeradius/3.0/certs/service.radius.* > ``` > > - configure eap module to use peap per default > > ``` > # /etc/freeradius/3.0/mods-available/eap > default_eap_type = peap > > #private_key_password = whatever > private_key_file = ${certdir}/service.radius.key > certificate_file = ${certdir}/service.radius.crt > > tls_min_version = "1.2" > > cache: enable = yes > cache: name = ?<somename>.radius" > cache: persist_dir = "${logdir}/tlscache" > > peap: copy_request_to...

...s/3.0/certs/service.radius.* >> ``` >> >> - configure eap module to use peap per default >> >> ``` >> # /etc/freeradius/3.0/mods-available/eap >> default_eap_type = peap >> >> #private_key_password = whatever >> private_key_file = ${certdir}/service.radius.key >> certificate_file = ${certdir}/service.radius.crt >> >> tls_min_version = "1.2" >> >> cache: enable = yes >> cache: name = ?<somename>.radius" >> cache: persist_dir = "${logdir...

...rad /etc/freeradius/3.0/certs/service.radius.* > > ``` > > > > - configure eap module to use peap per default > > > > ``` > > # /etc/freeradius/3.0/mods-available/eap > > default_eap_type = peap > > > > #private_key_password = whatever > > private_key_file = ${certdir}/service.radius.key > > certificate_file = ${certdir}/service.radius.crt > > > > tls_min_version = "1.2" > > > > cache: enable = yes > > cache: name = ?<somename>.radius" > > cache: persist_dir = "${logdir}/tlscache&qu...

> I guess we have to look at the conf files then, first these two: Thank you for the config file snippets. I can confirm mine were almost identical, so I've tweaked them so that they are now exactly the same as yours except for the "--require-membership-of=example\authorization_groupname" line in ntlm_auth. Unfortunately it's still erroring out: (7) mschap: Creating

Hello Tim, Hello samba-people, is there an uptodate guide for authenticating via freeradius somewhere? I have some Ubiquiti APs plus a Cloud Key and I want to authenticate WLAN clients via WPA2-Enterprise instead of a (shared) PSK. It seems like https://wiki.samba.org/index.php/Authenticating_Freeradius_against_Active_Directory is missing some steps (basic setup of freeradius). Can you