EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Distributed Signing Word 2013 document

Also by EldoS: RawDisk
Access locked and protected files in Windows, read and write disks and partitions and more.
#25540
Posted: 07/04/2013 14:43:36
by Dmytro Bogatskyy (EldoS Corp.)

Quote
The problems is that if we try to sign existing signatureline, then InitiateAsyncSign() starts throwing exception.

Thank you for the sample.
What exactly exception did you get? Also, could you please post a sample document here or to helpdesk.
Quote
Furthermore, the signing process is taking a lot of time as well.

If you are using a trial key then a 95-99% is a time delay.
You can request the time-limited key, which removes time delays and the nag screen, using the web form on http://www.eldos.com/sbb/keyreq/
#25552
Posted: 07/05/2013 09:13:06
by Jahangir Shah (Basic support level)
Joined: 06/25/2013
Posts: 18

Quote

What exactly exception did you get? Also, could you please post a sample document here or to help desk.


Exception:
Code
Cann't apply C14N transform to binary data. (XML parse error at position 1 (0x1): TElXMLDOMDocument: element expected)

SBXMLDefs.EElXMLTransformError was unhandled
  HResult=-2146233088
  Message=Cann't apply C14N transform to binary data. (XML parse error at position 1 (0x1): TElXMLDOMDocument: element expected)
  Source=SecureBlackbox.XMLSecurity
  ErrorCode=0
  StackTrace:
       at SBXMLTransform.TElXMLC14NTransform.TransformData(Byte[] Data) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\XML\SBXMLTransform.pas:line 1764
       at SBXMLTransform.TElXMLTransformChain.TransformData(Byte[] Data, TElXMLDOMNode Node, TElXMLDOMNodeList Nodes, TElXMLDOMNode ReferenceNode, TElXMLDOMNode[] ReferenceNodes, Int16 CanonicalizationMethod) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\XML\SBXMLTransform.pas:line 1114
       at SBXMLTransform.TElXMLTransformChain.TransformData(Byte[] Data, Int16 CanonicalizationMethod) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\XML\SBXMLTransform.pas:line 1162
       at SBXMLSec.TElXMLReference.ProcessData(TElHashFunction HashFunc, Int16 CanonicalizationMethod) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\XML\SBXMLSec.pas:line 2387
       at SBXMLSec.TElXMLReference.ProcessData(TElHashFunction HashFunc) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\XML\SBXMLSec.pas:line 2331
       at SBXMLSec.TElXMLReference.UpdateDigestValue(TElCustomCryptoProviderManager Manager, TElCustomCryptoProvider Prov) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\XML\SBXMLSec.pas:line 2436
       at SBOfficeSecurity.TElOfficeOpenXMLSignedPart.CalculateDigest(TElXMLReference Ref) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\Office\SBOfficeSecurity.pas:line 7575
       at SBOfficeSecurity.TElOfficeOpenXMLBaseSignatureHandler.InternalSign(TElXMLKeyInfoData KeyData, Int16 SignatureMethod, Boolean IncludeKey) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\Office\SBOfficeSecurity.pas:line 8786
       at SBOfficeSecurity.TElOfficeOpenXMLBaseSignatureHandler.Sign(TElX509Certificate Certificate, TSBOfficeOpenXMLEmbedCertificate EmbedCertificate) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\Office\SBOfficeSecurity.pas:line 9212
       at SBOfficeSecurity.TElOfficeOpenXMLBaseSignatureHandler.Sign(TElX509Certificate Certificate) in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\Office\SBOfficeSecurity.pas:line 9120
       at SBOfficeSecurity.TElOfficeOpenXMLBaseSignatureHandler.InitiateAsyncSign() in d:\Work\SecureBlackbox\PackagesChrome\Files\..\..\Sources\Office\SBOfficeSecurity.pas:line 8659
       at Tester.MySigner.PreSign(Int32 signatureLineNumber, Boolean signDocument, Boolean signProperties) in D:\Ascertia\Products\AscertiaDocs\RnDs\MS Word Signing\ELDos\XAdES WordSample\ASPNet_Distributed\Tester\Program.cs:line 127
       at Tester.MySigner.doSign() in D:\Ascertia\Products\AscertiaDocs\RnDs\MS Word Signing\ELDos\XAdES WordSample\ASPNet_Distributed\Tester\Program.cs:line 49
       at Tester.Program.Main(String[] args) in D:\Ascertia\Products\AscertiaDocs\RnDs\MS Word Signing\ELDos\XAdES WordSample\ASPNet_Distributed\Tester\Program.cs:line 27
       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException:


