-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feitian epass2003 is not working with pcsc-lite 1.8.21 after pcscd restart on freebsd 11 #38
Comments
From your log:
Why do you stop pcscd? |
It's the easiest way I've found to reproduce the loss of communication between the Token feitian epass2003 and pcscd, with the error: |
I am not surprised that communication fails after you stop pcscd in the middle of a command to the token. Just don't do that. The way to reset the token is to remove it as you have already found. There is no problem in the log you sent. |
if a start of the pcscd process occurs during the solicitation of the fetian key, the communication becomes impossible with the Token without a hard reboot.
here is a way to reproduce the bug:
#=======================================================
echo ">>>> run pcscd in debug mode:"
LIBCCID_ifdLogLevel=0x000F pcscd --foreground --debug --apdu --color &
#pcscd -dfa &
if [ "$1" == "init" ]; then
echo ">>>> RAZ token"
#box_init_token -f
/usr/local/bin/pkcs15-init --erase-card
/usr/local/bin/pkcs15-init --create-pkcs15 --profile pkcs15+onepin --use-default-transport-key --label "TOKEN" --pin 0000 --puk 1111
fi
echo ">>>> Generate-key"
pkcs15-init --generate-key rsa/2048 --id 3 --auth-id 1 --key-usage sign,decrypt --label "KEY" --pin 0000 & {
sleep 2; #wait for generate to begin
echo '>>>> kill pcscd !!!!'; pkill pcscd ;
}
sleep 1
echo ">>>> Restart pcscd..."
LIBCCID_ifdLogLevel=0x000F pcscd --foreground --debug --apdu --color &
echo ">>>> Try to get serial"
opensc-tool --serial
sleep 3
echo ">>>> Finally kill pcscd"
pkill pcscd
#=======================================================
traces_pcscd_pb.txt
The text was updated successfully, but these errors were encountered: