Date: | Thu, 11 Sep 2014 14:22:37 -0700 |
From: | Neng Xue <neng.xue@oracle.com> |
To: | krb5-bugs@mit.edu |
Subject: | Problem regarding 'Pass phrase' prompt length limit in pkinit plugins |
Hi,
I am Neng Xue currently working in MIT dropin project in Oracle Solaris group as a software developer. Recently we noticed an occasionally happened test failure of python test t_pkinit.py[54] in our build environment. Then I tried to debug into the issue. I noticed that after reading the certs file for test case 54, the pass phrase prompt did not even appear before reporting the test case failure. So I turned on the -DDEBUG option for debug mode. I saw the following error message:
Prompt string, 'Pass phrase for /*****/*******/*****/*****/user-enc.p12', is too long!
The prompt_string length limit is set to 128 characters, in our build environment, the file path length around 100 which makes the total length of prompt_string exceeding the 128 limit. I was wondering is there a particular reason for this limit? Or is there a workaround for this issue? Thanks!
I am Neng Xue currently working in MIT dropin project in Oracle Solaris group as a software developer. Recently we noticed an occasionally happened test failure of python test t_pkinit.py[54] in our build environment. Then I tried to debug into the issue. I noticed that after reading the certs file for test case 54, the pass phrase prompt did not even appear before reporting the test case failure. So I turned on the -DDEBUG option for debug mode. I saw the following error message:
Prompt string, 'Pass phrase for /*****/*******/*****/*****/user-enc.p12', is too long!
The prompt_string length limit is set to 128 characters, in our build environment, the file path length around 100 which makes the total length of prompt_string exceeding the 128 limit. I was wondering is there a particular reason for this limit? Or is there a workaround for this issue? Thanks!
-- Neng Xue Oracle Solaris Software Engineer Santa Clara, CA, USA