This is essentially correct, although the "Data Integrity" option actually uses
an _encrypted_ hash in the GSS/Kerberos token. BTW, JDBC, Cache Direct, et al.,
offer the same options.
--Dave
Mark Sires wrote:
Markus,
As I recall (also a little jetlagged), there were several options in the new
ODBC driver.
First was regular (as it is now) Cache username/password authentication. No
additional options if this is chosen.
The second was to use Kerberos authentication. If this was chosen, then you
could also either provide data source/content assurance (a hash of the
source/data information included with each packet, but no encryption of the
data), or encrypt the data stream.
Mark
"Markus" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hi folks,
being heavily jetjagged at the time, did i actually see an option to have
the odbc/cache direct connection being an encrypted stream? or was i
dreaming during that part?
Thanking you in advance, and (a phrase that i hardly heard in the past
week), I appreciated it
--
W. David Shambroom, Ph.D.
Security Architect 617.551.2143
InterSystems Corporation [EMAIL PROTECTED]
