From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Ossman Subject: Re: [patch 0/6] [RFC] Add MMC Password Protection (lock/unlock) support V6 Date: Sat, 18 Nov 2006 22:42:02 +0100 Message-ID: <455F7E2A.60009@drzeus.cx> References: <455DB1FB.1060403@indt.org.br> <200611181117.54242.david-b@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200611181117.54242.david-b@pacbell.net> Sender: linux-kernel-owner@vger.kernel.org To: David Brownell Cc: Anderson Briglia , "Linux-omap-open-source@linux.omap.com" , linux-kernel@vger.kernel.org, Russell King , Tony Lindgren , "Aguiar Carlos (EXT-INdT/Manaus)" , "Biris Ilias (EXT-INdT/Manaus)" List-Id: linux-omap@vger.kernel.org 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. Rgds -- -- Pierre Ossman Linux kernel, MMC maintainer http://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org