RE: Keytool weirdness

This appears to be an inconsistent translation problem between QSH and keytool. QSH 5250 interface is EBCDIC-oriented and keytool is all ASCII. It looks like your keystore password is being stored one place in EBCDIC and another in ASCII. QSH should be translating everthing from whatever EBCDIC code page you're using to 819 USASCII. I can't tell you why it wouldn't.

Have you tried with CALL QP2TERM?

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Tuesday, January 10, 2012 11:11 AM
To: Java Programming on and around the IBM i
Subject: Keytool weirdness

Turns out that my problem (or at least my current problem) with HTTPS-enabling Tomcat is with Keytool:

It seems that when I create a keystore with Keytool, in a QShell session, not only can't Tomcat get into the keystore: KEYTOOL ITSELF can't get in!

Here's a QShell transcript (the same one as in the "HTTPS-enabling Tomcat" thread) from a test I ran specifically so that I could post everything without betraying any passwords:

keytool -genkey -alias foo -keyalg RSA -keystore /foo

Enter keystore password:

bar

What is your first and last name? [Unknown]:

James Lampert

What is the name of your organizational unit? [Unknown]:

Development Lab

What is the name of your organization? [Unknown]:

Touchtone Corporation

What is the name of your City or Locality? [Unknown]:

Costa Mesa

What is the name of your State or Province? [Unknown]:

California

What is the two-letter country code for this unit? [Unknown]:

US

Is CN="James Lampert
", OU="Development Lab

>
", O="Touchtone Corporation

", L="Costa Mesa
", ST="California
", C="US

" correct? (type "yes" or "no")
[no]:

yes

Enter key password for <foo>: (RETURN if same as keystore password):

bar

$

keytool -list -keystore /foo -storepass bar

keytool error (likely untranslated): java.io.IOException: Keystore

was tampered with, or password was incorrect >$


I ran a similar test from a WinDoze command line, and it worked just fine.

CCSID on the keystore is 819, which is kind-of to be expected. But is that what it should be?

Another thought occurred to me: Could the trailing blanks shown in the confirmation message have anything to do with the problem?

--
JHHL
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.