Slashdot Mirror

eldavojohn writes "On Friday, CBS launched a TV Classics section to their ad based online service. Which means that Trekkies can now watch all three seasons of Star Trek: The Original Series online at the expense of a few commercials. Alongside this CBS is offering all of MacGyver, Twin Peaks and even three seasons of the original Twilight Zone. A side note, they seem to work perfectly fine in Linux. "

eldavojohn writes "On Friday, CBS launched a TV Classics section to their ad based online service. Which means that Trekkies can now watch all three seasons of Star Trek: The Original Series online at the expense of a few commercials. Alongside this CBS is offering all of MacGyver, Twin Peaks and even three seasons of the original Twilight Zone. A side note, they seem to work perfectly fine in Linux. "

nuts-to-CBS writes "After presenting 'Jericho' fans with a cliffhanging season finale, CBS promptly cancelled the program. The shocked fans quickly banded together, many using CBS' own public "Jericho" discussion forum, and began brainstorming on ways to convince the network to bring back the show for a second season. A plot point in the final episode of "Jericho" involving the expletive "Nuts!" (in reference to an historic conversation between generals) was turned into a campaign to send large quantities of nuts to CBS' NY, LA, and affiliate offices. Fans have sent a total of $26,000 for a pooled campaign hosted at Nuts Online to ship over 19,000 pounds of peanuts to CBS. Other efforts acquired over $9,000 to publish full page advertisements in Variety (National Edition) and The Hollywood Reporter for Tuesday, May 29th. This is expected to become the largest ever fan campaign to bring a television show back from cancellation." There's more about the massive fan rollout below. CBS created rich, interactive content online to accompany their show "Jericho," in order to extend its fan base to the Internet-savvy, TiVo-owning generations. Despite suffering through the all-too-familiar mid-season hiatus employed by many shows, the "Jericho" fan base remained strong throughout the break, partially due to the episodes being posted both for free on the CBS site as well as for purchase on iTunes. "Jericho" returned from the hiatus in the same timeslot occupied by "American Idol." CBS — which apparently still determines programming primarily on Nielsen ratings — decided to drop the show, regardless of the ever-growing and loyal fan base. Nuts Online includes live blogging from Jeffrey Braverman, the company's 26-year old CEO. Jeffrey's company has been shipping up to 5,000 pounds of peanuts a day to the CBS New York headquarters, and has been using their site to describe his experience along the way. Three other fan sites are documenting the progress: CBS Jericho Message Board, Jericho Lives, and Jericho Rally Point. Fans of Roswell were successful in bringing back their favorite program by sending mass quantities of tiny bottles of Tabasco sauce."

nuts-to-CBS writes "After presenting 'Jericho' fans with a cliffhanging season finale, CBS promptly cancelled the program. The shocked fans quickly banded together, many using CBS' own public "Jericho" discussion forum, and began brainstorming on ways to convince the network to bring back the show for a second season. A plot point in the final episode of "Jericho" involving the expletive "Nuts!" (in reference to an historic conversation between generals) was turned into a campaign to send large quantities of nuts to CBS' NY, LA, and affiliate offices. Fans have sent a total of $26,000 for a pooled campaign hosted at Nuts Online to ship over 19,000 pounds of peanuts to CBS. Other efforts acquired over $9,000 to publish full page advertisements in Variety (National Edition) and The Hollywood Reporter for Tuesday, May 29th. This is expected to become the largest ever fan campaign to bring a television show back from cancellation." There's more about the massive fan rollout below. CBS created rich, interactive content online to accompany their show "Jericho," in order to extend its fan base to the Internet-savvy, TiVo-owning generations. Despite suffering through the all-too-familiar mid-season hiatus employed by many shows, the "Jericho" fan base remained strong throughout the break, partially due to the episodes being posted both for free on the CBS site as well as for purchase on iTunes. "Jericho" returned from the hiatus in the same timeslot occupied by "American Idol." CBS — which apparently still determines programming primarily on Nielsen ratings — decided to drop the show, regardless of the ever-growing and loyal fan base. Nuts Online includes live blogging from Jeffrey Braverman, the company's 26-year old CEO. Jeffrey's company has been shipping up to 5,000 pounds of peanuts a day to the CBS New York headquarters, and has been using their site to describe his experience along the way. Three other fan sites are documenting the progress: CBS Jericho Message Board, Jericho Lives, and Jericho Rally Point. Fans of Roswell were successful in bringing back their favorite program by sending mass quantities of tiny bottles of Tabasco sauce."

techstar25 writes "With the recent success of movies incorporating mathematics, Dr. Jonathan Farley, a professor of mathematics at the State University of New York at Buffalo who is currently doing research at Harvard, tapped into his professional knowledge and headed west to Hollywood, where he and Dr. Elizabeth Burns, founded Hollywood Math and Science Consulting to help television and movie producers portray accurate mathematics on screen. Their first client: the CBS drama Numb3rs. 'In many cases, they want me to elaborate on some of the math already in the script,' said Farley. 'I help add dialogue and fine tune the math already in the script. It's not just about fixing mathematical mistakes . . . It's also about helping them get the culture right.'"

