Codesigning for SIP enabled!

MrLyannMusic · Mar 22, 2024

Mauwurf said: ↑

Go to Sister Site in https://audioz.download/software/24...g-cubase-pro-13-v13020-u2b-macos.html#comment. There is a exact describtion how to solve the License Problem.

take those 2 License Files and copy it into applicationsupport/Steinberg/Activation Manger
Replace Existing or when this folder not there, then create one. (Activation Manger)

Put these two files in and Codesign afterwards.

1. Follow smc92 instructions and copy the files that he uploaded manually to the folder ( create folder incase is not there). https://mega.nz/file/xK9xUZKZ#-E7HnkPvJ54MdNbj2X9BUjAtKKmmtkoBtClTcZC-f0g

Install Cubase
if you patched cubase and you getting no valid license error
you need to copy manual these file to :
/Libray/Application Support/Steinberg/Activation Manager folder
if this folder not exist in this path you need to create a one with same name.

2. Open terminal and use this command:

xattr -cr

3. Drag to the terminal after the command the Steinberg Licence Engine file that is in the application support/Steinberg/Activation manager (where you copied the files that smc92 uploaded).

4. dont forget that it should be a space after the commando and before the path to the file it should be something like this:

xattr -cr /Library/Application\ Support/Steinberg/Activation\ Manager/Steinberg\ License\ Engine.app

