Warn when using deprecated SASL mechanisms #62
Merged
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.
Mark obolete SASL mechanisms as deprecated (fixes GH-55):
warn_deprecation: false
#initialize
, and convert the gems to development dependencies.Additionally:
#new). I was originally going to register deprecated authenticators
with a Proc that required the file and issued a warning, but I decided
to put everything into the initializer instead.
#authenticator
needed to be updated to safely delegate all args, and I left this in.
The DIGEST-MD5 bug was originally reported, tested, and fixed by
@singpolyma here: nevans/net-sasl#3.
Co-authored-by: Stephen Paul Weber [email protected]