Thanks Thanks:  0
Page 2 of 2 FirstFirst 12
Showing results 11 to 16 of 16

Thread: Build LMCrypt without LM_SEED3?

  1. #11
    Junior Member Reputation: 10
    Join Date
    2020-06-04
    Posts
    12


    Default Re: Build LMCrypt without LM_SEED3?

    Code:
    /******************************************************************************
     *
     *      Module: $Id: //stg/eng/flexnet/licensing/c/v10-1/machind/blank_lm_code.h#1 $
     *
     *          COPYRIGHT (c) 1990, 2004 by Macrovision Corporation.
     *      This software has been provided pursuant to a License Agreement
     *      containing restrictions on its use.  This software contains
     *      valuable trade secrets and proprietary information of
     *      Macrovision Corporation and is protected by law.  It may
     *      not be copied or distributed in any form or medium, disclosed
     *      to third parties, reverse engineered or used in any manner not
     *      provided for in said License Agreement except with the prior
     *      written authorization from Macrovision Corporation.
     ******************************************************************************
     *
     *      Description:    Used to generate lm_new.o/.obj and by license-
     *                      generators.
     *
     *      Once the kit is "built" (using make or nmake) this file is no longer 
     *    needed, but should be stored somewhere safe.
     *
     *    Set the following values:
     *      VENDOR_KEY1-5         Provided by Macrovision Corporation.
     *      VENDOR_NAME         If not evaluating, set to vendor name.
     *      LM_SEED1-3             Make up 3 32-bit numbers, (or use 
     *                'lmrand1 -seed' to make up), keep secret, safe, 
     *                and never change.  
     *    TRL_KEY1-2         Provided by Macrovision if TRL used.
     *      LM_STRENGTH:         If using TRL, set to desired length 
     *
     *    Upgrading:         from version older than 8.1: Copy your 
     *                ENCRYPTION_SEEDs from the old lm_code.h file.
     *                Make sure LM_STRENGTH matches, if you were
     *                using LM_STRENGTH
     */
    
    #ifndef LM_CODE_H
    #define LM_CODE_H
    #include "lm_trl.h"
    /*
     *     Vendor keys:           Enter keys received from Macrovision.
     *                Changing keys has NO impact on license files 
     *                (unlike LM_SEEDs).
     */
    #define VENDOR_KEY1 0x035954af
    #define VENDOR_KEY2 0xa12ce87d
    #define VENDOR_KEY3 0xd858921a
    #define VENDOR_KEY4 0xd642974a
    #define VENDOR_KEY5 0x6a3d64e1
    /*
     *     Vendor name.          Leave "demo" if evaluating.  Otherwise,
     *                 set to your vendor daemon name.
     */
    #define VENDOR_NAME "INTEL"    
    /* 
     *     Private SEEDs:         Make up 3, 8-hex-char numbers, replace and 
     *                guard securely.  You can also use the command
     *                'lmrand1 -seed' to make these numbers up.
     */
    #define LM_SEED1 0xdeadcafe
    #define LM_SEED2 0xc45eef33
    #define LM_SEED3 0xdeadc0d3
    /*
     *    Pick an LM_STRENGTH:       
     */
    #define LM_STRENGTH LM_STRENGTH_DEFAULT
    /*     
     *                       LM_STRENGTH Options are
     *                       LM_STRENGTH_DEFAULT:
     *                       Public key protection unused. Use SIGN= 
     *                       attribute. sign length = 12
     *                       TRL: 
     *                       LM_STRENGTH_113BIT, LOW:   sign length= 58 chars
     *                       LM_STRENGTH_163BIT, MEDIUM:sign length= 84 chars
     *                       LM_STRENGTH_239BIT, HIGH:  sign length=120 chars
     *                Pre-v7.1:
     *                       LM_STRENGTH_LICENSE_KEY:   Use old license-key.
     *                       If you're upgrading from 
     *                       pre-v7.1, and want no changes, set this to 
     *                       LM_STRENGTH_LICENSE_KEY.   
    */
    /*
     *    TRL Keys:        Provided by Macrovision Corporation, if TRL is used.
     *                 Be sure to set LM_STRENGTH to 
     *                 LM_STRENGTH_DEFAULT, above, if TRL_KEYs are zero.
     */
    #define TRL_KEY1    0x0
    #define TRL_KEY2    0x0
    
    
    #include "lm_code2.h"
    #endif /* LM_CODE_H */

    As you can see my lm_code.h does not have mention of seeds. I think my SDK is missing files/code.

    And If I try to define in lm_code.h

    Code:
     */
    #define ENCRYPTION_SEED1 0xEE25A77E
    #define ENCRYPTION_SEED2 0xE8FF3A1E
    #define VENDOR_KEY1 0x035954ae
    #define VENDOR_KEY2 0xa12ce876
    #define VENDOR_KEY3 0xd858921c
    #define VENDOR_KEY4 0xd642974f
    #define VENDOR_KEY5 0x6a3d64e0
    /*
    On compile - ERROR:

    Code:
            if exist lm_new.c del lm_new.c
            lmnewgen.exe INTEL -o lm_new.c
    ERROR:  Inconsistent lm_code.h file, unknown state
            Probably ENCRYPTION_SEEDs or LM_STRENGTH set incorrectly
    NMAKE : fatal error U1077: '.\lmnewgen.exe' : return code '0x1'
    Do you have a copy of the SDK? Could you upload to gofile.io?
    Last edited by wssh; 2020-06-12 at 03:30 AM

  2. #12
    Member Reputation: 271
    Join Date
    2009-09-10
    Location
    Earth...
    Posts
    346


    Default Re: Build LMCrypt without LM_SEED3?

    why you use different VENDOR_KEY1/2/3/4/5 ?! i give to you valid for v9.x and v11.x of the sdk

  3. #13
    Junior Member Reputation: 10
    Join Date
    2020-06-04
    Posts
    12


    Default Re: Build LMCrypt without LM_SEED3?

    Quote Originally Posted by BfoX View Post
    why you use different VENDOR_KEY1/2/3/4/5 ?!


    Only changed in post on forum. Not when compiling.

    I have lmkeygen3.0. Valid vendor keys are not the problem.
    Last edited by wssh; 2020-06-12 at 04:10 AM

  4. #14
    Member Reputation: 271
    Join Date
    2009-09-10
    Location
    Earth...
    Posts
    346


    Default Re: Build LMCrypt without LM_SEED3?

    FLEXlm SDK v9.2 build with the some set:

    /* Version 9 keys */
    #define VENDOR_KEY1 0x71114ae4
    #define VENDOR_KEY2 0x02c8ded4
    #define VENDOR_KEY3 0xac043b8e
    #define VENDOR_KEY4 0x54a02c82
    #define VENDOR_KEY5 0x6a3d64e0
    #define CRO_KEY1 0
    #define CRO_KEY2 0

    #define VENDOR_NAME "INTEL"

    #define ENCRYPTION_SEED1 0xEE25A77E
    #define ENCRYPTION_SEED2 0xE8FF3A1E
    #define ENCRYPTION_SEED3 0xEE25A77F
    #define ENCRYPTION_SEED4 0xE8FF3A1F

    #define LM_SEED1 0xdeadcafe
    #define LM_SEED2 0xc45eef33
    #define LM_SEED3 0xdeadc0d3

    #define LM_STRENGTH LM_STRENGTH_DEFAULT

    attached....

    and with
    #define CRO_KEY1 0xb2b100e6
    #define CRO_KEY2 0x30d44d76
    Attached Files Attached Files
    Last edited by BfoX; 2020-06-12 at 05:27 AM

  5. #15
    Junior Member Reputation: 10
    Join Date
    2020-06-04
    Posts
    12


    Default Re: Build LMCrypt without LM_SEED3?

    I Managed to build lmcrypt.exe in 11.x SDK! Thank you BfoX!

    Code:
    ---------
    FlexNet Licensing v11.14.0.0 build 183228 (ipv6) i86_n3 (lmgr.lib), Copyright (c) 1988-2016 Flexera Software LLC. All Rights Reserved.
    there is a file called lmseeds.h *DUUUH*

    LMCODE.h

    Code:
    /******************************************************************************
     *
     *      Module: $Id: //stg/eng/flexnet/licensing/c/v10-1/machind/blank_lm_code.h#1 $
     *
     *          COPYRIGHT (c) 1990, 2004 by Macrovision Corporation.
     *      This software has been provided pursuant to a License Agreement
     *      containing restrictions on its use.  This software contains
     *      valuable trade secrets and proprietary information of
     *      Macrovision Corporation and is protected by law.  It may
     *      not be copied or distributed in any form or medium, disclosed
     *      to third parties, reverse engineered or used in any manner not
     *      provided for in said License Agreement except with the prior
     *      written authorization from Macrovision Corporation.
     ******************************************************************************
     *
     *      Description:    Used to generate lm_new.o/.obj and by license-
     *                      generators.
     *
     *      Once the kit is "built" (using make or nmake) this file is no longer 
     *    needed, but should be stored somewhere safe.
     *
     *    Set the following values:
     *      VENDOR_KEY1-5         Provided by Macrovision Corporation.
     *      VENDOR_NAME         If not evaluating, set to vendor name.
     *      LM_SEED1-3             Make up 3 32-bit numbers, (or use 
     *                'lmrand1 -seed' to make up), keep secret, safe, 
     *                and never change.  
     *    TRL_KEY1-2         Provided by Macrovision if TRL used.
     *      LM_STRENGTH:         If using TRL, set to desired length 
     *
     *    Upgrading:         from version older than 8.1: Copy your 
     *                ENCRYPTION_SEEDs from the old lm_code.h file.
     *                Make sure LM_STRENGTH matches, if you were
     *                using LM_STRENGTH
     */
    
    #ifndef LM_CODE_H
    #define LM_CODE_H
    #include "lm_trl.h"
    #include "lmseeds.h"
    /*
     *     Vendor keys:           Enter keys received from Macrovision.
     *                Changing keys has NO impact on license files 
     *                (unlike LM_SEEDs).
     */
    
    #define VENDOR_KEY1 0x25886387
    #define VENDOR_KEY2 0xde6a60f1
    #define VENDOR_KEY3 0x4bb77d13
    #define VENDOR_KEY4 0x11dea93f
    #define VENDOR_KEY5 0x6a3d64e0
    /*
     *     Vendor name.          Leave "demo" if evaluating.  Otherwise,
     *                 set to your vendor daemon name.
     */
    #define VENDOR_NAME "INTEL"    
    /* 
     *     Private SEEDs:         Make up 3, 8-hex-char numbers, replace and 
     *                guard securely.  You can also use the command
     *                'lmrand1 -seed' to make these numbers up.
     */
    #define LM_SEED1 0xdeadcafe
    #define LM_SEED2 0xc45eef33
    #define LM_SEED3 0xdeadc0d3
    /*
     *    Pick an LM_STRENGTH:       
     */
    #define LM_STRENGTH LM_STRENGTH_LICENSE_KEY
    /*     
     *                       LM_STRENGTH Options are
     *                       LM_STRENGTH_DEFAULT:
     *                       Public key protection unused. Use SIGN= 
     *                       attribute. sign length = 12
     *                       TRL: 
     *                       LM_STRENGTH_113BIT, LOW:   sign length= 58 chars
     *                       LM_STRENGTH_163BIT, MEDIUM:sign length= 84 chars
     *                       LM_STRENGTH_239BIT, HIGH:  sign length=120 chars
     *                Pre-v7.1:
     *                       LM_STRENGTH_LICENSE_KEY:   Use old license-key.
     *                       If you're upgrading from 
     *                       pre-v7.1, and want no changes, set this to 
     *                       LM_STRENGTH_LICENSE_KEY.   
    */
    /*
     *    TRL Keys:        Provided by Macrovision Corporation, if TRL is used.
     *                 Be sure to set LM_STRENGTH to 
     *                 LM_STRENGTH_DEFAULT, above, if TRL_KEYs are zero.
     */
    #define TRL_KEY1    0x0
    #define TRL_KEY2    0x0
    
    
    #include "lm_code2.h"
    #endif /* LM_CODE_H */
    LMSEEDS.h:

    Code:
    #undef ENCRYPTION_SEED1
    #undef ENCRYPTION_SEED2
    #undef ENCRYPTION_SEED3
    #undef ENCRYPTION_SEED4
    #define ENCRYPTION_SEED1 0xEE25A77F
    #define ENCRYPTION_SEED2 0xF762C3A4
    #define ENCRYPTION_SEED3 0xBABEFACE
    #define ENCRYPTION_SEED4 0xC0D3F00D

    file compiles and build valid .lic file with this command:

    Code:
    lmcrypt.exe -i lictest_wssh.txt -o wsshh_fullsign2.lic -verfmt 7.1 -longkey
    or:
    Code:
    lmcrypt.exe -i lictest_wssh.txt -o FLEXLM11-SHADYSIGN.lic
    THANK YOU SO MUCH AGAIN BfoX!!!!!!!
    Last edited by wssh; 2020-06-12 at 06:47 AM

  6. #16
    Member Reputation: 33
    Join Date
    2014-05-02
    Posts
    28


    Default Re: Build LMCrypt without LM_SEED3?

    Intel as far i know still use standard licensing even if the vendor use trusted storage.. Standard license is enough without the ECC patch..

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •