signtool time server rate limited?
See original GitHub issue- Version: 20.19.2
- Target: Windows
In 20.19.1, one of the bug fixes is “sign all exe and dll files, not only root (37bb121)”.
If the application contains a lot of dll and exe files, then I think signing of the files is getting rate limited or something because the first ~17 or so files sign correctly but after that I get an exception: SignTool Error: The specified timestamp server either could not be reached or returned an invalid response
Reverting back to an older version of electron-builder (19.55.3) where only a few files are signed and my application builds successfully again.
Output log:
C:\directory_ommited>electron-builder --publish never
• electron-builder version=20.19.2
• loaded configuration file=package.json ("build" field)
• rebuilding native production dependencies platform=win32 arch=x64
• packaging platform=win32 arch=x64 electron=1.7.9 appOutDir=dist\win-unpacked
• signing file=dist\win-unpacked\resources\alex\MSVCP140.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\hdf.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\hdf5_cpp.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\hdf5_hl_cpp.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\hdf5_hl.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\hdf5_tools.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\jpeg.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\libcurl.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\r\unins000.exe certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\hdf5.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\alex\zlib.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\alex\ucrtbase.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\alex\tk86t.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\alex\tcl86t.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\alex\sqlite3.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\alex\pywintypes36.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
• signing file=dist\win-unpacked\resources\alex\pythoncom36.dll certificateFile=C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12
Error: Exit code: 1. Command failed: C:\Users\jenkins\AppData\Local\electron-builder\cache\winCodeSign\winCodeSign-2.1.0\windows-10\x64\signtool.exe sign /t http://timestamp.globalsign.com/scripts/timstamp.dll /f C:\Users\jenkins\AppData\Local\Temp\temp-dir-Jab5Po\0.p12 /d app_name_ommited /du url_ommited /p hash_ommited (sha256 hash) /debug C:\directory_ommited\hdf5_hl.dll
SignTool Error: The specified timestamp server either could not be reached or
returned an invalid response.
SignTool Error: An error occurred while attempting to sign: C:\directory_ommited\hdf5_hl.dll
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Developers - signtool time server rate limited? - - Bountysource
In 20.19.1, one of the bug fixes is "sign all exe and dll files, not only root (37bb121)". If the application contains a...
Read more >Timestamp Server And Stamping Protocols | Sectigo® Official
Tools like Microsoft's SignTool let you timestamp the signature block based on the current date and time that a timestamping service provider, such...
Read more >Troubleshooting timestamping problems
The most common timestamping problems and the troubleshooting instructions are:
Read more >Whether/how to avoid SHA-1 signed timestamp when code ...
It's a two-step process that first signs with SHA-1, then appends a SHA-256 signature. Though it is not explicit, the first run of...
Read more >Code signing with SHA-256 - InstallAware
Can a comodo SHA-256 time stamping server be used with InstallAware X2? ... folder of InstallAware; rename signtool.exe to signtool2.exe ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
rfc3161TimeStampServer
, here’s my config:@aluxian, how did you switch the timestamp server? (I checked the config options but didn’t find anything related, sorry if I missed it)