Slashdot Mirror


NETI@home Data Analyzed

An anonymous reader writes "The NETI@home Internet traffic statistics project (featured in Wired and Slashdot previously) has a quick analysis on the malicious traffic they observed. It's a rough world out there." Perhaps not suprising, but still disheartening, the researchers find among other things that a large portion of typical end-user traffic consists of malicious connection attempts.

18 of 155 comments (clear)

  1. But did they find intelligent life? by miracle69 · · Score: 5, Funny

    That's what we need to know.

    --
    Linux - Because Mommy taught me to Share.
    1. Re:But did they find intelligent life? by eobanb · · Score: 5, Funny

      Well, they found people with a bunch of Windows Services on and all their ports open. Does that answer your question?

      --

      Take off every sig. For great justice.

    2. Re:But did they find intelligent life? by netcrusher88 · · Score: 4, Funny

      Coming soon: NETI@home discovers sentient penguins and daemons... "Penguins were seen to be working alongside daemons, cultivating apples and mischievously breaking windows..."

      --
      There's an old saying that says pretty much whatever you want it to.
  2. Considering.. by Renraku · · Score: 4, Insightful

    Considering these malicious programs aren't following any kind of 'standard' to reduce bandwidth utilization when checking over entire subnets of IPs that have been checked by 100000x other copies of the virus, it doesn't suprise me one bit.

    It would be like setting up a massive feedback loop on a mail server. When user X gets message X, he passes message X to user Y, who upon receiving message X sends it back to user X.

    --
    Job? I don't have time to get a job! Who will sit around and bitch about being broke and unemployed then?
  3. RBL of infected/malicious sites? by nizo · · Score: 4, Interesting

    Does anything like this exist already? It would be nice if I could filter, say, ssh traffic coming from "known" naughty sites, and report sites that portscan me, though probably I should look at using smartcards or something more secure at this point. I can't just restrict the ssh port at the firewall, since people could be coming in from pretty much anywhere because of travel to remote sites. Aside from complaining to upstream providers (which so far has yielded zero responses) when I see people banging away at ssh, I don't see much else I can do.

    1. Re:RBL of infected/malicious sites? by delirium+of+disorder · · Score: 4, Insightful

      Why can't you restrict access to ssh from the firewall? One solution could be port knocking. You only let your firewall open up ssh after a series of connections on pre-defined parts are made. So say you choose "233 457 69 876 2094 576" to be your "password". You would make a client that would connect to those ports in that order and only after that initiate an ssh connection on port 22.

      --
      ------ Take away the right to say fuck and you take away the right to say fuck the government.
  4. In other news... by Anonymous Coward · · Score: 5, Funny

    Yeti@home has yet to yield conclusive results.

  5. Root of the problem by SamMichaels · · Score: 5, Insightful

    Ignoring all complaints about Windows, the root of the problem goes back to having access to the network in the first place. If ISPs would spent a few bucks on implementing passive traffic analyzers to search for the viral/trojan patterns and null route offenders, we'd clean things up pretty quick. Why do we have all these piracy probes going on to sue people and no infected probes going on to cut people's access?

    Now, stepping back to the Windows complaints...wouldn't the ISP turning off your access motivate you to get a BASIC education in computing and maintain your PC?

    To make an analogy, in most states you need to have your car inspected (and some require emissions inspection, too). PUBLIC roadways means you share it with other people...an unsafe car affects more than just you. When you're connected to the net, your PC affects everyone else. I'm not suggesting the ISPs make an inspection system or a law passes to force ISPs to monitor traffic, but the same logic applies....someone should be doing checkups and flagging the offenders.

    1. Re:Root of the problem by EvilTwinSkippy · · Score: 4, Funny

      Amen to that. Car analogies have just plain run out of gas. People get too much mileage on them. They start more flamewars than a Pinto.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    2. Re:Root of the problem by glesga_kiss · · Score: 4, Insightful
      If ISPs would spent a few bucks on implementing passive traffic analyzers to search for the viral/trojan patterns and null route offenders, we'd clean things up pretty quick.

      Bollocks.

      The aren't running a network in their parents basement you know. Their networks are massive, with nodes LITERALY spanning thousands of miles. The volume of traffic they deal with is HUGE. They use cutting-edge routers just to keep up with the demand.

      How on earth do you do traffic analysis on that level? You might be able to catch some of the more obvious spammers, but how do you differentiate (on the IP level) between: a) a residential user b) a commercial user who maildrops willing customers c) a zombie d) a community group or e) blah. Blocking someone based on traffic is not possible, unless you want to lose your valid customers.

      What they should do is be more responsive to complaints. If a customer of theirs is a zombie spambot or acting as a stepping stone for some script kiddie, they should have their connection suspended until it is remedied. But they can only do this based on a complaint.

      Besides, what's the profit in spending any resource on the problem in the first place? Until that is affected, they won't care about it.

  6. In a few minutes... by vectorian798 · · Score: 4, Funny

    ...they will realize that there isn't anything more malicious than the traffic from Slashdot.

  7. Standards for viruses? by MarkByers · · Score: 4, Insightful

    You can't impose a standard upon viruses. What will you do if a virus doesn't follow the standard? Find the author and punish them unless they fix it and release a new version that fully supports the standard?

    The only way viruses will ever get standards is if the authors agree that they will get a considerable benefit by working together. I can't see that happening.

    --
    I'll probably be modded down for this...
  8. DSL/modem/router by FidelCatsro · · Score: 4, Insightful

    Its insane the ammount of bandwidth this is sucking up (i remember a time when virus's and worms were relativly well programed, still as bad but less collaterol dammage).
    I would like to see more ISP isntead of suplying basic DSL modems with those overpriced sign up deals but instead a proper firewall/router/Dsl modem.
    This would save us all alot of pain in the long run .

    --
    The only things certain in war are Propaganda and Death. You can never be sure which is which though
  9. Re:Not necessarily a Bad Thing... by Anonymous Coward · · Score: 4, Insightful

    I'm pretty sure internet connectivity is neither a privilege nor a right. It's just a service, plain and simple. You pay ISP, they provide internet connectivity. You don't pay, you don't get internet. No rights or privileges involved.

  10. Time to drag out this old chestnut by This+Old+Chestnut · · Score: 4, Funny

    "Those willing to give up a little security by using a little obscurity deserve neither security nor root privileges".

    -Benjamin Franklin

  11. Cheap access means unsafe computing by jfengel · · Score: 4, Interesting

    Sadly, while some customers might get motivated to learn something, others would just be motivated to switch ISPs. Which costs the ISPs money, which means that they won't do it.

    At least such is their thought process as often presented. I suspect it's bad cost-benefit analysis; if your dumber customers leave, it's probably a net win for you. Smarter customers mean less bandwidth (at least, they don't act as spam zombies maxing out the bandwidth) and fewer tech support hours explaining how to fix the cup holder.

    The big players (AOL, Comcast) are the best targets for this logic, but they live for those left-side-of-the-bell-curve customers. They're the "default" ISPs that people get because they're so readily available, so they get all the customers who don't know better. (Hell, I don't know better; I use Verizon for my DSL but I don't let them do anything but provide me bits.)

    So AOL and Comcast are in a bit of a bind; they don't want these customers, but they don't want to lose them, either. I think that they're probably going to have to use gentle persuasion to say, "Hey, it looks like you've a spam zombie. Please call your cousin's best friend to clean the crap off your computer again and give you a stern talking-to. And please stop downloading Bonzi Buddy."

  12. Don't use SSH password authentication by SIGBUS · · Score: 4, Insightful

    You really should be using RSA or DSA keys instead of passwords. Hardly a day goes by that my systems don't get at least one script-kiddie SSH password guessing scan. Since I'm requiring keys for authentication, they're wasting their effort; if someone manages to crack a public key, we have far worse problems than password guessing.

    --
    Oh, no! You have walked into the slavering fangs of a lurking grue!
  13. Re:Not necessarily a Bad Thing... by Mr.Sharpy · · Score: 4, Interesting

    The ISP KNOWS the physical addresses of the cable/dsl modem a home user has. It's not like the ISP has no idea which ip addresses are home user or account is using at any given time. How do you think they can reliably (for the most part) identify people for the likes of the RIAA when they ask. Likewise, with modern hardware and software its a pretty trivial task for an ISP to turn your internet access down to a crawl or off with the click of a button. They can do this, they just don't want to.

    Maybe it would be a good idea to throttle the users down to a bare minimum and redirect all http traffic to a gateway page to tell them they have a problem with their computer they need to correct. It seems to work for wireless access points in hotels/airports/coffeeshops. Why can't big ISPs do the same thing?