Title: Support additional SLH-DSA parameter sets from NIST FIPS 800-230 (limited signature use cases) · Issue #2402 · bcgit/bc-java · GitHub
Open Graph Title: Support additional SLH-DSA parameter sets from NIST FIPS 800-230 (limited signature use cases) · Issue #2402 · bcgit/bc-java
X Title: Support additional SLH-DSA parameter sets from NIST FIPS 800-230 (limited signature use cases) · Issue #2402 · bcgit/bc-java
Description: Hi there, I would like to ask whether Bouncy Castle would consider supporting the six additional SLH-DSA parameter sets specified in the NIST FIPS SP 800-230: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-230.ipd.pdf ...
Open Graph Description: Hi there, I would like to ask whether Bouncy Castle would consider supporting the six additional SLH-DSA parameter sets specified in the NIST FIPS SP 800-230: https://nvlpubs.nist.gov/nistpubs/Spec...
X Description: Hi there, I would like to ask whether Bouncy Castle would consider supporting the six additional SLH-DSA parameter sets specified in the NIST FIPS SP 800-230: https://nvlpubs.nist.gov/nistpubs/Spec...
Opengraph URL: https://github.com/bcgit/bc-java/issues/2402
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support additional SLH-DSA parameter sets from NIST FIPS 800-230 (limited signature use cases)","articleBody":"Hi there,\n\nI would like to ask whether Bouncy Castle would consider supporting the six additional SLH-DSA parameter sets specified in the NIST FIPS SP 800-230: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-230.ipd.pdf\n\nThe current status of the draft at this moment I'm writing to you is published on 13th April 2026 and it already received comments: https://csrc.nist.gov/files/pubs/sp/800/230/ipd/docs/sp800-230_ipd_comments_received.pdf\n\nThe draft explicitly positions the sets for \"sign-once, verify-many\" scenarios. There is no final version yet, so this is meant as a tracking request. I would very appreciate if it can be implemented, since we need this limited signature counts version for many PKI applications. I find one of the comments published in the document I've included the link here is that one from MTG AG would be relevant for us. We would probably use the 2^16 signature count limit (this is a request from MTG AG to NIST) as well as the 2^24 signature count limit for our prototypes.\n\nUse case: Smartcard-based identity credentials\nSignatures are produced offline in HSMs, stored on a memory-constrained card and verified off-card by a reader. The card never signs, so the slower signing path is irrelevant. What binds now is how many bytes the signature occupies in card memory. The saving multiplies accordingly, where a card carries more than one signature (e.g., a signed data object + signer's certificate).\n\nThe higher security categories 3 and 5 are where this matters most.\n\nAt category 3 \"SLH-DSA-{SHA2, SHAKE}-192-24\" with signature size of 7,752 bytes the result is workable on current cards.\n\nAt category 5 \"SLH-DSA-{SHA2, SHAKE}-256-24\" with signature size of 14,944 bytes remains a hard fit, since two stored signatures would need a space of almost 30 KB.\n\nI know that NIST does not have object identifiers for these parameters sets yet. The existing twelve SLH-DSA OIDs occupy sigAlgs 20-31 in the NIST CSOR. So this is about the lightweight API only, not JCA registration and not the OID mapping tables. As I understand it, BC already ships algorithms reachable only through the lightweight API, so the precedent seems to fit.\n\nOn naming: \n- If these were added before the final SP is published, would you name them in a way that marks the draft status?\n- If the final document changes any parameter values and the names stay the same, two applications requesting the same name across a version bump would silently compute different things, whereas a draft-marked name gives a clean failure at instantiation.\n\nI would then like to know:\n1. Would these parameter sets be in scope once SP 800-230 is finalized and published?\n2. If there is interest earlier, would a lightweight-API-only addition under a draft-marked name be acceptable?\n3. How much work would this actually be at your end? From the outside, it looks like additional parameter instances rather than new algorithm code, but I personally don't know whether the current design allow sets to be added that way, and lg_w = 2 in particular is not exercised by any the twelve FIPS 205 sets, which all use lg_w = 4, so the WOTS+ chain and base-2^(lg_w) handling may have path that have never run at w = 4.\n\nThanks very much in advance :-)","author":{"url":"https://github.com/lukinalutuna","@type":"Person","name":"lukinalutuna"},"datePublished":"2026-08-21T12:17:44Z","url":"https://github.com/bcgit/bc-java/issues/2402"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:d602e748-24bb-5982-136b-76d263362ff0 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B99A:22DFDB:4E5283:694DCF:6AFBEFFF |
| html-safe-nonce | 89365a9061b92715714dd257fef14aab8bece3bb2361e5c1dbfaa928f3ac6b14 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCOTlBOjIyREZEQjo0RTUyODM6Njk0RENGOjZBRkJFRkZGIiwidmlzaXRvcl9pZCI6IjEwOTQyNDc1ODAyMTM5NjQ3OTkiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 9b847d391426cb9f66b6f89065f69d1609d12c2d5f44c98a976bb5e054c0add5 |
| hovercard-subject-tag | issue:5213958558 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/bcgit/bc-java/2402/issue_layout |
| twitter:image | https://opengraph.githubassets.com/79423cfa9392fb9daf1d322958c0ec01d38cdf5825140fee3a2b93005f95fd55/bcgit/bc-java/issues/2402 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/79423cfa9392fb9daf1d322958c0ec01d38cdf5825140fee3a2b93005f95fd55/bcgit/bc-java/issues/2402 |
| og:image:alt | Hi there, I would like to ask whether Bouncy Castle would consider supporting the six additional SLH-DSA parameter sets specified in the NIST FIPS SP 800-230: https://nvlpubs.nist.gov/nistpubs/Spec... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | lukinalutuna |
| hostname | github.com |
| expected-hostname | github.com |
| None | fa74413a1d84dac536fcca0740780bcbd3207bafec0e51873b73ff8e8cca032f |
| turbo-cache-control | no-preview |
| go-import | github.com/bcgit/bc-java git https://github.com/bcgit/bc-java.git |
| octolytics-dimension-user_id | 4566970 |
| octolytics-dimension-user_login | bcgit |
| octolytics-dimension-repository_id | 10416648 |
| octolytics-dimension-repository_nwo | bcgit/bc-java |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 10416648 |
| octolytics-dimension-repository_network_root_nwo | bcgit/bc-java |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | b3b5633a74535d9c23385512d534c66c8fde1907 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width