3 ms·
I'm talking about user access. At least other browsers still allow it (but that's also prone to change at the whims of the developers), but in Safari for iOS th
by j1elo 6y ago
I'm talking about user access. At least other browsers still allow it (but that's also prone to change at the whims of the developers), but in Safari for iOS the page will fail silently and won't load, with absolutely no feedback as to why.
Having to install custom-made Root CAs into all and every client device doesn't sound to me like an ideal solution...
- shadowgovt 6y agoUnfortunately, since one is breaking the SSL trust model, that's probably the right solution. Not unlike having to explicitly enable "Developer mode" before a whole host of security-breaking options are available. Actually, that's one solution Apple could consider: if a user has enabled Developer Mode on a given iOS device, allow the trust model to be broken with an "Are you sure you know what you're doing?" button instead of a silent failure.
- ericbarrett 6y agoScammers: "You have to enable developer mode to see our new bank website because it's in development"
- Wowfunhappy 6y agoAt that point, isn’t it easier to send the user to chase.com.scammer.com? The goal isn’t to make a 100% foolproof system (because you can’t), and needing to flip a switch called “developer mode”, which preferably also displays a warning message, should make it clear something is wrong. ...I think this whole discussion is kind of missing the point though. Developers are not the only people who need to log in to routers.