fixed typos
This commit is contained in:
parent
d98eafd6b6
commit
94c9289b64
|
@ -17,7 +17,7 @@ During installation the user's PIN is set to 000000 (six times zero). The PIN le
|
|||
failed authentication attempts the PIN is blocked and authentication is not possible anymore. A blocked PIN can be
|
||||
replaced and unblocked using a PUK. The PUK is a 12-digit number, unique for each installation and is generated off-card
|
||||
and passed as an installation parameter to the applet according to the JavaCard specifications. After 5 failed attempts
|
||||
to unblock the applet using the PUK, the PUK is blocked, meaning the the wallet is lost.
|
||||
to unblock the applet using the PUK, the PUK is blocked, meaning the wallet is lost.
|
||||
|
||||
After authentication, the user remains authenticated until the application is either deselected or the card is reset.
|
||||
Authentication with PIN is a requirement for most commands to succeed.
|
||||
|
|
|
@ -172,7 +172,7 @@ public class SecureChannel {
|
|||
}
|
||||
|
||||
/**
|
||||
* Performs the first step of pairing. In this step the card solves the challenge sent by the card, thus authenticating
|
||||
* Performs the first step of pairing. In this step the card solves the challenge sent by the client, thus authenticating
|
||||
* itself to the client. At the same time, it creates a challenge for the client. This can only fail if the card has
|
||||
* already paired with the maximum allowed amount of clients.
|
||||
*
|
||||
|
|
Loading…
Reference in New Issue