Print

Welcome to Smokey's Security Forums.

Guests have only limited access to the board and it's features, please consider registering to gain full access!

Registration is free and it only takes a few moments to complete.

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DennisMoore]

Thanks for the reply. I have a lot of 10 64k Tokens and some of them seem to be broken.
I just tested all of them and only 6 are working with BCVE. Yesterday I tried 2 of the non-working 

2 of them are completely rejected by BCVE. The program and PKIClient say the serial number is 0xffffffff and the color is unknown. When I choose them, the password box remains locked.

Well, I think I have to send them back to the dealer.

[Jetico]

You wrote that you have initialized eToken device.

Please note that eToken device has to be formatted in compatibility
mode with Aladdin Run-Time Environment (RTE) v. 3.65. It is necessary
to allow programs like BCVE to access eToken devices at boot-time.

If possible, could you please run PKI Client program to
format the eToken in compatibility mode with RTE 3.65?

"Format" procedure is called as "Initialization" in the
program. In more detail, to format the eToken please do
the following:

- in PKI Client window select the 'eToken' in the left pane;

- press 'Initialize eToken' button;

- in appeared window press 'Advanced' button;

- set the '3.65 compatibility mode' checkbox in appeared window
and complete the initialization process.

[DennisMoore]

Hi.

eToken 32k does work with BCVE, but eToken 64k does not.

I initialized a 64k-Token with PKI Client 5.1, changed Password but BCVE does not accept the password.
It tells me that I entered a wrong password, but thats not true. Also, it tells it instantly. Seems BCVE does not even try to logon. However my 32k-Tokens do not have these problems.

Anything special to be aware of when changing from 32k to 64k eToken Pro?