Archives of the TeradataForum
Message Posted: Mon, 25 Jan 2005 @ 01:30:09 GMT
I just wanted to remind everyone that the DBD::Teradata module does not work at V2R5.1.0 and beyond because of encrypted logons. We are advising our users to convert to DBD::ODBC and use the Teradata ODBC driver to isolate themselves from changes in the low level protocol (5.0.x, 5.1.0 and 5.1.1 use different protocols for example).
The perl DBD::Teradata module implements the communications protocol at a very low level, and the new encrypted logon handshake is not handled by the module. The author has moved on to other things and has no plans to upgrade the GPLed module, though there is some indication that a commercial version of the module would be made available.
Yes you can set the "allow deprecated logons flag" to get around this, remembering that after every node failure you have to set the flag again because the GDO is reset (don't have the DR handy - not fixed until V2R6.x). But at some point you or your security department is going to want encrypted logons.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|