Larva
A hacker's page. Hackers usually know many complicated languages like Assembler, C++, but as we will see, this does not mean they are polyglots:
The Hacker's Dictionary
A Guide to the World OF computer Wizards
Computer wizards, but not translation wizards!
To You find those words defined here won't. This, we warn
you, is supposed to a fun book.
It is funny, indeed. Not for the reasons which the author was thinking of, though.
Thesis of AR the words used for fun by the people who use of
computer for fun: the of hacker. Here you wants finds almost
NOT-HUNG OF those awful computer LANGUAGES visits as BASIC that CAN written but NOT
spoken. (...) Our course OF six contributed to this file more over the
years, and to this revision for publication. (Steele coordinated the EFF
place and did most OF the polish work. Occasional first person of
references into the Main text of AR his unless otherwise identified). Many OTHER of
hacker around the country, too numerous to of cunning, larva helpful
suggestions; to them we AR grateful.
Again this totally off-topic larva! Where could it come from ?
(...) Confessions OF a Happy hacker By Guy Steele
I which a tea-gnaw hackers.
When I which about twelve or so, a lab secretary RK WITH who knew I
which " interested into science " (it more accurate to might say " a latently
nerd ") arranged for one OF the computers of hacker there to give ME on
informal route. I more remember stumbling around racks full OF circuit boards
and of wires, a screeching cabinet that printed a full PAGE every six
seconds, and rows OF blinking lights:
(...) This PDP-6 which thus versatile: it had two speakers and a stereo more
amplifier sitting on top OF it. The hacker typed a couple OF COMMAND on a key
board, and the PDP-6 burst into a brook Brandenburg Concerto (No. 6, as I recall).
One part OF that route of status out most clearly in my at least I which
told to sit down in front OF a large, round, glass screen, and given a
box that had some buttons and a stick on the top. My hacker guide typed
a COMMAND on the key board, and suddenly, green and pure-polarizes space ships
appeared on the screen! The pure-polarizes one started shooting little talks dots
RK the green one, which which soon obliterated in a multicolored more shower
OF of sparkles. The green ship which " mine ", and the hackers had expertly
shot it down. This which a color version OF space was, one OF the very
first video of games.
Note that the lower two thirds of the page are perfectly written. Apparently the guy tried to run his article through Astalavista's Babelfish and forgot a piece of text.
This is not the case with the hacker course III. Plenty of German leftovers are scattered through the whole page, because the very popular writing style - Scheisse (shit), Proggi (program) - confused the translator:
Halloechen young,
on a new... This time it is a TP Proggi, which we want to look at ourselves...
With high-level languages Proggis is it always ' n bissel
scheisse, because there Calls in it are actually, those no direct meaning for that
Run time behavior have, it one gepusht, gepopped and all possible,
however all of this is completely uninteresting.
Okay, but now ran to the code...
I recommend all, which feel large itself genung to crack the Proggi
here no more read on, and also the PAS source code to look at...
The problem with a code query is usually not to go around
this but these too _ find _ and that are here ' n bissel bloed, there
continuously any Queries to be made...
Always the program is however simple... as first traced one it simply times through...
and see there, at offset 0É1 finds one the password input routine.
thus restarted one the Proggi and traced times the routine through...
' n few lines beforehand is transferred the storage point, into nacher the mine
Text is... Looks times at offset 03D9, there after DI 0144(hex) one geMOVt.
If one looks at oneself this storage point with DDS:144(hex), then one finds
there first a byte of which the length of the stringer indicates and the stringer
even again...
In the routine sieht's net particularly interesting out..., thus raus from the routine,
and further looked... Useful it is from now on always the Watch function of its
debugger on that Offset DS:0144 to set, because always is here my PWText, and
so can I detect each modification...
Far steppes... AND one already sees also a modification, because the call at
offset 03F1 caused amusing-proves rotate the letters... thus BRKPT set
and up to then again to execute let tracen, times the routine and which to find we??
A XOR routine... with XOR 1 (offset 0214)
Hmmm either one could rausmachen this routine now and the PWText of the
Proggis look up and always a blank instead of the PW byte there enter,
then one must stop always a certain number of blanks and Enter
press or one go around the protection completely... Since I do not want all before-prayed
naturally, I become only briefly this Tracen and you then the field fully left to routine to
end...
(...) There I many inquiries because of any Tools " which one for debugging
absolutely needs " got, I times will few enumerate here...
1. Absolutely necessarily a HEX wordprocessor, with memory, (schneller) look-up, Hex
and ASCII function.
2. A UNProtector, like UNP, TRON, XOPEN, UX, etc.... the PKLite, LZEXE,
Tinyprog, protect!, Ultrapress, etc.. Proggis to unpack can...
(that is sometimes nervig by hand... (((;)
3. Debugger, which one must buy stop, or from ' nem friend
naturally borrow (with original disk... to that may it during you it have
naturally on its disk do not have logo... Raupkopieren is punishable!!) borrow as said...
If possible which good like the TD or the CodeView... so'n D86 (Shareware) commodity is not so
whole...
4. DEBUG.EXE, in order to store the program, sometimes is it with the HEX wordprocessor
Scheisse, because one does not see instruction, but only their Opcodes...
(or a debugger with memory function, that would be naturally best...)
6. possibly programming languages (to the NOT also QBasic does) around sections out
the program for ribs, data for XORen, then one can also in the sample program
the passwords decipher, (simply XOR 1-Verknuepfung with the PWBytes make) etc....
7. Much patience...
8. Which also totally important I find, is 2. Monitor. And so on... 
