summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorbeck <beck@openbsd.org>2000-10-24 21:50:24 +0000
committerbeck <beck@openbsd.org>2000-10-24 21:50:24 +0000
commitac73e718ee4aca07ef0a49ff42da3b89f86a8ab2 (patch)
treeec5a4697bfc966b0e20bfce231723e05c81fc5e3
parentDuh, C_WAIT will always be set if the card is inactive, but that interrupt (diff)
downloadwireguard-openbsd-ac73e718ee4aca07ef0a49ff42da3b89f86a8ab2.tar.xz
wireguard-openbsd-ac73e718ee4aca07ef0a49ff42da3b89f86a8ab2.zip
Add the punchline to the procedure for making web server certificates
to indicate that people should test their server with a self signed certificate, then simply replace the certificate with a real one to go production.
-rw-r--r--share/man/man8/ssl.813
1 files changed, 12 insertions, 1 deletions
diff --git a/share/man/man8/ssl.8 b/share/man/man8/ssl.8
index cd1111c0b6b..285b6a1482d 100644
--- a/share/man/man8/ssl.8
+++ b/share/man/man8/ssl.8
@@ -172,7 +172,18 @@ with the
.Ar -DSSL
flag, enabling
.Ar https
-transactions with your machine on port 443.
+transactions with your machine on port 443.
+.Pp
+You will most likely want to generate a self-signed certificate in the
+manner above along with your certificate signing request to test your
+server's functionality even if you are going to have the certificate
+signed by another Certifying Authority. Once your Certifying
+Authority returns the signed certificate to you, you can switch to
+using the new certificate by replacing the self-signed
+.Pa /etc/ssl/server.crt
+with the certificate signed by your Certifying Authority, and then
+restarting
+.Xr httpd 8
.Sh BUGS
.Pp
The world needs more