mirror of
https://github.com/nmap/nmap.git
synced 2025-12-06 12:41:29 +00:00
Note a done task: Bug tracker is http://issues.nmap.org/
This commit is contained in:
@@ -1,5 +1,15 @@
|
|||||||
DONE:
|
DONE:
|
||||||
|
|
||||||
|
o Adopt an issue tracking system for Nmap and related tools. We
|
||||||
|
should probably look at our needs and options and then decide on and
|
||||||
|
either install it on our own infrastructure or use it hosted elsewhere.
|
||||||
|
- David notes that Trac seems to work well for Tor -- see
|
||||||
|
https://trac.torproject.org/projects/tor
|
||||||
|
- One thing which can be nice is being able to interact with the
|
||||||
|
system through email. Like for bugs people file on the Nmap package
|
||||||
|
in Debian, I can just reply to the mail and it gets added in the tracker.
|
||||||
|
- This is now live at http://issues.nmap.org/
|
||||||
|
|
||||||
o Update OpenSSL library to 1.0.1j
|
o Update OpenSSL library to 1.0.1j
|
||||||
|
|
||||||
o Our "make uninstall" should uninstall ndiff if it was installed too.
|
o Our "make uninstall" should uninstall ndiff if it was installed too.
|
||||||
|
|||||||
@@ -136,15 +136,6 @@ o We should fix nsedoc generation so it doesn't fail when blocks like
|
|||||||
just can't be fixed, we will have to document the heck out of it, I
|
just can't be fixed, we will have to document the heck out of it, I
|
||||||
suppose.
|
suppose.
|
||||||
|
|
||||||
o Adopt an issue tracking system for Nmap and related tools. We
|
|
||||||
should probably look at our needs and options and then decide on and
|
|
||||||
either install it on our own infrastructure or use it hosted elsewhere.
|
|
||||||
- David notes that Trac seems to work well for Tor -- see
|
|
||||||
https://trac.torproject.org/projects/tor
|
|
||||||
- One thing which can be nice is being able to interact with the
|
|
||||||
system through email. Like for bugs people file on the Nmap package
|
|
||||||
in Debian, I can just reply to the mail and it gets added in the tracker.
|
|
||||||
|
|
||||||
o When scanning your own IP from Windows, Nmap currently recognizes
|
o When scanning your own IP from Windows, Nmap currently recognizes
|
||||||
the problem (can't do a raw scan like that on Windows) and skips the
|
the problem (can't do a raw scan like that on Windows) and skips the
|
||||||
SYN scan, leading to Nmap printing a bunch of ports in "unknown"
|
SYN scan, leading to Nmap printing a bunch of ports in "unknown"
|
||||||
|
|||||||
Reference in New Issue
Block a user