McAfee MEJCAE-AM-DA Product Guide - Page 48

Verifying a digital signature, Storing signed files: signing a file without encrypting

Page 48 highlights

Working with Digital Signatures Verifying a digital signature To create a separate, detached signature certificate file, combine the --detached modifier with the --sign option. You can optionally specify which private key to use to sign the file. ebs --sign --detached [--output ] [--sign-with ] For example: ebs --sign letter.txt --detached This instructs E-Business Server to produce a separate, detached signature certificate in a file named letter.txt.sig. The contents of letter.txt.sig are not appended to letter.txt. Verifying a digital signature To determine whether an attached digital signature is valid, you verify it. E-Business Server automatically verifies signatures as part of the decryption operation. If you want to verify a file, use the same syntax as that for decryption: ebs Verifying a detached signature When you attempt to process a detached signature certificate file, E-Business Server asks you to identify the corresponding text file. Once the text file is identified, E-Business Server checks the signature integrity. If you know that a signature is detached from a text file, you can specify both filenames on the command line: ebs For example: ebs letter.txt.sig letter.txt If the text file exists in the same directory as the detached signature certificate file, you can enter the following shortened command: ebs letter.txt.sig E-Business Server assumes that the signed text has the same name as the signature (.sig) file-if it does not, then you must specify the filename. Storing signed files: signing a file without encrypting If you sign a plaintext file without specifying encryption, E-Business Server compresses the file after you sign it. This makes the file unreadable to the casual human observer. This is a suitable way to store signed files in archival applications because it saves space. However, it is not an especially secure means for storing the data. Validity and trust Every user in a public key system is vulnerable to mistaking a phony key (certificate) for a real one. Validity is confidence that a public key certificate belongs to its purported owner. Validity is essential in a public key environment where you must constantly establish whether or not a particular certificate is authentic. When you've assured yourself that a key belonging to someone else is valid, you can sign the copy on your keyring to attest to the fact that you've checked the key and that it's an authentic one. If you want others to know that you gave the key your stamp of approval, you can export the signature to a certificate server so that others can see it. E-Business Server™ 8.6 Product Guide 46

  • 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

E-Business Server
8.6
Product Guide
46
Working with Digital Signatures
Verifying a digital signature
To create a separate, detached signature certificate file, combine the
--detached
modifier with the
--sign
option. You can optionally specify which private key to use to sign the file.
ebs --sign <plaintext_filename> --detached [--output <filename>] [--sign-with <your_userid>]
For example:
ebs --sign letter.txt --detached
This instructs E-Business Server to produce a separate, detached signature certificate in a file named
letter.txt.sig
. The contents of
letter.txt.sig
are not appended to
letter.txt
.
Verifying a digital signature
To determine whether an attached digital signature is valid, you
verify
it. E-Business Server automatically
verifies signatures as part of the decryption operation. If you want to verify a file, use the same syntax as
that for decryption:
ebs <filename>
Verifying a detached signature
When you attempt to process a detached signature certificate file, E-Business Server asks you to identify
the corresponding text file. Once the text file is identified, E-Business Server checks the signature integrity.
If you know that a signature is detached from a text file, you can specify both filenames on the command
line:
ebs <signature_filename.sig> <textfile.txt>
For example:
ebs letter.txt.sig letter.txt
If the text file exists in the same directory as the detached signature certificate file, you can enter the
following shortened command:
ebs letter.txt.sig
E-Business Server assumes that the signed text has the same name as the signature (
.sig
) file—if it does
not, then you must specify the filename.
Storing signed files: signing a file without encrypting
If you sign a plaintext file without specifying encryption, E-Business Server compresses the file after you
sign it. This makes the file unreadable to the casual human observer. This is a suitable way to store signed
files in archival applications because it saves space. However, it is not an especially secure means for storing
the data.
Validity and trust
Every user in a public key system is vulnerable to mistaking a phony key (certificate) for a real one.
Validity
is confidence that a public key certificate belongs to its purported owner. Validity is essential in a public key
environment where you must constantly establish whether or not a particular certificate is authentic.
When you’ve assured yourself that a key belonging to someone else is valid, you can sign the copy on your
keyring to attest to the fact that you’ve checked the key and that it’s an authentic one. If you want others
to know that you gave the key your stamp of approval, you can export the signature to a certificate server
so that others can see it.