<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi,</div>
<div> </div>
<div>recently I have been struggling with secure handling of my username and password in ODBC connections to MS SQL when using GDAL/OGR.</div>
<div> </div>
<div>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...</div>
<div> </div>
<div>So, the only alternatives are</div>
<div>a) using trusted connctions and kerberos or</div>
<div>b) provide username and password in the connection string.</div>
<div> </div>
<div>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.</div>
<div>I guess not reading username and password from odbc.ini is a limitation that originates from unixODBC / FreeTDS.</div>
<div>However, it would be great to avoid providing password on the command line in GDAL.</div>
<div> </div>
<div>If could use environment variables or a passwordfile (like .pgpass with PostgreSQL) that would be great.</div>
<div>My question is, did I overlook an option to securly handle login info in MSSQL ODBC connections in GDAL? </div>
<div> </div>
<div>Cheers</div>
<div>Stefan</div>
<div> </div></div></body></html>