What are the limitations of using Long UNC filenames for catalog signature forgery?

The main limitations include: (1) the spoofed file cannot be executed via double-click or a standard path that includes a trailing space; (2) it requires write access to the target directory (e.g., `C:\Windows\System32`); (3) tools like `certutil.exe` and hash verifiers see the real file content, not the forged signature; (4) on 64-bit systems, file system redirection may interfere; (5) only files with catalog signatures (not Authenticode) can be spoofed this way. The article also contrasts this with [Authenticode Signature Forgery - PE File Signature Forgery and Signature Verification Hijacking](/news/authenticode-signature-forgery-pe-file-signature-forgery-and-signature-verification-hijacking).