MySQL: add the option to force sending the password as plain text#18252
MySQL: add the option to force sending the password as plain text#18252jafl wants to merge 4 commits intophp:masterfrom
Conversation
* This re-uses the pam authentication method * pdo_mysql: added option MYSQL_ATTR_SEND_CLEAR_PASSWORD * mysqlnd: implemented CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA option in order to send auth data longer than 255 bytes
jafl
requested review from
SakiTakamachi,
bukka,
kamil-tekiela and
kocsismate
as code owners
|
Ideally, a similar option should be added to mysqli, but I'll wait with that until people have a chance to review this and decide whether it's the right approach. |
jafl
force-pushed
the
mysql-aws-iam-token
branch
from
a0f9e24 to
93e6505
Compare
| plugin_data[plugin_data_len] = '\0'; | ||
|
|
||
| requested_protocol = mnd_pestrdup(auth_protocol? auth_protocol : MYSQLND_DEFAULT_AUTH_PROTOCOL, FALSE); | ||
| requested_protocol = mnd_pestrdup(mysql_flags & CLIENT_SEND_CLEAR_PASSWORD ? MYSQLND_CLEAR_PASSWORD_AUTH_PROTOCOL : (auth_protocol? auth_protocol : MYSQLND_DEFAULT_AUTH_PROTOCOL), FALSE); |
There was a problem hiding this comment.
Is this really the correct place to set this? Why not set it where the function is called? auth_protocol is a parameter.
There was a problem hiding this comment.
See my other comment. There is no way to control the value of auth_protocol that is passed to this function from the PHP layer.
| /* | ||
| This is a mysqlnd extension. CLIENT_IGNORE_SIGPIPE is not used anyway. We will reuse it for our case and translate it to forcing the mysql_clear_password protocol | ||
| */ | ||
| #define CLIENT_SEND_CLEAR_PASSWORD CLIENT_IGNORE_SIGPIPE /* Force plaintext password */ |
There was a problem hiding this comment.
What exactly is this for? Can we not use CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA?
There was a problem hiding this comment.
The sensible, default behavior of mysqlnd is to use the protocol requested by the server, which is mysql_native_password. This protocol is appropriate for authenticating with username & password.
However, AWS AuroraDB also supports sending an IAM token in place of a password, and this must be sent in the clear. The problem is that AuroraDB doesn't know which authentication method the client intends to use, so it always sends mysql_native_password, and it's up to the client to decide how to send the password data.
Thus, there needs to be a way force mysqlnd to send the password in the clear. That is why I introduced this flag.
2 participants
The use case is authenticating to AWS RDS with an IAM token, which has to be sent in the clear.
This may solve #10800