Simple shell script to quickly and easily force Outlook 2016 for Mac out of sandbox.
More info here.
See the script in action here.
|echo "Patching old binary... "|
|cd "/Applications/Microsoft Outlook.app/Contents/MacOS/"|
|hexdump -ve '1/1 "%.2X"' "Microsoft Outlook" | \|
|sed "s/73616E64626F783C2F6B65793E0A093C747275652F3E/73616E64626F783C2F6B65793E0A093C66616C732F3E/g" | \|
|xxd -r -p > "Microsoft Outlook.patched"|
|# hexdump -> creates hex dump of the binary executable|
|# sed -> replaces 'sandbox</key><true/>' with 'sandbox</key><fals/>' in the hex dump|
|# xxd -> rebuilds the edited hex dump back into executable binary|
|chmod `stat -f %A "Microsoft Outlook"` "Microsoft Outlook.patched"|
|# copies permissions from the original binary to the patched binary|
|mv "Microsoft Outlook" ~/Desktop/Microsoft\ Outlook.bak|
|# backs up the original executable|
|mv "Microsoft Outlook.patched" "Microsoft Outlook"|
|echo "Proceed with signing the new binary:"|
|echo "sudo codesign -f -s \"CERIFICATE NAME HERE\" /Applications/Microsoft\ Outlook.app/"|
|# After the binary is successfully patched, sign it with the above command|
|echo "Then verify that signing finished properly:"|
|echo "sudo codesign -v /Applications/Microsoft\ Outlook.app/"|
|# Verify the signature. If everything went smoothly, you won't get any output from the above command|
|# More info: https://ツ.sh/move-profile-folder-location-in-outlook-2016-for-mac/|
|# @jansoucek 2015|
I have followed everything through by your HexFriend change status to "fals" way. After I have successfully created Alias, whenever I try to open the outlook, it shows the following error::
An error occurred while launching
The “Outlook Temp” folder could not be found. It is likely that you have a file with the same name or an alias that doesn’t point to a folder
Can you teach me what and how I can fix this?
My files for Outlook are located in the dmg file that connected as device. Maybe problem with that?
Hi Jan and everybody,
@jankais3r, If I recall correctly, it was signing the app. The resulting binary wouldn't run as if it had become corrupt. I had detailed notes and screenshots but they were accidentally deleted when I was trying to learn how to delete things in AppleScript :/
I found the problem, but I haven't found a solution yet. The moment we sign Outlook binary with our own certificate it stops working. Even if no other change was done to the executable. If there is just a problem with the signing process, we might be able to make it work. But if Microsoft decided to start checking the certificate the app was signed with, then there is nothing we can do.
If I just modify the binary, I get the following crash:
If I make my changes and re-sign the app, I get a different one:
I also tried to disable Gatekeeper (
@BourneLoser , @jankais3r,