EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Signature.handler is null

Also by EldoS: Solid File System
A virtual file system that offers a feature-rich storage for application documents and data with built-in compression and encryption.
#13883
Posted: 07/12/2010 04:49:08
by scamy sc (Basic support level)
Joined: 07/12/2010
Posts: 1

why CertStorage.GetIssuerCertificate(Cert) = -1 ?


Parameter Cert = {SBX509.TElX509Certificate}
base {SBUtils.TSBControlBase}: {SBX509.TElX509Certificate}
BelongsTo: 0
CAAvailable: false
CanEncrypt: true
CanSign: true
CertHandle: 0
CertificateBinary: {byte[1502]}
CertificateSize: 1502
CertStorage: null
Chain: null
CryptoProvider: null
CryptoProviderManager: null
Extensions: {SBX509Ext.TElCertificateExtensions}
IssuerName: {SBX509.TName}
IssuerRDN: {SBRDN.TElRelativeDistinguishedName}
IssuerUniqueID: {byte[0]}
KeyMaterial: {SBPublicKeyCrypto.TElRSAKeyMaterial}
NegativeSerial: false
PrivateKeyExists: false
PrivateKeyExtractable: true
PublicKeyAlgorithm: 0
PublicKeyAlgorithmIdentifier: {SBAlgorithmIdentifier.TElRSAAlgorithmIdentifier}
ReportErrorOnPartialLoad: false
SelfSigned: false
SerialNumber: {byte[4]}
Signature: {byte[256]}
SignatureAlgorithm: 3
SignatureAlgorithmIdentifier: {SBAlgorithmIdentifier.TElRSAAlgorithmIdentifier}
StorageName: null
StrictMode: false
SubjectName: {SBX509.TName}
SubjectRDN: {SBRDN.TElRelativeDistinguishedName}
SubjectUniqueID: {byte[0]}
UseUTF8: false
ValidFrom: {21/05/2009 11:23:32}
ValidTo: {21/11/2011 12:53:30}
Version: 3

this is my code.

private ......
{
TElWinCertStorage CertStorage = new TElWinCertStorage();
CertStorage.SystemStores.Add("CA");

int x = CertStorage.GetIssuerCertificate(Cert); //here x=-1

TElX509Certificate C = CertStorage.get_Certificates(x);//not found.
return C;
}
#13886
Posted: 07/12/2010 07:36:14
by Ken Ivanov (EldoS Corp.)

This just means that no issuer certificate is available in the storage. If the certificate you are looking for is supposed to be widely-known CA certificate, it it can reside in the "ROOT" system store (not only CA).
#37100
Posted: 06/24/2016 05:04:07
by Kadir Akdeniz (Basic support level)
Joined: 06/21/2016
Posts: 9

Hello, I am having the same problem with a document that I signed with PDFBlackbox (using certificates from PKCS11 devices - HSM). After reading the answers here, I added the codes to initialize the SBPDF and SBPDFSecurity units before validating. But signatures still do not have Handlers, it is just null.

I thought that maybe I should have initalize these when I sign the document as well and I signed the document again after initializing them. However, this didn't work either.

I also tried to verify the signatures on TinyProcessor c# sample project, it also throws "No security handler available."

What am I missing here?
#37101
Posted: 06/24/2016 05:25:06
by Dmytro Bogatskyy (EldoS Corp.)

Thank you for contacting us,

Quote
I also tried to verify the signatures on TinyProcessor c# sample project, it also throws "No security handler available."

What am I missing here?

The Processor sample is designed only for standard signatures, not PAdES signatures. Please use PAdES sample to verify such signatures.
As for the error, to "register" PAdES handler you need to call:
Code
SBPAdES.Unit.Initialize();
#37102
Posted: 06/24/2016 06:51:45
by Kadir Akdeniz (Basic support level)
Joined: 06/21/2016
Posts: 9

Thanks a lot, that solved the issue, I can see the handler and the certificates now. :)

Btw, I used the tinyprocessor project that was in PDFBlackbox folder. Just letting you know.

Quote
Dmytro Bogatskyy wrote:
Thank you for contacting us,

Quote
I also tried to verify the signatures on TinyProcessor c# sample project, it also throws "No security handler available."

What am I missing here?

The Processor sample is designed only for standard signatures, not PAdES signatures. Please use PAdES sample to verify such signatures.
As for the error, to "register" PAdES handler you need to call:
Code
SBPAdES.Unit.Initialize();
Also by EldoS: CallbackProcess
A component to control process creation and termination in Windows and .NET applications.

Reply

Statistics

Topic viewed 4169 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!