maria-discuss team mailing list archive

[Sergei Golubchik <serg@xxxxxxxxxxx>]

Hi, Felipe!

On Apr 14, Felipe Gasper wrote:
> On 13 Apr 2015 5:34 PM, Sergei Golubchik wrote:
>  >
> >> Should MariaDB not accept “mysql_native_password” as a value in that column?
> >
> > Right, that's exactly the issue I was referring to.
> > I know about this case because I've fixed it.
> > It's MDEV-6253 and it was fixed in 10.0.12.
> >
> > But ok, now I see that the bug was about the user being unable to
> > connect. That part was fixed. But SHOW GRANTS apparently wasn't.
> >
> > Reported as MDEV-7985
> 
> What will the “life” of this bug and its fix look like? Is there 
> anything that could be done to help bump it along?

The bug has fixVersion 10.0, which generally means it should be fixed in
the next 10.0 release (unless we'll have too many higher-priority bugs).

So for now you can expect that nothing will happen to MDEV-7985 until
10.0 is the next release in our release schedule. After that you can
expect this bug to be fixed.

The release schedule is in Jira (I'm keeping it up to date, so I
encourage people to look at it :).  The current plan is to have 5.5.43
released on 2015-04-21, then 10.0.18 on 2015-04-28, then 10.1.5 on
2015-05-12.

So, unless the plan changes, you can expect no activity on the bug until
2015-04-21, and then it should be closed as fixed no later than 2015-04-28.

There is no need to bump the priority - it's high enough to almost
guarantee a fix in 10.0.18.

> As a workaround I’m going to do:
> 
> UPDATE mysql.user SET plugin='' WHERE plugin='mysql_native_password'; 
> FLUSH PRIVILEGES;
> 
> Does this look like a reasonable workaround?

Yes. Perfectly reasonable.

> Also, are all 10.0 releases affected, do we know?

I think so, yes :(

Regards,
Sergei