SUMMARY: WORKAROUND | 21E230 | X86_64 | cryptexctl | 3ef28a3 | EXC_BAD_ACCESS #25
Comments
|
It has been found that there are other command line args that will cause a Crash: PoC: lldb -- cryptexctl ${CRYPTEXCTL_PERSONALIZE_FLAGS} personalize --replace com.example.cryptex.cxbd |
|
The arg --persist also causes a Crash |
xsscx
added a commit
that referenced
this issue
May 5, 2022
On arm64e, building the default Apple example-cryptex fails. Conftest is the issue with invalid code signature, which makes the dropbear build useless for SRD. Use the pre-built DMG's using arm64e. Also, cryptex personalizations from X86_64 result with a Crash, see Issues #26 & #25. Creating a workaround now() for a fix. Use pre-built DMG's and install from arm64e only since X86_64 doesn't work ffor cryptexctl or CryptexManager due to AMFIResearch Complaints.
xsscx
added a commit
that referenced
this issue
May 5, 2022
… is the issue with invalid code signature On arm64e, building the default Apple example-cryptex fails. Conftest is the issue with invalid code signature, which makes the dropbear build useless for SRD. Use the pre-built DMG's using arm64e. Also, cryptex personalizations from X86_64 result with a Crash, see Issues #26 & #25. Creating a workaround now() for a fix. Use pre-built DMG's and install from arm64e only since X86_64 doesn't work ffor cryptexctl or CryptexManager due to AMFIResearch Complaints.
xsscx
added a commit
that referenced
this issue
May 5, 2022
1. Building the default Apple example-cryptex fails 2. Posted a quick workaround for dropbear and its configure.ac. 3. Use the pre-built DMG's using arm64e. 4. Cryptex personalizations from X86_64 result with a Crashwhen using cryptexctl, see Issues #26 & #25. Use arm64e, X86_64 is a special snowflake. 5. This Repo will become Code Only with basic readme.rtfm and all Write-ups, Comments moved to https://srd.cx to lower the Noise for Cloning. Hopefully the mothership will catchup soon with fixes this will make this exercise m00t. X86_64 Bugs du Jour for cryptexctl ------------ - macOS 12.3.1 (21E230) X86_64 Note: cryptexctl == EXC_BAD_ACCESS (SIGSEGV) - [CryptexManager](https://github.com/pinauten/CryptexManager) on X86_64 has AMFI complaints and isn't reliable - cryptexctl X86_64 Error: manifest constraint violated: BORD: 13 - com.apple.cryptex == firmware execution failed: 13: Permission denied - MobileStorageMounter Failed to install cryptex (<private>): 13 (Permission denied)
xsscx
added a commit
that referenced
this issue
May 5, 2022
1. Building the default Apple example-cryptex fails 2. Posted a quick workaround for dropbear and its configure.ac. 3. Use the pre-built DMG's using arm64e. 4. Cryptex personalizations from X86_64 result with a Crashwhen using cryptexctl, see Issues #26 & #25. Use arm64e, X86_64 is a special snowflake. 5. This Repo will become Code Only with basic readme.rtfm and all Write-ups, Comments moved to https://srd.cx to lower the Noise for Cloning. Hopefully the mothership will catchup soon with fixes this will make this exercise m00t. X86_64 Bugs du Jour for cryptexctl ------------ - macOS 12.3.1 (21E230) X86_64 Note: cryptexctl == EXC_BAD_ACCESS (SIGSEGV) - [CryptexManager](https://github.com/pinauten/CryptexManager) on X86_64 has AMFI complaints and isn't reliable - cryptexctl X86_64 Error: manifest constraint violated: BORD: 13 - com.apple.cryptex == firmware execution failed: 13: Permission denied - MobileStorageMounter Failed to install cryptex (<private>): 13 (Permission denied)
|
This is also helpful for debugging cryptex issues: now go kill -HUP logd and check Console Log |
|
Re-opening as Feedback had questions...... |
|
This is a dead horse.. use CryptexManager |
xsscx
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY: 21E230 | X86_64 | cryptexctl | EXC_BAD_ACCESS
It has been found that macOS 12.3 (21E230) X86_64 and the most recent update to cryptexctl from URL:
https://github.com/apple/security-research-device/tree/main/bin
from commit
https://github.com/apple/security-research-device/commit/3ef28a37a70d5b288a2da1a3e073975c9bae4a35
Results with EXC_BAD_ACCESS when applying the command line arg "--variant=research" from the X86_64 Platform.
Workaround
Use Cryptex Manager
Reproduction
lldb -- cryptexctl install -p -l --variant=research --persist com.example.cryptex.cxbd.signed
Crash Reproduction with lldb
Reported
The text was updated successfully, but these errors were encountered: