>Guide to (mostly) Harmless Hacking
>Vol. 5 Programmers' Series
>No. 4: How to Program in C, part 1

>Newbie note:  Wonder why there are all those "Free Kevin Mitnick" Web
>sites in the haxor scene?  Many people think it is ludicrous to keep that
>man behind bars because he was such a lame hacker that he apparently

has nothing to do with his ability. It has to do with right vs wrong, and
unjust treatment in our court system. 

>Newbie note:  A socket is a round-trip or two-way network connection.
>For example, when you telnet into another computer's login sequence, you
>connect to port 23 on that computer.  It completes a round-trip
>connection by assigning some high number port, for example port 3587, to
>complete the socket.  If you have a shell account on a good ISP, you can
>see everyone's sockets by giving the "last" or "netstat" commands.

flatland ~$ last jericho
jericho   ttypa    ip98.ts6.phx.inf Wed Sep  9 02:10 - 08:44  (06:33)
jericho   ttypf    ip98.ts6.phx.inf Tue Sep  8 20:50 - 02:02  (05:12)
jericho   ttyq6    ip2.ts1.phx.infi Tue Sep  8 07:40 - 20:50  (13:09)
jericho   ttyp6    ip179.ts3.phx.in Mon Sep  7 21:41 - 07:41  (09:59)
jericho   ttyp6    ip103.ts2.phx.in Mon Sep  7 09:29 - 09:56  (00:26)
jericho   ttypa    ip103.ts2.phx.in Mon Sep  7 05:54 - 09:25  (03:30)
jericho   ttyp9    ip168.ts3.phx.in Sun Sep  6 19:37 - 05:44  (10:06)

Err.. where does it show my sockets? (it doesn't)

>	The first thing you need is a C compiler.  While in your shell
>account, give the command "cc".  If you get the message "command not
>found," try the command "gcc" If these don't work, try "whereis cc" ,
>"whereis gcc", "which cc" (in Linux), "locate cc" or "locate gcc".  If
>none of those work, complain to tech support at your ISP.  Don't email
>us, because we can't help you with this problem!  If you have a free

You repeatedly say complain to tech support when there are other options
or things to consider. Many ISPs don't see the need to give compiler
access to everyone. So how about "ls -al" if you find the compiler and
check to see if it is group access controlled.

>problem.  If your shell account is set up like mine, no program can
>execute from the home directory.  It's a precaution I take against
>Trojans. (Imagine this, sometimes meanies put surprises in my account.)
>However, I have a directory named "bin" in my account.  Normally on Unix
>systems we name directories that hold programs "bin".  On my account,

or we could tell them about "./a.out"

>try to compile them and they don't work.  Aha, you have just discovered
>why hacker gangs are so popular.  There are many groups of criminal
>hackers out there who help each other out by figuring out how to compile
>exploits.  That is how Kevin Mitnick got as far as he did -- he had his
>buddies compile programs for him.

There are non criminal gangs that help each other figure out exploit code
too. And it's amusing how you believe everything you read.

>programming.  Real hackers simply call it "K&R." You can get eliteness
>points by responding to guys who talk reverently about "K&R" by saying,

eliteness points? ugh..