Slashdot Mirror

Nice article:

The TMC Primer

I can dig that, old-timer. I can see where you are coming from too. I came in on the tail-end of the BBS era, just when it was really starting to die, and the internet was just started to get around, in Australia. I could really have done with some of these phreaking deals when I was a kid ($2000AU phone bill, ouch).

The thing is, I'd hire you, as you have not been caught, yet you freely admit your past. Mitnick, however, was caught - yet he repeatedly complains about the rough deal. Who is the better hire?

• You mean this?

Interestingly enough, you can read about it here

--

Was it the sheep climbing onto the altar, or the cattle lowing to be slain,
or the Son of God hanging dead and bloodied on a cross that told me this was a world condemned, but loved and bought with blood.

DISCLAIMER:
This somewhat editorialized post is meant to provide some possible answers for you to ponder. I don't know if any of this is true. I do wonder though... and YOU SHOULD TOO!

Security firms have nothing better to do most of the time except sit around and think of a way to scare up another emergency. If they think it up (and make the claim publicly), they get headlines. If we don't rush to pay them for their services, then they will release the exploit to the kiddies (aka start breakin' kneecaps). It's totally conflict-of-interest and its totally protection-racket.

That's why they give us dilligent sysadmins a break. They release a warning that's just good enough for the 5-10% of the market who would never pay them for their dubius services willingly. The rest of the people get "You should be more like them. Pay us to show you how." ... or something BAD might happen...

That's what they call "white-hat" cracking. You sit around with computers full of the most popular software/versions and hammer the protocols with garbage until you get some kind of scream-in-agony from the victim servers' debugger/log windows. Then you get a cup of coffee. Then you go back to your source-code review, and look for ways to tweak your brute-force buffer-overflow hammer perl script. You drink a lot of coffee in that job.

When you find something, you ponder heavily whether to brag on IRC #l33t or start a boring vulnerability report. Maybe you can get a payroll wannabe to do your work while you brag on #l33t.

Go read back-issues of PHRACK or PHRACK or cDc for some introduction to the boring-ass-world of trying to boost your self-esteem at the expense of dumber folks.

DISCLAIMER:
This somewhat editorialized post is meant to provide some possible answers for you to ponder. I don't know if any of this is true. I do wonder though... and YOU SHOULD TOO!

Security firms have nothing better to do most of the time except sit around and think of a way to scare up another emergency. If they think it up (and make the claim publicly), they get headlines. If we don't rush to pay them for their services, then they will release the exploit to the kiddies (aka start breakin' kneecaps). It's totally conflict-of-interest and its totally protection-racket.

That's why they give us dilligent sysadmins a break. They release a warning that's just good enough for the 5-10% of the market who would never pay them for their dubius services willingly. The rest of the people get "You should be more like them. Pay us to show you how." ... or something BAD might happen...

That's what they call "white-hat" cracking. You sit around with computers full of the most popular software/versions and hammer the protocols with garbage until you get some kind of scream-in-agony from the victim servers' debugger/log windows. Then you get a cup of coffee. Then you go back to your source-code review, and look for ways to tweak your brute-force buffer-overflow hammer perl script. You drink a lot of coffee in that job.

When you find something, you ponder heavily whether to brag on IRC #l33t or start a boring vulnerability report. Maybe you can get a payroll wannabe to do your work while you brag on #l33t.

Go read back-issues of PHRACK or PHRACK or cDc for some introduction to the boring-ass-world of trying to boost your self-esteem at the expense of dumber folks.

I suggest ketchup with your hat.

It is right here

Love them phrack DNS'.

Remote OS detection via TCP/IP StackF ingerPrinting

TCP/IP Stack Fingerprinting Principles

Graphing Randomness in TCP Initial Sequence Numbers

Security Problems in the TCP/IP Protocol Suite

System Fingerprinting With Nmap

Remote OS detection via TCP/IP Stack FingerPrinting

You should really read this article on Phrack 58, about binaries encryption in order to defeat debuggers/disassemblers (and the few decompilers out there).

all you open source fags are a bunch of pussies.

don't you know how real mean do it.

Sure ESR has a lot of guns but if you're just some law abiding pussy then it really makes no difference eh fags?

Looks like people better start working on this article in the latest issue of Phrack. It has the details of how to build a GPS jammer. When we people in power start to realise technology is a double-edged sword and raising the bar constantly like this just pisses people off?

Check the article for a technicle solution. Jam the GPS

Hoch

...and build one of these:

GPS Blocker

Cellular Telephones come in two basic versions, as car phones and portable phones, with a briefcase hybrid. Car phones are by far the most common, because they are much cheaper. But most believe that, ultimately, portables will be the most popular. Washington Post Company president Richard Simmons, whose company is a partner in several cellular systems, even predicts that by the early 1990's "There will be phones roughly the size of a calculators that you carry around in your pocket. They will cost no more than five hundred dollars. They will emancipate people from the necessity of locating a phone to make calls. The bad news is, you will never be able to get away from the phone, and we'll call it progress."

It turns out these guys were predicting the future...

I remember back in the day, I was on an internship at a local comp-sci research center. Of course I was only given a lowly user account, actually even worse than that. Anyhow, I had fun exploring Solaris, creating a lot of core dmps mainly, and came about the new issue of phrack.

I had looked through a few issues before after reading about it in Bruce Sterling's "Hacker Crackdown". I had perused the all-time favorites: how to build a bomb, a gun, how to break into cars, and so on. Back then, phrack was already archieved on the www, but the newest issue was only available as tarball. After lunch break, the admin asked me if had been reading phrack, he refered to it as "hacker stuff"---yes, I said, annoyed about him snooping around.

But then I actually read the new issue.

There was an article in it about how to get root on a Solaris workstation, exploiting the availability of FORTH on Sparc machines.

I was sitting in front of a Solaris workstation.

I smiled.

I kept smiling.

Four days and a lot of experimentation later, the administrator found a new file in his personal TODO directory (yes, he had actually called it that). It read


*""""""""""""""""""*
[pHraCK]

MAYBE YOU SHOULD READ IT, TOO.
*""""""""""""""""""*

The link to the phrack article.

The gzipped tarball of Phrack #60 is available at http://www.phrack-dont-give-a-shit-about-dmca.org/ archives/phrack60.tar.gz