hi all ..

i was told that if i want to lern FlexLM i should read the Crackz tut page ...
so i did ..
i read and read and read and read etc...
but all the tut there are starting from the middle ..
i searched for more and all was the same ... all
starts from the middle of the cracking !!

there is no (or i didn't find any) STEP BY STEP tut about
FlexLM thats why i got SAD !!!

if any1 can help me with that plz post once and for all
a g00d tut !

tnx
LaBBa ....

Search for the first part and the end part.Fixed the puzzle and write a tutorial

Howdy,

Check some of the other links at the bottom of this page.

Woodmann

first of all :
i'm sorry if i offended someone by sayin : Lame tut
they r very high level cracking and i got Mad that i didn't
found any full tut....

i will write a full tut step by step about all that will contain all
as soon as i will crack at least 1 fucking FlexLm

if anyone would like to join and help ... plz DO !!

=D

Personally, with programs protected with FlexLM and the like, unless the program is updated regularly (say once a month or so), I believe the protection should be removed completely, and not key-genned.

It's true that there's no "from the ground up" tut on FlexLM, but if you search this board and the tuts, you'll find everything you need.

yea i gess u r right..

i gess i got used to unpacking and the approach of cracking...
thats why i got lasy....

Didn't you've read my title.I'm insane DDDD

I think we all know that esther

Hmm Sqoodge,

Do you really think you know I'm insane? Probably you are the same

quite possibly

There are a couple of comments that I should make here.

Firstly, when dealing with flexlm based protections, its generally better to build a key generator, since sometimes critical data is stored in the license file. The program does not have to be patched, so this greatly lessens the probability of a bad crack. Unless all the calls are properly patched out, there is a chance that various problems such as memory leaks may be introduced, or locations that patching may be required are missed. Certainly some of the later versions of flexlm require some patching, but this should be done as minimally as possible to reduce the chances of introducing defects into the program. The attitude that a keygen is superior to a crack is fairly pervasive; that is why a "keygen" can be released when there is a "crack" released already, but the converse is not true. Keygens often work for minor updates of a program too, cracks (execpt for certain context dependent ones) are dependent on the version being exactly right.

As far as tutorial go, flexlm has been fairly heavily documented. Generally the documents that you'll find won't be pure hand holding, since by any reasonable measure basic flexlm is fairly straightforward, and you won't generally have to deal with packing and antidebug tricks, and for that matter in most cases you won't even have to rip any code.

Some add ons/options require more reverse engineering, or the use of some proprietary flexlm tools, and some versions of flexlm require patching. In the Fravia archives, and on CrackZ' page, you will find what you need for most flexlm targets. If you need to go beyond that, the path, even though not publicly document isn't that hard to find.

Having said that, you'll probably get a lot more help from here if you put down what you've tried, and where you're having difficulty.