[Pkg-owncloud-commits] [owncloud-doc] 04/38: better handling of custom certificates

[David Prévot]

This is an automated email from the git hooks/post-receive script.

taffit pushed a commit to branch master
in repository owncloud-doc.

commit 6de76cc3b198713954d62b5aa7f37940690e511f
Author: adorableGNU <adorablegnu at hushmail.com>
Date:   Wed Oct 15 18:50:31 2014 +0200

    better handling of custom certificates
    
    I followed your steps to setup webdav via command-line. I also use a custom certificate and thought, that it is a bad idea to not check the fingerprint of the certificate. I solved it, by addressing the "pem"-file in the configuration. I think this is a far better solution.
    
    Regards
---
 user_manual/files/files.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/user_manual/files/files.rst b/user_manual/files/files.rst
index 810610e..d3bb64a 100644
--- a/user_manual/files/files.rst
+++ b/user_manual/files/files.rst
@@ -106,9 +106,10 @@ Known Issues
 
 **Problem:** Certificate warnings
 
-**Solution:** If you use a self-signed certificate, you will get a warning. If you are willing to take the risk of a man in the middle attack, run this command instead::
-
-    echo "y" | mount ~/owncloud > /dev/null 2>&1
+**Solution:** If you use a self-signed certificate, you will get a warning. To change this, you need to adress the "pem"-file of your certificate. 
+At first copy ``mycertificate.pem`` to  - for example - ``/etc/davfs2/certs/``. After that edit :file:`/etc/davfs2/davfs2.conf` and uncomment the line ``servercert`` (or add it). 
+Now add the path of your certificate. In this this example::
+    servercert   /etc/davfs2/certs/mycertificate.pem
 
 Accessing Files Using MAC OSX
 -----------------------------

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-owncloud/owncloud-doc.git