6 ms·
Apple's own services make extensive use of plaintext HTTP. Even if they're only doing so in ways that are safe (due to other application layer encryption mechan
by bgentry 10y ago
Apple's own services make extensive use of plaintext HTTP. Even if they're only doing so in ways that are safe (due to other application layer encryption mechanisms like in iMessage) it's hypocritical for them to enforce a requirement on 3rd parties that they themselves cannot meet.
- azinman2 10y agoCan you give an example of this? I've been using charles proxy for various tasks a bunch on my iPhone, and so far it seems that all the calls to Apple that I've noticed are HTTPS.
- mahyarm 10y agoUse little snitch on your mac OS computer, you'll see all sorts of port 80 connections to things like mzstatic.com and so on.
- orbitur 10y agoOh. That's the platform they don't really care about.
- bgentry 10y agoHere's a partial list from my Little Snitch config on macOS Sierra: - com.apple.geod.xpc tried to establish a connection to gspe19.ls.apple.com on port 80 - App Store / softwareupdated uses port 80 to download updates from swcdn.apple.com - helpd uses port 80 to fetch help docs from the web - IMTransferAgent tried to establish a connection to ussjc.ce.apple-dns.net on port 80. This is used by Messages.app when picture messages are received. - iTunes uses port 80 all over the place to fetch content from the mzstatic CDN and others - nsurlsessiond uses port 80 to fetch from apple-dns.net, blobstore.apple.com, icloud-content.com, aaplimg.com - photolibraryd via com.apple.photomoments.xpc tried to establish a connection to gspe21.ls.apple.com on port 80 - Photos Agent tried to establish a connection to s3-w-a.us-west-2.amazonaws.com on port 80 - storeaccountd tried to establish a connection to sandbox.itunes-apple.com.akadns.net on port 80 - storedownloadd tried to establish a connection to osxapps.itunes.apple.com on port 80 - SpotlightNetHelper tried to establish a connection to wu-calculator.apple.com on port 80
- willstrafach 10y agoFYI, some of those are due to content being non-secret + already digitally signed and wanting to assure they can be served from the "Cache Server" within enterprises to help speeds.