The Wayback Machine - https://web.archive.org/web/20220326135849/https://github.com/topics/x509
Skip to content
#

x509

Here are 310 public repositories matching this topic...

certificates
tashian
tashian commented Jan 10, 2022

The recommendation is to set Cache-Control: private, no-store on any endpoint with sensitive information. Because while you can protect the traffic with TLS, you also need to keep sensitive information out of a client's (unencrypted) HTTP cache. I'm not sure how relevant this is to the API context of step-ca though—I've never seen an HTTP client library that caches content. But I guess the poi

cli
Delapouite
Delapouite commented Jan 19, 2022

Hello

What would you like to be added

Currently the step-cli certificate fingerprint foo.pem command only outputs the fingerprint as a SHA256 hash. It would be convenient to have an option to display a SHA1 fingerprint instead.

Why this is needed

Azure Iot Hub services display the fingerprints as SHA1 hashes on the Azure portal, so it's not easy to compare both types of finge

Improve this page

Add a description, image, and links to the x509 topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the x509 topic, visit your repo's landing page and select "manage topics."

Learn more