Simon Sobisch

@stripedpajamas wrote: > The Windows binary is not being codesigned at this time. I should prioritize that if it would help with malware false positives. It definitely would. Ideally both...

Just adding the reference: #527 (already closed, but found first in my search).

I bet there's a configuration option to explicit set it (or best: activate "try to find the one matching the OS"), I suggest we see if someone knows of that...

I'm quite sure that this will work - but that it won't be the correct solution. There has to be a configuration option for that...

The project has the ability (the worker have `signtool` and the password can be used as secure token (if it isn't set then no signing would happen). But so far...

@stripedpajamas "Does the project have the ability to accept donations [...]?" I don't know. But something that may work much easier is ask the vendors directly to create the certificate...

> I'd expect any CA selling code signing certificates to be pretty universally accepted? Not completely, it depends where their root certificate is installed (some older/newer Windows versions may not...

Can you verify if version 1.52.0 has the same issue?

Finally implemented with #1217 - binaries available with https://github.com/VSCodium/vscodium-insiders/releases; the build scripts (and workflows) are directly used from this repo (in case someone wants to use it to build an...

@paulcarroty Using `apt` with the registered repositories does not bring up any insider version - could you add that, please?