summaryrefslogtreecommitdiff
path: root/doc/Certificates.txt
blob: 6a71526ee6e0ee030e5686b5807f18007aa7c8e2 (plain)
  1. Public Key Infrastructure (PKI)
  2. ===============================
  3. Hosts
  4. -----
  5. Host certificates can be either self-signed or signed by a CA. The
  6. private key can be either embedded into the same file as the certificate
  7. or in a separate file.
  8. The simplest form is a self-signed certificate with null-password
  9. embedded key.
  10. Self-signed host certificates contain both certificate and key in same
  11. file. The file is placed in /etc/ssl/certs/ named by the service it
  12. provides appended ".pem".
  13. CA signed host certificates , or symlinked with that name from
  14. hostname.key or whatever makes best sense in the situation, either with
  15. the key embedded or the key at the same place.
  16. The script /usr/share/local/localmksslcerts can be used to make
  17. self-signed certificates with embedded keys.
  18. Certificate Authority
  19. ---------------------
  20. CA Certificates are divided in a public certificate and a private key.
  21. The CA certificate is placed in /etc/ssl/certs/ and named loosely by the
  22. CN of the organisation using digits [a-zA-Z0-9_-], appended "_CA.pem".
  23. Example: IT_guide_dr_Jones_CA.pem
  24. CA Key is located in /etc/ssl/private/ equally named.
  25. Certificate is symlinked to "/etc/ssl/certs/cacert.pem" for easy
  26. locating by scripts.
  27. Read here about confusion between commercial CAs and actual security:
  28. http://www.counterpane.com/pki-risks.html
  29. Users
  30. -----
  31. Have a look at this web page:
  32. http://www.cise.ufl.edu/help/secure-access/ssl-mail-setup.shtml
  33. The script is at /usr/share/local/mycert - adapted to Debian GNU/Linux.
  34. --
  35. $Id: Certificates.txt,v 1.2 2002-12-28 02:03:20 jonas Exp $