Exetools  

Go Back   Exetools > General > General Discussion

Notices

Reply
 
Thread Tools Display Modes
  #1  
Old 01-30-2005, 02:19
alastone
 
Posts: n/a
Question need help on compiling FlexLM v9.2

maybe I asked a stupid question, and I am sorry for this.

I tried to compile FlexLM 9.2 FULL SOURCE CODE (demo or other vendors), but it always gets into error and stops at here (demo, with default vendor keys and CRO keys):

......
lmnewgen demo -o lm_new.c
v8.1+ FLEXlm, non-CRO
lc_init failed: Invalid FLEXlm key data supplied
FLEXlm error: -44,49
......

even I had changed those three seeds with random numbers. any other changes were not made, exept for some errors in makefiles. I tried to use the lmv8gen.exe to generate keys, or keys fetched with OllyDBG from a FlexLM v9.2 victim (maybe I got wrong key5 and CRO keys), failed.

thanks in advance!
Reply With Quote
  #2  
Old 01-30-2005, 05:04
dirkmill dirkmill is offline
Friend
 
Join Date: Jul 2004
Posts: 23
Rept. Given: 0
Rept. Rcvd 0 Times in 0 Posts
Thanks Given: 0
Thanks Rcvd at 1 Time in 1 Post
dirkmill Reputation: 0
Wink

The 9.x SDKs don't work with v8 vendor-keys.
You may try the following keys for vendor "alastone"
Quote:
v9.x
VENDOR_KEY1 0xf1bd324f
VENDOR_KEY2 0xc0d8c168
VENDOR_KEY3 0x813080d2
VENDOR_KEY4 0xc5eb45fc
VENDOR_KEY5 0x7a703fb3

v10.x
VENDOR_KEY1 0x83f52c05
VENDOR_KEY2 0x633cf7ca
VENDOR_KEY3 0xf56c2940
VENDOR_KEY4 0x4709fe31
VENDOR_KEY5 0x7a703fb3
Your captured v9.2 data should work. You're probably missing something...

Dirk

P.S. You might want to get Nolan Blender's lmrecode source
Reply With Quote
  #3  
Old 01-30-2005, 05:17
Dmit
 
Posts: n/a
Quote:
Originally Posted by alastone
I tried to compile FlexLM 9.2 FULL SOURCE CODE (demo or other vendors), but it always gets into error and stops at here (demo, with default vendor keys and CRO keys):

even I had changed those three seeds with random numbers. any other changes were not made, exept for some errors in makefiles. I tried to use the lmv8gen.exe to generate keys, or keys fetched with OllyDBG from a FlexLM v9.2 victim (maybe I got wrong key5 and CRO keys), failed.
I'm not sure about DEMO, but message you got is normal if Vendor/CRO keys are invalid. Random number almost always leads to invalid keys.
lmv8gen generates keys for v8 only. It could be easily adapted to v9 by modifying 2 constants (both present in FlexLM 9.2 FULL SOURCE CODE :).
Getting key5 from victim seems to me much harder (if ever possible) than writing lmv*gen using info from Inet (where * from 4 to 10).

If you would post first 4 VendorKeys and VendorName, I could try to calc VK5 and CRO for you.
Reply With Quote
  #4  
Old 01-30-2005, 20:52
alastone
 
Posts: n/a
Thanks!

As an alternative way, I tried to use v7.2d & v8.4b SDK to generate licenses. v8.4 failed. even I specified -verfmt 7. I donot know why.

for Dmit,
thanks! I pm you the details.

Last edited by alastone; 02-01-2005 at 12:31.
Reply With Quote
  #5  
Old 01-30-2005, 23:55
alastone
 
Posts: n/a
Quote:
Originally Posted by dirkmill
The 9.x SDKs don't work with v8 vendor-keys.
You may try the following keys for vendor "alastone"
v9.x
VENDOR_KEY1 0xf1bd324f
VENDOR_KEY2 0xc0d8c168
VENDOR_KEY3 0x813080d2
VENDOR_KEY4 0xc5eb45fc
VENDOR_KEY5 0x7a703fb3

Your captured v9.2 data should work. You're probably missing something...

Dirk

P.S. You might want to get Nolan Blender's lmrecode source
Big thanks to Dirk and Dmit
Yes, I can reach here now:

#define VENDOR_KEY1 0xf1bd324f
#define VENDOR_KEY2 0xc0d8c168
#define VENDOR_KEY3 0x813080d2
#define VENDOR_KEY4 0xc5eb45fc
#define VENDOR_KEY5 0x7a703fb3

