This is a multi-part message in MIME format.
------_=_NextPart_001_01C8E5D1.2D21B632
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable=20
There's apps that do this, like kdewallet.=20
=20
I was thinking of a picture pin entry. You display a small set of
pictures with lots of detail, user must tap 1 or more points on each
pictures.=20
=20
Quick entry, good number of bits of encryption, easy to remeber.
=20
Plus, when the phone comes up with a picture, to anybody else it just
looks like it's stuck booting or broken.________________________________
From: community-bounces@lists.openmoko.org
[mailto:community-bounces@lists.openmoko.org] On Behalf Of thomasg
Sent: Monday, July 14, 2008 12:19 PM
To: List for Openmoko community discussion
Subject: Re: MokSec - The Security FrameworkOn Mon, Jul 14, 2008 at 6:13 PM, Kalle Happonen
wrote:=09
I had some thoughts about that, too.
Would be cool if it wasn't necessary to have a PIN at all - you
enter the PIN in the "first-run-wizard", that will store it.
After that you only have one password (of your choise) that does
all - the security daemon would lookup in a key/password-database and
use your password for all things, like decrypting the other containers
(phonebook, messages, e.g.), authing you on the network with the stored
pin, unlocking the phone screen, .....
=09------_=_NextPart_001_01C8E5D1.2D21B632
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
There's apps that do this, like=20
kdewallet.
I was thinking of a picture pin entry. =
You display a=20
small set of pictures with lots of detail, user must tap 1 or more =
points on=20
each pictures.
Quick entry, good number of bits of encryption, =
easy to=20
remeber.
Plus, when the phone comes up with a picture, =
to anybody=20
else it just looks like it's stuck booting or =
broken.
From: =
community-bounces@lists.openmoko.org=20
[mailto:community-bounces@lists.openmoko.org] On Behalf Of=20
thomasg
Sent: Monday, July 14, 2008 12:19 PM
To: =
List=20
for Openmoko community discussion
Subject: Re: MokSec - The =
Security=20
Framework
On Mon, Jul 14, 2008 at 6:13 PM, Kalle Happonen <kalle.happonen@iki.fi> =
wrote:
I had some thoughts =
about that,=20
too.
Would be cool if it wasn't necessary to have a PIN at all - =
you enter=20
the PIN in the "first-run-wizard", that will store it.
After that =
you only=20
have one password (of your choise) that does all - the security daemon =
would=20
lookup in a key/password-database and use your password for all =
things, like=20
decrypting the other containers (phonebook, messages, e.g.), authing =
you on=20
the network with the stored pin, unlocking the phone screen,=20
.....------_=_NextPart_001_01C8E5D1.2D21B632--
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | 2.6.25-mm1 |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Natalie Protasevich | [BUG] New Kernel Bugs |
