Skip to Content.

geteduroam - Re: iOS bug resolved in 15.2, Windows client update

Subject: An open discussion list for topics related to the geteduroam service

List archive


Re: iOS bug resolved in 15.2, Windows client update


Chronological Thread 
  • From: Paul Dekkers <paul.dekkers AT surf.nl>
  • To: Ralf Paffrath <paffrath AT dfn.de>
  • Cc: "geteduroam AT lists.geant.org" <geteduroam AT lists.geant.org>
  • Subject: Re: iOS bug resolved in 15.2, Windows client update
  • Date: Fri, 12 Nov 2021 09:44:11 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=surf.nl; dmarc=pass action=none header.from=surf.nl; dkim=pass header.d=surf.nl; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=AUOJpEAWvDgkL8DDgoUEf4odQ8hr3ErzCCYkDgdIia4=; b=Zex5wd/fYD6VCxgUFQEPBhrhKy6tKcoZxIT4j5asoZzuGlnc61HGkkRxI96ccABNBKijERAdoaQ6LZMt0mwEgUZ+T9EWYmetOt6sAM+V0ZcEuWqKAx+5ST29geLg4hsMfc9HWR6zQIPMMosgL8iKvIiy1HLkMPEzLcfcftJJ0H6SmLJOqf0mltOe372fNJ8aRb964GmdNUwOKTfzQnUHMCVNKJIG3m+YYHraLGMc8whDART8yk/VYMB6MtrCOBa7P2FQzFt0G5R7hdT3eoQD32sJn53XeRE+nlLWe3q6alYs/pEN8kc+VnYYDmcZSUQtumn3030XkUpfmjb1Oc6tAg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TSJQ4RzqqjjL/arogxsyV4HBJgj6VRq6lxwf1F+TW7jCdyBDEB851O197WkcPVOwfzZMhMk5QrSC4g4j0Q5SM+8mij1fK6IiPJLWWAWI7qsNVAByKvDxbC5gqrEKXeWY2IufJ4xXD+m1Jo2Z8uGC0UlGC3i1qzQN10ZzDImUQHcxFJp/03rwQkI907c4UvnpvjQ4NXxJIsjXcwz54KnC9CXR5cTnQb6D9vE1Nud8fBPavW/yqqLwuX5SliEiTV4kKaIJqbdNZnQK6MwQGSk2muj7Wjjk7arNjEg5gFr4E+E2NjX0X9Oyuzw/CveMrmBya7oaBJwQbcYokIXp13JuqA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=surf.nl;

Hi,

Ah, maybe I wasn't clear about the API; it doesn't affect the way the Apps work on the profile side, it uses a different Android API to install the WiFi networks. This was non-existant in Android 10, it caused a crash in the first release of Android 11, but it works well on A11+ now, but we have some remaining issues that we're still working on.

So it will continue to use .eap-config files, which is an answer to your second question also: all current Apps read .eap-config files, also iOS, and not .mobileconfig. (In fact I think that wouldn't even be possible.) We may have a different strategy on a macOS version, but that's for later.

Hope this clarifies things,

Regards,
Paul


On 12/11/2021 09:03, Ralf Paffrath wrote:
Hi Paul,

is there any documentation for the new API?

Will the new GETEDUROAM App read in the .mobileconfig on iOS?

Best regards,
Ralf

On 11. Nov 2021, at 12:44, Paul Dekkers (via geteduroam Mailing List)
<geteduroam AT lists.geant.org> wrote:

Hi geteduroam-list,

We wrote earlier about the bug in iOS 15 that made it impossible to install
certificates (both client and CA) from the iOS geteduroam App. Fortunately,
this bug is resolved in the upcoming iOS 15.2 release; we have confirmation
from Apple and verified with the past 2 beta builds. Now hope iOS 15.2 is
released soon ;-)

Little news on the Android App; we continue to work on a new version, and now
have one that uses a different API compared to the current published beta:
it's behavior is more natural for the users, but there are a few issues still
to resolve before we could release it. (If it doesn't work out, we could
still use the version as published in beta now: it is stable.)

I'll also take the opportunity to also highlight a new release of the
geteduroam Windows client; there was a bug where we didn't use the
(anonymous) outer identity for EAP-PEAP accounts (just EAP-TTLS). This is
fixed in version 3.2.6, via
https://github.com/geteduroam/windows-app/releases or the downloads on
https://geteduroam.app/ (Thanks to Guy Halse for finding it and creating an
issue for this.)

Regards,
Paul



--
Security, Trust & Identity Services

E-Mail: eduroam AT dfn.de, eduvpn AT dfn.de, easyroam4edu AT dfn.de | Fon: +49 30
884299-9121/9120 | Fax: 030 88 42 99 370
__________________________________________________________________________________

DFN - Deutsches Forschungsnetz | German National Research and Education
Network
Verein zur Förderung eines Deutschen Forschungsnetzes e.V.
Alexanderplatz 1 | 10178 Berlin
https://www.dfn.de

Vorstand: Prof. Dr. Odej Kao (Vorsitzender) | Dr. Rainer Bockholt | Christian
Zens
Geschäftsführung: Dr. Christian Grimm | Jochem Pattloch
VR AG Charlottenburg 7729NZ | USt.-ID. DE 136623822




Archive powered by MHonArc 2.6.19.

Top of Page