Software
Publishers

Reprise resources for Software Publishers – Our customers know that our skilled and attentive technical support sets us apart from the “the other guys.” Benefit from our 25+ years of experience in the field and receive exceptional technical support for that “it just works” experience.

Developer Kits

for Software Publishers

RLM v16.1 (BL1) – Release Date October 23, 2024

This update adds Windows ARM64 support and upgrades OpenSSL to version 3.0.15 (see notes below).

 

Important notes:

  • There are new build requirements for Mac and Windows:
    • Mac – Link with:
      • fobjc-arc
      • framework CoreWLAN
    • Windows – Add link:
      • bcrypt.lib
      • crypt32.lib
  • Upgraded to OpenSSL 3.0.15
    • Removed the rlmssl namespace. If you need to link an older or newer build of OpenSSL to RLM, build the NOSSL from the RLM makefile.
    • Removed the rlmssl_ERR_remove_state(0); call. This call must be removed from your code after upgrading.
  • All new web management interface starting in v16.0. Please see documentation for detailed information.

 

New Platforms:

  • Windows ARM64

 

To add Windows ARM64 to your licensed platforms, please contact sales@reprisesoftware.com.

 

Bug fixes:

  • Debuglog not working correctly in web interface.
  • UI functions not working when ISV name is 10 characters.
  • RLM crashing when no certificate is present.
  • License usage not displaying when license password is set.
  • Web server error when license file is larger than 1024KB(Linux)/2048KB(Windows).

 

Security fixes:

  • CVE-2018-15573
  • CVE-2018-5716

 

Documentation:

 

To install:

  • Unix/Mac: download, gunzip the kit, tar xf, then run INSTALL. (If your browser gunzipped the file during transfer, you should skip the gunzip step). Note arm64_m2 does not have Java support.
  • Windows: download, execute the installer, then run “nmake” in the binary directory (x86_w4, x64_w4, x86_w3, or x64_w3).

 

Note: All RLM kits contain both the machine-independent and the machine-dependent part.

 

Java:

  • Java for Unix (java_unix.tar.gz) (RLM has java support only on the following Unix platforms: x86_l2, x64_l1, x86_m2, and x64_m2. Windows kits include the Java interface.)

 

Linux:

 

Mac

 

Windows:

 

For general questions, please send email to support@reprisesoftware.com.

RLM and RLM
Activation Pro

What’s the difference?

Reprise License Manager (RLM)

Software License Manager

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

As a Software publisher, you integrate RLM into your product, and RLM keeps track at runtime of who is using the licenses of your software.

RLM can do this entirely within the client library (linked into your application), or, more commonly, your application makes a request of the RLM Lincese Server to check out a license.

The lincese server runs either on your customers network, or in the cloud if you are using our RLMCloud™ service.

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

RLM Activation Pro

Software Activation Manager

Activation Pro is
used once when your customer purchases your software in order to retrieve the license which is specific to that customer.

Software Activation’s purpose in life is to get the licenses for your product to your customers with a minimum of fuss.

Activation Pro also has a server component wich we call the activation server.

Your application contacts the activation server and supplies a short text activation key, and in exchange, the activation server returns the license which enables your product.

Generally, this is done once, right after your customer purchases your software, not every time your software is invoked.