>>>>> On Wed, 11 Feb 2026, Arsen Arsenović wrote: > A tragic development!
> https://github.com/oasis-tcs/pkcs11/issues/9#issuecomment-3881379096 > So, I'm not sure what the right thing to do at all is anymore. Rewrite > it not to use these headers but still provides a compatible ABI? Mark > it proprietary? Use p11-kit and assume there was some behind-the-scenes > dealing to make it distributable under the terms specified in it? Those > terms being: > /* pkcs11.h > Copyright 2006, 2007 g10 Code GmbH > Copyright 2006 Andreas Jellinghaus > Copyright 2017, 2021-2025 Red Hat, Inc. > This file is free software; as a special exception the author gives > unlimited permission to copy and/or distribute it, with or without > modifications, as long as this notice is preserved. > This file is distributed in the hope that it will be useful, but > WITHOUT ANY WARRANTY, to the extent permitted by law; without even > the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. */ Looking at common/pkcs11.h from p11-kit-0.26.2.tar.xz, it doesn't have much in common with the header files from OASIS. It's just type definitions and function declarations, and arguably there may be only one possible way to express these. In particular, all the comments from the OASIS files are gone. (But still, we are in muddy waters.) > I mean, as the file states, it is derived from the OASIS one, but > there's a "special exception" granted by RH. It's not unheard-of that > such special exceptions are granted to companies in order to release > stuff as free software, so I reckon that's a possibility. Maybe reach out to Redhat? If anyone, then they should know the story behind their copyright notice.
signature.asc
Description: PGP signature
