Maintained by Boreal Cryptosystems. Contact: Benoit de Mulder bendemulder@borealcryptosystems.com. Use the issue tracker, or contact the maintainer for coordination. Security reports go privately to security@borealcryptosystems.com.
Describe the expected PKCS#11 behavior, applicable specification section, affected version and platform, and observed behavior. Distinguish library defects, module behavior and unconfirmed hypotheses. Remove all secrets and identifying token data.
Keep changes focused, preserve API capabilities, explain ownership and unsafe invariants, and document behavior and compatibility changes. Keep source files under 1,000 physical lines by splitting responsibilities, not compressing code. Do not introduce vendor-specific branches or silently retry failed operations. Contributions are reviewed under Apache-2.0; preserve applicable third-party notices.