[patch 0/5] Add MMC password protection (lock/unlock) support V3

[Anderson Briglia <anderson.briglia@indt.org.br>]

Hi all,

New in this version:

- Block size calculation functions replaced by a native kernel function.
- Added a flag (pwd_disabled) to mmc_host structure for disabling password
protection support on the hosts that cannot handle this feature (such as
mmci driver).
- Common code included in the mmc_key_instantiate() and mmc_key_update()
was reorganized into a single function.
- Added more 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
block I/O.

Password management and caching is done through the "Kernel Key
Retention Service" mechanism and the sysfs filesystem. The Key Retention
Service is used for (1) unlocking the card, (2) assigning a password to
an unlocked card and
(3) change a card's password. To remove the password and check
locked/unlocked status, a new sysfs attribute was added to the MMC driver.

A sample text-mode reference UI written in shell script (using the
keyctl command from the keyutils package), can be found at:

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


TODO:

- 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.

- Currently, some host drivers assume the block length will always be a
power of 2. This is not true for the MMC_LOCK_UNLOCK command, which is a
block command that accepts arbitratry block lengths. We have made the
necessary changes to the omap.c driver (present on the linux-omap tree),
but the same needs to be done for other hosts' drivers.

Known Issue:

- 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 password.

Observation:

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.

---
Anderson Briglia,
Anderson Lizardo,
Carlos Eduardo Aguiar
Embedded Linux Lab - 10LE
Nokia Institute of Technology - INdT
Manaus - Brazil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/