Skip to content

[release/2.8 backport] replace rsc.io/letsencrypt in favour of golang.org/x/crypto #3134

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

Closed

Conversation

thaJeztah
Copy link
Member

backport of #2926

As per the readme over here, it's recommended to use acme/autocerts.

closes #1976

@thaJeztah
Copy link
Member Author

@dmcgowan @manishtomar PTAL

@dmcgowan
Copy link
Collaborator

dmcgowan commented Apr 1, 2020

We don't have any test automation for Let's encrypt today. How is this being verified on the 2.7 branch?

@milosgajdos
Copy link
Member

@thaJeztah can you rebase this, please?

@thaJeztah thaJeztah force-pushed the 2.7_backport_no_rsc branch from 4c33cf6 to 3996fd7 Compare May 5, 2021 19:48
@codecov-commenter
Copy link

codecov-commenter commented May 5, 2021

Codecov Report

Patch coverage has no change and project coverage change: +0.01% 🎉

Comparison is base (7c354a4) 58.87% compared to head (d0a332d) 58.89%.
Report is 2 commits behind head on release/2.8.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@               Coverage Diff               @@
##           release/2.8    #3134      +/-   ##
===============================================
+ Coverage        58.87%   58.89%   +0.01%     
===============================================
  Files              102      102              
  Lines             7120     7118       -2     
===============================================
  Hits              4192     4192              
+ Misses            2284     2282       -2     
  Partials           644      644              

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@thaJeztah
Copy link
Member Author

I rebased this one, but per discussion above, if there's risk involved in this change, and with (I think) version v3.0.0 (main branch) starting to take shape, I think it would be ok to close this one and just acknowledge that the current implementation in v2.7.x is broken.

@dmcgowan
Copy link
Collaborator

dmcgowan commented May 6, 2021

My concern was more just, was this tested and verified. I don't have any specific concern over risk since it is not in a good shape today anyway

@milosgajdos
Copy link
Member

I'm happy to close this. I think there are few people reporting letsencrypt support on the long overdue 2.7 release, but if we can't make sure this works I say let's chuck it and see if anyone screams. We can always reopen it and pick it up again

@thaJeztah
Copy link
Member Author

@milosgajdos IIUC, current implementation in 2.7 was broken, so I guess it can't be worse than that, but it'd be good to test it (haven't found time to do so, but if you do have time to give it a spin)

@eclipseo
Copy link

eclipseo commented Aug 21, 2022

Could this be merged for another point release?
Pretty please

@milosgajdos milosgajdos removed this from the Registry/3.0.0 milestone Apr 13, 2023
@milosgajdos
Copy link
Member

@thaJeztah should we close this? Given it was opened against the v2.7 branch and we won't be adding it into any v2.X branches

@milosgajdos
Copy link
Member

@thaJeztah do you mind closing this?

@thaJeztah thaJeztah changed the base branch from release/2.7 to release/2.8 August 20, 2023 17:54
Signed-off-by: Tariq Ibrahim <tariq181290@gmail.com>
(cherry picked from commit 8f9c809)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah force-pushed the 2.7_backport_no_rsc branch from 3996fd7 to d0a332d Compare August 20, 2023 17:55
@thaJeztah thaJeztah changed the title [release/2.7 backport] replace rsc.io/letsencrypt in favour of golang.org/x/crypto [release/2.8 backport] replace rsc.io/letsencrypt in favour of golang.org/x/crypto Aug 20, 2023
@milosgajdos
Copy link
Member

@thaJeztah let's close this

@thaJeztah
Copy link
Member Author

yup SGTM

@thaJeztah thaJeztah closed this Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants