Differences

This shows you the differences between two versions of the page.

--- eduroam_linux [2014/12/11 16:25] – tested on F20 costesbn
+++ eduroam_linux [2023/03/29 15:02] (current) – admin
@@ Line 16: / Line 16: @@
   * PEAP version: Automatic
   * Inner authentication: MSCHAPv2
-  * Username: <your username>@h-its.org
+  * Username: //<your username>//@h-its.org
-  * check "Ask for this password every time", or (not recommended) enter the password. The is the same password that you use to access your e-mail.
+  * check "Ask for this password every time", or (not recommended) enter the password. This is the same password that you use to access your e-mail.
 Using TTLS/MSCHAPv2 requires the following settings:
@@ Line 27: / Line 27: @@
   * CA certificate: download {{:hits-eduroam-ca.der|the certificate}} to your computer, then select it
   * Inner authentication: MSCHAPv2
-  * Username: <your username>@h-its.org
+  * Username: //<your username>//@h-its.org
-  * check "Ask for this password every time", or (not recommended) enter the password. The is the same password that you use to access your e-mail.
+  * check "Ask for this password every time", or (not recommended) enter the password. This is the same password that you use to access your e-mail.
 **Step 3.** Click on the WiFi icon again and choose "eduroam". If "Ask for this password every time" was checked (as recommended) in Step 2, you'll be asked for a password - this is the same password that you use to access your e-mail. After entering the password, the authentication should succeed and access to the "eduroam" network should be granted.
+<WRAP center round important 60%>
+Ubuntu 22.04 configuration
+Please activate the following option in the initial setup:
+"No CA certificate is required"
+</WRAP>
+<WRAP center round important 80%>
+Starting from Fedora 33, the settings for crypto algorithms have become more stringent, such that the certificate used above is no longer considered valid and the eduroam authentication fails. The settings can be switched back to the ones in Fedora 32 with the command (run as root):
+<code>
+update-crypto-policies --set DEFAULT:FEDORA32
+</code>
+followed by a restart of the computer.
+</WRAP>