News for hackers. Stuff that matters.
Re:MacOS 10.12.6 Source by eridius on Thursday September 14, 2017 @05:40PM (#15252748)
It's worth pointing out that this solution neuters Activation Lock, because the thief can now put the phone into DFU, then factory reset it, and then use the new private key to disable Activation Lock.

Compared to destroying the security model of iOS in general this is pretty tame, but it is still a non-trivial downside.

Re:MacOS 10.12.6 Source by geofft on Thursday September 14, 2017 @05:45PM (#15252782)
Huh, good point, I didn't know about Activation Lock.

I think this design still works if you only allow generating a signing keypair if Activation Lock is disabled? I think that still satisfies the requirements of GPLv3 sect. 6, although we're probably in territory extremely far from settled caselaw.

> “Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

The "method"/"procedure" is signing out of iCloud, doing a factory reset, and holding down the button. It doesn't interfere with the continued functioning of the modified object code, i.e., of the OS itself, just with any user data present before you started the procedure.

Re:MacOS 10.12.6 Source by baybal2 on Thursday September 14, 2017 @06:16PM (#15252943)
It didn't prevent Chinese refurbishers from working around it in the most simple way http://www.zdnet.com/article/iphone-lock-did-hackers-drive-a...