OS

Windows 10.0.26100

Programming Language

any

VPK Version

0.0.1298

Library Version

any

What happened?

When signing our own library, we sign our library with a --signParams containing another escaped string in square brackets. The vpk invocation then fails with SignTool Error: No private key is available and the verbose log shows that the square brackets and everything in between got removed.

So for example vpk --signParams "/kc \"[foo]=bar\"" causes the invocation of /path/to/signtool.exe sign /kc "=bar". This also occurs with --signTemplate. I am running the command in cmd.exe, so it is probably not a powershell escape issue on my side.

(obviously, I can't give you the actual invocation)

Relevant log output