Archives of the TeradataForum
Message Posted: Fri, 16 Jul 2004 @ 22:43:15 GMT
I'm glad that the author is updating DBD::Teradata for password encryption, but I strongly recommend that new implementers choose DBD::ODBC instead. The ODBC interface isolates you from changes in the low level protocol, such as password encryption, and makes it easier to rehost your application (just change ODBC drivers).
And before you commit to DBD::Teradata with encryption, you need to find out
1. if NCR has published their encryption algorithm (I couldn't find it), and
2. will DBD::Teradata support V2R5.1.0 or V2R5.1.1 encryption (they're different).
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|