| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 18 Nov 2006 14:18:09 -0800 From: David Brownell <david-b@...bell.net> To: Pierre Ossman <drzeus-list@...eus.cx> Cc: Anderson Briglia <anderson.briglia@...t.org.br>, "Linux-omap-open-source@...ux.omap.com" <linux-omap-open-source@...ux.omap.com>, linux-kernel@...r.kernel.org, Russell King <rmk+lkml@....linux.org.uk>, Tony Lindgren <tony@...mide.com>, "Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@...t.org.br>, "Biris Ilias (EXT-INdT/Manaus)" <Ilias.Biris@...t.org.br> Subject: Re: [patch 0/6] [RFC] Add MMC Password Protection (lock/unlock) support V6 On Saturday 18 November 2006 1:42 pm, Pierre Ossman wrote: > 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. The kernel shouldn't hash, right. But the userspace toos probably should be doing that ... they're the other part of the infrastructure. :) - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists