Hi,
starting with version 3.65 the aladdin software is able to reformat also
4.2b cardos.
Kind regards
Cornelius
Jean-Pierre Szikora schrieb:
> Jacob H. Wiseman a écrit :
>
>> Has anyone been able to reformat an Aladdin eToken with CardOS 4.2b to
>> an uninitialized state? The software provid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
unfortunately I guess at the moment it will not make it easier for your
users. The integration of smartcards is not seamless into any linux
distribution yet.
Even if all opensc software is installed and your token/smartcard is
recognized, the user
Wow,
you would have to implement any kind of client server protocol, that is
not part of pkcs11.
Hm, such a thing sound very interesting...
regards
Cornelius
Ph. Marek schrieb:
> Hello everbody!
>
> I seem to remember having read about a pkcs#11 forwarding driver, which
> allows
> to forward pk
to configure udev for the etoken.
Kind regards
Cornelius Kölbel
Hans Rembeck schrieb:
> Hello
>
> when Iam using the PKCS#11 Event Manager and insert an etoken into usb,
> there is no verification.
> It means that when i remove etoken A and insert etoken B never mind.
>
>
Hello,
tried to write a patch for pkcs11-tool, that would allow to write the
public key to the smartcard.
Hm, does not work for me, yet. Maybe due to the middle of the night... ;-)
...but maybe due to my pkcs11-library.
Maybe some of you got an enlighting idea.
Kind regards
Cornelius
--- opensc
Hello,
I wrote a small, dirty patch for the pkcs11-tool (0.11.1) do be able to write
data objects to a smartcard.
...if it is of any interest:
It would be invoked like this to write the contents of the file "test":
./pkcs11-tool -w test -y data --application-id TEST --label CORNY -l
(My pkcs11
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello Nils,
Nils Larsch schrieb:
> Cornelius Koelbel wrote:
>> Hello,
>>
>> I liked the pkcs11-tool very much and used it with aladdin's own
>> pkcs11-lib. But I could not manage to initialize the token and i
>> could not change the pin.
>>
>> Th
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello,
what are the command line parameters to change the SO_PIN?
As far as I know, the SO_PIN has to be changed by C_Login using the
SO_PIN and the doing a C_SetPin.
But from looking at the code, I get no idea what parameters should be
combined.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Marc Bevand schrieb:
> Cornelius Kölbel wrote:
> | Hello,
> |
> | I am using pkcs11-tool with the Aladdin's pkcs11-lib.
> | Many things work out fine.
> | But when I try to initialize a eTokenPro I get the following
t has _no_
administrator password aka. SO Pin set. Now I can do pkcs11-tool
--module /usr/local/lib/libetpkcs11.so --init-pin As the SO-PIN I can
enter my user pin and now I can enter a new user pin. Kind regards
Cornelius
--
Dipl.-Phys. Cornelius Kölbel (Security Consultant)
LSE Leading Sec
rv = CKR_DEVICE_ERROR;
goto out;
}
opensc-pkcs11 looks somehow hardcoded. Is this a reason the --init-token
will not work with third-party pkcs11-libs?
Or is it a matter of the pkcs11-lib I am using?
Regards
Cornelius
--
Dipl.-Phys. Cornelius Kölbel (Secur
11 matches
Mail list logo
