public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Aguiar <carlos.aguiar@indt.org.br>
To: Anderson Lizardo <anderson.lizardo@gmail.com>
Cc: David Brownell <david-b@pacbell.net>,
	Anderson Lizardo <anderson.lizardo@indt.org.br>,
	linux-omap-open-source@linux.omap.com,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-kernel@vger.kernel.org,
	Anderson Briglia <anderson.briglia@indt.org.br>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [patch 0/5] Add MMC password protection (lock/unlock) support
Date: Tue, 27 Dec 2005 14:48:21 -0400	[thread overview]
Message-ID: <43B18C75.6030807@indt.org.br> (raw)
In-Reply-To: <5b5833aa0512141448o1014e7a5vdfd62cfdc61c7d11@mail.gmail.com>

Anderson Lizardo wrote:

>On 12/13/05, David Brownell <david-b@pacbell.net> wrote:
>  
>
>>Is there a writeup on how to hook this up with the key retention
>>infrastructure?  I know many folk are unfamiliar with that, and
>>I seem to recall a need for some userspace tweaks.  (Like SHA1
>>hashing of passphrases to generate MMC keys, and maybe storing
>>keys in some per-user file using some user interface.)
>>    
>>
>
>We have created a sample text-mode reference UI (using keyctl from the
>keyutils[1] package to interface with the key retention service) that
>shows how everything works together. We are setting up some web space
>to put such UI (actually a set of shell scripts) and we will provide
>links soon.
>
>Regarding the userspace tweaks, we have not gone into this aspect, but
>just provided the "core" kernel code. Usually, those integrating the
>system will dictate policies regarding password hashing, persistent
>caching etc. The policies for our reference UI were:
>
>- no hashing (password is sent/stored clear-text)
>- in-memory caching (so if the user reboots the system, the password
>will have to be re-typed).
>
>I think those policies can be done still on userspace, so the kernel
>code remains "policy-free".
>
>[1] http://people.redhat.com/~dhowells/keyutils/
>--
>Anderson Lizardo
>Embedded Linux Lab - 10LE
>Nokia Institute of Technology - INdT
>Manaus - Brazil
>
>  
>
Hi all,

As promised, you can find a simple text-mode reference UI for the MMC 
password protection
support, written in shell script, that shows how everything works 
together on the links below:

http://www.indt.org.br/10le/mmc_pwd/mmc_reference_ui-20051215.tar.gz
http://www.indt.org.br/10le/mmc_pwd/mmc_test-20051215.sh


BR,

Carlos Aguiar.



-- 
Carlos Eduardo
Software Engineer
Nokia Institute of Technology - INdT
Embedded Linux Laboratory - 10LE
Phone: +55 92 2126-1079
Mobile: +55 92 8127-1797
E-mail: carlos.aguiar@indt.org.br


  reply	other threads:[~2005-12-27 18:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051213213208.303580000@localhost.localdomain>
2005-12-13 22:03 ` [patch 0/5] Add MMC password protection (lock/unlock) support David Brownell
2005-12-14 22:48   ` Anderson Lizardo
2005-12-27 18:48     ` Carlos Aguiar [this message]
2005-12-13 22:27 ` Anderson Briglia
2005-12-14  7:07   ` Pierre Ossman
2005-12-14 23:51     ` Anderson Lizardo
2005-12-15  6:49       ` Pierre Ossman
2005-12-15  9:12         ` Russell King
2005-12-15  9:27           ` Pierre Ossman
2005-12-15 10:06             ` Russell King
2005-12-15 13:44               ` Russell King
2005-12-15 16:01                 ` Pierre Ossman
2005-12-29 19:06                 ` Anderson Lizardo
2005-12-29 20:09                   ` Russell King
2005-12-29 21:23                     ` Anderson Lizardo
2005-12-29 21:37                       ` Russell King
2005-12-29 19:17                 ` Anderson Lizardo

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=43B18C75.6030807@indt.org.br \
    --to=carlos.aguiar@indt.org.br \
    --cc=anderson.briglia@indt.org.br \
    --cc=anderson.lizardo@gmail.com \
    --cc=anderson.lizardo@indt.org.br \
    --cc=david-b@pacbell.net \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.com \
    /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