summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorPliablePixels <pliablepixels@gmail.com>2015-06-25 16:50:43 -0400
committerPliablePixels <pliablepixels@gmail.com>2015-06-25 16:50:43 -0400
commit1fe8b6ca69fe575bb3433502c8a179f3250264da (patch)
tree33f993aca125aa98e9a4d05057e8e98c2129b5d0 /docs
parent9d95a27ad0db82ce048fd5e4862421e7d6fa9e62 (diff)
SSL configuration instructions
Diffstat (limited to 'docs')
-rw-r--r--docs/SSL-Configuration.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/SSL-Configuration.md b/docs/SSL-Configuration.md
index c3c06d8e..36969289 100644
--- a/docs/SSL-Configuration.md
+++ b/docs/SSL-Configuration.md
@@ -1,13 +1,13 @@
-***SSL Configuration notes
+##SSL Configuration notes
If your Zoneminder instance has SSL configured and you need zmNinja to connect to ZM over SSL you need to:
1) Make sure you generate the certificates correctly
2) Import the certificate into iOS and Android
-****Certificate generation
+###Certificate generation
-*****Self-signed certificates
+####Self-signed certificates
If you are using self signed certificated, you should make sure the "common name" matches the hostname (or public IP)
of the server you are installing ZM in. If not, zmNinja's SSL handshake will fail.
@@ -44,5 +44,5 @@ iOS and Android. Make sure you install it and go through the prompts
Once you are done with these steps, zmNinja should be able to connect to ZM via SSL. Make sure you select SSL in the settings
-*****CA signed certificates
-If you purchase a signed certificate, or set up your own root CA zmNinja should just work over SSL. I haven't tried it so far.
+####CA signed certificates
+If you purchase a signed certificate, or set up your own root CA zmNinja should just work over SSL. I haven't tried it so far.