2 ms·
Our chief leverage for pushing back on IE8 support is that out-of-the-box (which is pretty much how that have it configured) it doesn't support SSL settings tha
by dspillett 8y ago
Our chief leverage for pushing back on IE8 support is that out-of-the-box (which is pretty much how that have it configured) it doesn't support SSL settings that pass up-to-date recommendations.
Each year we are pen-tested by a third party, each year that client complains that the testers say the SSL setup is potentially insecure, every year we point out that we'd be more than happy to follow the recommendations (in fact we feel dirty not doing!) but it would lock out a number of their users if they were not given an alternate browser or otherwise reconfigured.
Fingers crossed this year is the last time: everyone there should have Chrome as an option, and everyone not depending on old apps (ActivX etc) should have IE11 not IE8. The login screens have had "are you sure you want to use this browser?" messages for IE8 users for a while, but some still use it, though only a few.
This is legacy application. Thankfully for our new applications the contracts state nothing older than IE11 will be supported, and that we only begrudgingly support that so users of IE may experience display issues or other minor usability problems from time-to-time.