title: How to secure database traffic the other way around, that is to say, from client to server
body: <p><strong>My scenary:</strong></p>
  
  <p>I am trying to develop a service which will query different databases. </p>
  
  <p>To clear the above statement up:</p>
  
  <ol>
  <li><p>I use the word service in its broadest sense: a sofware component that will provide some value to the database owner.</p></li>
  <li><p>These databases will be in no way under my control as they will belong to different companies. They won't be known beforehand and multiple vendors are to be supported: Oracle, MS (SQL Server), MySql, PostgreSQL. Also, OLE DB and ODBC connections will be supported. </p></li>
  </ol>
  
  <p><strong>The problem</strong>: security of database credentials and overall traffic is a big concern but the configuration effort should be reduced at a minimum. Ideally, all the security issues should be addressed programmatically in the service implementation and require no configuration effort for the database owner other than provide a valid connection string.</p>
  
  <p>Usually, database SSL support is done through server certificates which I want to avoid as it is cumbersome for the client (the database owner).
  I have been looking into how to do this to no avail. Hopefully this might be done with openssl, SSPI, client SSL certificate or any form of tunneling; or may be it is just not posible. Some advice would be greatly apreciatted.   </p>