status-im
/
status-keycard
mirror of https://github.com/status-im/status-keycard.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #4 from tista3/master 

fixed typos in code documentation and markdown
This commit is contained in:
Bitgamma 2018-05-04 12:48:55 +03:00 committed by GitHub
parent d98eafd6b6 94c9289b64
commit eb233757fc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
APPLICATION.MD
View File

@ -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.

2
src/main/java/im/status/wallet/SecureChannel.java
View File

@ -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.
*