Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update certbot readme's with entrust end of support #31

Merged
2 commits merged into from
Oct 6, 2023
Merged

Conversation

TimCsaky
Copy link
Collaborator

Description

with Entrust dropping support for certbot (using the V1 entrust endpoint) we need to let BC users know Entrust is no longer an option for certs in a production environment.

Types of changes

Documentation (non-breaking change with enhancements to documentation)

Checklist

  • I have read the CONTRIBUTING doc
  • I have checked that unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

Copy link
Member

@WadeBarnes WadeBarnes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TimCsaky, Are you able to provide links to the Entrust wording on this subject? Are they planning support for the ACME v2 endpoints? For example, Let Encrypt stopped using ACME v1 back in June of 2020.

There is a hint that Entrust does/may/will support ACME v2 here, https://www.entrust.com/blog/2023/04/googles-90-day-proposal-for-tls-certificates/, and here, https://www.entrust.com/-/media/documentation/datasheets/certificate-enrollment-gateway-ss.pdf?la=en&hash=06208F40D2C9A6E0B9E98CDE8B12C759.

@TimCsaky
Copy link
Collaborator Author

TimCsaky commented Sep 11, 2023

The only Entrust docs i see are here: https://www.entrust.com/knowledgebase/ssl/how-to-use-acme-to-install-ssl-tls-certificates-in-entrust-certificate-services-apache
The BC gov Entrust server does not currently support V2.
Certbot will also require some modification if V2 becomes an option: https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment#API_versions

@WadeBarnes
Copy link
Member

Certbot does work with the ACME v2 endpoints, I'm using Certbot with the Let's Encrypt ACME v2 endpoints on a few of our demo services for the DITP team.

@WadeBarnes
Copy link
Member

WadeBarnes commented Sep 11, 2023

Based on the documentation I found I don't think we can confidently make the statement that Entrust has discontinued support for Certbot. I do recall somewhere some wording around them discontinuing support for ACME v1, but Cerbot supports ACME v2, and the documents seem to indicate Entrust is or will be supporting ACME v2.

@WadeBarnes
Copy link
Member

WadeBarnes commented Sep 11, 2023

Do we know if someone on the BC Gov side is looking into Entrust's support for ACME v2?

@TimCsaky
Copy link
Collaborator Author

TimCsaky commented Sep 11, 2023

Thanks @WadeBarnes . Yes important to get these details clear.
i've been advised by middle-tier/infrastructure that the entrust service they use does not support acme v2 api.
They've asked that for entrust certs the requests are handled manually. (https://apps.nrs.gov.bc.ca/int/confluence/display/DEVGUILD/Generating+a+CSR)

If the Entrust service that the gov uses does support V2, i would hope this certbot container gets updated.

@ghost
Copy link

ghost commented Oct 6, 2023

Merge overriding as this PR only contains readme documentation changes.

@ghost ghost merged commit 9e28037 into master Oct 6, 2023
1 check failed
@ghost ghost deleted the doc/entrust branch October 6, 2023 22:15
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants