Hello Peter! > What kind of logon do you mean (ie. Windows-logon, SSH-logon, ...)
Just authenticate user for security operation. > This only happens if you are using an Aladdin eToken that > was formatted by the Aladdin-tools. If you format your > eToken with OpenSC your keys will be protected the > "normal" way. Yes I have problem only with AKS application, PKCS15 on eToken is working correctly. > http://www.opensc-project.org/pipermail/opensc-devel/2006-December/009396.html > Same problem ?? not quite, I want to provide data signing with eToken application AKS. I have no problem with MSE and PSO, but first I need authenticate user. As I wrote, > Aladdin's utility eToken Property use EXTERNAL_AUTHENTICATE for this. > Utility send adpu GET_CHALLENGE "00 84 00 00 08" and > EXTERNAL_AUTHENTICATE "00 82 00 81 08 2D 42 BC F8 C1 65 A3 D5" > > But I don't know how built EXTERNAL_AUTHENTICATE data. > It's look like hashed pin + challenge response. > But how correctly combine pin and challenge response, and which hash alg is > using? I don't have enough documentation for making EXTERNAL_AUTHENTICATE data. Aladdin don't publish it and promote theirs own pkcs11 library. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
