Issue with Spire.XLS License Signature on RHEL9

[nobu_441]

Dear Spire Support,

We are developing a cross-platform .NET library that utilizes Spire.XLS.

When testing on Red Hat Enterprise Linux 9.5 (RHEL 9.5), we encountered an issue where the license file (`license.elic.xml`) was not recognized, resulting in a license error.

This issue was resolved by changing the system's crypto policy using the command:
```
update-crypto-policies --set LEGACY
```
This suggests that the license file is signed using an outdated cryptographic algorithm (e.g., SHA1withRSA), which is no longer accepted under RHEL 9’s default security policy (OpenSSL 3.x).

We would appreciate your assistance with the following points:

1. What cryptographic signature algorithm (including hash function and padding mode) is used for `license.elic.xml`?
2. Is there a license file format available that is compatible with RHEL 9 or FIPS-compliant environments?
3. Do you have any plans to support more secure signature algorithms (e.g., SHA256withRSA) in future releases?

Thank you for your support.

[William.Zhang]

Hello,

Thanks for your inquiry.
After initial confirmation with our development team, the license file does not appear to be related to the system's crypto policy. Could you specify what you mean by "license error"? Do you have any relevant error messages? To assist with further investigation, would you be able to share your test code with us? Thank you in advance.

Sincerely,
William
E-iceblue support team

[nobu_441]

Dear Spire Support,

Thank you for your reply.

To clarify the situation:
We are currently using Spire.XLS 12.10.1.5420 (NETStandard).
Although the license file (license.elic.xml) was correctly placed, we still encountered a license error, and the generated PDF showed the following red evaluation warning:

"Evaluation Warning : The document was created with Spire.XLS for .NET"

As I mentioned in the original post, when we changed the system's crypto policy to LEGACY, the issue was resolved.
Therefore, we believe that the license file itself is valid, but it could not be properly verified or read under the default security policy of RHEL9.

Since the license file contains sensitive information, could you please let us know how we can securely provide it to you (e.g., via email or private upload)?

Thank you for your support.

Best regards,

[William.Zhang]

Hello,

Thanks for your reply.
Please send your license file to this email address: [email protected]. In addition, can I confirm with you whether the license takes effect after manually setting the crypto policy?

Sincerely,
William
E-iceblue support team