From 3466bf833859290d219f302e83dd92e745cdfac4 Mon Sep 17 00:00:00 2001 From: david Date: Fri, 27 Aug 2010 04:01:50 +0000 Subject: [PATCH] Add a note about how the OpenVAS feed works. --- todo/nmap.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/todo/nmap.txt b/todo/nmap.txt index 2b2bbdd91..89e60f8a2 100644 --- a/todo/nmap.txt +++ b/todo/nmap.txt @@ -206,7 +206,8 @@ o Consider an update feed system for Nmap which let's people obtain separate branch for each release that gets updated version/OS databases and scripts. o Another approach is a special feed system as is used by Nessus and - OpenVAS. I haven't looked in detail at how those work. + OpenVAS. OpenVAS uses a script wrapper around rsync, or an HTTP + download if that fails. o The latest IANA services file (http://www.iana.org/assignments/port-numbers) has many identified