Tycoon Guy writes "With CSI: Crime Scene Investigation airing its 100th episode this week, I wonder, how do Slashdot readers feel about the show, and its two spinoffs? On the one hand, they've caused a boom in the popularity of forensic science college courses, and they glamorize geeks bent over microscopes, rather than smarmy lawyers. On the other hand, they may also promote an inaccurate view of science: prosecutors throughout the country now worry about juries that refuse to accept eyewitness accounts or even outright confessions, and instead exclusively demand the kind of forensic evidence they see on CSI. But of course, in the real world, you don't get a test like that in mere seconds - or without spending a substantial amount of money. So where does CSI rate on the geek scale for you?"

Tycoon Guy writes "With CSI: Crime Scene Investigation airing its 100th episode this week, I wonder, how do Slashdot readers feel about the show, and its two spinoffs? On the one hand, they've caused a boom in the popularity of forensic science college courses, and they glamorize geeks bent over microscopes, rather than smarmy lawyers. On the other hand, they may also promote an inaccurate view of science: prosecutors throughout the country now worry about juries that refuse to accept eyewitness accounts or even outright confessions, and instead exclusively demand the kind of forensic evidence they see on CSI. But of course, in the real world, you don't get a test like that in mere seconds - or without spending a substantial amount of money. So where does CSI rate on the geek scale for you?"

An assortment of Super Bowl tidbits: Supposedly sports gambling sites are being threatened with denial of service attacks if they don't pay protection money - also a Reuters story. Infinitus writes "The NFL's legal firm has a PDF up that outlines the NFL's intellectual property rights to words like 'Super Bowl' and 'NFL'. Including a neat little chart that tells you what you can and can't say..." VeggiePossum23 writes "Panthers Upset Patriots, 29 to 21... at least in the Sony Sponsored '989 Sports Game Before the Game' played on NFL Gameday 2004 on the PS2 Console. This annual event, held Wednesday night in Houston, has a perfect 8-year track record of picking the winner of the Super Bowl. Carolina Panthers Wide Receiver Steve Smith controlled the Panthers, winning an upset victory against New England Patriots' Wide Out Troy Brown, also controlling his own team." lordbyron writes "CBS is doing a SuperBowl of commercials that will include a vote for the best commercial in history. You can watch the top 10 now and make sure that you vote at 9pm on Sunday 1/31. It includes some classics like the Apple commercial and the exploding mosquitos from Tabasco."Wing Bowl.--->

Thanks to Skotos.net for their article discussing why the TV show Big Brother 4 is an example of good game design, and what we can learn from it. It's pointed out that "a group of n/2 (rounded down) + 1 people can dominate the game", if well-organized, but "the producers of Big Brother have made changes which dramatically reduce the power of a majority", including the ability to veto potential evictees. But it's argued the jury of previously evicted players voting on the final two contestants means "...if you backstab someone or betray them, even if it gets you further in the game, it could prevent you from winning." Is there a perfect strategy for winning Big Brother, and if not, is the concept of "unworthy winners" dissatisfying?

You asked nmap creator Fyodor many excellent questions, and his answers (below) are just as excellent. You'll want to set aside significant time to read and digest this interview, because Fyodor didn't just toss off a few words, but put some real time and energy into his answers.

1) Interesting stories involving nmap?
by Neologic

Nmap has obviously become a huge success in the *nix world. I would wager that practically all sysadmins and security folk use nmap. With this sort of use by such creative and lazy people, there must have been some interesting stories involving nmap, perhaps unusual uses of it, or funny anecdotes. Are there any you would like to share?

Fyodor

The coolest use ever was undoubtedly when Trinity used it to try and save the human race :). But the use I find most gratifying are the Chinese students and residents who have written me about how they use Nmap to locate open proxies. These proxies allow for surfing the uncensored Internet, including the news, educational, pornographic, religious, open source software, government, political, search engine, and human rights sites that are blocked by the Great Firewall of China.

Many of the best features in Nmap came from the user community in ideas if not implementation. For example, the protocol scan (-sO) determines what IP protocols (TCP, UDP, GRE, etc.) a host is listening for. I had not thought of this, but the idea and patch came out of the blue one day in an email from Gerhard Rieger. On another day, a guy named Saurik sent a patch called Nmap+V that allows Nmap to do basic service/version fingerprinting against open ports. It has attracted a cult following, and I plan to add similar functionality to Nmap this year. The initial Windows port by eEye arrived similarly. Despite all these great suggestions, certain other user-contributed ideas are not on the agenda.

Then there are a small handful of users who detect problems nobody else would ever notice, like 4 byte/host memory leaks. They send me error messages with notes saying the bug happens "about once per 700,000 IPs". I have no idea what these guys are up to, but some have been sending me this kind of mail for years. They can't be spammers, as they are intelligent and also use more sophisticated scan techniques than you would need to just find SMTP servers.

2) Recent increases in anal-retentiveness...?
by Zeriel

There's been a marked increase in system administrators thinking that anything even remotely resembling a network scan is eeeeevil (case in point, last year I almost got kicked out of college for scanning port 80 on my dorm subnet looking for interesting websites to read)...

What do you think can be done to make scanning IP addresses/ports have less of a negative stigma? This is in the same sort of category as legit vs. illegit uses of anything else (P2P, whatever)--what's the rationale for punishing something that could maybe lead to criminal activity, and how can we make network scanning tools have practical uses again?

Fyodor

That is an excellent question, and one that concerns me as well. But first, I think your final statement is too extreme. I would guess 90% of network scanning is non-controversial. You will rarely be badgered for scanning your own machine or the networks you administer. The controversy comes when scanning other networks. There are a lot of (good and bad) reasons for doing this sort of network exploration. Perhaps you are scanning the other systems in your {dorm, department, cable LAN, conference LAN} to look for publicly shared files (FTP, SMB, WWW, etc.). Or perhaps your just trying to find the IP of a certain printer. Maybe you scanned your favorite web site to see if they are offering any other services, or because you are curious what OS they run. Perhaps you are just trying to test connectivity, or maybe you wanted to do a quick security sanity-check before handing off your credit card details to that ecommerce company. You might be conducting Internet research, or be bored on a rainy afternoon. Or are you conducting reconnaissance in preparation for a breakin attempt?

The remote administrators rarely know your true intentions, and do sometimes get suspicious. The best approach is to get permission first. I've seen a few people with non-administrative roles land in hot water after deciding to "prove" network insecurity by launching an intrusive scan of the entire company or campus. Admins tend to be more cooperative when asked in advance than when woken up at 3AM by an IDS alarm claiming they are under massive attack.

You compared Nmap to P2P tools in having a "negative stigma". In both cases, one effective way to fight the stigma is to limit your own use to "legitimate" purposes. Use BitTorrent to download RedHat ISOs, but not Matrix Reloaded. Use Nmap to secure and monitor your computers, but not to attack other networks. And if you decide to attack other networks anyway, please be courteous and set the evil bit.

Now I'll admit that I don't always obtain explicit permission before scanning other networks. I don't believe (but IANAL) that a simple port/OS scan of a remote system is or should be illegal. Any machine connected to the Internet will be scanned so often that most admins ignore such "white noise" anyhow. But scan other networks often enough, and someone will eventually complain. So my advice would be:

1. Don't do anything controversial from your work or school connections. Even though your intentions may be good, you have too much to lose if someone in power (boss, dean) decides you are a malicious cracker. Do you really want to explain your actions to someone who may not even understand the terms "port scanner" or "packet"? Spend $10 bucks a month for a dialup or shell account. You didn't really violate this rule, as scanning your dorm subnet for just port 80 should not even be remotely controversial!
2. Target your scan as tightly as possible. If you are only looking for web servers, specify -p80 rather than scanning all 65,535 TCP ports on each machine. If you are only trying to find available hosts, do an Nmap ping scan. Don't scan a /16 when a /24 will suffice. The random scan mode now takes an argument specifying the number of hosts, rather than running forever. So consider -iR 1000 rather than -iR 10000 if the former is sufficient. Use the default timing (or even "-T Polite") rather than "-T Insane".
3. Nmap offers many options for stealthy scans, including source-IP spoofing, decoy scanning, and the more recent Idle Scan technique. But remember there is always a trade-off. You will be harder to detect if you launch scans from an open WAP far from your house, with 17 decoys, while doing followup probes through a chain of 9 open proxies. But if anyone (such as Tsutomu Shimomura) does track you down, they will be mighty suspicious of your intentions.

I occasionally consider adding some sort of "notification packet" prior to a scan that would give hosts the chance to respond and opt-out. This would be like the /robots.txt directives currently used to control polite Web robots. Perhaps the format could even include a text string that IDS systems could log, like: nmap -sS -p- -O -m "Direct questions about this scan to ops at x3512" 192.168.0.0/16 nmap -sS -p- -O -m "mY n4m3 iZ Zer0 |<00L and I'll 0wn j0o%#@" targetcompany.com/24 Of course Nmap would have an option to omit the notification or to send it and ignore any negative responses. Some scanners, such as ISS Internet Scanner already send out NetBIOS popup messages to scanned hosts by default, and other scanners use syslog. I won't be adding any features like this to Nmap unless I see substantial demand and the obvious issues are worked out.

3) OS fingerprinting
by neoThoth

What are the latest advances in fingerprinting networked devices that seem most promising to you? I have started reading papers on HTTP fingerprinting and such and wonder how these will figure into the NMAP architecture. What are the most elusive OS's that aren't on the NMAP OS fingerprint database?

Fyodor

There are a number of OS detection techniques I hope to add this year. One is to guess (or calculate) the initial TTL of response packets, since this varies by OS. Some operating systems also "reflect" your own chosen TTL under various circumstances. Then there are some newer TCP options, such as selective ack that I might test for. Explicit Congestion Notification (RFC 2481/3168) also shows promise. I'll probably add all of these at once later this year, after discussions with the Nmap-dev list. If you wish to participate, you can join that list by sending a blank email to nmap-dev-subscribe@insecure.org. There is also a low volume, moderated list for announcements about Nmap, Insecure.org, and related projects. You can join the 15,000 current members by mailing nmap-hackers-subscribe@insecure.org [archives].

While adding new fingerprinting techniques is fun and exciting, improving the signature database often ads more value. The DB now contains more than 850 signatures, from the Acorn RISC OS and Aironet wireless LAN bridge to the ZoomAir wireless gateway and Zyxel Prestige routers. We're talking gaming consoles, phones, PBX systems, PDAs, webcams, networked power switches, you name it! New fingerprints are submitted daily.

Application level fingerprinting (including HTTP) is coming. I usually regret stating dates, but I hope to develop this functionality within the next 3 months.

4) Stepping into a network security career
by Anonymous Coward

I'll be graduating this month with a shiny new BS in Computer Science. I've done plenty of Unix sysadmin work throughout college and even deployed some high-interaction honeynets. I'm very interested in network security and systems programming. Do you have any advice for people in my situation who want to head into a career in network security?

Fyodor

Congratulations on your graduation! Unfortunately (for newcomers), the security field is one that often expects substantial experience and references. This is partly because these jobs require extraordinary trust, and also because of an aversion to mistakes. Everyone makes mistakes, but they can be extraordinarily costly in security and neophytes tend to make more of them. But don't lose hope! Talented security minds are still in very high demand, just be aware that you will have to work even harder to prove yourself.

Here are my suggestions for anyone starting out in network security, whether for fun or profit:

Step 1: Learn everything you can

1. You may wish to start with reading a general overview of security, such as Practical Unix and Internet Security 3rd Edition.
2. Reading alone won't teach you much. Hands-on experience is critical, so I would set up at least a basic test network. At the very minimum you should have a Unix box or two and a Windows machine (because these are very common in the real world). You can use very cheap machines, or even emulate a large network with virtualization software such as VMWare.
3. Next you should learn more about how attacks are performed. Take a look at the excellent and free Open Source Security Testing Methodology Manual (OSSTMM). This document aims to provide a comprehensive framework for security testing. But it mostly lists tasks to perform, without specifying how to do so. You will gain a lot from this manual if you research the tasks you don't know how to complete, and if you actually try performing the tasks on your test network. If this manual is too curt or hard to follow, you could try a more verbose book on vulnerability assessment, such as Hacking Exposed 4th Edition.
4. Now that you understand many of the general security ideas, it is time to get current. This is one area that has actually become easier in the last decade. The thinking used to be that vulnerability information should only be distributed to well-known and trusted administrators and security researchers through private digests such as Zardoz. This was a disaster for many reasons, and the full disclosure movement was born. In the last couple of years things have started to shift toward more limited ("responsible") disclosure and there is also a disturbing pay-money-for-early-disclosure trend. But information is still much more available than it used to be. Most of the news is carried on mailing lists, and I archive the ones I consider the best at Lists.Insecure.Org. You must subscribe to Bugtraq, and I would also highly recommend pen-test, vuln-dev, and security-basics. Read at least the last 6-12 months of archives. Choose other lists that correspond to your interests. SecurityFocus also offers a security-jobs list which is an excellent resource for finding jobs or just understanding what employers desire.

   There are two major reasons for reading Bugtraq. One is that you must react quickly to new vulnerabilities by patching your servers, notifying your clients, etc. You can get this by simply scanning the subject lines or advisory summaries for bugs that directly apply to you. But then you will miss out on another crucial purpose of Bugtraq. Actually understanding a vulnerability helps you defend against it, exploit it, and identify/prevent similar bugs in the future. When you are lucky, the advisory itself will provide full details on the bug. Check out this excellent recent advisory by Core Security Technologies. Note how they describe exactly how the Snort TCP Stream Reassembly vulnerability works in detail and even include a proof-of-concept demonstration. Unfortunately, not all advisories are so forthcoming. For bugs in Open Source software, you can understand the problem by reading the diff. The next step is to actually write and test an exploit. I would recommend writing at least one for each general class of bug (buffer overflow, format string, SQL injection, etc.) or whenever a bug is particularly interesting.

   Be sure to read the latest issues of Phrack and the research papers posted to the mailing lists. Send your comments and questions to the authors and you may start interesting discussions. Read well-regarded books on the security topics that interest you most.

   I can't emphasize enough that you should intersperse hands-on work with all of this reading. Install unpatched RedHat 8 (or whatever) and run Nmap and Nessus against it. Then compromise it remotely, maybe via the latest Samba hole. Start out with a prewritten exploit from Bugtraq, which isn't quite as easy as it sounds. You may have to modify the 'sploit to compile, brute force the proper offset, etc. Then break in again using a different technique, and your own exploit. Install Ethereal and/or tcpdump and ensure you understand the traffic on your network during both your exploitation and normal network activity. Install Snort on an Internet-facing machine and watch the attacks and probes you'll experience. Wander around your neighborhood with Kismet, Netstumbler, or Wellenreiter on your Laptop or PDA to look for open WAPs. Install DSniff and execute an active MITM attack on an SSH or SSL connection between two of your computers. Take a look at my Top 75 Tools List and ensure you understand what each does and when it would be useful. Try out as many as you can.

5. Take a vacation, or at least a weekend camping! You deserve it! The steps above would probably take at least 3-12 months full-time, depending on your motivation level and the depth and breadth of your research.

Step 2: Now apply your newfound knowledge

Now you have learned enough to be dangerous. At this point, you would have little trouble obtaining most certifications, after studying the specifics of each topic. If your main goal is to find a job quickly, perhaps adding these extra feathers to your cap might be worthwhile. But I think your best bet is to prove your knowledge by joining and contributing to the security community. While this does indeed help others, it isn't an entirely selfless act. It improves your skills, leads to important contacts, and demonstrates your knowledge and ability in a constructive way. The latter is important if securing a career is one of your goals. These steps should also be fun! If not, perhaps you should keep looking at other fields. Here are some ideas:

Start participating with insightful comment and answers on the mailing lists. This is very easy and serves as a great learning experience, way to meet people, and garners some name recognition. If a security manager with a stack of 60 resumes recognizes your name, that is a huge win!

When a new worm or a big new vulnerability comes out, everyone wants to know the details. If you stay up all night disassembling the worm/patch and write the first comprehensive analysis, many folks will find that valuable. And you will learn a lot. Let your first priority be quality - if someone beats you to it, just compare your results with theirs to see if you (or they) missed (or misinterpreted) anything. You can also post your own exploits, although that is more of a political hot potato.

Attending security conferences is a great way to learn, party with fellow hackers, and network (in every sense of the word). Much better is to speak at these conferences. This field changes rapidly so there are always new topics and technologies to discuss. You don't have to be a well-known expert with a long history - just learn your topic well and put in the effort for a quality presentation. You could present at Defcon, at one of the more commercial events, or at a smaller regional con like ToorCon, CodeCon, Hivercon, etc. Among other advantages (often free admission/travel/hotel), this is a great way to meet people with similar interests. I spoke at the latest CanSecWest and have submitted a proposal for the next Defcon.

Now that you've seen and understand a wide variety of software vulnerabilities from your Bugtraq research, start finding your own. You can start by downloading any PHP app from Sourceforge. Most of those are hopelessly vulnerable to Cross-Site-Scripting, SQL injection, and/or remote code execution by "remote include" directives. Many (if not most) Windows shareware daemons are also vulnerable to simple buffer overflows and format-string bugs. Notify the authors and then write an advisory. After a few of these "easy targets", try breaking some more widely deployed programs.

Write a security tool! I could list some suggestions, but by this point you will have many of your own ideas as to what is needed. Scratch an itch.

I hope this helps. If you want more suggestions, Ask Slashdot. From that story, I found this post particularly insightful, especially the emphasis on "people skills". I don't claim to have any, but understand the value :).

5) Have you ever been tempted to use your gifts...
by Tim_F

...in a negative manner?

Have you ever hacked into someone else's computer? Have you ever considered it? What would cause you to think of doing this? Would your tools (nmap, etc.) be enough to allow you to do this?

And if you haven't, why is that the case?

Fyodor

I never do script-kiddie style "hack any random vulnerable box on the Internet" cracking. But sometimes I will launch targeted attacks at specific companies. I'll usually start with just a web browser and various search engines to learn everything I can about my target. I need to understand what the company does, who it partners with, and whether it has any corporate siblings, subsidiaries, or parents. Beyond that, posts by individual employees can be a gold mine. Besides providing names and titles for social engineering and brute force password attacks, the IPs in the mail/news routing headers can be very valuable. One of the reasons I run my own mailing list archive is to maintain access to the raw mail folders which contain the routing info and X-no-archive posts that web archives strip out. Another advantage to locating employees is that you can send them trojan executable attachments, which can be a very effective way into the network.

Next I'll gather known IP network information on the companies via DNS, whois, regional registries like ARIN, routing info, Netcraft, etc. Then comes the scanning (I tend to use Nmap), application-probing, vulnerability discovery, and exploitation stages.

Of course, I only do this when the company is paying me to do so. Performing these pen-tests offers several advantages over blackhat activity:

1. You don't go to jail (If you've worded your contract carefully.)
2. Instead of having to keep your übertechniques secret to avoid prosecution, you get to demonstrate them to management.
3. They actually pay you for this! And you are helping to protect them and the privacy of their customers.

Now some people might ask how you gain these skills without practicing on other networks first. Cheap hardware and the evolution of free UNIX operating systems have made this much easier than in the past. See the previous answer for some suggestions. And remember that you can always work together with friends, or participate in hacking contests like Defcon's Capture the Flag.

6) You'll have seen a lot of breakins.
by Hulver

During your time running Honeypots, you'll have seen a lot of compromised systems. Is there any incident that's really stuck in your mind because of the audacity of the attempt, or the stupidity of the person attempting the breakin.

Fyodor

