Bu sayfanın seçili sürümü ile mevcut sürümü arasındaki farkları gösterir.
en:esya:cades:imza-tipleri [2013/08/29 13:02] Dindar Öz |
en:esya:cades:imza-tipleri [2014/01/21 09:41] (mevcut) Beytullah Yiğit [ESA] |
||
---|---|---|---|
Satır 85: | Satır 85: | ||
get unreliable after 10 years.The signatures must be converted to ESA type before the signatur algorithm becomes insecure. When converting to ESA, the signature algorithm must be changed with more secure ones. This process must be repeated whenever the current signature algorithm starts to be considered as weakened. | get unreliable after 10 years.The signatures must be converted to ESA type before the signatur algorithm becomes insecure. When converting to ESA, the signature algorithm must be changed with more secure ones. This process must be repeated whenever the current signature algorithm starts to be considered as weakened. | ||
- | Another reason for converting a signature to ESA may be to lock the signature tree so that no new signature can be added or none of the the existing ones can be removed. | + | Another reason for converting a signature to ESA may be to prevent signature modification. ESA protects all counter signatures which held as countersignature attributes of the signature. Hence counter signatures do not require independent archive time-stamps. If any counter signature exists, it cannot be upgraded or removed from signature tree. In CAdES-A with archive timestamp v2 attribute, no new counter signature or validation data can be added too. In CAdES-A with archive timestamp v3 attribute, these addition are allowed. |
ESA can not be created from scratch. Firstly, a signature of another signature type must be created then it can be converted to ESA. During this conversion archival type timestamp is used. | ESA can not be created from scratch. Firstly, a signature of another signature type must be created then it can be converted to ESA. During this conversion archival type timestamp is used. |