Can you sign the dll's? #396
Replies: 4 comments 4 replies
-
Hi As I think you are aware, certificates cost quite some money. It would be interesting to have these signed, but generally I don’t think it adds much value, since the chain of trust is pretty much guaranteed with the current setup: the code is public, builds are automated so that my potentially unsafe machine is excluded, and then builds are hosted on GitHub’s infrastructure. If one trusts my code and GitHub, then the file they get is virtually guaranteed to have only these 2 actors involved, so what would signing achieve in this instance for the general public…? DLLs are still accessible, as noted, in the build page, as artifacts. There has already been a lengthy discussion about this. The current setup is more easy to understand for users, so it will stick. GitHub has a public API for accessing the artifacts and downloading them etc. Alternatively, simply download the exe and extract the resources you want from it, for example: More details about these approaches in this other thread: #347 Alternatively alternatively, even more fancy, host your own update server! It’s super simple: host the signed ep_setup at some endpoint, let’s say http://10.1.1.222/ep/ep_setup.exe. Then, just go to The source code is the best manual for this software, it’s hard for me as a single entity to keep everything else updated with the latest changes at the pace the questions arrive. There is a plan to document this thoughtfully in the wiki, but time is the main issue: I can’t be instantaneous, it takes time and I have lots of other things to take care of as well, I also have a workplace etc. So yeah, I think there are some great methods available out there and at least 3 alternatives out there, the last one being my favorite, since it’s pretty easy to set up a web server (IIS is fine for this task, takes 3 minutes to install) and it works nicely with the updater in EP. As for checking for updates, again, the source code tells you the mechanism: the md5 hash of Thanks, hope you put together something with the info provided. Good luck! |
Beta Was this translation helpful? Give feedback.
-
Thanks for the lengthy explanation. I read through the thread your provided the link to and it provides a mechanism for me to follow. |
Beta Was this translation helpful? Give feedback.
-
Signed the files or added the ability to extract the files? So I was just working on my way using our signing cert. I had the script all done but found an issue with restarting Explorer. Anyway take a look at the PS code below, but for me the last line no longer works:
|
Beta Was this translation helpful? Give feedback.
-
OK, but is rundll32 "C:\Windows\dxgi.dll",ZZRestartExplorer still supposed to work - for me it doesn't? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Valinet,
In our enterprise we have quite rigorous monitoring of system files on all desktop clients. Typically they are flagging files in system areas that look to be making "hijacks" to files like Explorer.
Our security team has seen me testing explorerpatcher and saw it as a possible hijack. After investigation they determined what the file was for was but they have asked me to enquire if you can sign the files with a valid software cert?
Previously I had a script to download new versions, install and then sign before I reloaded explorer.
With your new process of updating it makes it more difficult. I suppose I could just disable your updater and continue my old process as long as the dll's were still programmatically accessible on your site. Currently under releases you only have the setup file.
I did look here: "An archive containing all the files generated during the build process (including dxgi.dll and symbol files) is available here." but accessing dxgi.dll this way would be programmatically difficult.
Pete
Beta Was this translation helpful? Give feedback.
All reactions