aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormaxigas <maxigas@anargeek.net>2013-04-11 19:13:05 +0200
committermaxigas <maxigas@anargeek.net>2013-04-11 19:13:05 +0200
commit7466a710c2333b36eb3b687783efa9a979db4961 (patch)
tree199dba573ead8dcf44bd7b8de2c6d1e3cfcfd201
parent27d1c46fc83808b90aac3e6467c3aec1ab527bd7 (diff)
downloadpolicy-7466a710c2333b36eb3b687783efa9a979db4961.tar.gz
policy-7466a710c2333b36eb3b687783efa9a979db4961.tar.bz2
small change
-rw-r--r--best_practices.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/best_practices.mdwn b/best_practices.mdwn
index 974261a..9349779 100644
--- a/best_practices.mdwn
+++ b/best_practices.mdwn
@@ -47,7 +47,7 @@ b. CaCert: Users still need to validate and install CaCert's root certificates b
c. Self Signed certificates/Own Authority: con: not included in the default mail user clients of your users. They have to install the (root-)certificates. If they don't use certificate pinning and have other commercial authorities still installed you win nothing but confusion. You risk to teach your users into bypassing security warning messages. If properly applied by your collective of crypto-ninjas, it *can* be more secure.
-d. Monkeysphere: You can use openPGP keys (certifications) to authenticate services. This is technically an excellent solution, albeit not really supported in popular software. If you have power users, we recommend trying it out. More information on http://monkeysphere.info/
+d. Monkeysphere: You can use openPGP keys (certifications) to authenticate services. This is technically an excellent solution, albeit not really supported in popular software. If you have power users, we recommend trying it out. More information on [Monkeysphere website](http://monkeysphere.info/)
### Level 2