Spacc BBS Spacc BBS
    • Categorie
    • Recenti
    • Tag
    • Popolare
    • Mondo
    • Utenti
    • Gruppi
    • Registrati
    • Accedi
    La nuova BBS è in fase Alpha. I post precedenti al 22 luglio 2024 potrebbero non essere trasferibili, ma rimarranno disponibili per la lettura su /old/.

    Okay why is eduroam not working this time (2.4 not either), I swear KU Leuven is trying to block me, fucking colonial university

    Pianificato Fissato Bloccato Spostato Uncategorized
    6 Post 2 Autori 3 Visualizzazioni
    Caricamento altri post
    • Da Vecchi a Nuovi
    • Da Nuovi a Vecchi
    • Più Voti
    Rispondi
    • Topic risposta
    Effettua l'accesso per rispondere
    Questa discussione è stata eliminata. Solo gli utenti con diritti di gestione possono vederla.
    • queerthoughts@tech.lgbtQ Questo utente è esterno a questo forum
      queerthoughts@tech.lgbt
      ultima modifica di

      Okay why is eduroam not working this time (2.4 not either), I swear KU Leuven is trying to block me, fucking colonial university

      lucent@antani.cyouL 1 Risposta Ultima Risposta Rispondi Cita 0
      • lucent@antani.cyouL Questo utente è esterno a questo forum
        lucent@antani.cyou @queerthoughts@tech.lgbt
        ultima modifica di lucent@antani.cyou

        @queerthoughts@tech.lgbt might https://cat.eduroam.org/ be helpful?
        it depends on Python and python-dbus to communicate with NetworkManager to autoconfigure the profile (if you happen to use that or a desktop environment that relies on it)

        also this troubleshooting from the Arch Wiki might be useful:
        https://wiki.archlinux.org/title/Network_configuration/Wireless#eduroam

        queerthoughts@tech.lgbtQ 1 Risposta Ultima Risposta Rispondi Cita 0
        • queerthoughts@tech.lgbtQ Questo utente è esterno a questo forum
          queerthoughts@tech.lgbt @lucent@antani.cyou
          ultima modifica di

          @lucent I already explained in a separate reply that didn't work. I doubt it's a technical issue, I am becoming convinced it's a block disguised as a technical issue.

          lucent@antani.cyouL 1 Risposta Ultima Risposta Rispondi Cita 0
          • lucent@antani.cyouL Questo utente è esterno a questo forum
            lucent@antani.cyou @queerthoughts@tech.lgbt
            ultima modifica di lucent@antani.cyou

            @queerthoughts@tech.lgbt yeah, I figured out your other post after firing the reply, I modified the message to include a link small troubleshooting paragraph on the Arch Wiki (which applies anyways to whatever distro uses the same network management stack) about OpenSSL woes, such as old TLS being disabled (as it's deprecated by default) on modern distros and permissions

            queerthoughts@tech.lgbtQ 1 Risposta Ultima Risposta Rispondi Cita 0
            • queerthoughts@tech.lgbtQ Questo utente è esterno a questo forum
              queerthoughts@tech.lgbt @lucent@antani.cyou
              ultima modifica di

              @lucent I don't really understand what's written on the Arch Wiki there. It's weird how it just suddely failed. I know it's not an issue with the network because no one else is having issues. It just suddenly stopped working without any changes made to the configuration on my end.

              lucent@antani.cyouL 1 Risposta Ultima Risposta Rispondi Cita 0
              • lucent@antani.cyouL Questo utente è esterno a questo forum
                lucent@antani.cyou @queerthoughts@tech.lgbt
                ultima modifica di

                @queerthoughts@tech.lgbt that little eduroam paragraph boils down to two possibilities:
                - the NetworkManager profile should be set to be readable&writable only for root (so
                chmod 600 profile, the location for profiles is usually /etc/NetworkManager/system-connections/) so NM/wpa-supplicant don't complain about secrets being "world readable"
                - the authentication fails due to a crypto suite mismatch, since OpenSSL 3 disabled all vulnerable protocols and you need to override that behaviour by setting on NetworkManager to authenticate using TLS 1.0 or TLS 1.1, explained further on this other troubleshooting page:
                https://wiki.archlinux.org/title/NetworkManager#WPA_Enterprise_connections_fail_to_authenticate_with_OpenSSL_%22unsupported_protocol%22_error

                1 Risposta Ultima Risposta Rispondi Cita 0
                • Primo post
                  Ultimo post