Try RLM for Free

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.0 (BL3) – Release Date August 22, 2024

This update adds an all-new web management interface to the on-premises license server.

 

It also fixes multiple vulnerabilities related to the web interface.

 

Important notes: 

  • Starting in v16.0 the rlm.pw file is no longer used for access control. New access roles have been created.
  • HTTPS is now required for accessing the web interface and will be enabled automatically. Users will receive certificate warning the first time they access the web interface if they use the self-signed certificate.

 

Bug fixes:

  • Activation URL incorrectly shortened when using RLM web UI to activate a license.
  • Cookie issues with Safari browser.
  • BL2 fixes an issue with RLMAUTH failing to authenticate.
  • BL3 fixes:
    • Hostid issues with macOS 15 and WiFi privacy
    • Usage not displaying in RLM web server when password is set
    • Some functions not working in web UI when ISV name is 10 characters
    • Web server crashing when no certificate is present
    • Debuglog not working in web server

 

Security fixes:

  • CVE-2018-15574
  • CVE-2021-37500
  • CVE-2021-44154
  • CVE-2021-45422
  • CVE-2022-28363
  • CVE-2022-28364
  • CVE-2022-30519
  • CVE-2023-43183
  • CVE-2023-44031

 

Note: All RLM kits contain both the machine-independent and the machine-dependent part (including the Reference manual).

 

Documentation:

 

To install:

  • Unix/Mac: download, gunzip the kit, tar xf, then run INSTALL. See README above. (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).

 

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.