how do you run a script with safari on a remote mac via the internet ?

ChatGPT Fact check:

 

It is those same "exaggerations" that allowed Meltdown and Spectre to be used because everyone ignored it and thought it was impossible, until it blew on everyone's faces.

You do realize that China, Israel, USA, Europe have access to MacOS, IOS, Windows Server-Desktop source code? So having said that someone will leak something eventually out of their conscience or due to financial ties.

If the Snowden saga did not teach us anything then we are lost.

 

This latest response touches on a valid concern regarding security vulnerabilities and the potential for state-level actors to exploit software systems. However, it also includes misunderstandings and exaggerations. Let’s break it down:



1. Meltdown and Spectre Comparison:



• True, but misleading: Meltdown and Spectre were indeed major vulnerabilities affecting nearly all modern processors, including those used in macOS, Windows, and Linux systems. These hardware-level vulnerabilities exploited speculative execution—a core performance optimization technique in CPUs—and allowed attackers to access sensitive data.

• However, comparing these vulnerabilities to general issues with macOS or SIP is misleading. Meltdown and Spectre were processor-specific vulnerabilities that impacted all operating systems, not specific issues related to macOS or Apple’s security architecture. They were widely believed to be theoretical for a long time until proof-of-concept attacks were demonstrated, forcing all major OS vendors to implement mitigations. The commenter is right in pointing out that underestimating risks can lead to disastrous consequences, but their analogy is not directly applicable to the specifics of macOS and SIP.



2. Access to macOS, iOS, Windows Source Code:



• True in some cases, but not inherently problematic: It is known that governments and intelligence agencies in certain countries may have access to proprietary operating system source code through official partnerships or due to legal requirements (for example, Microsoft’s Government Security Program gives certain governments access to source code for security auditing purposes).

• However: Having access to source code doesn’t automatically imply vulnerabilities are being exploited. It’s possible, but major tech companies like Apple and Microsoft implement strict security protocols to prevent unauthorized use or leaking of their source code. The possibility of malicious actors or “leaks” is always a concern, but this doesn’t equate to a widespread, inevitable breach of macOS or iOS systems.

• Additionally, having access to the source code doesn’t necessarily mean the system is insecure. Security through obscurity is a weak defense; most security experts agree that systems should be secure even if their source code is visible.



3. Snowden’s Revelations:



• Valid Point: The commenter mentions the Edward Snowden saga, which exposed how intelligence agencies (especially the NSA) were able to exploit software vulnerabilities, tap into communication networks, and gain access to private information. Snowden’s leaks did reveal that governments had significant capabilities to bypass many commercial security measures.

• However: The Snowden revelations primarily concerned government surveillance programs and vulnerabilities in encryption and communication systems, rather than flaws in macOS or iOS source code specifically. Snowden’s case teaches us about the potential for mass surveillance, but it doesn’t directly relate to vulnerabilities like those the commenter is concerned with in macOS and SIP.



4. Risk of Leaked Vulnerabilities:



• True: The risk of someone leaking vulnerabilities or exploits due to “conscience” or “financial ties” is always present in the cybersecurity world. There have been cases where hackers, whistleblowers, or even employees have disclosed vulnerabilities, either to the public or malicious actors.

• However: While this is a legitimate concern, it doesn’t imply that Apple’s SIP or macOS is fundamentally flawed or that such leaks are inevitable. The cybersecurity world is a constant arms race, with new vulnerabilities being discovered and patched all the time.



Conclusion:



The commenter is using valid historical events (like Meltdown/Spectre and Snowden) to raise concerns about the general security environment, but they are applying these examples in an exaggerated and somewhat misdirected way to the specific topic of macOS and SIP. The risks of state-sponsored exploitation and leaks of vulnerabilities are real, but they are not new or unique to macOS. These risks apply across all major operating systems and require constant vigilance, but they don’t invalidate the security measures like SIP, which still serve an important role in protecting everyday users.



It’s important not to conflate hardware vulnerabilities (like Spectre and Meltdown) or surveillance exploits (like those revealed by Snowden) with specific features like SIP that are designed to protect the integrity of the operating system itself.

 

Since I don’t use any cracked software, there’s no need for me to even consider disabling SIP. I would, however, question why some crackers want you to disable it while others don’t.

 

This is the right question, in my opinion. The teams who cracked Cubase for Mac should answer it, and they should do so in a very specific way, stating technically what areas of the system need a write concession in permissions.

Regarding your questions for ChatGPT, I believe they're fine if you want to expand the scope of information you need to develop your own insights.
But I would not be impressed by his "True" and "False" answers. Who is judging what is true and false? Who.
Question to yourself, in your opinion, Who, where and how is ChatGPT getting the info it's giving you?
And (in case you wanted to approach the reflection from this point of view) what model of logic is it using? Human? Terrestrial? Martian? Pleiadian? Romulan? Forgive the regression, but you know what I mean!, right?

 

I don’t trust anyone but myself I use ChatGPT to gather information and insights that I can evaluate myself. ChatGPT also functions as a smart search engine since it can look up information, and sources can be easily verified.


The concern is that disabling SIP might lead to future errors—there’s no way to know for sure.

If issues arise, who would you contact for resolution? Steinberg?
With a compromised system and traces of VR or R2R everywhere?!

When you send a system report, it lists all the software you’ve installed.
(unless you manually clear it in Terminal).


I’d rather receive legitimate support and resolve issues than continuously try new software without any support

 

Last edited: Oct 8, 2024

Excuse me,
First of all, thank you!
i've done everything as it said here successfully!

The app works 100% on my end with sip enabled.

- Just dont forget to :

sudo chown -R YOURUSERNAME
before codesign with your certificate every file you have to codesign.

 

Last edited: Nov 19, 2024

SanySany WROTE 1 day AGO:

Works with SIP enabled, I checked the VR version.
It's easy to create your own certificate and sign it too. But there are a few things.
If your certificate is not reliable you need a "WWDR Intermediate Certificate".
I downloaded and added them all to the keychain from here.

https://www.apple.com/certificateauthority/

After that you need to sign these files with your certificate

/Applications/Cubase 14.app/Contents/MacOS/Cubase 14'.
'/Library/Application Support/Steinberg/Activation Manager/license-engine-access.bundle'
'/Library/Application Support/Steinberg/Activation Manager/Steinberg License Engine.app'

And you can also remove attributes and adjust permissions with these commands
sudo xattr -cr
sudo chown -R ${USER}
sudo chmod -R 777

How to create your certificate and add your details to the codesign command I won't, read it on the forum.
Your command will look something like this

sudo codesign --force --deep --sign "Apple Development: [email protected] (111111111)"

Again, note that in addition to Cubase 14, you need to apply this to these two files in the Activation Manager folder.
Keychain Access.app in macOS 15 are located in
/System/Library/CoreServices/Applications

Forum with instructions

https://audiosex.pro/threads/codesigning-for-sip-enabled.74681/

Once again, you must sign and apply commands not only to Cubase14.app but also to the files in the Activation Manager folder.
If your certificate is not reliable, download the "WWDR Intermediate Certificate" or all certificates.

 

Reading all those definitely removed my idea to buy a mac !

 

https://github.com/alienator88/Sentinel

 

Did you tried this on Steinberg stuff?
It will be awsome if this just works too

 

Nope I haven't tried it on Steinberg stuff.

 

This is a high detailed and easy to understand process in order to use Steinberg products without touching SIP (not even reboot). The process shows how to use it with Cubase Pro 14 but also shows how you can use it with any other Steinberg product.

I tried it with Cubase Pro 14 and Spectralayers.

Keep in mind that any legit Steinberg license most probably won't work. In my case, I had to download the Cubase Pro 13 release in order to apply the process to Cubase 13 and being able to open it again.

Tested on Macbook Pro ARM M2 Pro, Sequoia.

Download PDF

Apple Certificates

 

Cubase with sip enabled. I have managed it. Thanks a lot!