aboutsummaryrefslogtreecommitdiffstats
path: root/doc/apps/smime.pod
diff options
context:
space:
mode:
Diffstat (limited to 'doc/apps/smime.pod')
-rw-r--r--doc/apps/smime.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/apps/smime.pod b/doc/apps/smime.pod
index caf2d2689e62..1b0d4f95392a 100644
--- a/doc/apps/smime.pod
+++ b/doc/apps/smime.pod
@@ -300,7 +300,7 @@ Create a cleartext signed message:
openssl smime -sign -in message.txt -text -out mail.msg \
-signer mycert.pem
-Create and opaque signed message
+Create and opaque signed message:
openssl smime -sign -in message.txt -text -out mail.msg -nodetach \
-signer mycert.pem
@@ -349,11 +349,11 @@ it with:
-----BEGIN PKCS7-----
-----END PKCS7-----
-and using the command,
+and using the command:
openssl smime -verify -inform PEM -in signature.pem -content content.txt
-alternatively you can base64 decode the signature and use
+Alternatively you can base64 decode the signature and use:
openssl smime -verify -inform DER -in signature.der -content content.txt
@@ -373,7 +373,7 @@ should be some heuristic that determines the correct encryption certificate.
Ideally a database should be maintained of a certificates for each email address.
The code doesn't currently take note of the permitted symmetric encryption
-algorithms as supplied in the SMIMECapabilities signed attribute. this means the
+algorithms as supplied in the SMIMECapabilities signed attribute. This means the
user has to manually include the correct encryption algorithm. It should store
the list of permitted ciphers in a database and only use those.