Inquiry on generating a floating Saltd license

joshua2784920

Below licenses generated with SaltdKG are only valid for node-locked versions.
https://bbs.eetop.cn/thread-980204-1-1.html
https://bbs.eetop.cn/thread-964572-1-1.html

This presents several inconveniences, including a very long license checkout time.

Please advise on how to generate this license as a floating version.

nepuba

using -? for help and using -f to generate floating license

joshua2784920

   

nepuba 发表于 2025-9-20 09:50
using -? for help and using -f to generate floating license

A floating license generated using the -f option successfully lists license features when the fetched saltd daemon is executed. However, when the application is run, an UNSUPPORTED feature message appears in the saltd daemon execution log file, and the checkout fails, causing the application to terminate with a "No License" message.

This is consistent with the statement in the link https://bbs.eetop.cn/thread-964572-1-1.html that only the nodelocked version is supported.

joshua2784920

When running SaltdKG with the -f -i lic.src -o lic.txt option and including SIGN=0 and SIGN2=0 in lic.src,
the generated license will have values ​​assigned to SIGN and SIGN2,
and all features will be listed correctly in the saltd daemon log.

INCREMENT calibregpumfg saltd 2028.080 12-sep-2028 99 \
      0F99909C19DE9167D06F VENDOR_STRING=EA4532E4 vendor_info=global \
      SN=43422402 SIGN="0D93 1F62 1F07 CB9E 0B50 AFBD 8C97 B567 FB10 \
      0C91 BCAF 6241 E73E F693 080A 0FC3 59D3 3C0D CC41 1C4C 4EFC \
      1293 C211 7F58 E6F1 FFF1 E974 44A8 234F D2FD" SIGN2="1FBF 6477 \
      14AA 2480 EE11 89F1 A616 6983 2470 51DF C9A7 46D4 5833 01FD \
      B947 0587 9770 4E32 9696 1252 8197 6E0A ACD7 4D7B 189E F2F2 \
      86F1 AADD 8445 90A5"

However, when checking out, the "UNSUPPORT" feature will be displayed and the checkout will not proceed.

nepuba

   

joshua2784920 发表于 2025-9-20 14:03
When running SaltdKG with the -f -i lic.src -o lic.txt option and including SIGN=0 and SIGN2=0 in li ...

did you patch your app