FreeTDS Development Group

[Михаил Гаврилов <mikhail.v.gavrilov AT gmail.com>]

2013/11/23 James K. Lowden <jklowden AT freetds.org>:
> (It is helpful to readers of the archive if you don't top-quote.)
>
> We don't read passwords from odbc.ini for security reasons.  We
> recommend that people who want passwordless connections use Kerberos or
> similar.  FreeTDS supports it for all servers and clients, as far as
> I'm aware.
>
> If you don't need security, you could set up an account with no
> password (or a known one, and hard-code it).
>
> If you want a little security, the kind that will discourage your
> grandmother, keep your passwords in a file or environment variable.  I
> used to keep mine in ~/.netrc, and use awk to parse out the bits.
>
> HTH.


Excuse me, but why do not you leave the choice for developers , where
to store the passwords from the database connection . For my web
application I store passwords in clear text in the config file on the
server and as time has shown it is more than enough. But now we are
not talking about it. I want to use the latest feature of MariaDB
which allows you to access any database tables having the ODBC driver
as native tables. And I believe more secure in this case is to store
passwords in odbc.ini than talking passwords to everyone who creates
their tables. About using Kerberos. I'm not admin MS SQL and could not
affect to admins of MS SQL. I have been working through the usual SQL
account that I was given. I came here because I expected on your help,
but instead got a story that shoot in the leg is hurt, I know about
this, let me leave the choice, in my case for connect to MS SQL from
MariaDB ideal is storing passwords in odbc.ini. I also can't modify
MariaDB to that use ~/.netrc for store passwords. :(

sorry for my english.




--
Best Regards,
Mike Gavrilov.