From 496445d9e00609c075b69501cd4a39d246e8e1fd Mon Sep 17 00:00:00 2001 From: Nick Cooke <36927374+ncooke3@users.noreply.github.com> Date: Thu, 10 Aug 2023 18:02:20 -0400 Subject: [PATCH] [Infra] Remove non-license information from `third_party` code --- third_party/IsAppEncrypted/IsAppEncrypted.m | 21 ------------------- third_party/IsAppEncrypted/LICENSE | 19 +---------------- .../IsAppEncrypted/Public/IsAppEncrypted.h | 21 ------------------- 3 files changed, 1 insertion(+), 60 deletions(-) diff --git a/third_party/IsAppEncrypted/IsAppEncrypted.m b/third_party/IsAppEncrypted/IsAppEncrypted.m index e2f7275d..50033eb8 100644 --- a/third_party/IsAppEncrypted/IsAppEncrypted.m +++ b/third_party/IsAppEncrypted/IsAppEncrypted.m @@ -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 -// iPhone Dev -// Wiki Crack Prevention: -// 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 -// Landon Fuller's blog #import "third_party/IsAppEncrypted/Public/IsAppEncrypted.h" diff --git a/third_party/IsAppEncrypted/LICENSE b/third_party/IsAppEncrypted/LICENSE index 6328f101..6a2d8d15 100644 --- a/third_party/IsAppEncrypted/LICENSE +++ b/third_party/IsAppEncrypted/LICENSE @@ -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 iPhone Dev Wiki -Crack Prevention: -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 Landon Fuller's blog +FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \ No newline at end of file diff --git a/third_party/IsAppEncrypted/Public/IsAppEncrypted.h b/third_party/IsAppEncrypted/Public/IsAppEncrypted.h index b26bae20..1a4305aa 100644 --- a/third_party/IsAppEncrypted/Public/IsAppEncrypted.h +++ b/third_party/IsAppEncrypted/Public/IsAppEncrypted.h @@ -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 -// iPhone Dev -// Wiki Crack Prevention: -// 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 -// Landon Fuller's blog #import