On the humorous front, one attacker was was running a public webcam during his exploits, so we were able to watch him crack into our boxes in real time :). I will resist the urge to link a screenshot. His rough location was determined when we noticed Mrs. Doubtfire playing on his TV and correlated that with public schedule listings. He was working with a Pakistani group, but was actually on the US East Coast.

In the "disturbing audacity" front, this year we found that a group of crackers had broken into an ecommerce site and actually programmed an automated billing-sytem-to-IRC gateway. They could obtain or validate credit card numbers by simply querying the channel bot! Expect a more detailed writeup soon.

7) What makes a honey net enticing?
by cornice

It seems that many of the honey nets that the average hobbyist would run are built to attract a lesser cracker. What I mean is that ports are left open that normally would not be left open. Services are running that normally should not, etc. I think that a really smart fish would see this as nothing but a cheap lure and refuse the bait. Do you think it's possible to fool the really smart fish? Is is possible to bait with something enticing enough without tipping off the big fish? Does publication of your work make this task more difficult?

Fyodor

Excellent question, and I had many of the same concerns upon joining the project. Then I remembered that most of the attacks and real-world compromises are committed by these marginally skilled script kiddies. So there is still a lot of value in understanding their tools, tactics, and motives. Despite this apparent limitation, I have been surprised by some of the sophisticated things we have found. For example, the first known "in the wild" attack using the Solaris dtspcd vulnerability was caught by one of our honeynets and resulted in this CERT advisory. Then one of our Honeynet Alliance members had their Win2K honeypot compromised and joined into a botnet with 18,000 machines! Attackers on such a grand scale won't even know all of the companies they have compromised, much less whether any of the systems are honeynets.

I do believe baiting the "smart fish" might be possible, but I have never done this. Is not legally entrapment, as we aren't any sort of police force, but I am not very comfortable with the idea. If someone attacks my box that is just unobtrusively sitting on the network, I believe the attacker should have no expectation of privacy for his activities on the system. Things become more complex if I try to lure the attacker.

8) IPv6
by caluml

Do you think that with the very large address space of IPv6 that random scanning for a certain port will die off? (I notice nmap doesn't support random IPv6 address scanning - maybe you've already come to the same conclusion?) Simply put, the chances of finding a machine if it's not advertised anywhere will be very much reduced. Will this make people lazy and complacent, trusting on the large numbers involved to protect them?

Fyodor

Finding a machine by by pinging a completely random 128-bit address will probably never be effective. Fortunately, we won't have to! Nmap does not even do that for 32-bit IPv4 addresses - it is smart enough to skip huge blocks of address space that are unallocated or used for private (RFC1918, localhost) addresses. We will also see patterns emerge for IPv6. For example, they may often be allocated sequentially so that finding one leads to many others. I am waiting until adoption rises and we start seeing these patterns emerge before I can implement them appropriately in Nmap. Certain new DNS features may also prove useful for locating IPv6 machines and networks.

9) standalones and small home nets
by zogger

it seems like most of the emphasis is on enterprise networks, but that still leaves millions and millions of home machines and small home networks just stuck. What do you see as some of the trends and solutions for those people? Their data and system integrity is just as important to them as any corporations is, and usually not having the appropriate skill set, is even harder to implement.

Fyodor

I am afraid the focus by security companies on enterprise networks will continue, as that is where the money is. The good news is that securing small home networks is far easier. But that doesn't make it simple, nor mean that many people will bother. I would categorize the risks into 3 categories:

Traditional network server vulnerabilities: Your average home user doesn't need to run any network daemons or have any TCP/UDP ports open to the Internet. Most of the time they only have 1 IP, used either by a standalone PC or a NAT device (e.g. "broadband router") in front of their small network. This is a good configuration, as it limits what attackers can reach directly. But you need to be sure that the IP doesn't have any unnecessary ports open. You can verify this by running 'netstat' on the Windows or UNIX machine using the IP. I would also recommend confirming using a port scanner such as Nmap. Here are example commands:

nmap -p- -sS -T4 -v -O [your IP]
nmap -p- -sU -v [ your IP ]

The TCP and UDP scans could be combined into one execution, but are listed separately since the TCP scan may go much faster. Remote UDP scans are also less reliable against some heavily filtered hosts. You may have to rely on the netstat info or configuration details in this case.

Any open ports found should be evaluated with extreme prejudice. Unless clearly necessary, close Windows file sharing, external NAT device admin ports, and everything else found.

Don't forget the wireless backdoor! Blocking the Internet link from your private machines is insufficient if anyone can hop on your open WLAN and attack your machines. WEP isn't perfect, but the 104-bit (so-called 128-bit) version should at least keep people from accidentally connecting to your network or sniffing your data. Be sure to set a good password and upgrade to recent firmware for your WAP and other network devices.

Subscribe to the security advisory lists for all the operating systems (and devices, if available) you run. Major vendors such as RedHat, Debian, FreeBSD, Mandrake, and Microsoft all offer these. Most even offer automatic updates if you desire that.

