From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Mueller Subject: Re: [PATCH v2 0/5] crypto: add algif_akcipher user space API Date: Wed, 28 Oct 2015 11:12:05 +0100 Message-ID: <3674514.AfR75N8aU6@tauon.atsec.com> References: <1831785.BBs8Hj3CxY@myon.chronox.de> <4777180.cceLVNSOUa@myon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Marcel Holtmann Cc: David Woodhouse , Herbert Xu , linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, David Howells List-Id: linux-api@vger.kernel.org Am Mittwoch, 28. Oktober 2015, 11:56:59 schrieb Marcel Holtmann: Hi Marcel, >> >> With all due respect, I would object here. When we say yes to TLS (even if >> it is parts of TLS up to the point where the KDF happens), we invite all >> higher level crypto implementations: IKE, SNMP, SSH -- I would not want to >> go down that path that started by simply supporting accelerated asymmetric >> ciphers. >Reality is that TLS in the kernel is happening. Reality is also that we do This is simply wrong IMHO for anything beyond the key handling. But that is not the topic here, I guess. Ciao Stephan From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965466AbbJ1KMN (ORCPT ); Wed, 28 Oct 2015 06:12:13 -0400 Received: from mail.eperm.de ([89.247.134.16]:34436 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754871AbbJ1KMK (ORCPT ); Wed, 28 Oct 2015 06:12:10 -0400 From: Stephan Mueller To: Marcel Holtmann Cc: David Woodhouse , Herbert Xu , linux-crypto@vger.kernel.org, linux-kernel , linux-api@vger.kernel.org, David Howells Subject: Re: [PATCH v2 0/5] crypto: add algif_akcipher user space API Date: Wed, 28 Oct 2015 11:12:05 +0100 Message-ID: <3674514.AfR75N8aU6@tauon.atsec.com> User-Agent: KMail/4.14.9 (Linux/4.1.8-200.fc22.x86_64; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1831785.BBs8Hj3CxY@myon.chronox.de> <4777180.cceLVNSOUa@myon.chronox.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, 28. Oktober 2015, 11:56:59 schrieb Marcel Holtmann: Hi Marcel, >> >> With all due respect, I would object here. When we say yes to TLS (even if >> it is parts of TLS up to the point where the KDF happens), we invite all >> higher level crypto implementations: IKE, SNMP, SSH -- I would not want to >> go down that path that started by simply supporting accelerated asymmetric >> ciphers. >Reality is that TLS in the kernel is happening. Reality is also that we do This is simply wrong IMHO for anything beyond the key handling. But that is not the topic here, I guess. Ciao Stephan