(i don't know if its exactly like this, this is what i did in my mac)

Press Enter.

after that is done, open cubase again and it should open just fine.
Click to expand...

Thank you for your help but it didn't work...

luongvo · Mar 23, 2024

I don't understand how to write this command line correctly:
codesign --force --deep --sign "Apple Development: YOURAPPLEID (YOURTEAMID)"

For example my apple id is [email protected] then my command line is?:
codesign --force --deep --sign "Apple Development: [email protected]"

I'm sorry, I've tried every change but still don't have a correct command line for my certificates

jimklk · Apr 3, 2024

The whole installation and signing process seems ok but my version went from Pro to Artist on the 1st restart. Any info?

jimklk · Apr 4, 2024

luongvo said: ↑

I don't understand how to write this command line correctly:
codesign --force --deep --sign "Apple Development: YOURAPPLEID (YOURTEAMID)"

For example my apple id is [email protected] then my command line is?:
codesign --force --deep --sign "Apple Development: [email protected]"

I'm sorry, I've tried every change but still don't have a correct command line for my certificates
Click to expand...

check the utilities folder on the application folder you'll see a keychain access app. open that click login and check the list for your apple developer certificate e.g. Apple Development: [email protected] (3MDBIOD92). the command in this case is

codesign --force --deep --sign "Apple Development: [email protected] (3MDBIOD92)"

Lucas Schauer · Apr 10, 2024

Hey guys i also got the
unable to build chain to self-signed root for signer "Apple Development: xxx" error.

What could be the problem has anyone fixed this ?

Mauwurf · May 15, 2024

Placeholder..

I dont know how to delete this thread.

Last edited: May 15, 2024

Lucas Schauer · Apr 10, 2024

Mauwurf said: ↑

More information Required. Otherwise i can't help.

Also: I never faced such Problems.

Maybe something like this:

This error usually occurs if a certificate has not been loaded properly into the certificate store or if there are problems with the certificate chain. Here are some possible solutions:
Check the certificate: make sure that the certificate you want to use (in this case, the certificate named "Apple Development: xxx") is correct and has not expired. You can check this in the keychain or in the certificate settings of your developer tool.
Check the certificate chain: Check the certificate chain to ensure that all intermediate certificates are properly installed. Sometimes a self-signed certificate requires additional intermediate certificates to form a chain of trust.
Check trust policies: Ensure that the certificate complies with the trust policies set by the development platform (in this case Apple). This may include the use of a specific encryption algorithm or compliance with specific key lengths.
Reissuing the certificate: If all other options fail, you can attempt to reissue the certificate and ensure that it is properly installed in the certificate store.
Translated with www.DeepL.com/Translator (free version)
Click to expand...

Thank you for your help ! The problem was i had it on trust always now i set it on Default System preferences and it worked but the problem is even with the licenses fold it shows no license found. Should i put the K'd cubase file in there also ? because when i do that and sign it again it just crashes with this error message. I don't know what to do anymore

Last edited: Apr 10, 2024

Diego Xavier Sousa · Apr 11, 2024

Thanks so much for this guide, I got it working with SIP enabled! Mac Mini M2 Pro - Sonoma 14.4.1

I failed for the V.R version but succeeded with the U2B release (the main difference seems to be that the U2B release has a pre-patched binary?)
I did all the steps listed in this thread with the U2B version and rebooted, including replacing the license files posted by @Mauwurf here, after reboot I was asked to allow a system extension by "Apple", but still nothing = Invalid license.
But as soon as I replaced the patched binary that came with the U2B released and codesigned it with my Apple developer ID + quarantine and
"chmod +x" it started working fine!

Mauwurf · May 15, 2024

Placeholder

Last edited: May 15, 2024

jimklk · Apr 12, 2024

Mauwurf said: ↑

Exactly.

Good to hear that it is working.

Maybe someone of you can help me to improve and correct my first Post.

So that everybody can understand immediately from the beginning without asking so much Questions afterwards.

Who wants to?
Click to expand...

I mean I've done the whole process like 10 times(without exaggerating at all) and everything works perfectly until the first restart when Cubase loads up as Artist version and not Pro, other than that I can help you make a more concise guide.

Mauwurf · Aug 31, 2024

Bumb

rahul4848 · Sep 26, 2024 at 9:32 AM

Mauwurf said: ↑

Now its on Again!

### Guide to Creating a Local Apple Developer ID with Xcode
To create a local Apple Developer ID, you need an Apple Developer account and Xcode, Apple's integrated development environment. This guide will walk you through the steps to create and configure your local Apple Developer ID:
#### Prerequisites:
1. **Apple Developer Account**: You don't need an Apple Developer account. If you don't have one.

2. **Xcode**: Ensure you have Xcode installed. You can download Xcode from the Mac App Store.
#### Step-by-Step Guide:
1. **Open Xcode**:
- Launch Xcode on your Mac.
2. **Open Xcode Preferences**:
- Go to the `Xcode` menu and select `Preferences...` (or press `Cmd + ,`).
3. **Add Account**:
- In the Preferences window, click on the `Accounts` tab.
- Click the `+` button in the lower-left corner and select `Apple ID...` from the dropdown menu.
4. **Add Apple ID**:
- Enter your Apple ID and password, then click `Next`.
- If you have two-factor authentication enabled, enter the verification code sent to your device.
5. **Link Apple Developer Account**:
- After adding your Apple ID, Xcode will automatically recognize and link your Apple Developer account.
6. **Create a Signing Certificate**:
- Click on your Apple Developer account in the list on the left.
- Click `Manage Certificates...`.
- Click the `+` button in the lower-left corner and select `Apple Development`.
- Xcode will automatically create a new development certificate and add it to your keychain.
7. **Retrieve the Apple Developer ID**:
- Open `Keychain Access` on your Mac (`Applications > Utilities > Keychain Access`).
- Look for your newly created `Apple Development` certificate. It should look something like: `Apple Development: Your Name (Your Apple ID)`.
- Note down the full name of the certificate, including the name and ID in parentheses.
8. **Use the Apple Developer ID in Your Script**:
- Copy the full name of the certificate and paste it into your script:
```bash
DEVELOPER_ID="Apple Development: John Doe (ABCDEFGHIJ)"
```
#### Example:
Assuming your name is `John Doe` and your Apple ID is `[email protected]`, your Apple Developer ID might look like this:
```bash
DEVELOPER_ID="Apple Development: John Doe (ABCDEFGHIJ)"
```
#### Conclusion:
You have now successfully created and configured a local Apple Developer ID. You can use this ID to sign your applications and plugins with Xcode. Make sure to regularly check and renew your certificates to ensure your signed applications remain trustworthy.
Good luck with your development and signing projects!

Next Steps:

Using 4 Commands in a row. these are Examples..... you can do that with every File. *.app | *.vst | *.component | *.clap | *.VST3

1. sudo chown -R [yourusernameofyourfuckingComputer] /Library/Audio/Plug-Ins/VST/Spire-1.5.vst
2. codesign --force --deep --sign "Apple Development: John Doe (ABCDEFGHIJ)" /Applications/Rectangle\ Pro.app
3. sudo xattr -r -d com.apple.quarantine /Applications/Rectangle\ Pro.app
4. sudo xattr -cr /Applications/Rectangle\ Pro.app

Sometimes you need all of them. Sometimes you need only Codesign. Most of all you need the ownership Command!

Here is an explanation for each command to help less experienced computer users understand what each step does:

### Commands and Their Explanations
1. **Signing the application with your own certificate**
```bash
codesign --force --deep --sign "Apple Development: John Doe (ABCDEFGHIJ)" /Applications/Rectangle\ Pro.app
```
- `codesign`: This is the command-line tool for code signing on macOS.
- `--force`: Forces the overwriting of any existing signature.
- `--deep`: Signs not only the main application but also all embedded components and frameworks.
- `--sign "Apple Development: John Doe (ABCDEFGHIJ)"`: Specifies the certificate to be used for signing. Replace "John Doe" and "ABCDEFGHIJ" with your own certificate information.
- `/Applications/Rectangle\ Pro.app`: The path to the application you want to sign. The backslash (`\`) before the space ensures the space is correctly interpreted.

2. **Removing the quarantine attribute from the application**
```bash
sudo xattr -r -d com.apple.quarantine /Applications/Rectangle\ Pro.app
```
- `sudo`: Runs the command with superuser (administrator) privileges, which is often necessary to modify system files.
- `xattr`: This is the command-line tool for managing extended attributes of files.
- `-r`: Recursively, meaning it will also process all subdirectories and files within the specified directory.
- `-d com.apple.quarantine`: Deletes the quarantine attribute, which macOS applies to files downloaded from the internet. This attribute can prevent the application from running.
- `/Applications/Rectangle\ Pro.app`: The path to the application from which you want to remove the quarantine attribute.
3. **Removing all extended attributes from the application**
```bash
sudo xattr -cr /Applications/Rectangle\ Pro.app
```
- `sudo`: Runs the command with superuser privileges.
- `xattr`: The command-line tool for managing extended attributes of files.
- `-c`: Clears (deletes) all extended attributes of the specified file or directory.
- `-r`: Recursively processes all subdirectories and files within the specified directory.
- `/Applications/Rectangle\ Pro.app`: The path to the application from which you want to clear all extended attributes.
4. **Changing the owner of a directory**
```bash
sudo chown -R username /Library/Audio/Plug-Ins/VST/Spire-1.5.vst
```
- `sudo`: Runs the command with superuser privileges.
- `chown`: This is the command-line tool for changing the ownership of a file or directory.
- `-R`: Recursively processes all subdirectories and files within the specified directory.
- `spee`: The new owner of the file or directory. Replace this with your own username.
- `/Library/Audio/Plug-Ins/VST/Spire-1.5.vst`: The path to the directory or file whose ownership you want to change.

Sometimes: you get something like this:

The error message `resource fork, Finder information, or similar detritus not allowed` typically occurs when there are extended attributes or resource forks attached to the file that `codesign` does not allow. You can resolve this issue by removing the extended attributes from the file before signing it.
Here’s how you can do it step-by-step:
1. **Remove Extended Attributes**:
Use the `xattr` command to clear all extended attributes from the file. This should be done before attempting to sign the file.
```bash
sudo xattr -cr /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13
```
2. **Sign the Application**:
After clearing the extended attributes, you can proceed with signing the application.
```bash
codesign --force --deep --sign "Apple Development: "Apple Development: John Doe (ABCDEFGHIJ)" /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13
```
### Explanation of Each Command
1. **Removing Extended Attributes**:
```bash
sudo xattr -cr /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13
```
- `sudo`: Runs the command with superuser privileges.
- `xattr`: The command-line tool for managing extended attributes of files.
- `-c`: Clears (deletes) all extended attributes of the specified file or directory.
- `-r`: Recursively processes all subdirectories and files within the specified directory.
- `/Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13`: The path to the file from which you want to clear all extended attributes.
2. **Signing the Application**:
```bash
codesign --force --deep --sign "Apple Development: "Apple Development: John Doe (ABCDEFGHIJ)" /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13
```
- `codesign`: This is the command-line tool for code signing on macOS.
- `--force`: Forces the overwriting of any existing signature.
- `--deep`: Signs not only the main application but also all embedded components and frameworks.
- `--sign "Apple Development: "Apple Development: John Doe (ABCDEFGHIJ)"`: Specifies the certificate to be used for signing. Replace this with your own certificate information.
- `/Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13`: The path to the application you want to sign.
### Complete Workflow
Here’s the complete workflow to avoid the error and successfully sign your application:
```bash
# Step 1: Remove extended attributes
sudo xattr -cr /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13
# Step 2: Sign the application
codesign --force --deep --sign "Apple Development: "Apple Development: John Doe (ABCDEFGHIJ)" /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13
```
By following these steps, you should be able to sign your application without encountering the `resource fork, Finder information, or similar detritus not allowed` error.

### Summary
These commands sign an application with your own certificate, remove the quarantine attribute and all other extended attributes that may prevent the application from running correctly, and change the owner of a specific directory. These steps are often necessary to ensure that applications and plugins run smoothly on macOS, especially if they were downloaded from the internet or obtained from third-party sources.
Click to expand...

Hey! So i got it all right until the 4 commands. I have created a Developer id. But cant seem to get Cubase to get going.

Please note: I disabled SIP. Installed Cubase 13(it's working). Enabled SIP. Now Cubase is not working.

Now, in an enabled state of SIP, i have created this developer ID and am trying to get Cubase to work.

the following are the codes i entered into the terminal one after another:

1. sudo xattr -cr /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13

2. codesign --force --deep --sign "Apple Development: "Apple Development: [email protected] (xxxxxxxxxx)" /Applications/Cubase\ 13.app/Contents/MacOS/Cubase\ 13

After this i get : dquote>

This does nothing nor does Cubase work.

I dont know what that means. Previously i even got a request to switch to ZCH or something like that. Didnt know what that meant either. Can someone guide me please on how to get Cubase to work with SIP enabled??

Emma Evi · Sep 26, 2024 at 10:15 AM

TL;DR:
1.) open terminal
2.) paste: sudo codesign --force --sign - (make surte to have a space after the last -)
3.) drag the app to be code signed to the terminal, that will add teh path automatically
4.) hit enter

