hi guyz, can anyone pleeze help me with crypkey files, whats the easiest way 2 find out the password or better still, hex code addresses 2 change 2 bypass the protection .....

Does it use Crypkey Instant or SDK?
What's the URL?

read the tut by amois:

h**p://www.woodmann.net/fravia/amois_sf_editor_2002_english.htm

theres no url m8, its a file i have, is there any way i can send it 2 u.. ??

solomon2000@gmx.net

Hi Sadsack/Solomon,
I'm following this one with interest. I've reloaded the file but only had 1/2 an hour to play with it & can't seem to find the oep via getprocaddress. Procdump seems to dump it OK using 'unknown' option but obviously the ep & header are screwed.
|Scally

Hi guys,
I dl'd the tut & app that was recommended by Solomon but when I try & run the sf thingy, I get an error message saying that the required file cryp95e is not found. It's there alright, so is this an instability in crypkey where a previous app can f* up a newer one?
I'll play some more when I got more time but the more I see, the wierder this thing becomes.
Scally

Wierd is not the word. I had filemon/regmon sitting on this on (re)install after cleaning the reg & naff 1K files from everywhere (20+) and it recreated a temp directory I'd used for a wdasm dump/procdump dump (& deleleted+removed from the recycle bin). I've tried patching the dumped exe (which runs, but exits before running the prog proper) and the original file but it never seems to get to the condx jumps that choose between the demo/std/pro versions of the file. The use of mfc42 may mean I've missed something but I'd sure like to know where I'm going wrong.
The (3) Crypkey tuts I've d'l'd & the apps they refer to don't seem to help. Even the one Solomon mentions in the post above doesn't seem to apply with the app I d'l'd - which went straight into the crypkey 'not authorised' screen rather than the 14day demo its supposed to be.
Can anyone with more experience shed some light on this protection please? So far I guess I have four apps I don't want eating up my hd space but not being able to understand how this works is really bugging me - particularly because the earlier tuts say its an easy protection to defeat.
Scally

yes CrypKey is easy to unpack. Finding the OEP is easy.

I just played with SF Editor 2002 and successfully unpacked it. It runs well in my Win2K server. No errors encountered. Only the offset changes coz the version differs.

To find the OEP, sure you can use GetProcAddress as a breakpoint. But I use another way. Change the section characteristics to E0000020, load it with SoftICE symbol loader, press F10/F8 to trace it from the beginning. After a short while, you will find the OEP