Updater is not signed #629

Closed
opened 2025-09-10 23:46:24 -05:00 by giteasync · 1 comment
Owner

Originally created by @Verequus on GitHub.

Describe the bug
The updater executable is not signed. So it is not possible to create policies in regards to this executable.

Please confirm that this problem is VSCodium-specific

  • [ X] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

  • [ X] I checked the Docs page and my issue is not mentioned there.

To Reproduce
Not applicable.

Expected behavior
The updater is signed.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows 10

Additional context
In my company, the administration rights are handled stringently. The software which can be easily installed is placed into a special repository, which is updated manually by the IT. Software that is frequently updated places a hard burden on the staff. So alternatively, it is possible to make special exceptions to certain executables. But for that, these files need to be signed properly.

Originally created by @Verequus on GitHub. **Describe the bug** The updater executable is not signed. So it is not possible to create policies in regards to this executable. **Please confirm that this problem is VSCodium-specific** - [ X] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium. **Please confirm that the issue/resolution isn't already documented** - [ X] I checked [the Docs page](https://github.com/VSCodium/vscodium/blob/master/DOCS.md) and my issue is not mentioned there. **To Reproduce** Not applicable. **Expected behavior** The updater is signed. **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - OS: Windows 10 **Additional context** In my company, the administration rights are handled stringently. The software which can be easily installed is placed into a special repository, which is updated manually by the IT. Software that is frequently updated places a hard burden on the staff. So alternatively, it is possible to make special exceptions to certain executables. But for that, these files need to be signed properly.
giteasync added the bug label 2025-09-10 23:46:24 -05:00
Author
Owner

@GitMensch commented on GitHub:

The installer is not signed either, because - as I see it - no one sponsored a code signing certificate along with adjusting the CI to use it for code signing. This is actually a duplicate as #174 (after I've reopened it...), so please feel free to discuss there.
You may want to discuss with your IT staff to sponsor the certificate and the work to integrate it if it is important to you.

@GitMensch commented on GitHub: The installer is not signed either, because - as I see it - no one sponsored a code signing certificate along with adjusting the CI to use it for code signing. This is actually a duplicate as #174 (after I've reopened it...), so please feel free to discuss there. You may want to discuss with your IT staff to sponsor the certificate and the work to integrate it if it is important to you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: VSCodium/vscodium#629