allietbo / playbook-pki

layout	permalink
default	/

How to Contribute

We welcome contributions in the form of requests, issues and pages.

• Requests: You've identified a useful addition to the playbook which benefits USG Agencies

  • Open an Issue on this repository
  • State the recommendation
  • Include any links or other information
  • Discuss the request with other contributors

• Issues: You've identified an issue with the information

  • Open an Issue on this repository
  • Discuss the Issue with other contributors
  • Follow the progress of the updates

• Pages: You'd like to contribute a Page and content

  • Open an Issue on this repository, identifying the content you would like to contribute
  • Limit each Issue to one content topic
  • Fork the repository
  • Add a new Page or modify an existing Page with your suggested content
  • Submit a Pull Request, referencing the Issue Number

Public domain

This project is in the worldwide public domain. As stated in CONTRIBUTING:

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.

Special Thanks

This site is based on GitHub Pages and Jekyll templates. The templates are based on DOCter from CFPB.

The README, LICENSING and CONTRIBUTING are based on 18F Pages.

Special thanks to the teams at 18F, 18F Pages, and US Digital Services Playbooks for their open and transparent model which benefits citizens, government and technology.

playbook-pki's Issues

self-signed FPKI certificates

Although I know we provide information about how to get the self-signed certificates for the FBCA - there is no reason anyone should actually require these certificates because the FBCA (and FBCA 2013) certificates should NOT be used as trust anchors.
On the other hand the FCPCA self-signed certificate should be so the Common Policy CA self-signed cert should be made available from here, but not the Bridge ones. I actually beleive that printing the SHA1 thumbprint & DN on this page and a link (even though not HTTPS) should be secure because the cert is digitally signed and you can verify the SHA-1 hash by matching the thumbprint.

The SHA1 FRCA self-signed cert is probably no longer required - however it was meant to be a trust anchor for anyone who couldn't handle even the sha-256 signature of the cert from Common Policy.

There is only 1 CPS (which should be Certification Practice Statement) for the Common Policy, FBCA & SHA1 FRCA

the Common Policy CP can be found here:
https://gsageo.force.com/IDM/s/document_detail?Id=kA0t00000008ObqCAE

the bridge CP here:
https://www.idmanagement.gov/IDM/servlet/fileField?entityId=ka0t0000000TNYEAA4&field=File__Body__s