web commit by joey

diff --git a/doc/security.mdwn b/doc/security.mdwn
index 3c85f57de39d8a8aadf5bf7d3823556506c5737b..e514223e378573f23fa6866bec46d0c5d2f7c5b8 100644 (file)
--- a/doc/security.mdwn
+++ b/doc/security.mdwn
@@ -6,6 +6,8 @@ security issues with this program than with cat(1). If, however, you let
 others edit pages in your wiki, then some possible security issues do need
 to be kept in mind.
 
 others edit pages in your wiki, then some possible security issues do need
 to be kept in mind.
 

+----
+

 # Probable holes
 
 ## XSS holes in CGI output
 # Probable holes
 
 ## XSS holes in CGI output


@@ -39,7 +41,7 @@ ikiwiki escapes any html in svn commit logs to prevent other mischief.
 
 # Potential gotchas
 
 
 # Potential gotchas
 

-Things not to do.
+_(Things not to do.)_

 
 ## multiple accessors of wiki directory
 
 
 ## multiple accessors of wiki directory
 


@@ -72,7 +74,7 @@ they can try to use this to exploit your web server.
 
 # Hopefully non-holes
 
 
 # Hopefully non-holes
 

-(AKA, the assumptions that will be the root of most security holes...)
+_(AKA, the assumptions that will be the root of most security holes...)_

 
 ## exploting ikiwiki with bad content
 
 
 ## exploting ikiwiki with bad content
 


@@ -128,6 +130,8 @@ Login to the wiki involves sending a password in cleartext over the net.
 Cracking the password only allows editing the wiki as that user though.
 If you care, you can use https, I suppose.
 
 Cracking the password only allows editing the wiki as that user though.
 If you care, you can use https, I suppose.
 

+----
+

 # Fixed holes
 
 _(Unless otherwise noted, these were discovered and immediatey fixed by the
 # Fixed holes
 
 _(Unless otherwise noted, these were discovered and immediatey fixed by the