From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Mueller Subject: Re: x509 parsing bug + fuzzing crypto in the userspace Date: Fri, 24 Nov 2017 17:31:35 +0100 Message-ID: <1684405.FoYHGhiAJd@tauon.chronox.de> References: <1838350.iOjUKSrnbm@tauon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Eric Biggers , Alexander Potapenko , linux-crypto@vger.kernel.org, Kostya Serebryany , keyrings@vger.kernel.org, Andrey Konovalov To: Dmitry Vyukov Return-path: Received: from mail.eperm.de ([89.247.134.16]:42488 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753848AbdKXQbh (ORCPT ); Fri, 24 Nov 2017 11:31:37 -0500 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: Am Freitag, 24. November 2017, 17:25:55 CET schrieb Dmitry Vyukov: Hi Dmitry, > Eric also pointed me to grep. But I can't say the code is intuitive. > I've spent way more time than I expected to just get a list of all > algorithms with their types. Say, in some cases algorithm descriptions > do not specify their type, it's somehow plumbed somewhere later. > Getting the list at runtime allowed me to get relevant ones with > proper types. Hehe, getting the list of ciphers in the script I sent the other day took me a long time. Maybe you leave it for now and come back later for a good grepping code to search the sources. Ciao Stephan From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Mueller Date: Fri, 24 Nov 2017 16:31:35 +0000 Subject: Re: x509 parsing bug + fuzzing crypto in the userspace Message-Id: <1684405.FoYHGhiAJd@tauon.chronox.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit List-Id: References: <1838350.iOjUKSrnbm@tauon.chronox.de> In-Reply-To: To: Dmitry Vyukov Cc: Eric Biggers , Alexander Potapenko , linux-crypto@vger.kernel.org, Kostya Serebryany , keyrings@vger.kernel.org, Andrey Konovalov Am Freitag, 24. November 2017, 17:25:55 CET schrieb Dmitry Vyukov: Hi Dmitry, > Eric also pointed me to grep. But I can't say the code is intuitive. > I've spent way more time than I expected to just get a list of all > algorithms with their types. Say, in some cases algorithm descriptions > do not specify their type, it's somehow plumbed somewhere later. > Getting the list at runtime allowed me to get relevant ones with > proper types. Hehe, getting the list of ciphers in the script I sent the other day took me a long time. Maybe you leave it for now and come back later for a good grepping code to search the sources. Ciao Stephan