Discover millions of ebooks, audiobooks, and so much more with a free trial

Only $11.99/month after trial. Cancel anytime.

Stealing The Network: How to Own the Box
Stealing The Network: How to Own the Box
Stealing The Network: How to Own the Box
Ebook459 pages6 hours

Stealing The Network: How to Own the Box

Rating: 3.5 out of 5 stars

3.5/5

()

Read preview

About this ebook

"Stealing the Network: How to Own the Box" is NOT intended to be a "install, configure, update, troubleshoot, and defend book." It is also NOT another one of the countless Hacker books out there. So, what IS it? It is an edgy, provocative, attack-oriented series of chapters written in a first hand, conversational style. World-renowned network security personalities present a series of 25 to 30 page chapters written from the point of an attacker who is gaining access to a particular system. This book portrays the "street fighting" tactics used to attack networks and systems.

Not just another "hacker" book, it plays on "edgy" market success of Steal this Computer Book with first hand, eyewitness accounts
A highly provocative expose of advanced security exploits
Written by some of the most high profile "White Hats", "Black Hats" and "Gray Hats"
Gives readers a "first ever" look inside some of the most notorious network intrusions
LanguageEnglish
Release dateMay 19, 2003
ISBN9780080481111
Stealing The Network: How to Own the Box

Read more from Syngress

Related to Stealing The Network

Related ebooks

Security For You

View More

Related articles

Reviews for Stealing The Network

Rating: 3.5 out of 5 stars
3.5/5

18 ratings0 reviews

What did you think?

Tap to rate

Review must be at least 10 words

    Book preview

    Stealing The Network - Syngress

    Questions

    Hide and Sneak

    by Ido Dubrawsky

    If you want to hack into someone else’s network, the week between Christmas and New Year’s Day is the best time. I love that time of year. No one is around, and most places are running on a skeleton crew at best. If you’re good, and you do it right, you won’t be noticed even by the automated systems. And that was a perfect time of year to hit these guys with their nice e-commerce site—plenty of credit card numbers, I figured.

    The people who ran this site had ticked me off. I bought some computer hardware from them, and they took forever to ship it to me. On top of that, when the stuff finally arrived, it was damaged. I called their support line and asked for a return or an exchange, but they said that they wouldn’t take the card back because it was a closeout. Their site didn’t say that the card was a closeout! I told the support drones that, but they wouldn’t listen. They said, policy is policy, and didn’t you read the fine print? Well, if they’re going to take that position.… Look, they were okay guys on the whole. They just needed a bit of a lesson. That’s all.

    So, there I was, the day after Christmas, with nothing to do. The family gathering was over. I decided to see just how good their site was. Just a little peek at what’s under the hood. There’s nothing wrong with that. I’ve hacked a few Web sites here and there—no defacements, but just looking around. Most of what I hit in the past were some universities and county government sites. I had done some more interesting sites recently, but these guys would be very interesting. In fact, they proved to be a nice challenge for a boring afternoon.

    Now, one of my rules is to never storm the castle through the drawbridge. Their Web farm for their e-commerce stuff (and probably their databases) was colocated at some data center. I could tell because when I did traceroutes to their Web farm, I got a totally different route than when I did some traceroutes to other hosts I had discovered off their main Web site. So, it looked like they kept their e-commerce stuff separated from their corporate network, which sounds reasonable to me. That made it easy for me to decide how I would approach their network. I would look at the corporate network, rather than their data center, since I figured they probably had tighter security on their data center.

    Tools

    First off, my platform of choice should be pretty obvious. It’s Linux. Almost every tool that I have and use runs under Linux. On top of that, my collection of exploits runs really well under Linux. Now, OpenBSD is okay, and I’m something of a Solaris fan as well, but when I work, I work off a Linux platform. I don’t care whether it’s Red Hat, Mandrake, or Debian. That’s not important. What’s important is that you can tune the operating system to your needs. That’s the key. You need to be able to be sure that the underlying operating system is reliable. On a related note, my homegrown tools are a mixture of Bourne shell, Expect, and Python scripts. There’s a small amount of Perl in there as well, but most of the scripts are written in Python. Code reuse is important if you want to be successful at this

    Enjoying the preview?
    Page 1 of 1