# Re: Re: Javakey: could not initialize scope

Jose Ramon Huerga (jrhuerga@sag.es)
Tue, 23 Dec 1997 18:34:11 +0100

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Sheri Good: "Newer release of JCE"
- Previous message: Arijit Chakraborty: "Jav Security Standards"

    Message-Id: <s4a0048b.096@sag.es>

    Date: Tue, 23 Dec 1997 18:34:11 +0100

    From: Jose Ramon Huerga <jrhuerga@sag.es>

    To: Charlie.Lai@Eng, java-security@web2.javasoft.com

    Subject: Re: Re: Javakey: could not initialize scope

Hi:

>> Jose Ramon Huerga <jrhuerga@sag.es>
>> I'm using NT 4.0 server and JDK 1.1.4. When I launch javakey, I get
>> the > following:
>>
>> C:\> javakey
>> could not initialize scope

> Charlie Lai <Charlie.Lai@Eng.Sun.COM>
> if you have an old identity database lying around,
> and you don't need the keys anymore, remove it.
> the filename is called: identitydb.obj.
> then try running javakey again...

If identitydb.obj is removed, the next time 'javakey' runs, it generates
another identitydb.obj and the problem is the same: it can initialize scope.

The right solution is to change the permissions for identitydb.obj. By default,
only SYSTEM has full access; this isn't enough. At least the user that is
going to work with 'javakey' must be granted to read/write identitydb.obj.

I changed the permissions with explorer, and it worked nice: I ran the
signed jar file example!!

Thanks a lot Charlie

- Next message: Sheri Good: "Newer release of JCE"
- Previous message: Arijit Chakraborty: "Jav Security Standards"