#define CRO_KEY1 0x321d784d
#define CRO_KEY2 0xf2c452ca

#define VENDOR_NAME "alastone"

and now I can successfully compiled the v9.2 SDK. the question is, the vendor keys I generated by using this protocol are not identical to the ones I captured in the memory. mmmh, I got obfuscated keys?
the keys coming with lm_code.h (demo) are wrong? stupid question again
Reply With Quote
  #6  
Old 02-01-2005, 05:55
CrackZ CrackZ is offline
VIP
 
Join Date: Sep 2004
Posts: 50
Rept. Given: 2
Rept. Rcvd 66 Times in 8 Posts
Thanks Given: 0
Thanks Rcvd at 14 Times in 8 Posts
CrackZ Reputation: 67
Hiya,

The keys in your target are not obfuscated, other than key 5 in the same old method.

The reason your keys differ is that the vendor keys as issued by Macrovision have options such as checksums, expiry dates etc, etc taken into the generation process, in fact in terms of generating a license the vendor keys aren't even used anymore.

Regards

CrackZ.
Reply With Quote
  #7  
Old 02-01-2005, 18:08
alastone
 
Posts: n/a
Quote:
Originally Posted by CrackZ
Hiya,

The keys in your target are not obfuscated, other than key 5 in the same old method.

The reason your keys differ is that the vendor keys as issued by Macrovision have options such as checksums, expiry dates etc, etc taken into the generation process, in fact in terms of generating a license the vendor keys aren't even used anymore.

Regards

CrackZ.
Yes, now I understant this. The vendor keys generated by myself and the other set with the help of Dmit are not identical: key1-4 are different, while key5 and CRO keys are same. There are all valid. Compiled two lmcrypt.exe resulted in same license sign strings. Unfortunately, the license is invalid.
I am trying to figure out the problem. Any hints are much appreciated.
Reply With Quote
  #8  
Old 02-01-2005, 21:50
CrackZ CrackZ is offline
VIP
 
Join Date: Sep 2004
Posts: 50
Rept. Given: 2
Rept. Rcvd 66 Times in 8 Posts
Thanks Given: 0
Thanks Rcvd at 14 Times in 8 Posts
CrackZ Reputation: 67
Hiya,

Your question can be simply answered by telling us the return value of _lc_checkout() ;-).

Its going to be either bad seeds or a public key verification error.

Regards

CrackZ.
Reply With Quote
  #9  
Old 02-02-2005, 05:22
dirkmill dirkmill is offline
Friend
 
Join Date: Jul 2004
Posts: 23
Rept. Given: 0
Rept. Rcvd 0 Times in 0 Posts
Thanks Given: 0
Thanks Rcvd at 1 Time in 1 Post
dirkmill Reputation: 0
Quote:
Originally Posted by alastone
the keys coming with lm_code.h (demo) are wrong? stupid question again
hi alastone!

the demo-keys are not wrong, just expired
see below for the output of lmrecode

Quote:
Input vendor name (Actually daemon name):
demo
Version of input data (3, 4, 5, 6, 7, 8, 9 or 10=2):
9
Input decvals[0] = 37efbbfe
Input decvals[1] = ffffffe1
Input decvals[2] = ffffffff
Input decvals[3] = 71eed201
Expiry date: 1-jan-2005
Encryption seed1: 0b165dc9
Encryption seed2: 0b165dc9
VENDOR_KEY1 0xc945f9e3
VENDOR_KEY2 0x45083d28
VENDOR_KEY3 0xd42a1e0d
VENDOR_KEY4 0x16a59630
VENDOR_KEY5 0x0b165dc9
Dirk
Reply With Quote
  #10  
Old 02-15-2005, 20:13
simri
 
Posts: n/a
Is this correct check sum of LEXlm_v9.2_Full_Source.zip


FLEXlm_v9.2_Full_Source.sfv:
FLEXlm_v9.2_Full_Source.zip e8c505fe

FLEXlm_v9.2_Full_Source.md5:
5e7bb64ec8501818adbd4ecb9ff24b76 *FLEXlm_v9.2_Full_Source.zip
Reply With Quote
  #11  
Old 10-19-2005, 20:20
Git's Avatar
Git Git is offline
Old Git
 
