cat-users AT lists.geant.org
Subject: The mailing list for users of the eduroam Configuration Assistant Tool (CAT)
List archive
- From: <nicolas.velazquez AT uam.es>
- To: "'Stefan Winter'" <stefan.winter AT restena.lu>, <cat-users AT lists.geant.org>
- Subject: RE: [[cat-users]] Android versions. CN vs entire certificate
- Date: Tue, 4 May 2021 17:42:17 +0200
Hi Stefan,
Thanks for your answer.
We have been using eduroamCAT for years. And this certificate change is not the first we do. All previous certificate changes, at least on Android, were made with eduroamCAT.
The question arises because our colleagues who directly serve end users, told us that they have problems with older versions of Android now. Some older versions of Android show problems and need workarounds by hand to work well, although they are using eduroamCAT profiles as the first and main method for updating profiles for all platforms.
So, I seemed to remember that older Android versions did not support any other check of secure connection than having the certificate of the machine itself. And I don't know why, I seemed to remember that the feature of using ONLY the CN, and not needing the complete certificate, was a very new option in Android.
But, as you said, I am wrong.
Most likely, Android, its different versions, and the different flavors that each manufacturer make for each model, are the true cause of these problems.
Thanks and regards,
Nicolás Velázquez Campoy Unidad Técnica de Comunicaciones
De: Stefan Winter <stefan.winter AT restena.lu>
Hello,
you are asking an Android archaeology question. I can only give you a partial answer.
We started supporting Android with eduroam CAT only by the time Android 4.3 was released. The reason is that only that version's API level allowed to configure the tuple of (CA; expected server name) and thus was the first version that could do EAP server validation "properly".
I don't know how things were before that. We only started caring about Android with 4.3, and the eduroamCAT app is not even installable on older versions.
But then, Android 4.3 is way older than 4 years (something like 2013, 9 years ago!).
Maybe this other way you are talking about lived side-by-side for a while, and has been finally obsoleted an unknown time ago. But then you were not using anything CAT offers to achieve onboarding with that other way of certificate pinning?
IMHO, the more interesting question is: why do you ask? CA+server name is much more flexible and "proper PKI" compared to pinning a single certificate. Do you need to support Android versions <4.3? If you don't, and care only about 4.3+, the advice would be to instruct users to use the "eduroamCAT" Android app and use that for configuring eduroam. The app will then install the root CA and expected server name, and things should work.
Greetings,
Stefan Winter
Am 04.05.21 um 12:14 schrieb nicolas.velazquez AT uam.es:
|
- [[cat-users]] Android versions. CN vs entire certificate, nicolas.velazquez, 05/04/2021
- Re: [[cat-users]] Android versions. CN vs entire certificate, Stefan Winter, 05/04/2021
- RE: [[cat-users]] Android versions. CN vs entire certificate, nicolas.velazquez, 05/04/2021
- Re: [[cat-users]] Android versions. CN vs entire certificate, Stefan Winter, 05/04/2021
Archive powered by MHonArc 2.6.19.