BBC BASIC for Windows
« Coding Signing Certificates: On behalf of RTR »
Welcome Guest. Please Login or Register. Apr 5th, 2018, 10:01pm
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
Coding Signing Certificates: On behalf of RTR
« Thread started on: Jan 3rd, 2016, 9:28pm »
Dear All,
Richard asked me to copy this here, which he posted on the Yahoo site:
As many of you will know, Windows support for SHA-1 Code Signing Certificates ended yesterday. From now on, only SHA-2 certificates will be accepted as valid. This should not have any immediate effect on 'BBC BASIC for Windows' because although the version 6.00a installer and upgrade EXEs are signed with an SHA-1 certificate they are time-stamped with a date prior to today, and that should mean they are still accepted.
However, any EXEs that I generate from now onwards, which may include updates to BB4W or just compiled BASIC programs, will need to be signed with an SHA-2 certificate. I am currently in the process of obtaining one (I thought that replacing my existing SHA-1 certificate would be an 'instant' exercise but it seems not).
One particular thing to note is that SHA-2 certificates are only recognised by versions of Windows from XP SP3 onwards. If you are running Windows XP, please ensure that Service Pack 3 is installed; if you are still using an even older version (e.g. Windows 2000) then executables signed with an SHA-2 certificate will not be accepted.
Richard.
However, I note later in that strand that he has now discovered that his replacement certificate is still an SHA-1 one.
Logged