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