Document: Any MS word 2007+ document with a signature line can be used. Nevertheless, we are attaching the sample we have been using here.
NOTE: WE HAVE CHANGED THE ATTACHED FILE's EXTENSION TO TXT, PLEASE CHANGE THE EXTENSION BACK TO DOCX.

Quote

If you are using a trial key then a 95-99% is a time delay.
You can request the time-limited key, which removes time delays and the nag screen, using the web form on http://www.eldos.com/sbb/keyreq/

We'll look into it.

Kindly let us know if you need any more info. Thanks


[ Download ]
#25591
Posted: 07/09/2013 11:31:14
by Dmytro Bogatskyy (EldoS Corp.)

Thank you for the sample and detailed log.

This issue should be fixed for the next build. The component incorrectly select a canonicalization method for embedded resources. This issue is present only in beta 11 version (version 10 should correctly sign those files, however it lack some features for distributed signing).
#25601
Posted: 07/10/2013 01:07:22
by Jahangir Shah (Basic support level)
Joined: 06/25/2013
Posts: 18

Thanks Dmytro. Can you, kindly tell us when we can expect the corrected sample?

Thanks.
#25615
Posted: 07/10/2013 15:00:44
by Dmytro Bogatskyy (EldoS Corp.)

Quote
Can you, kindly tell us when we can expect the corrected sample?

Usually, new build is released within a month after the last one.
#25624
Posted: 07/11/2013 00:43:29
by Jahangir Shah (Basic support level)
Joined: 06/25/2013
Posts: 18

Quote
Usually, new build is released within a month after the last one.


The last release we had of Eldos SDK was "SecureBlackbox - version 10.0.233 - Released February 28, 2013". Is this the last release of SecureBlackBox?

Can you give us some guesstimate for the next release?

Also, we sent you a sample console app implementing MS Word distributed signing with some issues. Should we expect a working version of that sample along with the new release as well?

Thanks
#25647
Posted: 07/11/2013 10:17:26
by Ken Ivanov (EldoS Corp.)

Hello Jahangir,

Quote
The last release we had of Eldos SDK was "SecureBlackbox - version 10.0.233 - Released February 28, 2013". Is this the last release of SecureBlackBox?

That is the latest stable version. The latest beta version is currently 11.0.237, released about a week ago.

Quote
Can you give us some guesstimate for the next release?

The next pre-release version is likely to be available by the end of July. If you would like to get the fix that Dmytro was talking about sooner (once it is technically read), we will probably be able to compile an SVN snapshot assembly for you, so that you could go on with the evaluation without waiting for the official product update. Just let us know.

Quote
Also, we sent you a sample console app implementing MS Word distributed signing with some issues. Should we expect a working version of that sample along with the new release as well?

I'm leaving this question up to Dmytro. He will answer you shortly.
#25654
Posted: 07/11/2013 12:25:23
by Dmytro Bogatskyy (EldoS Corp.)

Quote
Also, we sent you a sample console app implementing MS Word distributed signing with some issues. Should we expect a working version of that sample along with the new release as well?

Yes, it should work. But, you would need to slightly modify it to create XAdES-X-L form.
#25664
Posted: 07/12/2013 04:57:36
by Jahangir Shah (Basic support level)
Joined: 06/25/2013
Posts: 18

Quote
The next pre-release version is likely to be available by the end of July. If you would like to get the fix that Dmytro was talking about sooner (once it is technically read), we will probably be able to compile an SVN snapshot assembly for you, so that you could go on with the evaluation without waiting for the official product update. Just let us know.


Yes, it would be good to have the files earlier if possible. thanks

Quote
Yes, it should work. But, you would need to slightly modify it to create XAdES-X-L form.

Dmytro, is it possible that you do those X-L related modifications for us? This will save us a lot of time, and we would be able to finish the evaluation process quickly. Thanks
#25689
Posted: 07/16/2013 00:17:43
by Jahangir Shah (Basic support level)
Joined: 06/25/2013
Posts: 18

Hi Ken & Dmytro,

Just wanted to know if there is any update on the (XAdES-X-L) sample? Kindly, let us know as soon as possible. Thanks.
Also by EldoS: BizCrypto
Components for BizTalk® and SQL Server® Integration Services that let you securely store and transfer information in your business automation solutions.

Reply

Statistics

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