Similar Threads - Codesigning enabled	Forum	Date
Codesigning doesn't work anymore	Mac / Hackintosh	Feb 14, 2024
Cubase 13 (OSX) SIP enabled	Cubase / Nuendo	Feb 10, 2024
NI VSTs crashing when Windows graphics scaling enabled?	Samplers, Synthesizers	Aug 24, 2023
KVR MPE Month: Enter to win over $3500 worth of MPE enabled products	Giveaways	Mar 5, 2022
Latest waves r2r only works when network in enabled?	Software	May 5, 2017

Codesigning for SIP enabled!

MrLyannMusic Audiosexual

luongvo Newbie

jimklk Noisemaker

jimklk Noisemaker

Lucas Schauer Member

Mauwurf Member

Lucas Schauer Member

Attached Files:

Bildschirmfoto 2024-04-10 um 15.00.08.png

Diego Xavier Sousa Newbie

Mauwurf Member

jimklk Noisemaker

Mauwurf Member

rahul4848 Newbie

Emma Evi Ultrasonic

PROFESSIONAL AUDIO LOVERS

Codesigning for SIP enabled!

MrLyannMusic Audiosexual

luongvo Newbie

jimklk Noisemaker

jimklk Noisemaker

Lucas Schauer Member

Mauwurf Member

Lucas Schauer Member

Attached Files:

Bildschirmfoto 2024-04-10 um 15.00.08.png

Diego Xavier Sousa Newbie

Mauwurf Member

jimklk Noisemaker

Mauwurf Member

rahul4848 Newbie

Emma Evi Ultrasonic

Useful Searches