Although I've seen a lot of info on different aspects of Sentinel, I've never seen more than a few "works for me" replies as to the success rate.

I'd like to write up the fastest way (I think) for a user to go from a trial or local copy of a generic Sentinel soft to an unlimited network copy. This would act as a FAQ for those unable to piece together all the scattered data needed to get a working method. I'd like any feedback on your positive or negative experiences doing this yourselves.

I plan to have 3 parts - fishing out the necessary info, building the wlsc, and finally generating your strings. It may take a few days for me to write it all up, so I was going to collect info and opinions during that time - feel free to post that it's a lame idea everyone knows anyway... maybe it's true!

May be info from CrackZ site is Done?
Check
../crackz/Tutorials/Wlscgen.htm,
../crackz/Tools/Slmvidsn.zip

before

WBR

Sounds good to me, go for it. If you do it well and are a bit lucky, it might even become one of the "classics"...

I wish you good luck ;-).

Much of what has been written about v7.x is very much applicable to v8 of SentinelLM (license key formats have been slightly upgraded though).

The key things like the developer ID algorithm and so on are pretty much unchanged. There is some added protection to Wlscgen.exe though, 3 layers of decryption using the very familiar Sentinel 'message loop structure', didn't take me very long to dump each instance of message 0xB323 ;-).

Regards

CrackZ.

One quick question. If I have a exe file that in effect, "modbin's" another file, can I post it here or is that not OK.. I made this exe myself.

If you made the file and it does not contain "identified" code from a commercial product, I would not think it would violate our Rules. As long as the code does not "identify" or "specify" that it comes from another "commercial" product, it should be O.K.

If you Post it, and it appears to be a problem, we can always remove it, or ask you to censor some comment in it or find some other solution.

Regards,

OK, here's the first outline. The final writeup will have the details enclosed (but not copy/pasted from other tutorials) but for now I will just do the references.

1) Fishing the vendor ID from your target - ala Cyberheg
http://www.woodmann.com/fravia/nolan_sentinel.htm
This will probably be expanded a little to talk about dll vs embedded code, but the technique is equivalent.

2) Setting up a sacrificial Wlscgen, - ala Mayputra
http://www.woodmann.com/crackz/Tutorials/Wlscgen.htm

3) Some fun with modbin, and calling dll's from C - ala Nolan Blender
http://www.woodmann.com/fravia/nolan_sentinel.htm

Strangely enough, his demo program dumps an ID I recognized from back in the day - lol!

4) Modbinning an arbitrary target - writeup to follow.

5) Emulating the modbin in C - ala CrackZ, with some extensions
http://www.woodmann.com/crackz/Tutorials/Zenslm.htm

6) Arbitrarily emulating lscgen in C using Vendor ID and empty feature files - Probably a future work to avoid codesnatching, but you can see that it is possible. Basically to answer questions like - so how did XXX make this cool licgen that doesn't take 20 minutes to dump my strings?

And there you have it. I found that with the above references and a few sheets of notes it would be possible to make yourself a test key in about an hour or two, depending on if you started coding from scratch or not.

A trivia question I am still unable to solve completely - what is the param list of modbinfilelist? Seems to be 8, but sadly I only determined 4..!
1) Path
2) List file
3) Serial
4) "D" - to get the cool debug dump
5)?
6)?
7)?
8)?

It doesn't detract from the work, but it's pitiful to only decipher half a function - I'm not working from the installer, so I have one blind eye.