Jump to content

Root Certificates and Revoked Certificates for Windows XP


heinoganda

Recommended Posts

Quote

mirekprv said:
This is what I'm getting with @heinoganda's Cert_Updater.exe:

Nowy obraz.jpg

Update with 2 more root certificates:

CN = Swiss Government Root CA III
OU = www.pki.admin.ch
O = Swiss Government PKI
C = CH

CN = SI-TRUST Root
2.5.4.97 = VATSI-17659957
O = Republika Slovenija
C = SI

Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.

:)

Edited by heinoganda
Link to comment
Share on other sites

  • 2 months later...

Update with 2 more root certificates:

CN = Application CA G4 Root
O = LGPKI
C = JP

CN = PosDigicert Class 2 Root CA G2
O = Digicert Sdn. Bhd.
C = MY

Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.

:)

Link to comment
Share on other sites

Thanks!
The revoked certificates update failed the first time I tried it, but worked when I tried again.
I now have -

authroots.sst        13/06/17 20:02
delroots.sst           12/11/16 00:59
roots.sst                13/06/17 20:02
updroots.sst           13/06/17 20:02
disallowedcert.sst   20/04/17 16:59

:)
 

Link to comment
Share on other sites

  • 3 months later...

certupd201709.jpg

Update for root certificates:

Delete:

CN = Sonera Class1 CA
O = Sonera
C = FI

New:

OU = AC RAIZ FNMT-RCM
O = FNMT-RCM
C = ES
SN:5d 93 8d 30 67 36 c8 06 1d 1a c7 54 84 69 07

CN = GTS Root R1
O = Google Trust Services LLC
C = US

CN = GTS Root R2
O = Google Trust Services LLC
C = US

CN = Halcom Root Certificate Authority
2.5.4.97 = VATSI-43353126
O = Halcom d.d.
C = SI

CN = Netrust Root CA 2
OU = Netrust Certificate Authority
O = Netrust Pte Ltd
C = SG

CN = SSC GDL CA Root A
OU = CA ROOT Services
O = Skaitmeninio sertifikavimo centras
C = LT

CN = SSC GDL CA VS Root
OU = VS ROOT Services
O = Skaitmeninio sertifikavimo centras
C = LT

CN = SSL.com EV Root Certification Authority RSA R2
O = SSL Corporation
L = Houston
S = Texas
C = US

Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.

:)

Link to comment
Share on other sites

  • 1 month later...
Link to comment
Share on other sites

  • 4 weeks later...

cert201711.jpg

Update for root certificates:

New:

CN = ATHEX Root CA G2
O = ATHENS STOCK EXCHANGE
C = GR

CN = Microsoft Time Stamp Root Certificate Authority 2014
O = Microsoft Corporation
L = Redmond
S = Washington
C = US


Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.

:)

Link to comment
Share on other sites

Thanks!

Mine are now the same apart from the time stamps being one hour different as they always are.

Always been puzzled why my updater has slashes as dividers in the dates, and yours has full stops!

:dubbio:

Link to comment
Share on other sites

23 minutes ago, Dave-H said:

Always been puzzled why my updater has slashes as dividers in the dates, and yours has full stops!

Have a German Windows XP used, for this reason, this format of the date displayed.

cert2_201711.jpg

So you do not get sleepless night. :yes:

:)

Edited by heinoganda
Link to comment
Share on other sites

  • 6 months later...

 

@heinoganda

I am not sure and sorry if I am wrong - but is it possible that your very helpfull tool has an old UPDROOTS.EXE ?

Randomly I found a hint in the www, that there is a newer version 5.2.xxx available, but in your updater is version 5.1.xxx used.

And I don't know if there is such a newer version running under XP, but can you check it please?

May be that this is the reason for some certificate issues reported here, but it is only a guess of course. :)

On 10/23/2015 at 3:49 PM, heinoganda said:

For all who are interested in an independent Update Root Certificates and revoked certificates, I want to offer a small downloader and updater (available now) without version confusion.

 

Download

 

Archive Password:


xU7DWBLyTIZ38V5vJZpH5TsefB6vkJhS4QH5TIefi7m9n1XfR2phS41XB6j

Eliminates misspellings, change from "Continue updating?" to "Do you want to update certificates?" thanks @hmuellers 

 

 

update 12/18/2015  Version 1.1

The creation date of the downloaded sst files appears.
 

update 02/16/2016  Version 1.2

Due Country-specific formats of date display, partly the creation date of sst files was not correctly displayed.
 
 

:)

 

Link to comment
Share on other sites

7 hours ago, Thomas S. said:

I am not sure and sorry if I am wrong - but is it possible that your very helpfull tool has an old UPDROOTS.EXE ?

The tool works perfectly even under Windows 7. Unfortunately the forum lacks many follow-up comments after February 2018, where also explains why it is so. Microsoft deletes stale or insecure root certificates with the "delroots.sst" file, which is not an error. Now there are users who are still working with very outdated e-mail programs, but these have their problems with modern encryption technologies. A workaround may be "ProxHTTPSProxyMII" or install from the file "delroots.sst" the timely, valid certificates, definitely not recommended.

:)

Edited by heinoganda
Link to comment
Share on other sites

I'm still getting the strings of errors in my Application Event Log, as you can see from this.
It's also started happening on my netbook as well now!

Crypt32Errors.thumb.jpg.02ec58ef343e9ec5c79c3efa135105eb.jpg

The yellow warning shown states "Reached crypt32 threshold of 50 events and will suspend logging for 60 minutes"!
:o

Edited by Dave-H
Typo
Link to comment
Share on other sites

Is KB2253680 of any help? Others say to...
 

Quote

Please register the following files:

Click start, click Run, type regsvr32 Softpub.dll and click OK.

Click start, click Run, type regsvr32 Wintrust.dll and click OK.

Click start, click Run, type regsvr32 Initpki.dll and click OK.

Click start, click Run, type regsvr32 Mssip32.dll and click OK.

Tim Quan

... although I doubt it may solve anything, it's harmless, so you lose nothing in trying that. Good luck! :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...