3 ms·
In addition, many less than 5-year-old Android phones (pre-Gingerbread) don't support SHA-2. TLS 1.2 (RFC 5246) added support for SHA-2 in August 2008. Androi
by leereeves 11y ago
In addition, many less than 5-year-old Android phones (pre-Gingerbread) don't support SHA-2.
TLS 1.2 (RFC 5246) added support for SHA-2 in August 2008.
Android Froyo was apparently released in May 2010 without support for TLS 1.2 or SHA-2.
Why the delay?
Edit:
Just found this:
> Android has the technical capability of handling SHA-256 certificates right from version 1.0. In practice, some users may encounter issues with validating certificates that use cross certificates (these help chain certificates to alternate roots). 1.6 improved this issue for some users, with the issue being resolved as of version 2.2.
https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility https://support.globalsign.com/customer/portal/articles/1499...
which helps explain the situation with SHA-2, but not the delay in implementing TLS 1.2.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- kuschku 11y agoAlso, pre-Gingerbread was abandoned by everyone nowadays. Even Gingerbread has been abandoned in the last 18 months.
- wiml 11y agoUntil the last few years, anything newer than TLS1.0+SHA1 was considered crypto-wonk neckbeard territory. Sure, it was standardized, but asking a vendor to implement it would get you an eyeroll and a "sure, we'll get right on that, uh huh".