Hi,
I got a simple question about SN in Feature line.
I read flexlm manuals about SN but I didn,t find any help. I searched RCE for that but it didn't help me any more.
I'm studying a flexlm protection. A nice respectable group has released is before with ANY license.dat. Now I'd like to study it.
One of the lines is:
FEATURE TIRE M*S*C 2005.1012 10-dec-2012 100 A03AEB3F2C14 \
ISSUED=19-dec-2004 SN=1283656-BA4DF72C40E9FFFFE26F

I want to know whats the role of SN here. I tested it, with a valid license made with a different SN. It didn't work. I want to know if its an external SN validation or its a flexlm capability to verify the SN with your own Seeds.

Could anybody give me a little help or any source to study , any tut...to make me to go ahead another simple step.

rgrds
FS

FLEXlm Reference Manual says:
"3.5.18 SN

SN=serial_num

Optional field. Useful for differentiating otherwise identical INCREMENT lines. Its only use by FLEXlm is to be encrypted in the signature. Similar to HOSTID."

All-in-one.

WBR

The "SN" number may be dependent on the featurename, licensce number, expiration time and the version. I also want somebody can help me to solve this trouble.

FoxB has answered this correctly.

From a FLEXlm perspective the SN field is only added to the license generation process so it guarantees different license keys, say on a per customer basis.

However from a developers point of view different SN values can be issued and validated on the application side to certain criteria, much like a serial number protection, the key to working this out is to find lc_auth_data() in your target, if you check the lmgr.lib (specifically l_check.obj) you shouldn't have much trouble finding it ;-).

Regards

CrackZ.

Hello, Crackz.
Could you please give me more detail information. I appreciate hearing from you.

What he's saying is, no its not checked by flexlm persay.

SN=ABCD, the flexLM manager wont check the ABCD like a serial, only hash it into the sign/checksum of the overall license, however the program its self could use the ABCD portion, for additional checks, and thus set the breakpoint at lc_auth_data as said