Skip to content

Closure Compiler Windows executable is not cryptographically signed #15

@juj

Description

@juj

The Windows executable node_modules\google-closure-compiler-windows\compiler.exe provided by the Closure Compiler project is not cryptographically signed.

STR:

> npm install google-closure-compiler-windows
> "C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x86\signtool" verify node_modules\google-closure-compiler-windows\compiler.exe
File: node_modules\google-closure-compiler-windows\compiler.exe
Index  Algorithm  Timestamp
========================================
SignTool Error: No signature found.

Number of errors: 1

(adjust path to C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x86\signtool on your system)

Alternatively navigate in file explorer in the compiler executable directory, right-click on the compiler.exe -> Properties -> Digital Signatures -> shows an empty list of Embedded Signatures, but was expected to show a signature of the author.

Would it be possible to sign all the releases?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions