Request PKCS#11 Spy logs in bug report template

[olszomal]

Pull Request Type

• Bug fix
• New feature
• Code style / formatting / renaming
• Refactoring (no functional or API changes)
• Build / CI related changes
• Documentation
• Other (please describe):

Related Issue

Issue number: N/A

Current Behavior

Bug reports involving PKCS#11 issues often lack low-level tracing information, making it difficult to diagnose token, module, or provider behavior.

New Behavior

The bug report template now explicitly requests PKCS#11 trace logs captured with PKCS#11 Spy, providing clearer guidance to reporters.

Scope of Changes

• Add a dedicated “PKCS#11 Spy log” section to the bug report template.
• Provide a reference link explaining how to capture PKCS#11 Spy logs.

Testing

• Existing tests
• New tests added
• Manual testing

Additional Notes

This change is documentation-only and does not affect runtime behavior or compatibility.

License Declaration

• I hereby agree to license my contribution under the project's license.

[dwmw2]

Shouldn't most people be in using p11-kit so capturing traces is a lot easier just by enabling it in the p11-kit module file rather than with pkcs11-spy?

[mtrojnar]

Shouldn't most people be in using p11-kit so capturing traces is a lot easier just by enabling it in the p11-kit module file rather than with pkcs11-spy?

Good point. Most users indeed already have p11-kit preinstalled on their Linux distro. Would you submit a PR to improve our bug template for those users?

Bear in mind though that libp11 is not limited to big Linux distros only.