RE: Cubase SIP enabled permanent.
Here is a little Description, what to do.



So here is my post again.

If you sign it with your own signing cert = Then you can leave SIP on!
You can always keep it on.
First of all, install this application from the following link:
https://objective-see.org/products/whatsyoursign.html
Read the explanation on how to use it.


Here's the text organized into a structured sequence:

Install the application "What's Your Sign" from the link provided.
Follow the instructions on how to use it.
Right-click on the license file and select "Signing Info" to check for any signing issues.
Setup Xcode and Development ID:

Install Xcode and Xcode Command Line Tools.
Open Xcode, go to Settings > Account, and log in with your Apple ID.
Check if your Apple Development ID is created and stored in Keychain under "My Certificates."
Codesigning with Your Development ID:

Use the command codesign --force --deep --sign "Apple Development: YOURAPPLEID (YOURTEAMID)" /Applications/ApplicationName.app.
Before executing the codesigning command, adjust permissions using sudo chown -R macusername for necessary directories.

Example: sudo chown -R macusername /Applications

or: sudo chown -R macusername /Library/Application \Support/Steinberg

Ensure that the path to the application includes escaped spaces and special characters using backslashes or quotes.
Verification and Additional Commands:

Verify the signing with "What's Your Sign."
If needed, execute additional commands after signing:
sudo xattr -cr /Applications/ApplicationName.app/Contents/MacOS/ApplicationName
sudo xattr -r -d com.apple.quarantine /Applications/ApplicationName.app/Contents/MacOS/ApplicationName

chmod +x /Applications/ApplicationName.app/Contents/MacOS/ApplicationName

to make it executable.


Consult AI for Explanation:

If any error messages occur, consult ChatGPT or any other AI for clarification.

The text is now structured and easier to follow for users intending to sign applications on macOS.

Use ChatGPT and co. for an explanation of all these stuff to yourself.


In Generell…. This Signing Method with your own Certificate works also well with a lot of other releases. Not to say…. with all.

And of Course it works with all Steinberg Releases down to Cubase 12 and Wavelab 11 and so on.

With the Instruments like Retrologue and Halion as well.

Please do not bother me with simple Questions like Example:

1- Should I follow the steps you explained to me while Qubizz is installed on the computer? Or do I delete Qbiz from the computer and all its contents and then do a new installation?
2- If it is a new installation, should I re-enable or disable the SIP?
3- As for Xcode, I installed it via the terminal, but I could not find it on the computer in order to go to its settings. I use the Monterey system.
4- SoundDept2020 is just an example to clarify? Or should I use that name
Finally, thank you and bear with me a little, my dear brother.


1. Cubase have to be already installed.

2. No need to disable SIP at all. When things got done right.

3. Xcode from Appstore and Xcode Command line Tools via Terminal. That are two different things.



when you say things like sudo chown -R Vedmore
you mean my Mac username I am assuming?

Exactly.

Do I have to keep 'whatstyoursign' on my Mac afterwards?

No


!! GOOD LUCK !!

 

Last edited: Mar 18, 2024

Hello, may I ask a question? Do I need to prepare my own paid Apple Development ID？

 

I hate n stop using from steinberg cracked if needed disable sip to makes an apps is workin on my mbpro,, its because a while ago it make my all apps position are messup, they are randomly change position everytime after restart and make loading restart a little bit glitching..

Note,,its fine if just needed turn off sip just for install first and after that still workin if turn on again,, like sonnox a years ago from..*iforgot*..

 

No.....

Just Create one with Xcode and your existent Apple ID.

If this is not working.

Create a Swift Projekt with Xcode. ---> Then you get automatically a local Apple Development ID.

HAs nothing to do with the paid one for 99 $

 

thank you for your reply. I'm trying your method.

 

Last edited: Mar 21, 2024

Great, I've made it! Thank you for sharing!

 

Steinberg requires a digital signature from Steinberg Software GmbH - your local certificate will not work for it

 

Congratulation.

Maybe you can. Optimise my first Post for better understanding for all the other guys.

Or you can summarize your steps. In a short Step Sequence Report.

 

So on my Computer it works.... and many many others. So maybe you did something Wrong.

Just did it again with the new Release Version 10 Minutes Ago ---> https://audioz.download/software/253131-download_steinberg-cubase-pro-13-v13030-u2b-macos.html

Working Wonderfull with SIP enabled.

The Computer Says ---> You are Wrong.

 

Last edited: Mar 21, 2024

Work great here for wavelab thank for the info a little tricky on beginning for me but it work very nice .. many thanks

 

not working when codesign, i got this error:
Warning: unable to build chain to self-signed root for signer "my xxx"

Warning: unable to build chain to self-signed root for signer "my xxx"

/Applications/cubase 13.app: errSecInternalComponent
In subcomponent: /Applications/Cubase 13.app/Contents/MacOS/libimagegenerator.dylib
sonoma 14.4 mac m3 pro

any help?

 

Do you think this system can also work with Auto-Tune and/or other plugins that require SIP disabled?

 

If by this, you mean modified libstdc+++ 6.0.9. dylib ilok bypass stuff using the old OpenSSH "exploit" then probably not. If you re-enable SIP with the two files replaced I think it will crash your DAW when you load the plugins you have installed to use those modified files.

Try it in a test project in your DAW. If you wait until you are really working on something; you could load the plugin, crash the daw and lose any unsaved work. Just check first. These tend to "disappear" your DAW when they crash, rather than giving you any error messages. I am not doing this method as posted in this thread, for now anyway.

 

I believe i have followed the post to the letter but i still get no valid liences found...

i included a screenshot of the Signing info app, is that what it should say?

 

Last edited: Mar 22, 2024

Why are you guys all hot to trot about re-enabling SIP now anyway? Older MacOS versions still?

https://support.apple.com/guide/mac-help/what-is-a-signed-system-volume-mchl0f9af76f/mac

What is a signed system volume?
macOS includes enhanced protection for your Mac with cryptographic technology (macOS 11 or later) that prevents access to or execution of files that don’t have a valid cryptographic signature from Apple. All system files are protected on the signed system volume (SSV). This advanced system volume technology provides a high level of security against malicious software and tampering with the operating system.

It also allows software updates to complete in the background while you work, which reduces the time it takes for your Mac to restart and complete updates.

 

Thanks for your valuable advice...

Too bad, also because where I live there isn't an Apple support service nearby, if my Mac crashed or had a serious problem I wouldn't know how to fix things quickly.
This is why I think I'll wait for a more secure system.

Yes, Sierra in my case

 

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.

 

Last edited: Mar 22, 2024

See in your keychain your developper username certificate is not valid ..

 

thanks for the answer, my certificate is ok in my keychain

 

i got the message that .bundle is damaged.. any help?