Automatically renew an expired cert, rather than throwing an error tot he user #143
No reviewers
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#143
Loading…
Reference in New Issue
No description provided.
Delete Branch "gemini-cert-expiry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When a cert expires for a gemini site the user is informed and they have to decide to purge the cert. This has been because we do not store the expiration date.
This PR updates the code to store the expiration along with the certificate hash as a
|
delimited string. This can be checked against and if the certificate has expired we can then just take the new certificate that is offered. If not non-expired cert is offered by the server, the user will still see an expired certificate error. Otehrwise, they should be able to seamlessly update their cert without having to resort to purge.This PR is in response to issue #142
This is a good thing to fix, and it seems to work well in that I can browse to a few different gemini sites I've not visited in a while without having to purge certs to get things working.
Awesome. I ahve had the same experience (far fewer purges). I'll merge this in when I get a moment and may have this one and the other that is on develop move over to master as a minor version since this ends up fixing something reasonably significant.
Closing this pull in favor of using a release branch ( #147 ).
Pull request closed