- C 89.5%
- Perl 9.6%
- Makefile 0.6%
- TeX 0.3%
1c311902f1
Some checks failed
Build Docs / Automatic Docs build (push) Has been cancelled
* Add PKCS #11 historical mechanisms docs This adds the markdown source files, Makefile, and build configurations for the PKCS #11 Historical Mechanisms Specification Version 3.0. These documents preserve the specifications for legacy cryptographic mechanisms (such as RC2, RC4, MD2, and SKIPJACK) that are no longer in general use. The included Makefile and Pandoc templates allow for automated generation of the specification in HTML and PDF formats. Co-authored-by: Gemini <gemini@google.com> Signed-off-by: Simo Sorce <simo@redhat.com> * Add PKCS #11 Profiles v3.2 documentation Add markdown source files, a Makefile, and Pandoc configurations for the PKCS and build process to generate the specification in HTML and PDF formats. Co-authored-by: Gemini <gemini@google.com> Signed-off-by: Simo Sorce <simo@redhat.com> * Add initial PKCS #11 v3.2 Usage Guide draft This adds the initial markdown sources, images, and build files for the PKCS #11 Cryptographic Token Interface Usage Guide Version 3.2. The usage guide provides updated guidance on implementing the PKCS #11 v3.2 specification. It resumes the previous v2.40 usage guide, retaining the core overview and security content while omitting outdated sections, and establishes a Pandoc-based build system to generate HTML and PDF documentation. Co-authored-by: Gemini <gemini@google.com> Signed-off-by: Simo Sorce <simo@redhat.com> --------- Signed-off-by: Simo Sorce <simo@redhat.com> Co-authored-by: Gemini <gemini@google.com> |
||
|---|---|---|
| .github/workflows | ||
| published | ||
| working | ||
| CONTRIBUTING.md | ||
| LICENSE.md | ||
| README.md | ||
README
Members of the OASIS PKCS 11 TC create and manage technical content in this TC GitHub repository ( https://github.com/oasis-tcs/pkcs11 ) as part of the TC's chartered work (i.e., the program of work and deliverables described in its charter).
OASIS TC GitHub repositories, as described in GitHub Repositories for OASIS TC Members' Chartered Work, are governed by the OASIS TC Process, IPR Policy, and other policies, similar to TC Wikis, TC JIRA issues tracking instances, TC SVN/Subversion repositories, etc. While they make use of public GitHub repositories, these TC GitHub repositories are distinct from OASIS Open Repositories, which are used for development of open source licensed content.
Description
The purpose of this repository is to support version control for development of technical files associated with the OASIS PKCS11 specification.
Contributions
As stated in this repository's CONTRIBUTING file, contributors to this repository are expected to be Members of the OASIS PKCS 11 TC, for any substantive change requests. Anyone wishing to contribute to this GitHub project and participate in the TC's technical activity is invited to join as an OASIS TC Member. Public feedback is also accepted, subject to the terms of the OASIS Feedback License.
Licensing
Please see the LICENSE file for description of the license terms and OASIS policies applicable to the TC's work in this GitHub project. Content in this repository is intended to be part of the PKCS 11 TC's permanent record of activity, visible and freely available for all to use, subject to applicable OASIS policies, as presented in the repository LICENSE file.
Further Description of this Repository
[Any narrative content may be provided here by the TC, for example, if the Members wish to provide an extended statement of purpose.]
Contact
Please send questions or comments about OASIS TC GitHub repositories to the TC Admin. For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the PKCS 11 TC's home page.