Message Body = i personally am not thrilled about the idea of making the hcuml repository a public link on pages
it may be somewhat public already, but i think the ability for us to choose with discretion who we show it to (until of course it becomes well known and we dont have much of a choice) is quite nice
at least that way it grows in a reasonable rate and remains the kind of list we want it to be, not a chatroom for just anything
regarding the anonymizer discussion, both sides have valid points...
1) yes people need to learn to do these things on their own
no good set of crackers/hackers can learn anything without hands on practice
2) anonymizer being relatively unique needs to be shared among us - much in the way softice has been traded
some tools of the trade are too important to not give freely (but then i am biased since my way is to give freely everything i can)
*) effectively what i mean by this is that some things should be shared in order to give ideas on how to do others (if you remember the way the tutorials are set out, a crack or three is done by the teacher to impart a few possibly new ideas, and the next few cracks are left for the students to complete - this is at least how hcu lessons go
port switching is a basic, but has not been really shown to the newest people - so it should be an exmple for future cracks (our lessons are based on learning by example - which is then worked through like any good textbook)
though no good textbook can expect to get anywhere if the basic methods are not outlined before the homework is assigned
you of course can have your own opinions, but this is mine
+gthorne
=====End of Issue 141===================================
well folks - i have finally gotten entirely frustrated
at the way the systen is going and have done what i said i would never do...
....use email and web forwarding
my new site is in norway (thanks to a friend there) and my net address is
*****************************
my email forever will be ********************
(for now it forwards to ******************* but since the hacking a few weeks ago and the shutting down of cracking.net, i have lost 2 websites, over 2mb of email and my patience)
i guess it was a long time coming.
i am going to take a bit to redo my site so it may be pretty lame for a little while
meanwhile,
take care all
+gthorne'98
=====End of Issue 143===================================
the only essay i have seen in a long time on interrupt vector hooking is in the orc tutorials themselves
the vector space is just a table of jump locations (vectors being the name for that) which is called by an interrupt.
each interrupt has its own jump in the table, and by doing a little math on the interrupt number itself you know the location of the corresponding vector
the reach for the skies program is one of the ones that uses vectors to point at a protection (by setting a tsr before the program runs, you can point the vector at a new location past the protection)
kinda funny that the protections can be defeated so easily - because the protections involved are often self checksumming or even rewritable code
so you cant patch the program without serious reverse engineering - so basically you patch the vector instead on the fly (change memory as the program runs instead of altering the program if i was too cryptic in my answer above)
since the orc tutorial on the subject discussed it, but showed no completely working model, i put together full assembly source for a tsr vector patcher for 'reach' in the orcpak on my site
....so you can see what is being done
effectively this is no different from cracking a file and hex editing it, only that you crack the file and tell your little tsr to hex edit it instead
i am sure there are plenty of uses for this type of crack patch still, but in my opinion - programmers are kind of lazy in the dos world of protectionism now, and the windows world requires different methods entirely
i hope this helps, and if anyone knows of any other information on the subject for halvar to read, please post
it would be interesting to see if anyone can make a windows on-the-fly patcher to solve some of the selfchecking windows apps that are sure to become more prevailent in the near future
razzia and madjester could easily i am sure, but then they have been writing win32 apps in asm using the debugging api
i am going to be playing with writing win32 apps in asm myself soon - though it is tedious, i am quite impressed with the idea and besides, program a fe and win cracking gets so much easier when you actually put your own code to work instead of simply following someone else's
