summaryrefslogtreecommitdiff
path: root/mail/exim-old/files/patch-..::exim-texinfo-3.30::doc::spec.texinfo
blob: 824276f27f63b5f3678b2ad88816069c601997e8 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
--- ../exim-texinfo-3.30/doc/spec.texinfo.orig	Tue Jun 12 12:20:49 2001
+++ ../exim-texinfo-3.30/doc/spec.texinfo	Tue Jan 15 17:19:46 2002
@@ -20785,6 +20785,19 @@
 may be adequate for all your requirements if you are mainly interested in
 encrypting transfers, and not in secure identification.
 
+However, many clients require that the certificate presented by Exim be a user
+(also called "leaf" or "site") certificate, and not a self-signed certificate.
+In this case, the self-signed certificate described above must be installed on
+the client host as a trusted root certification authority and the certificate
+used by Exim must be a user certificate signed with that self-signed
+certificate.
+
+For information on creating self-signed CA certificates and using them to sign
+user certificates, see the "General implementation overview" chapter of the
+Open-source PKI Book, available online at:
+
+http://ospkibook.sourceforge.net/
+