EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Signature & QualifyingProperties

Also by EldoS: CallbackDisk
Create virtual disks backed by memory or custom location, expose disk images as disks and more.
#3924
Posted: 10/02/2007 08:34:53
by Nuno Guedes (Basic support level)
Joined: 08/13/2007
Posts: 87

Hi,

as i said in another topic, i am currently developing a system to sign documents.

During the ETSI TS 101 903 (1.3.2) analyse, i had some doubts.

In the QualifyingProperties element description (pag 22) it says
Code
The mandatory Target attribute MUST refer to the Id attribute of the corresponding ds:Signature. Its value
MUST be an URI with a bare-name XPointer fragment. When this element is enveloped by the XAdES signature, its
not-fragment part MUST be empty. Otherwise, its not-fragment part MAY NOT be empty.
The optional Id attribute can be used to make a reference to the QualifyingProperties container.


But in the xml created, all the qualifyingProperties elements have the target="", and the signatures dont have Id. ???

Another question is in relationship with the sentence " XAdES versions 1.1.1, 1.2.2 and 1.3.2 are supported.". The created xml have reference to "http://uri.etsi.org/01903/v1.1.1", can this be change to 1.3.2? how? it makes difference?

thanks
#3926
Posted: 10/02/2007 11:35:55
by Dmytro Bogatskyy (EldoS Corp.)

Quote
Another question is in relationship with the sentence " XAdES versions 1.1.1, 1.2.2 and 1.3.2 are supported.". The created xml have reference to "http://uri.etsi.org/01903/v1.1.1", can this be change to 1.3.2? how?

Please, see SimpleSigner demo:
XAdESSigner.XAdESVersion = SBXMLAdES.Unit.XAdES_v1_3_2
Quote
it makes difference?

Yes, different versions have a different namespace uri and different number of elements and required attributes. Also, there is a big difference for timestamp elements.
Schema and Technical Specification:
http://uri.etsi.org/01903/v1.1.1/
http://uri.etsi.org/01903/v1.1.1/ts_101903v010101p.pdf
http://uri.etsi.org/01903/v1.2.2/
http://uri.etsi.org/01903/v1.2.2/ts_101903v010202p.pdf
http://uri.etsi.org/01903/v1.3.2/
http://webapp.etsi.org/action/PU/2006...10302p.pdf

Quote
But in the xml created, all the qualifyingProperties elements have the target="", and the signatures dont have Id. ???

If I'm not mistaken, in version 1.1.1 this attribute is not required. I'll check this.
At the moment you can set this as following:
before call Signer.Save method do
Signer.Signature.ID = "Sig-0";
XAdESSigner.QualifyingProperties.Target = "#" + Signer.Signature.ID;
#3948
Posted: 10/04/2007 07:55:18
by Nuno Guedes (Basic support level)
Joined: 08/13/2007
Posts: 87

thanks Bogatskyy,

Quote
Bogatskyy wrote:
Please, see SimpleSigner demo: XAdESSigner.XAdESVersion = SBXMLAdES.Unit.XAdES_v1_3­_2

in the simplesigner i didn´t found reference to version attribute, but i did as you said and it works.

Quote
Bogatskyy wrote:
before call Signer.Save method do Signer.Signature.ID = "Sig-0"; XAdESSigner.QualifyingPro­perties.Target = "#" + Signer.Signature.ID;


yes, it works. i only did one thing different, instead of give a static ID i give the actual date time (binary format for dont be explicity) to get a dynamic and unique ID.

Code
Signer.Signature.ID = DateTime.Now.ToUniversalTime().ToBinary().ToString();
            xadesSigner.QualifyingProperties.Target = "#" + Signer.Signature.ID;


thanks one more time for the help

Reply

Statistics

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