mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Anderson Lizardo" <anderson.lizardo@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: "Pierre Ossman" <drzeus-list@drzeus.cx>,
	"Russell King" <rmk+lkml@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org,
	"Anderson Briglia" <anderson.briglia@indt.org.br>
Subject: Re: [patch 0/6] [RFC] Add MMC Password Protection (lock/unlock) support V6
Date: Sat, 25 Nov 2006 11:35:29 -0400	[thread overview]
Message-ID: <5b5833aa0611250735h5bda01b5lc3ae8e2199f51215@mail.gmail.com> (raw)
In-Reply-To: <200611181418.10675.david-b@pacbell.net>

Hi David,

On 11/18/06, David Brownell <david-b@pacbell.net> wrote:
> On Saturday 18 November 2006 1:42 pm, Pierre Ossman wrote:
> > David Brownell wrote:
> > > I thought the MMC vendors expected to see the actual user-typed
> > > password get SHA1-hashed into a value which would take up the whole
> > > buffer?  In general that's a good idea, since it promotes use of
> > > longer passphrases (more information) over short ones (easy2crack).
> > >
> >
> > This sounds like policy though, so it is something user space should
> > concern itself with. We should just provide the infrastructure.
>
> The kernel shouldn't hash, right.  But the userspace toos
> probably should be doing that ... they're the other part of
> the infrastructure. :)

Interesting idea, indeed. We'll implement this in our reference UI
(which currently is just a bunch of shell scripts) so we can test the
feasibility of this approach. Additionally, I think it's a good idea
to investigate how other vendors currently support password protection
on their products (for now I've just seen Nokia cellphones with such
support, maybe PDAs or other mobile devices support this?), so we can
have compatible policies, allowing to lock/unlock cards across
devices.

Anyway, I also agree this is out of scope of the kernel support, but
still it's very important for a complete support.

Regards,
-- 
Anderson Lizardo
Open Source Mobile Research Center - OSMRC
Nokia Institute of Technology - INdT
Manaus - Brazil

      reply	other threads:[~2006-11-25 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 12:58 Anderson Briglia
2006-11-18 19:17 ` David Brownell
2006-11-18 21:42   ` Pierre Ossman
2006-11-18 22:18     ` David Brownell
2006-11-25 15:35       ` Anderson Lizardo [this message]

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=5b5833aa0611250735h5bda01b5lc3ae8e2199f51215@mail.gmail.com \
    --to=anderson.lizardo@gmail.com \
    --cc=anderson.briglia@indt.org.br \
    --cc=david-b@pacbell.net \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®