netdev - Re: RFC: Crypto API User-interface

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100907145127.GA13027@infradead.org>
Date:	Tue, 7 Sep 2010 10:51:27 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Miloslav Trmac <mitr@...hat.com>
Cc:	Herbert Xu <herbert@...dor.hengli.com.au>,
	Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
	netdev@...r.kernel.org
Subject: Re: RFC: Crypto API User-interface

On Tue, Sep 07, 2010 at 10:34:25AM -0400, Miloslav Trmac wrote:
> - Don't use a FD for associated data that is limited to 16? bytes
> 
> - Don't use file descriptors for input data at all, if it makes the interface so complex.

Calling into the kernel for 16 bytes of crypto is a braindead idea to
start with.  To preve3nt idiots like you from abusing it we should
simply limit any userlevel crypto API to:

 a) hardware crypto that is not directly user space accesible
 b) page size or larger data

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html