You are on page 1of 2

His Key == My Key

Introduction :
This is a quick level workouts to deal with the target Tecplot. I selected one of its product 360.
It is used to quickly plot and animate all your data exactly the way you want it. Analyze complex data, arrange
multiple layouts, and communicate your results with professional images and animations (image of plane shown).
Unlike the common shareware products which use mostly the custom made schemes here (version 2013) we
discuss about a widely used licensing schemes in the market RLM.
Lets do it :
These targets were closed by the keys based on Flexlm licensing upto the 2008 version. For those versions it was easy to
make a genuine license based on the derived encryption seeds from the soft, using the age old procedure for all the kids. The seeds are
MHhBMzRCN0IxMg== and MHgyRkU4M0VBMQ== and the license anyone can use is
FEATURE 360 teclmd 2010.1 30-dec-2014 uncounted HOSTID=ANY ISSUER=iceland NOTICE="Planet Earth Users Only" SIGN=957264084476
The newer one was based on reprise licensing (RLM). For anyone the soft can be found from this address. It is 2013 R2 version.
ZnRwOi8vZnRwLnRlY3Bsb3QuY29tL21pc2MvVGVjMzYwXzIwMTNfUjFfV2luNjQuemlw

There are several ways to break the RLM licensing, one of the quickest dirty way is to patch the call related to rlm_checkout. However a
more elegant is to make your own keys just like the original one and replace it. The licensing works in cryptographic sense which
generate a pair of public and private keys. The public keys are available in the software for the validation purpose of the license and the
private keys are kept secret and not in the soft. The private key is used to generate the license only.

Procedure :
Get hold of a rlm sdk using google and be ready. First thing to search is the name of ISV and signature specific to the software. This can
be easily done by any hex searcher (search sig=) we need to put this info in the file license_to_run.h
The only 3 commands you need to know in the sdk is
rlmgenkeys, nmake & rlmsign.
So first type rlmgenkeys to create the public & private
key pairs. The key consists of 3 parts [2 bytes of headers] + [1 byte of key size] + [actual key of this byte size]
The header is always [30 81] in hex and can be easily found again by any hex tool. key size
This is followed by actual key as shown below. Now check the same size (E0) here in the public keys which we generated using sdk. If the
key size does not match then run
again rlmgenkeys for new pairs.
once we are satisfied with length
compile the sdk using nmake. Finally
just replace key in the software (here
the file is tec360.exe). You can take
the keys from the file rlmclient.lib
and Thats it. The patching is finished.
Now the soft has our keys and a
original patched
license can be generated using rlmsign licfile. licfile template can be found in example.lic
Based on the patching above we can use the license below. One of the advantage of using a generic patching is that same patch and
similar lic can be used for any other product of the same vendor. For example here 3 products are licensed.
LICENSE teclmd 360 2013.10 30-dec-2019 uncounted hostid=ANY issuer=iceland _ck=1c1efc915d sig="60P04524YM0WBTNFT26478UC8GDHHFYDC2T935G22H7ASX4XHV49VJGHJVHQWKAQ7NXXT8CFC8"
LICENSE teclmd focus 2013.10 30-dec-2019 uncounted hostid=ANY issuer=iceland _ck=a31efca78b sig="60P0453A25PYBWWE5EHDW652HRPNE0SG934XK1822G7PNNK0BTPU6NY6U24UUG3WCK7D0KF4W0"
LICENSE teclmd rs 2013.10 30-dec-2019 uncounted hostid=ANY issuer=iceland _ck=681efc7e69 sig="60PG4580J25EYRVTAS9BBH4DBBYUDKXAR2W0HEYK08A4GFU3G5VWXCB577HYBE6QF9ST4G1R5UV0"

Once we open the soft we get


Side Note :
Its always a desire to make the original lic with no patching. The algo used in the
RLM keys are DSA-512. They took
freely available OpenSSL 0.9.8a.

I Thanks everyone who shared all these knowledge If you go deeper in DSA function to find more p,q,g & others, there might be
Its their credit. I am just using surprises. Just Enjoy !!!

You might also like