Client vulnerabilities: Once you close the services you don't need (ideally all of them), client vulnerabilities must be addressed. Keeping your web browser and mail reader up-to-date is particularly crucial. Also harden them as much as possible. For example, IE is full of holes but at least has a good interface for site-by-site security policies (Tools -> Internet Options -> Security). Go through and neuter the "Internet zone" settings by disabling ActiveX and Java. In the rare case that sites need this, find an alternative site or add them to the trusted zone. If your are really serious about security, neuter "trusted sites" and "local intranet" privileges as well. Many recent IE vulnerabilities trick the browser into using the wrong zones. Consider using a different browser. Also configure your mailer to disregard HTML and JavaScript.

Remember to pay careful attention to security warnings, whether they come from IE, Mozilla, your ssh client, or anything else. Don't just click OK. And don't shoot yourself in the foot when configuring your apps. It is hard to entirely blame the vendor when users tell P2P apps or Windows filesharing to share their whole drive without any password. Failing to change default passwords or enable basic restrictions on X Window or FTP servers is only slightly more forgivable. All of these errors happen frequently! The apps/devices should be secure by default, but you have the ultimate responsibility for protecting your data.

Malware: This is what I consider the biggest problem on desktops: people running applications they can't trust. Email borne viruses, worms and trojans are an obvious example. Be very careful what you click on. Unfortunately, it is very difficult to know what to trust. Mail is trivial to forge, and even the "proper" installers for many P2P applications infest your computer with loads of invasive spyware. Even Intuit TurboTax was caught writing to customers' boot information track.

What can you do? My honest suggestion is to run peer-reviewed open source applications on a free OS such as Linux or FreeBSD. You still have to be careful, but these problems are far less prevalent on UNIX platforms, which also have better tools and procedures to deal with them.

What if dumping Windows is not an option? Run NT/2K/XP instead of Win9X/ME, and try to run everything you can as an unprivileged (non-administrator) user. Be extraordinarily careful about what you install and run, and make frequent backups. You might also want to look into a personal firewall such as Zone Alarm (limited free version.

10) What is your favourite tool?
by Noryungi

I have just read your top 75 security tools list. Thank you for posting all this information, which I am going to study very carefully.

One question though: in all these tools, which one is your personal favourite? (This excludes Nmap, of course).

Fyodor

I have far too many favorites among this great group to choose just one! But here are a few developers and tools that are particularly worthy of mention:

One of the people I most admire in the security field is Solar Designer. He is a guru in networking, security, and low level kernel/assembly/architecture details. He has also created many tools that security professionals use daily. Yet he never exhibits the arrogance, elitism, and egotism that sadly characterizes so many "stars" of the security community.

Among SD's tools is John the Ripper, my longtime favorite local password hash cracker. It has been around forever, but was written with a flexible and powerful interface while keeping extensibility in mind. So it is still as useful in these days of shadowed password files and MD5/Blowfish hashes as it was back in the days of crypt() and unprotected /etc/passwd. Lately SD has been working on the Owl secure GNU/Linux distribution, which can be installed on disk for hardened systems like firewalls, or booted and run from CD as an easy way to run security tools such as John and Nmap.

Another of those "brilliant yet still nice" security developers is Dug Song. Even after the seminal "Insertion, Evasion, and Denial of Service" paper by Ptacek and Newsham, many IDS vendors continued to ignore the problem. When Doug released Fragrouter (now fragroute), which implements some of these attacks, vendors finally took notice! He has also written the excellent libdnet library, but my favorite of his tools is DSniff, a suite of tools for advanced network sniffing and "monkey-in-the-middle" attacks. It even handles ARP poisoning and other techniques for sniffing hosts on a switched LAN.

While I'm on this topic, let me also give "mad props" to the Hping2 packet prober, Kismet wireless stumbler, Ethereal packet decoder, Netcat, recent THC releases, Snort IDS, the Nessus vulnerability scanner, and all the other great Open Source tools out there!

I would also like to thank Slashdot for granting me this interview and to everyone who asked such excellent questions. I only wish I had time to answer more of them. Then again, I have probably rambled on enough. Now it is your turn to ramble in the comments :).

Cheers,
Fyodor

For years, big media outlets have feasted on the idea that the Net is a breeding ground for thieves and degenerates who prey on innocent youth. This generally false impression has panicked a whole generation of parents about technology, resulting in the hysterical jailing and persecution of some hackers, and triggered the installation of blocking and filtering systems on home computers, as well as many purchased with federal money. So it's especially interesting to see a new level of media hypocrisy: a major network -- CBS -- using the Web as a dumping ground for leftover trash (in this case, from the show "Big Brother") too offensive to broadcast over the air. Next will be shootings, accidents and executions.

Last week, CBS expelled a male contestant from the reality show Big Brother for holding a kitchen knife against a female contestant's throat. The 26-year-old man, warned previously about threatening behavior, was kicked off the show, whose producers concede they sought out more aggressive contestants this year to boost the program's ratings. CBS can air what it wants, of course, but here's a neat twist: Though the knife-wielder has been deemed too violent to remain on the program, the incident was aired on TV and live online, with additional footage available at extra cost on the Web. The network is selling around-the-clock views from all the cameras in the "Big Brother" home -- more than TV viewers can see -- to Net users for a $10 a month fee.

If you each had pocketed $10 every time CBS News broadcast an online danger story about hackers, intellectual property thieves, the violent effects of gaming, online predators or child pornographers, you could retire. This is the network whose 60 Minutes aired an hour-long program the week after Columbine titled "Are Video Games Turning Your Kids Into Killers?" Big media have been among the leading advocates of the idea that the Net is a dangerous, de-civilizing place for children, that they will encounter all sorts of violent, sexually explicit and other unwholesome material there.

But when I went onto the Big Brother site, I found no age restrictions or warnings about who could buy or see the knife incident. Any kid with access to a credit card could, as is often true of sex and other "unwholesome" sites online. But it's one thing for a pornographer to do that, another a media conglomerate that purports to cover public policy issues, including technology, and that constantly spouts the most high-minded sense of moral purpose. Listen to what Big Brother's producer said of the show's ethics: "I have been lecturing my staff about using the West Point code of honor in making sure we keep to the truth."

The blurring of news, information and entertainment has been underway for years, but the use of the Net as a profit center for trash programming is very new to so-called serious news organizations. The real danger to kids going online is that they will soon have no way of differentiating entertainment from factual information.

The next level seems clear: to round up convicted murders and psychopaths and have them tear one another up, then sell the grisly pictures over the Web to anybody with $10. Maybe fires, traffic accidents, shootings, or the next federal and state executions could be broadcast that way, too, a new revenue source for embattled popular media. Believe me, it will happen.

Big Brother is already cheesy trash; now it's clearly exploiting the possibility of violence to draw viewers. It's also using the Net to cash in on crap the network doesn't dare broadcast on it's publically-owned airwaves. This notion of the Net as a target-marketed toxic waste dump for dubious content is significant, particularly if it makes money and other networks and giant content producers like Disney, or AOL/Time-Warner adopt it. It's not hard to imagine a scenario where the most ubiqutious producers of dubious content for kids are the big media companies that can produce this garbage with one division, while condemning the immoral impact of new technology with another.

Maybe when some pompous Congressional gasbag like Joseph Lieberman next holds hearings about violence on TV and the Net, he can call in a CBS executive and ask him or her if their vision of the Net and ask if the networks' vision is to use cyberspace as a medium for profiting from content not fit for commercial broadcasting. The committee can also ask if, in the news division's next report on online depredations, Dan Rather will include his companys own entertainment division. Don't hold your breath.

abh writes " CNN is reporting on the Emmy nominations, apparently there is a new category for reality-based TV (such as Survivor), and none other than Junkyard Wars got a nomination." Junkyard Wars rocks - excellent recognition of good stuff. The Daily Show was nominated as well, and deserves it, IMHO.

We got a number of submissions about this. The Tribal Council Voting History page for the CBS TV show Survivor apparently contains a bug that lets you see which contestants have been kicked off the show before their names appear on the site, sort of like the Slashdot bug (now fixed) that sometimes let you see our stories before they appeared on the main page. The clearest instructions I saw for exploiting the "Survivor Spoiler" bug were here. I'm sure CBS will fix this soon, but you could still pull the trick as of 6:40 a.m. (US EDT) this morning. Do you think this is a true bug, or is CBS doing it on purpose (with the "wrong people" crossed out) to increase interest in the show?

We got a number of submissions about this. The Tribal Council Voting History page for the CBS TV show Survivor apparently contains a bug that lets you see which contestants have been kicked off the show before their names appear on the site, sort of like the Slashdot bug (now fixed) that sometimes let you see our stories before they appeared on the main page. The clearest instructions I saw for exploiting the "Survivor Spoiler" bug were here. I'm sure CBS will fix this soon, but you could still pull the trick as of 6:40 a.m. (US EDT) this morning. Do you think this is a true bug, or is CBS doing it on purpose (with the "wrong people" crossed out) to increase interest in the show?

Well, today is the day Kevin Mitnick is supposed to be released from prison. But many people feel sites like this one aren't obsolete quite yet, because it's hard for ex-cons to make their way in society, and it may be especially hard for Kevin because he isn't allowed to use computers - and that's what he's good at, right? A 60 Minutes interview with Kevin is scheduled to run this Sunday. Hemos comments, "One wonders if having a microphone near violates his Draconian parole computer restriction orders." An interesting - and scary - thought.

wilkinsm writes "CBS is starting a new game show this fall called "Survivor." 16 constestants will be sent to a deserted island for seven weeks. Eventually the one that "survives" becomes the winner. It looks like all you get to take with you is your shirt on your back. There are looking for a "diverse" group of contestants, so I thought maybe some of you would like to try. " So, tribal counsels vote people out - I see Lord of The Flies, II: The Revenge of Piggy.

wilkinsm writes "CBS is starting a new game show this fall called "Survivor." 16 constestants will be sent to a deserted island for seven weeks. Eventually the one that "survives" becomes the winner. It looks like all you get to take with you is your shirt on your back. There are looking for a "diverse" group of contestants, so I thought maybe some of you would like to try. " So, tribal counsels vote people out - I see Lord of The Flies, II: The Revenge of Piggy.