You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "zhubin (JIRA)" <ji...@apache.org> on 2014/09/25 08:19:34 UTC
[jira] [Updated] (HADOOP-11133) failed to read correct content of
keystore password file in hadoop-kms
[ https://issues.apache.org/jira/browse/HADOOP-11133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhubin updated HADOOP-11133:
----------------------------
Description:
When setup kms service to enable CFS feature, I created the keystore password file and input the password content (like '123456'). But it failed to start kms service with below error:
java.io.IOException: Keystore was tampered with, or password was incorrect
As debugging, the failure was caused by the invalid password content due the code read more char which is invisible (like file ending char). So the right behavior is to filter out the invisible chars during reading the password file.
was:
When setup kms service to enable CFS feature, I created the keystore password file and input the password content (like '123456'). But it failed to start kms service with below error:
java.io.IOException: Keystore was tampered with, or password was incorrect
As debugging, the failure was caused by the invalid password content due the code read more char which is invisible (like file ending char). So the right behavior is to filter out the invisible chars during reading password file.
> failed to read correct content of keystore password file in hadoop-kms
> ----------------------------------------------------------------------
>
> Key: HADOOP-11133
> URL: https://issues.apache.org/jira/browse/HADOOP-11133
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 3.0.0, 2.6.0
> Reporter: zhubin
>
> When setup kms service to enable CFS feature, I created the keystore password file and input the password content (like '123456'). But it failed to start kms service with below error:
> java.io.IOException: Keystore was tampered with, or password was incorrect
> As debugging, the failure was caused by the invalid password content due the code read more char which is invisible (like file ending char). So the right behavior is to filter out the invisible chars during reading the password file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)