mirror of
https://github.com/nmap/nmap.git
synced 2025-12-17 05:09:00 +00:00
some changes from a meeting with David today
This commit is contained in:
@@ -8,12 +8,37 @@ o Decide what to do about Nmap static binaries failing to work on new
|
|||||||
o Fix our mac builds so that they contain SSL support again (5.35DC1
|
o Fix our mac builds so that they contain SSL support again (5.35DC1
|
||||||
did, but TEST1 and TEST2 didn't for some reason.
|
did, but TEST1 and TEST2 didn't for some reason.
|
||||||
|
|
||||||
o Do another Nmap test/dev release
|
o Add our broadcast discovery scripts to a "broadcast" category (they
|
||||||
|
should generally just be in "broadcast" and (assuming they are safe)
|
||||||
o Process Nmap survey and send out results [Fyodor]
|
"safe", and not normal "discovery". Update scripting.xml to note
|
||||||
|
this new category too.
|
||||||
|
|
||||||
o Update changelog to note recent changes
|
o Update changelog to note recent changes
|
||||||
|
|
||||||
|
o Do final dev/test release
|
||||||
|
|
||||||
|
o [Ncat] Make --exec work in conjunction with --proxy. The --proxy
|
||||||
|
code path skips the --exec code. See
|
||||||
|
http://seclists.org/nmap-dev/2010/q4/604 and the test "--exec
|
||||||
|
through proxy" in ncat-test.pl.
|
||||||
|
|
||||||
|
==STUFF WE WANT IN STABLE RELEASE ABOVE THIS LINE==
|
||||||
|
|
||||||
|
o The -V option to Nmap, in addition to reporting the version number,
|
||||||
|
should give details on how Nmap was compiled and the environment it
|
||||||
|
is running on. This includes things like whether SSL is enabled,
|
||||||
|
the platform string, versions of libraries it is linked to, and
|
||||||
|
other stuff which is often useful in debugging problems.
|
||||||
|
|
||||||
|
o If Nping is compiled w/o SSL support, and the user specifies an
|
||||||
|
encryption key, it should fail and insist they use --no-crypto
|
||||||
|
rather than ignoring the key and omitting crypto. Otherwise the
|
||||||
|
user might think they're getting encryption when they're not. David
|
||||||
|
found this problem in the server, and we also should check how the
|
||||||
|
client behaves.
|
||||||
|
|
||||||
|
o Process Nmap survey and send out results [Fyodor]
|
||||||
|
|
||||||
o Do new Nmap release with the stuff merged from SoC students and
|
o Do new Nmap release with the stuff merged from SoC students and
|
||||||
other new developments.
|
other new developments.
|
||||||
- Need to have our SoC successes writeup for 2010 posted first.
|
- Need to have our SoC successes writeup for 2010 posted first.
|
||||||
@@ -67,11 +92,6 @@ o Investigate ways to limit Winpcap privileges so that only
|
|||||||
|
|
||||||
o Add some content to https://secwiki.org and announce it.
|
o Add some content to https://secwiki.org and announce it.
|
||||||
|
|
||||||
o [Ncat] Make --exec work in conjunction with --proxy. The --proxy
|
|
||||||
code path skips the --exec code. See
|
|
||||||
http://seclists.org/nmap-dev/2010/q4/604 and the test "--exec
|
|
||||||
through proxy" in ncat-test.pl.
|
|
||||||
|
|
||||||
o Create new default username list:
|
o Create new default username list:
|
||||||
http://seclists.org/nmap-dev/2010/q1/798
|
http://seclists.org/nmap-dev/2010/q1/798
|
||||||
o Could be a SoC Ncrack task, though should prove useful for Nmap
|
o Could be a SoC Ncrack task, though should prove useful for Nmap
|
||||||
@@ -193,14 +213,6 @@ o Consider an update feed system for Nmap which let's people obtain
|
|||||||
OpenVAS. OpenVAS uses a script wrapper around rsync, or an HTTP
|
OpenVAS. OpenVAS uses a script wrapper around rsync, or an HTTP
|
||||||
download if that fails.
|
download if that fails.
|
||||||
|
|
||||||
o The latest IANA services file
|
|
||||||
(http://www.iana.org/assignments/port-numbers) has many identified
|
|
||||||
services which are still "unknown" in our files because ours is
|
|
||||||
based on a much older version of that file. We should probably take
|
|
||||||
that file and add names and comments to our nmap-services-all where
|
|
||||||
they are "unknown" in our file. An example of such a port is 3872,
|
|
||||||
oem-agent.
|
|
||||||
|
|
||||||
o Investigate why and whether we need mswin32/pcap-include/pcap-int.h.
|
o Investigate why and whether we need mswin32/pcap-include/pcap-int.h.
|
||||||
This file is not included in the official WinPcap 4.1.1 developers'
|
This file is not included in the official WinPcap 4.1.1 developers'
|
||||||
pack
|
pack
|
||||||
@@ -686,6 +698,14 @@ o random tip database
|
|||||||
|
|
||||||
DONE:
|
DONE:
|
||||||
|
|
||||||
|
o The latest IANA services file
|
||||||
|
(http://www.iana.org/assignments/port-numbers) has many identified
|
||||||
|
services which are still "unknown" in our files because ours is
|
||||||
|
based on a much older version of that file. We should probably take
|
||||||
|
that file and add names and comments to our nmap-services-all where
|
||||||
|
they are "unknown" in our file. An example of such a port is 3872,
|
||||||
|
oem-agent.
|
||||||
|
|
||||||
o Script review:
|
o Script review:
|
||||||
- patch for ftp-proftpd-backdoor
|
- patch for ftp-proftpd-backdoor
|
||||||
http://seclists.org/nmap-dev/2010/q4/678
|
http://seclists.org/nmap-dev/2010/q4/678
|
||||||
|
|||||||
Reference in New Issue
Block a user