Metadata about well-known functions
The goal of the Lumina server is to hold metadata about well-known functions: their name, prototype, comments, operand types, ... IDA users can push metadata to, or pull metadata from the Lumina server.
When using Lumina, IDA does not send byte patterns to the server. Instead, it sends some hash values and this is enough for Lumina to find the corresponding metadata. When metadata is found, it will be downloaded and applied to the current database. This is a great way to improve the disassembly listing. It is possible to configure IDA to automatically request metadata at the end of analysis.
- Lumina servers are available for IDA Pro users as well as IDA Teams users, and they have the ability to either use their own private servers, or the public Lumina server hosted by Hex-Rays.
- Any user can send metadata to the Lumina server. The received metadata is stored by Lumina and is made available to all IDA users connecting to that server (either private, or the public one). Once again: when sending metadata, no byte patterns are sent to Lumina; IDA only sends the hash values and the metadata.
- Currently Lumina can work with x86/x64, ARM, PowerPC, and MIPS files. Support for other processors will be added in the future.
- Lumina can be used to "export" work that was done previously on another file, to other projects.
- It is possible to turn off automatic usage of Lumina (either private, or the public one) with the "Help, Check for free update" menu item.
- In any case your feedback is appreciated and will be accepted with gratitude. We do not promise to implement all your suggestions but we will take all measures to make it more powerful and more useful for everyone.
Public Lumina server
- While users have the possibility of installing their own private Lumina servers, Hex-Rays also provides a public Lumina server as a free alternative.
- Feel free to use the public Lumina server and to share your metadata with others. We will introduce some incentives for active users who share quality metadata.
- Note that Hex-Rays does not promise to routinely perform cleanups on the public server's database. Please use it with caution, do not abuse it, and try to populate it with useful metadata.
Private Lumina server
- Private Lumina servers are available starting with IDA 8.1. This can be extremely useful for keeping an in-house knowledge base of prior work, and hit the ground running faster on ulterior projects.
- The customer has full ownership of the private Lumina server, full
control over it and, through server logs & the associated
lcutility, all info about user activity. This is the perfect solution for privacy-conscious users who want to make use of Lumina's power, without the risk of leaking important/proprietary information.
lcutility can be used not only to manage the server but also to collect the usage statistics, including the general stats, per user stats, etc.
- It is very easy to keep the Lumina database healthy: not only
lchas the commands to delete undesired metadata, but also IDA users can do it on-the-fly after seeing the result of a Lumina operation.
Frequently asked questions
About the subscription model
1. What is a subscription model?
This means that users will pay a yearly fee to have access to the server, this includes any updates and support throughout the year.
2. Why use a subscription model?
A yearly subscription allows users to stay up to date with the latest versions of the server as soon as they are released as well as lowering the initial cost for the user.
What is included in the Lumina subscription
With a subscription you will have access to the latest version of the server, technical support by email, hot fixes for serious issues and vulnerabilities as well as participation in our user-only online forum.
4. How do I purchase the Private Lumina server?
You can contact us at email@example.com.
5. Can I pay for the subscription monthly?
Currently all subscriptions are paid in annual payments, monthly payments are not an available payment option.
6. What is the subscription duration?
Our standard subscriptions will be one year. For other options please contact firstname.lastname@example.org
7. How are subscriptions renewed?
You will be able to renew your subscription directly through our web shop or, for multi-seats subscriptions, by contacting email@example.com. In the future we will introduce automatic renewals.
8. What if I do not renew my subscription?
If subscriptions are not renewed, you will lose access to the server on the day that a new subscription should have started.
9 .What If I Want to Cancel My Subscription?
It is possible to cancel your subscription at any time but as subscriptions are charged yearly we are unable to issue any refunds.
10. How do I know when my license will expire?
You will receive 2 reminders: one 2 months in advance, the second a few days before the expiration.
1. What is the advantage of the Private Lumina server compared to the Public Lumina server?
Not all organizations can use our Public Lumina server due to confidentiality requirements, so now we offer an option of a private server which can be used to share functions metadata inside the organization.
This is the perfect solution for privacy-conscious users who want to make use of Lumina's power, without the risk of leaking important/proprietary information.
2. What is the added value of a Lumina server in my work?
When metadata is found, it will be downloaded and applied to the current database.
This is a great way to improve the disassembly listing. It is possible to configure IDA to automatically request metadata at the end of analysis and save time. Lumina can be used to "export" work that was done previously on another file, to other projects and you will benefit from your previous aanalysis.
3. Can I buy a license for the private lumina server alone?
No, a user without active IDA licenses cannot buy Lumina.
4. How does it count the seats? Is it the number of distinct IDA licenses that committed to an IDB or is this simultaneous access limit?
The administrator will have to create users on the Lumina server, and the number of users will be limited by the number of seats. Only the users created by the administrator will be able to connect to the Lumina server.
The seat count will be explicitly visible in the ida.key file, for the LUMINA product code.
5. Is it the same for Teams users?
In the case of IDA Teams licenses, the Lumina server will not have a separate user table but will connect to the Vault server to authenticate users. In this case admins will create users on the Vault server and the users will be able to connect both to the Vault and Lumina servers.
6. How about existing licenses? If somebody wants to add Lumina, do they need to provide the IDA license IDs and get new keys?
They will have to provide the license ids.