Join Date: Mar 2002
Location: Torino
Posts: 1,115
Rept. Given: 220
Rept. Rcvd 265 Times in 157 Posts
Thanks Given: 108
Thanks Rcvd at 216 Times in 124 Posts
Git Reputation: 200-299 Git Reputation: 200-299 Git Reputation: 200-299
Very late reply, but yes - I get the same MD5

Git
Reply With Quote
  #12  
Old 10-22-2005, 15:27
Sailor_EDA Sailor_EDA is offline
Friend
 
Join Date: Nov 2004
Posts: 67
Rept. Given: 8
Rept. Rcvd 2 Times in 2 Posts
Thanks Given: 42
Thanks Rcvd at 4 Times in 2 Posts
Sailor_EDA Reputation: 2
Question Having similar problem compiling flexlm 9.2 sdk

I'm also having a similar problem as Alastone in that I'm having trouble generating valid vendor keys for v9.2 sdk. I'm still learning about flexlm so I just thought I understand the basic application using what I can compile from the sdk first.
I was trying to follow Dmit's suggestion of modifying lmv8gen to modify it to work with v9.
I have a couple of questions on this and I needed some pointers.
1. I can't seem to locate where the constants are in lmv8gen, I'm still looking but at the bottom of the file it says "Crossfire PE Encryption System AK47 ..."
However I use PEiD on it doesn't detect anything. It does not look like the file is packed.
2. I've got Nolan's lmrecode.c code and also looking at the PGC lmkg7.exe, I can clearly see two constants that he defines and uses. A quick search in the v7 flexlm SDK didn't seem to come up with this value being defined anywhere but I guess is might be lodged in some library if I'm not wrong. I should probably do a binary string search. Well anyways I was trying to find out where this string might occur in the SDK to locate the corresponding value for the v9.2.
3. Why is it that in lmrecode.c, just one glseed is used per version whereas in lmkg7.exe there are 2 constants (also thats what Dmit suggests as well about lmv8gen)

Any suggestions?

Sailor_EDA
Reply With Quote
  #13  
Old 10-22-2005, 17:04
tom324 tom324 is offline
Friend
 
Join Date: Jan 2002
Posts: 231
Rept. Given: 5
Rept. Rcvd 7 Times in 6 Posts
Thanks Given: 21
Thanks Rcvd at 27 Times in 16 Posts
tom324 Reputation: 7
Valid constants are here:

h**p://www.woodmann.com/forum/showthread.php?t=7324

Tom
Reply With Quote
  #14  
Old 10-23-2005, 03:28
Sailor_EDA Sailor_EDA is offline
Friend
 
Join Date: Nov 2004
Posts: 67
Rept. Given: 8
Rept. Rcvd 2 Times in 2 Posts
Thanks Given: 42
Thanks Rcvd at 4 Times in 2 Posts
Sailor_EDA Reputation: 2
Smile

Quote:
Originally Posted by tom324
Valid constants are here:

h**p://www.woodmann.com/forum/showthread.php?t=7324

Tom
Thanks Tom, infact a couple of hours after making my post I happened to run into that thread at woodmann's.
However, that still doesn't help in "wanting to catch my own fish"
Reply With Quote
  #15  
Old 10-23-2005, 04:32
Ginfix
 
Posts: n/a
Quote:
Originally Posted by Sailor_EDA
2. I've got Nolan's lmrecode.c code and also looking at the PGC lmkg7.exe, I can clearly see two constants that he defines and uses. A quick search in the v7 flexlm SDK didn't seem to come up with this value being defined anywhere but I guess is might be lodged in some library if I'm not wrong. I should probably do a binary string search. Well anyways I was trying to find out where this string might occur in the SDK to locate the corresponding value for the v9.2.
3. Why is it that in lmrecode.c, just one glseed is used per version whereas in lmkg7.exe there are 2 constants (also thats what Dmit suggests as well about lmv8gen)

Any suggestions?

Sailor_EDA
As for point 2, you might want to take a look into l_sg and l_zinit subroutines
For point 3, take another look around in lmrecode.c, there are definatly two
seeds set.

Greetings

Ginfix
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
.Net native compiling atzplzw General Discussion 8 01-10-2011 15:47
Problem compiling IL loman General Discussion 6 06-25-2005 17:56
MS-DOS 6 Source Code - Compiling? PiG_DoG General Discussion 1 07-10-2003 22:59


All times are GMT +8. The time now is 22:59.


Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX, chessgod101
( 1998 - 2024 )