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

Jump to bottom

update golang.org/x/crypto vendor to use acme v2 #240

Merged
merged 2 commits into from Feb 9, 2020
Merged

update golang.org/x/crypto vendor to use acme v2 #240

merged 2 commits into from Feb 9, 2020

Conversation

techknowlogick
Copy link
Contributor

also run go mod tidy to clean up module files

fix #228

  • I have signed the CLA

thebaer
thebaer approved these changes Feb 9, 2020
View reviewed changes
Copy link
Member

@thebaer thebaer left a comment

Choose a reason for hiding this comment

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

Looks good, and works well! Thanks for helping with this, @techknowlogick!

@thebaer thebaer merged commit 9fb12ee into writefreely:develop Feb 9, 2020
@techknowlogick techknowlogick deleted the acme-v2 branch February 9, 2020 18:43
@thebaer thebaer added this to the 0.12 milestone Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@thebaer thebaer thebaer approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
0.12
Development

Successfully merging this pull request may close these issues.

ACMEv1 disabled by Let's Encrypt, can't automatically secure with HTTPS
2 participants
@techknowlogick @thebaer