Added TKTAuthDigest directive, updated docs & exmples. #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
New version v0.10 released – thank you very much for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses concern in issue #19 and adds an optional
TKTAuthDigestdirective to select other more modern digests (SHA224, SHA256, SHA384, and SHA512). If directive is not set, the old default SHA1/DSS1 is used.Obviously, the same algorithm selected for
TKTAuthDigestwill need to also be used by whatever code is doing the authnz, signing the ticket, and sending it back to the mod_auth_pubtkt website.Pull request includes version bump to v0.10.