# Generate SHA-256 checksum of the authentic setup manifest sha256secure maya_user_setup.conf > maya_setup_checksums.txt
For the end user, the verification runs silently in the background. There’s no extra step like typing a code or solving a CAPTCHA. The only noticeable difference is a slightly longer setup time (typically 1–3 seconds), which is a fair trade-off for security. maya secure user setup checksum verification
: Maya’s security system automates this process. When a user or a pipeline tool defines a userSetup script, Maya can compute a hash (a "digital finger print") for it and store this as a baseline. On subsequent launches, before executing the script, Maya recalculates the script's hash and compares it to the stored version. If there’s a mismatch, it indicates the script has been changed. Maya will then prompt the user with a warning and provide an option to either trust the new version and update the stored hash, or to investigate the change. By default, this checksum verification is disabled . # Generate SHA-256 checksum of the authentic setup
: Restrict user access permissions on production deployment folders. Ensure directories containing verified setup scripts are set to read-only for artist accounts, allowing modifications only via administrative deployment pipelines. : Maya’s security system automates this process
While checksum verification is a powerful first line of defense, it is not a comprehensive solution on its own. Autodesk provides a free, powerful suite called the . This tool acts as a dedicated antivirus for Maya. It can perform deep scans of the current scene to detect and remove malicious script nodes, scan and clean individual scene files without opening them, and analyze the user's userSetup files.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Even experienced developers can mis-implement checksum verification. Here are the top mistakes: