Re: Sybase Connection - trouble without protocol fallback
Frediano Ziglio <[email protected]> Wed, 5 Jul 2017 10:24:30 +0100
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <CAHt6W4d1q+Z8t2wRqgPSaasn44TKP9rnJak8_GmoSG70GAQ64A@mail.gmail.com> |
2017-07-04 16:28 GMT+01:00 Fredy Paquet <[email protected]>: > Hello Igor > > The FreeTDS user guide defines default encryption level is OFF: > (see http://www.freetds.org/userguide/freetdsconf.htm) > > The config file parser initializes encryption_level to > TDS_ENCRYPTION_DEFAULT. If you do not set encryption in any section of > your freetds.conf, the encryption_level in the login struct remains at > TDS_ENCRYPTION_DEFAULT. > > Today, the TDS 7.1 driver changes this value to TDS_ENCRYPTION_REQUEST, > which doesn't implement the documented behaviour. > The website documentation reflect the last stable release where the default was OFF. > I do not know wether MSSQL can accept unencrypted requests (no test > system available). > Recent ones do not allow unencrypted logins. > If MSSQL cannot accept unencrypted connections, it may be ok to fallback > to TDS_ENCRYPTION_REQUEST for TDS 7.1. But this clearly must not affect > further trials on the lower protocol levels. > > Agree, it would be good programming practise to introduce a #define for > the default encryption level. > What do you mean? Is an enum not enough? > fp > Frediano