Adobe 22002486 Digital Signature User Guide - Page 157

Export, Email the data to someone, Save the exported data to a file, Do not sign

Page 157 highlights

Acrobat 9 Family of Products Security Feature User Guide Migrating and Sharing Security Settings Exporting Application Settings with FDF Files 157 Figure 115 Selecting a certificate chain for export 6. Choose Export. 7. Choose one of the following:  Email the data to someone: Emailing the data automatically creates an FDF file that other Adobe product users can easily import.  Save the exported data to a file: Acrobat FDF Data Exchange. FDF is a format recognized by the Acrobat family of products. 8. Choose Next. 9. (Optional) If the Identity Information dialog appears, enter the your email address and any other information. If you have already configured your identity details, this screen may not appear. For details, see "Setting Identity Information" on page 14. 10. Do not sign if the certificate you use to sign uses the same trust anchor or you are distributing. Since recipients do not have this certificate yet, they will not be able to validate your signature. Note: Signing the FDF will only be useful if you have a digital ID that the recipient has already trusted (uses a trust anchor OTHER than the one you are currently distributing). The FDF file recipients must also already have that digital IDs certificate so that they can validate your signature without relying on the certificate you are currently sending. This workflow is uncommon, but it does allow recipients to automatically inherit your predefined trust settings for the certificate embedded in the file. 11. Choose Next.

  • 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
Migrating and Sharing Security Settings
Security Feature User Guide
Exporting Application Settings with FDF Files
157
Figure 115
Selecting a certificate chain for export
6.
Choose
Export
.
7.
Choose one of the following:
Email the data to someone
: Emailing the data automatically creates an FDF file that other Adobe
product users can easily import.
Save the exported data to a file
: Acrobat FDF Data Exchange. FDF is a format recognized by the
Acrobat family of products.
8.
Choose
Next
.
9.
(
Optional
) If the Identity Information dialog appears, enter the your email address and any other
information. If you have already configured your identity details, this screen may not appear. For
details, see
“Setting Identity Information” on page 14
.
10.
Do not sign
if the certificate you use to sign uses the same trust anchor or you are distributing. Since
recipients do not have this certificate yet, they will not be able to validate your signature.
Note:
Signing the FDF will only be useful if you have a digital ID that the recipient has already trusted
(uses a trust anchor OTHER than the one you are currently distributing). The FDF file recipients
must also already have that digital IDs certificate so that they can validate your signature
without relying on the certificate you are currently sending. This workflow is uncommon, but it
does allow recipients to automatically inherit your predefined trust settings for the certificate
embedded in the file.
11.
Choose
Next
.