Auth

[ghost]

It is improved version of module emysql_auth + coverage tests. Emysql_auth adapted for the MySQL 3.23-4.1

[jlouis]

What is the lure of supporting an old version of MySQL on the main master branch? While I recognize there are people who need support, I am much more inclined to say that it is better to keep this separate from the main repository.

Please educate me: Is there anyone using such an old version, and why are they doing so?

[ghost]

MySQL 4.0.27 is used in the hosting company (mtw.ru) where I work for some our clients. They use websites that are not adapdted to the Mysql 4.1+. It sounds unbelievable, but true. I want to work with some databases on such servers. I understand that now rare to find a similar problem, but do not exclude the possibility.

There are other advantages in these patch:

• code is prepared to implement ssl_exchange and auth_method_switch (http://dev.mysql.com/doc/internals/en/connection-phase.html)
• implemented coverage tests for all pure functions (in module emysql_auth)
• checked the work of the function password_old (which has not been tested yet)

[jlouis]

I'll look at this when I next integrate patches. I tend to batch them up. I'll probably take a look around the 20th or so.

[jlouis]

I have not forgotten this patch, but I'll do it in the next batch when #102 comes back as well :)

[jlouis]

Does this still have support? I'll get it in if possible, but I really really really want to rewrite a lot of the code, which means if it can be pushed to "later" it would be much better.

[maxim-komar]

Ok, lets write my code after your changes.

[jlouis]

I went over emysql_auth this evening. I should probably work on tcp or conn next.