synopsys_checksum v0.9:  first release
synopsys_checksum v1.0:  add windows support, and you can use synopsys_checksum -s to get encrypted strings from binary files(such as feature names)
pubkey_verify           v1.2:  add more rules to check patch point
synopsys_checksum v1.1: use nftw to search dirs, and not follow soft links
pubkey_verify           v1.3: use nftw to search dirs, and not follow soft links
synopsys_checksum v1.2:  fix a core dump bug
pukey_verify             v1.4:  recompile with big file system support
synopsys_checksum v1.3:  recompile with big file system support
synopsys_checksum v1.4:  imporve string search algorithm
synopsys_checksum v1.5:  fix bug when locate the patch point(linux64). Add synopsys.src. Add fix.bat
synopsys_checksum v1.6:  enhance patch point locate algorithm(windows).


for java
v1.0: fix a bug when unzip jar file in directory
v1.1: re-pack jar by update file, not create new jar file
v1.2: use binary search for locate the patch points

**********************************************************************************************************************************

It looks like there are still users who do not manage to get the most recent syn@psys tools (version newer than 2018.12) to properly work even after the great realease of the proper patcher. As a matter of fact, as explained in the "readme.txt" file found in the pubkey1.6 package, everything should go fairly smoothly by following the instructions but ... apparently not all the steps are included in the operation list !

Therefore, as done in the past for other tools, I decided to create a tutorial to succesfully apply the patch and create the license to finally clarify the complete procedure. The first 6 steps from the "readme.txt" are indeed correct:

    [in linux box]Patch files. Goto your product directory (eg syn_vP-20yy.mm), run pubkey_verify -y
          - (where yy.mm indicates the year and the month, eg 20.12)
    [in linux box]Patch files' checksum. Goto your product directory (e.g. syn_vP-20yy.mm), run synopsys_checksum -y  
          - (where yy.mm indicates the year and the month, eg 20.12)
    [in linux box]Repeat 1, 2 with all your $ynopsys , including the daemon scl_v2018.06 (or higher)
    [in windows box]Generate license file(Synopsys.dat) with scl_keygen.exe
           - on first run this will generate the settings.ini file which you can edit to specify hostid and expiration date for the SSS feature
           - and the Synopsys.src file which includes the tools version (e.g., 2108.12) and the expiration date (31-dec-2020) on the INCREMENT lines and you have to
              modify those to match your tools and to set the desired expiration date (e.g., INCREMENT FEATURE_NAME snpslmd 2030.12 31-dec-2030 ...)
           - remember to add teh full path for the daemon line as: DAEMON snpslmd <full_path_to_daemon>/snplmd
    [in windows box]Drap&drop the generated Synopsys.dat to fix.bat. This will add dummy SIGN= to the license file
    Copy the license file to you linux box, and start the license daemon.
            - E.g. lmgrd -c <path_to_license_file>/license.dat
    At this point the following unexpected message from the daemon may appear:

    (snpslmd) checking the integrity of the license file ...
    (snpslmd) The SSS features are garbled.
    (snpslmd) All revenue keys ("SN=RK:... " on feature line) have been excluded

    which will make your license file useless !!!
    Luckily there is an easy solution: just reread the license with lmreread
            - Eg lmreread -c <path_to_license_file>/license.dat
    and all the features will be re-enable ad you will be all set !