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
auth: Add option to use SHA-256 instead of MD5 in digest authentication #628
Conversation
…stead of MD5 for digest authentication.
The module paramter "algorithm" was added with the possible values "", "MD5" or "SHA-256". It allows chosing between MD5 or SHA-256 hash algorithm for digest authentication. The configured algorithm is advertised in the challenge header. The default values is "" which omits the algorithm field in the challenge header and uses MD5 for digest authentication.
Thanks for the contribution! Looking at the sequence of operations, only the patch 4a076a0 needs to be reviewed and merged, right? |
Hi. Yes, only patch 4a076a0 is relevant. |
Hi. Did anyone look at the proposed feature ? Regards, |
These days many of us are at Kamailio World Conference in Berlin, therefore some low activity around the online resources of the project. This looks like something I will have to review, but being one of the organizers these days I don't have much time to even breed. However, I will try to do it soon. |
Ok, no problem. |
…hentication - the module paramter "algorithm" was added with the possible values "", "MD5" or "SHA-256". - it allows chosing between MD5 or SHA-256 hash algorithm for digest authentication. - the configured algorithm is advertised in the challenge header. - the default values is "" which omits the algorithm field in the challenge header and uses MD5 for digest authentication. - submitted via GH pull request #628
Thanks, the patch was pushed manually on your behalf with commit e7faf1e . |
This is an alternative solution to pull request: #627