Hi all, Someone has comments for these patches?
Best regards, Anderson Briglia Anderson Briglia wrote: > Hi all, > > New in this version: > > - mmc_sysfs.c: "change" and "assign" code merged to avoid code > duplication. > - OMAP specific patch not include on this series. > - mmc_lock_unlock function: now, the host is claimed before > mmc_lock_unlock is called. > - Version according the latest mainline git repository. > > 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. 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: > > http://www.indt.org.br/10le/mmc_pwd/mmc_reference_ui-20060130.tar.bz2 > > > TODO: > > - Ongoing: Extend the MMC PWD Scheme to SD Cards. > > - 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. > > 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. > > > Comments and suggestions are always welcome. > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
