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

Bug fix for wrong salt used when calculating scramble after authentication switch. #93

Closed
wants to merge 1 commit into from

Conversation

twocode
Copy link

@twocode twocode commented Nov 28, 2016

https://dev.mysql.com/doc/internals/en/connection-phase-packets.html#packet-Protocol::AuthSwitchRequest

The last zero byte should not be included in the salt when re-calculating the scramble responding to auth switch request.

(related issue on JIRA: https://jira.mariadb.org/browse/CONJ-394)

@rusher
Copy link
Collaborator

rusher commented Dec 7, 2016

Hi twocode,

Thanks for you contribution, as explain in https://jira.mariadb.org/browse/CONJ-394, i agree that current implementation can be improve for better clarity.

Similar to other open source projects, the MariaDB Foundation needs to have shared ownership of all code that is included in the MariaDB distribution. The easiest way to achieve this is by submitting your code under the BSD-new license. (The other alternative is to sign the code contribution agreement which can be found here: https://mariadb.com/kb/en/mariadb/mca/)

Please indicate in a comment below that you are contributing your new code of the whole pull request, including one or several files that are either new files or modified ones, under the BSD-new license or that you have filled out the contribution agreement and sent it.

Thanks,
diego

@twocode
Copy link
Author

twocode commented Dec 12, 2016

@rusher Hey Diego, please verify if it's sufficient with the statement provided in the following comment above :)

Are you suggesting in JIRA that we should take this fix selectively per plugin, instead of what has been done in this PR where the last byte is trimmed under all circumstances? Since auth_pem takes them all.

@vaintroub
Copy link
Contributor

I think bytes are either trimmed or not. How can protocol selectively work for some plugins and not for others, Id like to understand that

@twocode
Copy link
Author

twocode commented Dec 12, 2016

@vaintroub Please see the JIRA thread. auth_pem will consumes all the data.

@rusher I have seen you committed the fix. Please close this PR :) Looking forward to next release.

@rusher
Copy link
Collaborator

rusher commented Dec 21, 2016

closing, since fixed differently in release 1.5.6

@rusher rusher closed this Dec 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants