EldoS | Feel safer!

Software components for data protection, secure storage and transfer

TElPGPSignature.SignatureClass value

Also by EldoS: MsgConnect
Cross-platform protocol-independent communication framework for building peer-to-peer and client-server applications and middleware components.
#36956
Posted: 06/09/2016 15:59:07
by Travis Mathison (Priority Standard support level)
Joined: 10/07/2015
Posts: 9

We have a situation where incoming files from a few clients have issues with their signatures as they event as "svCorrupted". We know the keyID and it's on our keyring so can continue processing them to make things work manually but our system is written to reject signatures that are not svValid.

I'm been trying to figure out what the issue may be. In the two cases I've identified they are binary files. I started performing dumps of the TElPGPSignature of all the files coming through and one thing I noticed was that the SignatureClass property on all signatures that worked was 0 and on the couple that come up svCorrupted it was set to 1.

Looking at the documentation I see the following details on these values:
SB_PGP_SIGTYPE_DOCUMENT 0 (0x00)
SB_PGP_SIGTYPE_STANDALONE 1 (0x01)

Is there something particular that these clients may be doing to their files when they sign them that we should be telling them not to do? This may be just a coincidence and not relevant to the issue that is actually going on. In either case, I'm trying to understand the difference of these two values (a good and bad dump are shown below):

====
Known Good signature
====
signatures[0]
{SBPGPKeys.TElPGPSignature}
CertificationType: 0
CreationTime: {9/14/2015 6:54:52 PM}
ExpirationTime: 0
Exportable: true
FDisposed: false
HashAlgorithm: 2
IsTextSignature: false
IsX509Certificate: false
KeyExpirationTime: 0
OnRead: null
OnWrite: null
PolicyURL: ""
PrimaryUserID: false
ReasonForRevocation: ""
RegularExpressionCount: 0
Revocable: true
Revocation: false
SignatureClass: 0
SignerUserID: "id-of-key"
StrictlyValid: false
Trust: {SBPGPKeys.TElPGPTrust}
TrustAmount: 0
TrustLevel: 0
UseOldPackets: false
Validated: true
Version: 4
X509Certificate: null

====
Signature that is SBPGPStreams.TSBPGPSignatureValidity.svCorrupted
====
signatures[0]
{SBPGPKeys.TElPGPSignature}
CertificationType: 0
CreationTime: {6/6/2016 10:52:49 AM}
ExpirationTime: 0
Exportable: true
FDisposed: false
HashAlgorithm: 2
IsTextSignature: true
IsX509Certificate: false
KeyExpirationTime: 0
OnRead: null
OnWrite: null
PolicyURL: ""
PrimaryUserID: false
ReasonForRevocation: ""
RegularExpressionCount: 0
Revocable: true
Revocation: false
SignatureClass: 1
SignerUserID: ""
StrictlyValid: false
Trust: {SBPGPKeys.TElPGPTrust}
TrustAmount: 0
TrustLevel: 0
UseOldPackets: false
Validated: false
Version: 4
X509Certificate: null
#36960
Posted: 06/10/2016 00:51:15
by Eugene Mayevski (EldoS Corp.)

I welcome you to continue the conversation in the Helpdesk ( https://www.eldos.com/helpdesk/ ).

Helpdesk is our easy-to-use individual support system that allows communicating and exchanging sample data with our support personnel privately. You will also get e-mail notifications about updates of your support request.


Sincerely yours
Eugene Mayevski

Reply

Statistics

Topic viewed 926 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!