From a7cc274e2fa2f4cd73ab3245ca2e38c7ffd47293 Mon Sep 17 00:00:00 2001 From: Zhiming Wang Date: Fri, 8 Jan 2016 12:29:32 -0800 Subject: Markdown source files: Revert YAML closing line from ... to --- GFM doesn't support closing with ..., and the rendered results are less than satisfactory. --- source/blog/2015-10-03-we-need-an-os-x-security-white-paper.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source/blog/2015-10-03-we-need-an-os-x-security-white-paper.md') diff --git a/source/blog/2015-10-03-we-need-an-os-x-security-white-paper.md b/source/blog/2015-10-03-we-need-an-os-x-security-white-paper.md index da0e87c9..f9060440 100644 --- a/source/blog/2015-10-03-we-need-an-os-x-security-white-paper.md +++ b/source/blog/2015-10-03-we-need-an-os-x-security-white-paper.md @@ -2,7 +2,7 @@ title: "We need an OS X security white paper" date: 2015-10-03T03:34:24-07:00 date_display: October 3, 2015 -... +--- Apple has been offering an excellent [iOS Security White Paper](https://www.apple.com/privacy/docs/iOS_Security_Guide.pdf) since at least 2012, and it's very informative. I highly encourage everyone to read it. It even explains some annoyances of iOS; for instance, [this week's Upgrade episode](http://www.relay.fm/upgrade/56) discussed, [in Gruber's words](https://daringfireball.net/linked/2015/10/01/upgrade-56), "the lousy, painstaking, and at times downright confusing experience of migrating to a new iOS device", and once you read the white paper you'll realize that many things just can't be migrated due to iOS's hardware security model — basically, certain classes of data are encrypted with crypto keys baked into the silicon (see the section "Hardware security features"). I'm not saying the migration experience should be this painful (I would love to see it fixed or improved), but at least there's an explanation.[^migration] -- cgit v1.2.1