4 ms·
When I was on Android, I never saw any reason not to use the open source Google Authenticator version (still available via F-Droid, or relatively easy to compil
by ocdtrekkie 9y ago
When I was on Android, I never saw any reason not to use the open source Google Authenticator version (still available via F-Droid, or relatively easy to compile yourself). It's simple, it's fast, it's open, and it works.
- StavrosK 9y agoHmm, that's a good alternative. Do you have a link to the F-Droid version? I can't seem to find it there. EDIT: It looks like it was taken down because it uses an MD5 signature for the APK.
- iou 9y agoIf that is the reasoning that would be very hipocritical of Google. I know for a fact they use MD5withRSA for some of their own apks including YouTube - https://www.josephkirwin.com/2016/05/05/humbled-by-md5/ https://www.josephkirwin.com/2016/05/05/humbled-by-md5/ * at least they did at the time that was written.
- klyubin 9y agoMD5 APK signatures are still supported by Android and are accepted by Google Play when you upload an APK there. See https://forum.f-droid.org/t/many-old-unmaintained-apps-have-been-archived/670/18 https://forum.f-droid.org/t/many-old-unmaintained-apps-have-... for more discussion about this in the context of F-Droid. I believe F-Droid was (is) using Oracle jarsigner to verify APK signatures and this is what causing F-Droid to reject APKs with MD5 signatures.