News for hackers. Stuff that matters.
Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by ancarda on Saturday February 10, 2018 @06:59AM (#16346956)
Maybe this will sound silly and ridiculous, but I’m going to ask regardless.

Why doesn’t Apple just opensource iBoot? It could be under a very restrictive license; one that doesn’t allow the code to be redistributed or used by anyone in any project. The assets and tradmarks would also be protected. However, it would let people study the code — yes, some people will use that knowledge to make jailbreaks, but you know some will tell Apple.

Apple has opened projects like ResearchKit before.

I guess my hope is the iOS community would be able to take a more direct approach to contributing to platform security that we depend on. How much code has been smuggled out? Probably way more than this if it’s so easy.

Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by quantummkv on Saturday February 10, 2018 @07:39AM (#16347057)
> It could be under a very restrictive license; one that doesn’t allow the code to be redistributed or used by anyone in any project.

Open source means allowing the usage of code. Putting code under a license that does not allow any kind of usage is definitely not open source. And then why should Apple allow people to view their proprietary code when it has no intention to allow 3rd party usage? Chinese firms are already aping Apple's design. Everyone knows what they will do if they can see all the code.

Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by ancarda on Saturday February 10, 2018 @08:00AM (#16347120)
You’re confusing open source with free software. You definitely can have open source code that you can’t use (legally). Taking the code off GitHub and using it without Apple’s permission would be theft.

Open Source only means the code is available to be seen by the general public. Free Software means you have specific rights, like the right to view, modify, and distribute the code.

A possible license could be APSL: https://en.wikipedia.org/wiki/Apple_Public_Source_License

Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by ghaff on Saturday February 10, 2018 @08:08AM (#16347149)
Code that can be viewed but not used would not be in compliance of an OSI-approved license. I suppose you can call anything open source but OSI is the arbiter in the minds of most.
Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by atonse on Saturday February 10, 2018 @08:50AM (#16347267)
Sure. If you use an OSI license maybe. But I seriously doubt they can stop me from using the phrase open source if my code’s source is open.
Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by rileymat2 on Saturday February 10, 2018 @09:11AM (#16347329)
Obviously thay cannot stop you from misusing a term. I used to believe like you that the definition was more broad like you indicated. But the people who coined it had a narrower free software defintion in mind.

https://en.m.wikipedia.org/wiki/Open-source_software

Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by ryanlol on Saturday February 10, 2018 @10:30AM (#16347684)
The fight over the meaning of "Open source" was lost by OSI almost two decades ago.

Here's a 2002 version of their website essentially admitting as much: https://web.archive.org/web/20021001164015/http://www.openso...

>The OSI Certified mark is OSI's way of certifying that the license under which the software is distributed conforms to the OSD; the generic term "Open Source" cannot provide that assurance, but we still encourage use of the term "Open Source" to mean conformance to the OSD.

Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by ghaff on Saturday February 10, 2018 @09:12AM (#16347334)
As I wrote, no one would likely try to legally prevent you from calling any proprietary license open source if you want to. It just won’t actually be open source license in the minds of most if it doesn’t comply anwith the OSI guidelines
Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by tzs on Saturday February 10, 2018 @11:46AM (#16348060)
What about code that complies with the OSI guidelines, but does not use an OSI-approved license? Would you say that is open source?
Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by ghaff on Sunday February 11, 2018 @02:43PM (#16354340)
Not up to me to say what is open source. If something was compliant with OSI guidelines, it’s probably fair to call it open source. Also probably pretty ill-advised to have a one-off license no one else uses.
Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by w0de0 on Saturday February 10, 2018 @03:41PM (#16349460)
Succinctly: free as in speech, not as in beer.
Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by denzil_correa on Saturday February 10, 2018 @08:13AM (#16347164)
> It could be under a very restrictive license; one that doesn’t allow the code to be redistributed or used by anyone in any project

It’s extremely difficult to enforce this and hence, the decision.

Re:How a Low-Level Apple Employee Leaked Some of the iPhone'... by catach on Saturday February 10, 2018 @12:56PM (#16348511)
"Reference source" is how Microsoft has named their license that has those restrictions, and seems like a reasonable term.