You should never see this message.
The Realterm executable and installer are code signed by Broadcast Equipment Ltd. I only release signed installers.
From V3.0.0.33+, Realterm checks its own signature and will show this message if it has been altered or re-signed by another entity (or there is a bug in the self-checking)
If you do see this message, report it below.
1) There could be an issue with Realterms self check
2) It might have been altered - viruses on your system, or downloading the installer from a shareware site.
Check both the installer and realterm.exe . In explorer->properties->Digital Signatures tab. You will see it is signed by Broadcast Equipment Ltd, not any other entity
If the Digital Signature tab is not present, then there is no signature. Release versions are signed
I downloaded, and successfully installed v3.0.0.33. Then I copied that installer over to another PC, isntaleld as administrator, and saw "Warning: Bad Code Signature" in big red letters. The second PC is isolated from the newwork. Could lack of network access be the cause of the signature issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Certainly disconnecting from the network does not cause a problem here, but then windows already knows that my key is ok.
Has the 2nd machine never been connected to the network?
Or just never since Realterm was installed?
If you run it when the interwebs are connected once, does the warning disappear for ever?
You should never see this message.
The Realterm executable and installer are code signed by Broadcast Equipment Ltd. I only release signed installers.
From V3.0.0.33+, Realterm checks its own signature and will show this message if it has been altered or re-signed by another entity (or there is a bug in the self-checking)
If you do see this message, report it below.
1) There could be an issue with Realterms self check
2) It might have been altered - viruses on your system, or downloading the installer from a shareware site.
Check both the installer and realterm.exe . In explorer->properties->Digital Signatures tab. You will see it is signed by Broadcast Equipment Ltd, not any other entity
If the Digital Signature tab is not present, then there is no signature. Release versions are signed
3) Your PC has not accessed the signature database used to verify. see:
https://stackoverflow.com/questions/38332814/why-does-winverifytrust-failing-only-on-machine-which-is-not-connected-to-inte
Last edit: Simon Bridger 2020-06-03
View and moderate all "Help and Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I downloaded, and successfully installed v3.0.0.33. Then I copied that installer over to another PC, isntaleld as administrator, and saw "Warning: Bad Code Signature" in big red letters. The second PC is isolated from the newwork. Could lack of network access be the cause of the signature issue?
Congragulations on being the first.
Certainly disconnecting from the network does not cause a problem here, but then windows already knows that my key is ok.
Has the 2nd machine never been connected to the network?
Or just never since Realterm was installed?
If you run it when the interwebs are connected once, does the warning disappear for ever?
Probably this is what it is about?
https://stackoverflow.com/questions/38332814/why-does-winverifytrust-failing-only-on-machine-which-is-not-connected-to-inte
Please make a bug report (you need to make an SF user), this may need changes or perhaps just rewording the warnings?
All of a sudden I am getting a red "Warning Bad Code" on v3.0.0.33 What gives?