From 48e21b7675e8844a4c3ccadaccd72ef56a8a32c9 Mon Sep 17 00:00:00 2001
From: david <david@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Tue, 13 Dec 2011 03:34:31 +0000
Subject: [PATCH] Update SVN installation instructions for new HTTPS repo
 location.

---
 docs/nmap-install.xml | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/docs/nmap-install.xml b/docs/nmap-install.xml
index 7b542b88d..9498df57d 100644
--- a/docs/nmap-install.xml
+++ b/docs/nmap-install.xml
@@ -252,15 +252,13 @@ hasn't yet been formally released.</para>
 <para>
 SVN write access is strictly limited to top Nmap
 developers, but everyone has read access to the repository.  Check out
-the latest code using the command <command>svn co --username guest
---password "" svn://svn.insecure.org/nmap/</command>.  Then you can later
+the latest code using the command <command>svn co
+https://svn.nmap.org/nmap</command>. Then you can later
 update your source code by typing <command>svn up</command> in your
-working directory.  The <quote>guest</quote> username is required due to an svnserve authorization bug.</para>
+working directory.</para>
 
 <para>While most users only follow the <filename>/nmap</filename>
-directory in svn (which pulls
-in <filename>/nbase</filename>, <filename>/nsock</filename>,
-and <filename>/zenmap</filename> on its own), there is one other
+directory in svn, there is one other
 interesting directory: <filename>/nmap-exp</filename>.  This directory
 contains <emphasis>experimental</emphasis> Nmap branches which Nmap
 developers create when they wish to try new things without