Getting syn@psys tools newer than 2018 to properly work

joshua2784920

This information has been known for a long time and was included in the README file of 1patch V0.3, which was released in 2021.
However, I am surprised by the many comments expressing gratitude, as it seems some were unaware of this.


Additionaly, you need to apply below patch command for the application using Java.

%  pubkey_verify_java -y

farmat913144

它是否与Syn2023.09工作？ 即使使用scl2024，我也遇到了麻烦

joshua2784920

farmat913144 发表于 2024-8-27 19:17
它是否与Syn2023.09工作？ 即使使用scl2024，我也遇到了麻烦

It doesn't matter whether it's the scl2024 or scl2023 version.


% pubkey_verify -y
% synopsys_checksum -y  
% pubkey_verify_java -y

Although it is named pubkey_v1.6,

% pubkey_verify -h
Generic ECC patcher by tanker, v1.4, 2020-04
Type -h for more help..

This tool will search the current directory and its sub-dir for ECC, then patch it.
Also, it can search a single file by specifying the file name in the command line.

Usage: pubkey_verify [filename] [-y][-h][-r][-c][-v][-a PatchAddress][-d DisassembleAddress]

-y: Confirm patch within all target files.
-r: Revert patch from the patch_log.txt.
-h: Show this screen.
-v: Verbose mode.
-a PatchAddress: Directly patch the address (in HEX format).
-d DisassembleAddress: Directly disassemble the address (in HEX format).
-c Do not patch the PE file checksum (DEFAULT will patch).


The version named pubkey_v1.7 shows:

% pubkey -h
Generic ECC pubkey replacer by tanker, v1.70, 2009-10-31

This tool will search the current directory and its sub-dir for pubkeys.
Also, it can search a single file by specifying the file name in the command line.

Flexlm has 4 groups of pubkeys, SIGN(Group0), SIGN2(Group1), SIGN3(Group2), SIGN4(Group3). Currently, this tool supports 2 groups pubkeys search & replace (SIGN, SIGN2)
Group 0: 113b, 163b, 239b;
Group 1: 113b, 163b, 239b;

This tool will replace the above pubkeys with the default pubkeys (both for Group0 and Group1):
PubKey113=0301CD7EEC4F18635E9E1FDDB3442353
PubKey163=02066A35C6F9EE2DC6EEE7D4529B4AC00FB30A372EA6
PubKey239=02026FDFCFAF73DFBBC6D2A580202CB4587FF1D27891D4D6D0EC601CB3F1A4

And the corresponding private keys are:
PriKey113=00B2452CBC7E72C13A395E6725CED9
PriKey163=021C8FA2E4B64F7A2CD20681B5D8F9F181064A8E17
PriKey239=03A05889D23022D8CA5EAC5933B369DC309BB68D24566023F08C11B8C2BA

NOTE: These key pairs can be generated by setting LM_SEEDs in your lm_code.h:
#define LM_SEED1 0x11111111
#define LM_SEED2 0x22222222
#define LM_SEED3 0x33333333

Options:
-d daemon: Set the vendor daemon to "daemon", you must specify a vendor daemon to make the tool work.
-y: Replace pubkeys which have the same value as the first found file's pubkey (targets with 'diff pubkey' will not be replaced).
-f: Force replace all pubkeys with all targets, ignore the diff pubkey warnings.
-s x: Replace only pubkeys with the strength 'x', x should be 0,1,2,3,4,5,100 (default). 0=Group0 113b, 1=Group0 163b, 2=Group0 239b, 3=Group1 113b, 4=Group1 163b, 5=Group1 239b, 100=all pubkeys.
-a: Show decoded pubkeys.
-h: Show this screen.



The pubkey_v1.7 package does not include synopsys_checksum or pubkey_verify_java.

zhqiangx

joshua2784920 发表于 2024-9-16 06:24
It doesn't matter whether it's the scl2024 or scl2023 version.

could you please share the 1.7? Thanks!