Ok thank you for your answer.
If I leave native folder available to the user so they can access its content (systa.exe, TurboActivate.dat, TurboActivate.dll and same for Mac) is that save in terms of possible fraud?
To user do not do this manually permision in the terminal, can I add this code like this below?
But also I am getting message "mac cannot verify that this app is free from malware run anyway"….how to take care this through code?
const os = require('os');
const platform = os.platform();
if (platform === 'darwin') {
const fs = require('fs');
// Define the file path and the desired permission mode
const filePath = String(__dirname + '/' +'client/native/Mac/systa');
const desiredPermissions = 0o755; // This represents read, write, and execute permissions for the owner, and read and execute permissions for others
// Change the file permissions
fs.chmod(filePath, desiredPermissions, (err) => {
if (err) {
alert(`Error setting permissions: ${err}`);
} else {
//alert('Permissions set successfully');
}
});
} else {
alert('This is not a Mac.');
}
To user do not do this manually permision in the terminal, can I add this code like this below?
Just have your installer handle both. Code may or may not work depending on the how Apple is feeling.
Also, see Gatekeeper / code-signing. Apple continually changes their security model. Mostly to push people into the Apple-store ecosystem and take a larger piece of software company revenues (unearned).
Ok thank you for your answer.
If I leave native folder available to the user so they can access its content (systa.exe, TurboActivate.dat, TurboActivate.dll and same for Mac) is that save in terms of possible fraud?