ESYAE-imza Kütüphaneleri

Bu sayfa salt okunur. Kaynağı görebilirsiniz ama değiştiremezsiniz. Bunun yanlış olduğunu düşünüyorsanız yöneticiye danışın.

<h2>Signature Types</h2> <div class="level2"> </div> <h3>CAdES-BES</h3> <div class="level3"> <p> BES signature is the simplest type of electronic signature. As demonstrated in the figure, signature document only includes signed document, signed attributes and signature. It does not have any information about the signing time. Therefore it is not suitable for the documents that are required to be stored for a long time. The documents that are kept for a period of time that is longer than the validity period of the signing certificate should not be signed in BES format. Otherwise, the signatures can not be verified after the signing certificate gets expired. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:4.png" class="media" title="esya:eimza:4.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:4.png" class="mediacenter" title=" Figure 4 CAdES-BES Signature Structure" alt=" Figure 4 CAdES-BES Signature Structure" /></a> </p> </div> <h3>CAdES-EPES</h3> <div class="level3"> <p> CAdES-EPES is very similar to the BES type. As shown in the figure, the only difference is the additional signed attribute which indicates the signature policy. In order to use EPES signature type, you must create the signed document in accordance with a previously specified policy. The accordance of the signature with a specific policy can be verified by signature policy identifier (Signature Policy ID) included in the signature document. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:5.png" class="media" title="esya:eimza:5.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:5.png" class="mediacenter" title="Figure 5 CAdES-EPES Signature Structureı" alt="Figure 5 CAdES-EPES Signature Structureı" /></a> </p> </div> <h3>CAdES-T (Signature with Timestamp)</h3> <div class="level3"> <p> CAdES-t, as shown in the figure, is generated from BES or EPES signatures by adding a timestamp indicating the signing time. It is mandatory that the timestamp is taken from an authorized electronic certificate service provider in Turkey. Upon verification of the signature, the time in the timestamp is used as validation time. Timestamp guarantees that the signature is created before the time indicated by the timestamp. Lomgterm documents must at least be signed in CAdES-T format. It is recommended that the timestamp is taken just after the signing operation. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:6.png" class="media" title="esya:eimza:6.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:6.png" class="mediacenter" title="Figure 6 CAdES-T Signature Structure" alt="Figure 6 CAdES-T Signature Structure" /></a> </p> </div> <h3>CAdES-C (Signature with Reference Data to All Validation Data)</h3> <div class="level3"> <p> CAdES-C is generated from ES-T signature. The difference from ES-T is the additional reference information to validation data. This validation data includes CA and Sub-CA certificates of the signing certificate and CRL or OCSP response data for revocation status control of the signing certificate. As the word reference implies, the validation data itself not included in the signature document. Only uniquely defined reference values are added to the document. The validation data needs to be retrieved from external sources by using the referential information. For example, the external source may be a database storing certificates and crls with their referential information. Though there may be such cases that using ES-C format is acceptable, it is not a recommended signature format. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:7.png" class="media" title="esya:eimza:7.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:7.png" class="mediacenter" title="Figure 7 CAdES-C Signature Structure" alt="Figure 7 CAdES-C Signature Structure" /></a> </p> </div> <h3>CAdES-X-LONG (Extended Long Electronic Signature Type)</h3> <div class="level3"> <p> The signature of this format is generated from ES-C signature. The difference is that ES-X-Long signatures includes the validation data itself rather than only including referential information to validation data.This makes ES-X-Long signatures do not require any external system or data source in order to be verified. All the data to be used in the signature verification process is already included in the signature document which makes verification of ES-X-Long signatures very easy and portable. Thus it is the most recommended signature format especially the portability of the signature documents is an issue. ES-X-Long signatures can be created when the signing performed. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:8.png" class="media" title="esya:eimza:8.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:8.png" class="mediacenter" title="Figure 8 CAdES-X-LONG Signature Structure" alt="Figure 8 CAdES-X-LONG Signature Structure" /></a> </p> </div> <h3>CAdES-X-Type 1 (Extended Electronic Signature Type 1 Timestamped)</h3> <div class="level3"> <p> ES-X-Type 1 is also generated from the ES-C signature. First a timestamp for the whole content of the ES-C signature is taken and then the timestamp is added to the signature document which makes ES-C signature an ES-X-Type 1 signature. Timestamp is a protection over the referential information to validation data and indicates before when those reference values are added to the document. Since this format requires an additional timestamp, it is not a commonly used signature type. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:9.png" class="media" title="esya:eimza:9.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:9.png" class="mediacenter" title="Figure 9 CAdES-X-Type 1 Signature Structure" alt="Figure 9 CAdES-X-Type 1 Signature Structure" /></a> </p> </div> <h3>CAdES-X-Type 2 (Extended Electronic Signature Type 2 Timestamped)</h3> <div class="level3"> <p> It is very similer to the ES-X-Type 1. The only difference is the scope of the additional timestamp. Unlike Type 1, the timestamp is taken for only the referential data in the signature document rather than for the whole document. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:10.png" class="media" title="esya:eimza:10.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:10.png" class="mediacenter" title="Figure 10 CAdES-X-Type 2 Signature Structure" alt="Figure 10 CAdES-X-Type 2 Signature Structure" /></a> </p> </div> <h3>CAdES-X-Long-Type 1 or Type 2 (Extended Long Electronic Signature Type 1 veya Tip 2 Timestamped)</h3> <div class="level3"> <p> They are similar to CAdES-X-Type 1 and Type 2. Similar to the relation between ES-C and ES-X-Long signatures, ES-X-Long-Type 1 is the different form of ES-X-Type 1 where signature document contains the whole validation data not only the references. The same relation is valid between the ES-X-Long-Type 2 and ES-X-Type 2. </p> <p> Like ES-X-Long signatures, these formats include all signature verification data. Because of the additional timestamp ,it is not recommended for many cases. </p> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:11.png" class="media" title="esya:eimza:11.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:11.png" class="mediacenter" title=" Figure 11 CAdES-X-Long-Type 1 or Type 2 Signature Structure" alt=" Figure 11 CAdES-X-Long-Type 1 or Type 2 Signature Structure" /></a> </p> </div> <h3>CAdES-A (Archive Electronic Signature Type)</h3> <div class="level3"> <p> ES-A signature format is used, when the signature documents need to be stored for longer than the validity of the CA certificate or when the algorithms used for signing the document or in the signing certificate are seriously weakened by technological or scientific advances. </p> <p> Archive signatures can also be created without the above conditions arise and archiving must be repeated whenever the archive timestamp certificate expires. The applications supporting this signature format must have this maintenance infrastructure properly. </p> </div> <h4>CAdES-A with Archive Timestamp v2 Attribute</h4> <div class="level4"> <p> An ES-A signature with archive timestamp v2 attribute is created by taking an archive timestamp v2 for the following signature documents: </p> <ul> <li class="level1"> CAdES-X-Long</li> <li class="level1"> CAdES-X-Long-Type 1</li> <li class="level1"> CAdES-X-Long-Type 2 </li> </ul> <p> <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:12.png" class="media" title="esya:eimza:12.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:12.png" class="mediacenter" title="Figure 12 CAdES-A Signature with Archive Timestamp v2 Attribute Structure" alt="Figure 12 CAdES-A Signature with Archive Timestamp v2 Attribute Structure" /></a> </p> </div> <h4>CAdES-A with Archive Timestamp v3 Attribute</h4> <div class="level4"> <p> An ES-A signature with archive timestamp v3 attribute is created by taking an archive timestamp v3 for the any signature fromat. <a href="/esya-api/lib/exe/detail.php?id=en%3Aesya%3Aeimza%3Atipler&media=esya:eimza:atsv3.png" class="media" title="esya:eimza:atsv3.png"><img src="/esya-api/lib/exe/fetch.php?media=esya:eimza:atsv3.png" class="mediacenter" title="Figure 13 CAdES-A Signature with Archive Timestamp v3 Attribute Structure" alt="Figure 13 CAdES-A Signature with Archive Timestamp v3 Attribute Structure" /></a> </p> </div>