Adobe 22002486 Digital Signature User Guide - Page 79

Specifying a Signature Hash Algorithm, Embedding Revocation Information in a Signature

Page 79 highlights

Acrobat 9 Family of Products Security Feature User Guide Controlling Signing with Seed Values Specifying a Signature Hash Algorithm 79 5.8 Specifying a Signature Hash Algorithm When a signer's digital ID contains RSA public and private keys, it is possible to specify alternative signature hash algorithms. The default algorithm is SHA1, and the alternatives are listed in Table 8. User interface impact: Once a document is signed, the signature's hash algorithm can be viewed by right clicking on a signature, choosing Show Signature Properties, and displaying the Document tab. The algorithm is displayed in the Hash Algorithm field. Caution: If a signer may be using FIPS mode, do NOT specify MD5 or RIPMD160. To specify a non-default algorithm: 1. Create a signature field with an intuitive name and tooltip. 2. Create the JavaScript that gets the field object and uses the seed value method (Example 5.7). 3. Specify the digestMethod. This can be an array of comma-separated items such as ['RIPEMD160','SHA384']. 4. Run the JavaScript, save the document, and test the field. Example 5.7 Hash algorithm seed value // Obtain the signature field object: var f = this.getField("mySigFieldName"); f.signatureSetSeedValue({ digestMethod:['SHA384'] }); 5.9 Embedding Revocation Information in a Signature Users (signers) have the option to embed certificate revocation status in a signature by turning on Include signature's revocation status when signing in their preferences. However, the default value is false (revocation information is not embedded), and document authors may need to force embedding of revocation information regardless of the users application settings. Embedding the signing certificate's revocation status in a document allows recipients to validate certificates (signatures) while offline and speeds up the revocation checking process. Moreover, if a certificate is revoked or expired at some time after signing, embedded revocation information enables the application to determine if a certificate was valid at the time of signing so that the signature status will remain valid. Note: Only relevant if subFilter is adbe.pkcs7.detached or adbe.pkcs7.sha1. If the subFilter is adbe.x509.rsa_sha1 and adding revocation information is required, the signing operation fails. To force embedding of certificate revocation information in a signature: 1. Create a signature field with an intuitive name and tooltip. 2. Create the JavaScript that gets the field object and uses the seed value method (Example 5.7). 3. Set shouldAddRevInfo to true.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189

Acrobat 9 Family of Products
Controlling Signing with Seed Values
Security Feature User Guide
Specifying a Signature Hash Algorithm
79
5.8
Specifying a Signature Hash Algorithm
When a signer’s digital ID contains RSA public and private keys, it is possible to specify alternative
signature hash algorithms. The default algorithm is SHA1, and the alternatives are listed in
Table 8
.
User interface impact
: Once a document is signed, the signature’s hash algorithm can be viewed by right
clicking on a signature, choosing
Show Signature Properties
, and displaying the Document tab. The
algorithm is displayed in the Hash Algorithm field.
Caution:
If a signer may be using FIPS mode, do NOT specify MD5 or RIPMD160.
To specify a non-default algorithm:
1.
Create a signature field with an intuitive name and tooltip.
2.
Create the JavaScript that gets the field object and uses the seed value method (
Example 5.7
).
3.
Specify the
digestMethod
. This can be an array of comma-separated items such as
['RIPEMD160','SHA384']
.
4.
Run the JavaScript, save the document, and test the field.
Example 5.7
Hash algorithm seed value
// Obtain the signature field object:
var f = this.getField("mySigFieldName");
f.signatureSetSeedValue({
digestMethod:['SHA384']
});
5.9
Embedding Revocation Information in a Signature
Users (signers) have the option to embed certificate revocation status in a signature by turning on
Include
signature’s revocation status when signing
in their preferences. However, the default value is false
(revocation information is not embedded), and document authors may need to force embedding of
revocation information regardless of the users application settings. Embedding the signing certificate’s
revocation status in a document allows recipients to validate certificates (signatures) while offline and
speeds up the revocation checking process. Moreover, if a certificate is revoked or expired at some time
after signing, embedded revocation information enables the application to determine if a certificate was
valid at the time of signing so that the signature status will remain valid.
Note:
Only relevant if subFilter is adbe.pkcs7.detached or adbe.pkcs7.sha1. If the subFilter is
adbe.x509.rsa_sha1 and adding revocation information is required, the signing operation fails.
To force embedding of certificate revocation information in a signature:
1.
Create a signature field with an intuitive name and tooltip.
2.
Create the JavaScript that gets the field object and uses the seed value method (
Example 5.7
).
3.
Set
shouldAddRevInfo
to true.