[Infra] Remove non-license information from third_party code (#122)

* [Infra] Remove non-license information from `third_party` code

* Review
This commit is contained in:
Nick Cooke authored and GitHub committed 2023-08-11 11:34:44 -04:00
1 parent 75202cc50f
commit 11758470de
2 files changed
+1 -39

No files matched your search

+1 -18
View File
@@ -14,21 +14,4 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Comment from <a href="http://iphonedevwiki.net/index.php/Crack_prevention">iPhone Dev Wiki
Crack Prevention</a>:
App Store binaries are signed by both their developer and Apple. This encrypts the binary so
that decryption keys are needed in order to make the binary readable. When iOS executes the
binary, the decryption keys are used to decrypt the binary into a readable state where it is
then loaded into memory and executed. iOS can tell the encryption status of a binary via the
cryptid structure member of LC_ENCRYPTION_INFO MachO load command. If cryptid is a non-zero
value then the binary is encrypted.
'Cracking' works by letting the kernel decrypt the binary then siphoning the decrypted data into
a new binary file, resigning, and repackaging. This will only work on jailbroken devices as
codesignature validation has been removed. Resigning takes place because while the codesignature
doesn't have to be valid thanks to the jailbreak, it does have to be in place unless you have
AppSync or similar to disable codesignature checks.
More information at <a href="http://landonf.org/2009/02/index.html">Landon Fuller's blog</a>
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-21
View File
@@ -18,27 +18,6 @@
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
// FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
// IN THE SOFTWARE.
//
// Comment from
// <a href="http://iphonedevwiki.net/index.php/Crack_prevention">iPhone Dev
// Wiki Crack Prevention</a>:
// App Store binaries are signed by both their developer and Apple. This
// encrypts the binary so that decryption keys are needed in order to make the
// binary readable. When iOS executes the binary, the decryption keys are used
// to decrypt the binary into a readable state where it is then loaded into
// memory and executed. iOS can tell the encryption status of a binary via the
// cryptid structure member of LC_ENCRYPTION_INFO MachO load command. If
// cryptid is a non-zero value then the binary is encrypted.
//
// 'Cracking' works by letting the kernel decrypt the binary then siphoning the
// decrypted data into a new binary file, resigning, and repackaging. This will
// only work on jailbroken devices as codesignature validation has been
// removed. Resigning takes place because while the codesignature doesn't have
// to be valid thanks to the jailbreak, it does have to be in place unless you
// have AppSync or similar to disable codesignature checks.
//
// More information at
// <a href="http://landonf.org/2009/02/index.html">Landon Fuller's blog</a>
#import <objc/objc.h>