redhat-developer / redhat-developer/vscode-xml
lemminx-win32.exe not properly signed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 328
- Forks
- 101
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 7
Description
Version : redhat.vscode-xml-0.29.0-win32-x64
Issue:
We are currently implementing Application Control for Business and some of our users use the Redhat XML extension.
Now we want to whitelist lemminx-win32.exe but to our surprise this executable isn't signed at all see screenshot:
For now, this is a blocking issue since we cannot do proper whitelisting.
Attempted solutions :
We can do whitelisting on file hash but that means that we need to whitelist it repeatedly every time the file hash changes.
Proposal :
Can you please sign this .exe properly with CA/ProductName in your future deployments.
Reference:
https://github.com/microsoft/python-environment-tools/issues/272
We had the same issue with a python extension and this was adjusted by them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the v0.29.0 Windows deployment that produces lemminx-win32.exe, along with the signing approach referenced from the Python extension issue. Confirm how CA/ProductName signing is configured for future deployments, then verify that the generated executable is properly signed and suitable for application whitelisting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100