EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Signing PDF in RDP session

Also by EldoS: CallbackRegistry
A component to monitor and control Windows registry access and create virtual registry keys.
#13732
Posted: 06/23/2010 06:19:16
by L S (Standard support level)
Joined: 04/27/2010
Posts: 6

Using Delphi 2010 and SecureBlackbox version 7.2.169.

My routine for signing PDF runs fine with both the smart card and the application on a local machine, but when I have the smart card connected to a local machine and runs the application on a development machine via a Remote Desktop session I always get 3 access violations on the following linje after the smart card password input box:

Document{TELPDFDocument}.Close(true);

When breaking the debugger tryes to open SBCryptoProvWin32.pas, but as I do not have the source code I am not able to see the cause. SBCryptoProvWin32 must be handling this exception since the Close routine completes and signes the document successfully.

Is this anything to worry about?


LS
#13733
Posted: 06/23/2010 07:11:50
by Ken Ivanov (EldoS Corp.)

Thank you for contacting us.

Could you please recheck that the exceptions you are getting are access violation exceptions (not the other types of exceptions)? If they are, please catch the call stack of the exception and post it here.
#13741
Posted: 06/24/2010 03:13:23
by L S (Standard support level)
Joined: 04/27/2010
Posts: 6

Yes the Debugger Exception Notification says Project xxx raised exception class $C000005 with message 'access violation at 0x75402f0a: read of address 0x00000074'.

The Call Stack:


Code
SBCryptoProvWin32.TElWin32CryptoProvider.SignPKI($5A83B90,???,???,nil,16384)
SBCryptoProvWin32.TElWin32CryptoProvider.SignFinal(???,nil,0,nil,(nil,nil),nil)
SBPublicKeyCrypto.TElRSAPublicKeyCrypto.SignFinal
SBPublicKeyCrypto.TElPublicKeyCrypto.InternalSignDetached
SBPublicKeyCrypto.TElPublicKeyCrypto.SignDetached($68A58A4,20,$2396F2C,128)
SBMessages.TElMessageProcessor.SignRSA($23627C0,???,20,'+'#$E#3#2#$1A,#$81#$81#0'„›ÌþGm'#5'½'#$90'¶ò'#$16'9Ï'#$18'ÏdÁ}¼lºG¦"'#$15'ï+™'#$F'¬B0¤IÕçSo'#8#4'ÌŸ7åé±çÂMÂÆ'#$9D'Wà‹Í²u'''#$11'_Ü…'#$1A'û嫉”n@u`Ÿ`b7°á+$¢½JÿB¨¾±·‹Q''3'#$B'´WÇÎIÒz=ÄæÊ’¤E'#5'ÿç5'' $IJÑÛ†ŒÄ')
SBMessages.TElMessageSigner.FillSigner($68E73D8,$23627C0,'+'#$E#3#2#$1A,$68A58A4,20)
SBMessages.TElMessageSigner.SignPublicKey($68BE8D8,20,$5CCA108,1614,nil,nil,0,True)
SBMessages.TElMessageSigner.Sign($68BE8D8,20,$5CCA108,1614,True)
SBPDFSecurity.TElPDFPublicKeySecurityHandler.SignHashPKCS7((86, 102, 89, 81, 211, 252, 39, 234, 50, 72, 102, 124, 227, 45, 160, 202, 85, 83, 204, 194),0,20)
SBPDFSecurity.TElPDFPublicKeySecurityHandler.SignHash((86, 102, 89, 81, 211, 252, 39, 234, 50, 72, 102, 124, 227, 45, 160, 202, 85, 83, 204, 194),0,20)
SBPDF.TElPDFDocument.InsertActualSignatureInformation(False)
SBPDF.TElPDFDocument.Close(???)
PDFSignaturClassMod.TPDFSignerClass.InternalSignPDFdocument
PDFSignaturClassMod.TPDFSignerClass.SignPDF('c:\tmp\chp.pdf',0,True,$6906B70)
PDFSignaturDlg.TPDFSignaturDialog.actSignerExecute($59D0230)
Classes.TBasicAction.Execute
ActnList.TContainedAction.Execute
ActnList.TCustomAction.Execute
Classes.TBasicActionLink.Execute(???)
Controls.TControl.Click
AdvGlowButton.TAdvCustomGlowButton.Click
AdvGlowButton.TAdvCustomGlowButton.InternalClick
AdvGlowButton.TAdvCustomGlowButton.CMDialogKey((45061, 13, 0, 1835009, 0))
Controls.TControl.WndProc(???)
Controls.TWinControl.WndProc((45061, 13, 1835009, 0, 13, 0, 1, 28, 0, 0))
Controls.TWinControl.Broadcast((no value))
Controls.TWinControl.CMDialogKey(???)
Controls.TControl.WndProc(???)
Controls.TWinControl.WndProc((45061, 13, 1835009, 0, 13, 0, 1, 28, 0, 0))
Controls.TWinControl.Broadcast((no value))
Controls.TWinControl.CMDialogKey(???)


LS
#13743
Posted: 06/24/2010 04:55:58
by Ken Ivanov (EldoS Corp.)

Thank you for the details. Unfortunately, I have no idea about the reason for the issue. If the created signature is correct, the issue is likely to have something to do with CryptoAPI internals (there can actually occur exceptions of other types inside the deepest SignPKI() call, but not AV's).

Reply

Statistics

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