Hi,
recently I have been struggling with secure handling of my username and password in ODBC connections to MS SQL when using GDAL/OGR.
From my understanding, username and password are not read from odbc.ini files, so I cannot specify a DSN where username and password are predefined in that file...
So, the only alternatives are
a) using trusted connctions and kerberos or
b) provide username and password in the connection string.
Unfortunately, a) is not available to me. While a file name with username and password is not ideal, providing username and password on the commandline seems worse, as it leaks many places.
I guess not reading username and password from odbc.ini is a limitation that originates from unixODBC / FreeTDS.
However, it would be great to avoid providing password on the command line in GDAL.
If could use environment variables or a passwordfile (like .pgpass with PostgreSQL) that would be great.
My question is, did I overlook an option to securly handle login info in MSSQL ODBC connections in GDAL?
Cheers
Stefan
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
