ASN1C License FAQs
The following are frequently asked questions and answers about licensing the ASN1C compiler and run-time:
SDK Licensing
What information is required to license an ASN.1 per-host SDK?
What information is needed to license a ASN.1 floating SDK?
Other questions are covered in our General Licensing FAQ.
Deployment (Run-time) Licensing
Can we use a floating license for our customers?
| Q. | What information is required to license an ASN.1 per-host SDK? |
| A. | The host id(s) of each development system is required to license the SDK. We use the host id for SDKs rather than the host name. |
| Q. | What information is required to license an ASN.1 floating SDK? |
| A. | The floating SDK relies on the RLM license server to validate the licenses. In this case, we need the server's IP address and host id in order to provide the server. A separate license is needed on the development systems that points to the licensing server. |
| Q. | The run-time node-locking for C/C++ appears to be controlled by a header file (rtkey.h). What do I do if I want to enable my product to run on additional hosts after it is deployed? |
| A. | It is possible to override this default
behavior through the use of a binary data file (rtkey.dat).
The ACLICFILE environment variable must be set to point at
the full pathname of this file for this to work. The
rtkey.dat file may be generated easily by running asn1c
-genlic from the command-line. |
| Q. | I bought the version that includes run-time source code. Can I include the run-time library source code with my product? |
| A. | The redistribution license allows you to redistribute binary versions of the run-time library free-of-charge, not the source-code. If you want to redistribute the source-code with your product, this can be done under a separate license agreement. Call us for details. |
| Q. | We have a large project where we expect to have multiple users accessing the compiler. Can we set it up on a shared file server? |
| A. | Yes, but in this case a floating license is recommended for use. Otherwise individual licenses for the developers must be purchased. |
| Q. | What if we have different types of platforms on which we want to run our application linked with the ASN1C run-time? |
| A. |
If you have a 'node-locked' license agreement, you would
need to purchase a separate license for each platform.
These can be dirrerent platform types.
If you have a 'binary unlimited redistribution' license for one computer type (for example, Windows PC's), you can add another computer type for the cost of an additional per-node license. If you purchased the version with run-time source code, you are free to build libraries for as many different machine types as you like. |
| Q. | Can we use a floating license for our customers? |
| A. | No. Floating licenses are used only with our SDK and must not be used with deployment kits. |