808bits

Thales Luna

documented

Luna is the HSM line most people mean when they say Thales, and its PKCS#11 library adds its own constants above the vendor range like every other vendor. What makes it worth a page of its own here is the overlap with ProtectServer: two product lines under one owner, both extending PKCS#11 for the same purpose, and in at least one family the same constant names sitting at different values. Looking a number up in the wrong one of these two tables gives a confident wrong answer. The comparison is on the libraries index.

Not to be confused with

Thales ProtectServer. Sold by the same company and easy to mistake for each other, but they are unrelated product lines. Luna arrived through Chrysalis and SafeNet. ProtectServer arrived through Eracom. Neither one's documentation describes the other, and where a constant name appears in both it can carry a different number.

This library is one column of Same name, different number, the table of constants that carry one name and more than one value.

Return values with a note for this library

  • CKR_ARGUMENTS_BAD · A pointer or a count the library will not accept. Sometimes a genuine bug, and sometimes a mechanism that requires an argument to be null.

How this page was made

Documented only. The BIP32 constants come from Thales' published Luna documentation, names and numbers, and the comparison with ProtectServer is on the libraries index under "Same name, different number". No Luna library was available to probe.

Scope. Documented rather than observed. Nothing on this page was read off a live Luna HSM, because there is no Luna library on the machine this site is built from. Every value here comes from Thales's published documentation, and the read date is on each source. Treat it as what the documentation says, which is not always the same as what a given firmware does.

Sources