Abuse Melding

Je hebt een klacht over de onderstaande posting:

22-05-2014, 22:51 door Anoniem

Confirmed here on XP SP3 also: same issue with the files Erik mentioned at 17:43. I 've been thinking what could possibly go wrong causing such a "weird countersignature/timestamp behaviour". Many causes are possible. I'm aware things can be complicated. But my first two suggestions would be: 1. sha256 hashes are longer than sha1. Could this here be causing some unforeseen bufferoverflow somewhere? 2. I noticed these "problemsignatures" contain some countersignature (timestamp) -related OID: 1.3.6.1.4.1.311.3.3.1 This OID is NOT defined in: http://support.microsoft.com/kb/287547 (outdated list or not?...) But this one is present in the list: SPC_TIME_STAMP_REQUEST_OBJID = 1.3.6.1.4.1.311.3.2.1 So almost the same OID-number. Almost... Might be worth checking. Anyway: in my opinion it's up to Microsoft's software engineers now. (I will still monitor this thread for some time, but less intensive and consider it solved) ;-) cheers and good luck, cluc-cluc

Beschrijf je klacht (Optioneel):

captcha