Getting support¶
Read first¶
- README.md: install, quick start, configuration and the example index.
- The user manual,
built from
docs/, with the API reference generated from the XML documentation comments. examples/: runnable projects, each run against crypto-server in CI.- DEVELOPMENT.md: building, testing and every CI gate on your own machine.
Questions and how-to¶
Open a GitHub issue. Include:
- the SDK version (
CryptoService.Sdkpackage or commit) and the .NET SDK version (dotnet --version); - the crypto-service version or commit (
GET /answers it); - the smallest code that shows the problem, with synthetic keys;
- the exception type,
StatusCode,Problem.Typeand message.
Never paste a real key, credential, token or plaintext.
A question about what the server accepts or answers (an algorithm, a parameter floor, a problem type) belongs in crypto-service: this SDK only carries the request and the answer.
Bugs and feature requests¶
Use the bug report or feature request form. Security reports never go in an issue: follow SECURITY.md.
Supported versions¶
While pre-1.0, only the latest 0.0.x receives fixes.
| Version | Status | Supported |
|---|---|---|
0.0.41 |
Current (in preparation on main) |
Yes |
0.0.40 |
First release (2026-11-16), latest on NuGet | Yes, until 0.0.41 is out |
Response times¶
This project has a single maintainer (see GOVERNANCE.md). Issues are usually answered within a few business days; there is no guaranteed response time.