From: Martin P. <Mar...@ia...> - 2007-07-16 10:44:18
|
Till Bentz wrote: > I think I found the error. It was the encoding of the used passwords. I > guess if the password is set via tpm_takeownership the encoding is ASCII > whereas jTSS expects UTF-16LE. jTSS takes whatever the client passes in. See JTpmTools optional parameters: -e encoding ... encoding for password strings (legal values: ASCII, UTF-16, UTF-16BE, UTF-16LE) (default: UTF-16LE) -n ... append null termination to password strings There is/was confusion about encoding of passwords in the 1.1 vs 1.2 spec vs. "reality" of various Windows stack vendors. In order to offer the user the choice, JTpmTools supports above flags to allow maximum compatibility (see source code how to handle the cases). I hope this is also your "Authentication" issue in your mail of 2007-07-04 18:44. HTH -- Martin Pirker IAIK, TU Graz |