|| ||Carlos Aguiar <firstname.lastname@example.org>|
|| ||[patch 0/6] Add MMC password protection (lock/unlock) support V4|
|| ||Tue, 31 Jan 2006 16:16:36 -0400|
|| ||email@example.com, David Brownell <firstname.lastname@example.org>,
Tony Lindgren <email@example.com>,
Russell King <firstname.lastname@example.org>,
"Aguiar Carlos (EXT-INdT/Manaus)" <email@example.com>,
"Lizardo Anderson (EXT-INdT/Manaus)" <firstname.lastname@example.org>,
Anderson Briglia <email@example.com>|
New in this version:
- The remaining MMC password operations previously executed by key
retention functions (change password, unlock card and assign password)
were implemented using the sysfs mechanism.
- Added the host MMC lock/unlock capability support for OMAP platform.
- Added verbose debugging messages
This series of patches add support for MultiMediaCard (MMC) password
protection, as described in the MMC Specification v4.1. This feature is
supported by all compliant MMC cards, and used by some devices such as
Symbian OS cell phones to optionally protect MMC cards with a password.
By default, a MMC card with no password assigned is always in "unlocked"
state. After password assignment, in the next power cycle the card
switches to a "locked" state where only the "basic" and "lock card"
command classes are accepted by the card. Only after unlocking it with
the correct password the card can be normally used for operations like
Password management and caching is done through the "Kernel Key
Retention Service" mechanism and the sysfs filesystem. A new sysfs
attribute was added to the MMC driver for unlocking the card, assigning
a password to an unlocked card, change a card's password, remove the
password and check locked/unlocked status.
A sample text-mode reference UI written in shell script (using the
keyctl command from the keyutils package), can be found at:
- Password caching: when inserting a locked card, the driver should try
to unlock it with the currently stored password (if any), and if it
fails, revoke the key containing it and fallback to the normal "no
password present" situation.
- Some cards have an incorrect behaviour (hardware bug?) regarding
password acceptance: if an affected card has password <pwd>, it
accepts <pwd><xxx> as the correct password too, where <xxx> is any
sequence of characters, of any length. In other words, on these cards
only the first <password length> bytes need to match the correct
We would like to ask you to test these patches. We believe they are
ready to be included on the kernel source.
Comments and suggestions are welcome.
Carlos Eduardo Aguiar
Embedded Linux Lab - 10LE
Nokia Institute of Technology - INdT
Manaus - Brazil