From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] sim: check if lock is locked after code changing attempt
Date: Wed, 12 Jan 2011 09:35:51 -0600 [thread overview]
Message-ID: <4D2DCA57.4080206@gmail.com> (raw)
In-Reply-To: <20A4FB08D632914F9C09B9F05CBDF258192D753286@EXMB02.eu.tieto.com>
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
Hi Jussi,
> I don't particularly wish to use the retry counters. I was just thinking that same
> information ( PUK required ) could be deduced by counting the retries.
To my knowledge you cannot. Correct me if I'm wrong, but the retry
counters are stored on the SIM and the SIM can be removed, and later
re-inserted. You would not know how the counters have been affected.
Regards,
-Denis
next prev parent reply other threads:[~2011-01-12 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 7:39 [PATCH] sim: check if lock is locked after code changing attempt Jussi.Kangas
2011-01-12 10:11 ` Lucas De Marchi
2011-01-12 15:35 ` Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-11 12:17 Jussi.Kangas
2011-01-11 14:08 ` Lucas De Marchi
2011-01-12 5:07 ` Denis Kenzior
2011-01-13 8:34 ` Jussi.Kangas
2011-01-13 13:35 ` Lucas De Marchi
2011-01-13 16:28 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D2DCA57.4080206@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.