When I enter my password and tap "Unlock", it
disappears for about 1 to 2 seconds. Maybe this is
while the decryption is occuring? I chose 1000 and
AES-256. I have a Zire 72 (pretty fast processor).
The button disappears while keyring checks the password.
This takes some time due to the 1000 iterations of HMAC-SHA1
that are used (that are used to prevent brute-force
attacks). You can lower the iteration count, if you feel
uncomfortable with that delay.
It would be useful to have an ARM implementation of sha-1
and pbkdf2. The code is easy to separate. I have no ARM
based palm, so I can't implement this myself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One possible solution would be to have a 2nd "Unlock"
button. Same place, same size. The first line of the real
unlock event handler could be to draw that button. The last
line could be to hide it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure what you meant by the last comment. The unlock button
is explicitly hidden, so that the user knows, that the palm is busy and
doesn't tap the button again.
Maybe it's useful to display "checking..." at the place where the button
was, so that it is clear what is going on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't realize you explicitely hid the button. Ignore my
last (not understood) comment. I would love to see
"checking..." or something else. Anything else, just some
user feedback to let me know it is thinking, not frozen or
buggy or something bad.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=18252
The button disappears while keyring checks the password.
This takes some time due to the 1000 iterations of HMAC-SHA1
that are used (that are used to prevent brute-force
attacks). You can lower the iteration count, if you feel
uncomfortable with that delay.
It would be useful to have an ARM implementation of sha-1
and pbkdf2. The code is easy to separate. I have no ARM
based palm, so I can't implement this myself.
Logged In: YES
user_id=192791
One possible solution would be to have a 2nd "Unlock"
button. Same place, same size. The first line of the real
unlock event handler could be to draw that button. The last
line could be to hide it.
Logged In: YES
user_id=18252
I'm not sure what you meant by the last comment. The unlock button
is explicitly hidden, so that the user knows, that the palm is busy and
doesn't tap the button again.
Maybe it's useful to display "checking..." at the place where the button
was, so that it is clear what is going on.
Logged In: YES
user_id=192791
I didn't realize you explicitely hid the button. Ignore my
last (not understood) comment. I would love to see
"checking..." or something else. Anything else, just some
user feedback to let me know it is thinking, not frozen or
buggy or something bad.