Slashdot Mirror


Nmap 4.00 Released

NoExec writes "Hot off the nmap-hackers list comes news that the Nmap Security Scanner version 4.00 has been released. Dozens of major changes since 3.50 (2 years ago) are listed in the announcement. These include a rewritten (for speed and memory efficiency) port scanning engine, ARP scanning, a brand new man page and install guide, 'l33t ASCII art, runtime interaction, massive version detection improvements, MAC address spoofing, increased Windows performance, 500 new OS detection fingerprints, completion time estimates, and much more."

5 of 43 comments (clear)

  1. No raw sockets in XP? by BerkeleyDude · · Score: 2, Insightful

    "This is particularly useful for Windows, since Microsoft has disabled raw socket support in XP."

    Does it mean that the lowest level you can use is TCP or UDP? How did nmap work in Windows before? (Did it?)

    I wonder what's the logic in disabling raw sockets...

  2. Comparison to Nessus by yesnoyes · · Score: 5, Insightful
    My favorite part of the release announcement actually relates to Nessus:

    A popular open source security scanner recently went proprietary, complaining that their community never contributes much. We are sorry to hear that, but happy to report that the Nmap community is as vibrant and productive as ever! We would like to acknowledge and thank the many people who contributed ideas and/or code to this release (since 3.50). Special thanks go out to Adam Kerrison, Adam Morgan, Adriano Monteiro Marques, Alan Bishoff [ huge list goes on and on ... ]

    So if Nessus can't get enough help, maybe that says more about how they run the project than their suggestion of an open source community of leeches who don't contribute back.

  3. Re:Gibson has no credibility by 0racle · · Score: 2, Insightful

    No but it would lend support to the statement that he's a moron and should make you take other things that he has said on similar subjects with a grain of salt.

    Calling into question ones expertise and intelligence regarding a subject when talking about their positions on similar subjects is not strictly an ad hominum attack because their abilities are at the core of their ability to even create their argument. For instance, I know nothing about cars beyond how to drive one. One day I start spouting out something about them. Saying 'but he knows nothing about cars,' is not an ad hominum attack because my abilities, knowledge and experience are directly related to my ability to make a correct argument on this subject.

    Ad Hominum is Slashdots phrase du jour.

    --
    "I use a Mac because I'm just better than you are."
  4. Re:Gibson has no credibility by Geoffreyerffoeg · · Score: 3, Insightful
    Saying 'but he knows nothing about cars,' is not an ad hominum attack because my abilities, knowledge and experience are directly related to my ability to make a correct argument on this subject.

    Correct.

    No but it would lend support to the statement that he's a moron

    Incorrect, non sequitur, and evidence of not understanding "ad hominem". Unless you're stating that he has that particular 10-point IQ range designated "moron", that fell out of use ages ago, calling him a moron is a personal attack. What if he's being paid off by an underling of Stallman to make as much noise as possible about Windows vulnerabilities - and since Windows is so vulnerable, he's generally right? What if he's just misguided but using useful sources? What if he jumped the shark some time back?

    If you can lend any support to the theory "Gibson is unqualified to offer opinions on Windows security," you'd have a leg. If you can simply prove "Raw sockets do not affect the attack level of the Internet," your case would be done, and you would be attacking the argument, not the person. Why risk making an unrelated ad hominem that could be a fallacy, if it's far easier, and more relevant to the Slashdot discussion at large, to prove the original statement?

    Here, to bring this on topic, refute these claims about raw sockets.
    • Raw sockets have no use in a workstation OS. If XP Home is coming without a webserver, a remote desktop, and so forth, then why does it need something as obscure as raw sockets?
    • If you need to build a specific interface that isn't, e.g., TCP/IP, then write a driver for the protocol, and either digitally sign it or let the user accept the unsigned driver.
    • If we need to allow application-level raw sockets, then only let it run as administrator. Kinda like UNIX only lets root run servers on the first 1024 ports.
    • Raw sockets are easily used by botnets to spoof their source address in a DDOS. Botnets exist.
    • The average user never needs raw sockets. (Nmap is not a tool for the average user.)

    Therefore, just like everything else they've been recently disabling in the name of security, raw sockets have ample justification not to be there.
  5. Re:Gibson has no credibility by Geoffreyerffoeg · · Score: 2, Insightful

    creating a cutsey neutered Paris Hilton froo-froo lap dog OS

    I won't even begin to list the fallacies in that, but since we're back on topic...isn't that what Windows (or at least Windows XP Home) is? If you want to do cool things with it, get XP Pro. If you want to do really cool things, get Windows Server 2003. If you want to do extremely cool things and avoid the Windows paradigm, get Linux.

    Paris Hilton needs an OS, and Microsoft has written it. Anyone who needs raw sockets on a regular basis should not also plan to use XP Home on a regular basis. Use the right tool for the job.