From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0488E1AAD4; Wed, 13 Mar 2024 08:57:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710320236; cv=none; b=FdKTjixzT4uQtnzwzaZFzePfb/kFoXpI5aOaIyPABAtyjT93SHnvm9UZO4h8PICsTlXQt8x/QiBjfiA1sM4glkjim+ICEBC9a7JhfTRXL65wps7MunBVvzVjP7Gl+t+DzrlX9WJJjA05PCrPq9ewTDtohnC47huvJsMTBMpmlRQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710320236; c=relaxed/simple; bh=qMFjOw5oWXHTNwfAIdt5NPZlOtPArHhvm1xObO8VH44=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=VpA+nCygPwfzXAVsONPwYhfuI6A5xuUxxMlIal/EriqTked0hPgYP9zF4qMVZMREL6k1Omz2WmMwmCqEGYV/s/hmZ+o0EarfxaX5pf1KG+rtPY6AZH+PF+2Ze+vBRobItYlj3Gnk6QgEQC/BUeKKzaYXSDhDiTv6FOFCxILcQEI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=Ab3VxTqE; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="Ab3VxTqE" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=7Z3xpgxMC3SabrhTXAHSyPXqOmddBGRm2jLKIlBKce0=; t=1710320234; x=1711529834; b=Ab3VxTqE9GZ/mGpgNWdO20gXFpnG8sqFCd4Dfl1/7f8lbDF IevLjr0RN7NoCLrp8O7XfRLjtbLQ6F54xkWZd51cIvoQGdPLjR4P1Z1fhdf4AxOzWLm3J2OCdZLPm tMOlP10dZt3Bmfwy2gnLtHHUO4+vI+sRrTegBw8rpcQSA7LCT/BVRzySJynIKnuRavwXJ0XOVE1v/ rJuBY3nVDIVURI0HntM5cr74WFg4Cm1wTuO5MqMdY1BC44CYOPU4RnM19fsb/mQtl59/jgbFuwcI8 BBiJapuJt54Jpdq1hihdCAd5WYpKdG1aRhAl2UoPbxFzguk9N5ZBMifA4g42F8+w==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97) (envelope-from ) id 1rkKPv-0000000F7E9-0rbB; Wed, 13 Mar 2024 09:56:55 +0100 Message-ID: <005f998ec59e27633b1b99fdf929e40ccfd401c1.camel@sipsolutions.net> Subject: Re: [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support From: Johannes Berg To: Karel Balej , dimitri.ledkov@canonical.com Cc: alexandre.torgue@foss.st.com, davem@davemloft.net, dhowells@redhat.com, herbert@gondor.apana.org.au, keyrings@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, mcgrof@kernel.org, mcoquelin.stm32@gmail.com, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, iwd@lists.linux.dev Date: Wed, 13 Mar 2024 09:56:53 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.4 (3.50.4-1.fc39) Precedence: bulk X-Mailing-List: iwd@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned Not sure why you're CC'ing the world, but I guess adding a few more doesn't hurt ... On Wed, 2024-03-13 at 09:50 +0100, Karel Balej wrote: >=20 > and I use iwd This is your problem, the wireless stack in the kernel doesn't use any kernel crypto code for 802.1X. I suppose iwd wants to use the kernel infrastructure but has no fallbacks to other implementations. johannes From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0733EC54791 for ; Wed, 13 Mar 2024 08:57:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Date:Cc:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=nEPnhJo5mu+ObLNFfNvLOCydxLF8xZF4iqiGqoIasAk=; b=UBEVkOfukx1U0g +0RSzXSM8K8jAKEYiBMgtluISi46+6y//VZIc2CV+ZI2KVo9LBGp9bqQqBQuC8kewKNI5QoIqLlGS 5eYB5nRJg2j+4roOTXlYShAhT67wzCHNDrqYwT5KscEsrAj44efjYCe/hXCo8LO6vFWaxCbaLDGOh wATJUIwvnmQgRGYqqSkAvt26Q/kKWeEMTlE2lcKoK3rk+WLApAAHma7ltjjgNhFNojCx++HWsrLK4 eipHKUhbBehvSUcHmV2bherl02Ty7YMj/TXTwhxgqhcuR/dDHLOtSBam6dnljWEeM+NzqS2tImA9M wqndDfafIjz9zAIjVkXg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rkKQ9-00000009OfM-1mA6; Wed, 13 Mar 2024 08:57:09 +0000 Received: from s3.sipsolutions.net ([2a01:4f8:242:246e::2] helo=sipsolutions.net) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rkKQ6-00000009OdM-2BPe for linux-arm-kernel@lists.infradead.org; Wed, 13 Mar 2024 08:57:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=7Z3xpgxMC3SabrhTXAHSyPXqOmddBGRm2jLKIlBKce0=; t=1710320223; x=1711529823; b=FNf/VDbKPBXp43d3fF/M/Aj7nkLKJhCwWCEiZNibST/MR3a PhZPQq5/O2/PMpS/RbvdRfC8rmPwl1KYU0iEzB4nClCU7MOC6jH6HgpdrT6lyUbatxWPQ7pgfx4Sk 227i7QiCbWcMvlAOizlpcjcQUwT4kfMAE9soit0FGcRGqNHMVHqsM+EMIZD/XLtKJIClTc5qrowx9 c9j8CcdvLseEEHd33tlIk5OBeB9Vckm7w2xqJuG/UA0o1yxqjZz4SykaTNHso/aPvpWnjfedbsJ4p c5YJl/uo1F7aH7dBvqG19VFGmh7M11c+/XHfs6WN3xzDW18kwNq2DO6FZbUMT/AA==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97) (envelope-from ) id 1rkKPv-0000000F7E9-0rbB; Wed, 13 Mar 2024 09:56:55 +0100 Message-ID: <005f998ec59e27633b1b99fdf929e40ccfd401c1.camel@sipsolutions.net> Subject: Re: [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support From: Johannes Berg To: Karel Balej , dimitri.ledkov@canonical.com Cc: alexandre.torgue@foss.st.com, davem@davemloft.net, dhowells@redhat.com, herbert@gondor.apana.org.au, keyrings@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, mcgrof@kernel.org, mcoquelin.stm32@gmail.com, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, iwd@lists.linux.dev Date: Wed, 13 Mar 2024 09:56:53 +0100 In-Reply-To: References: User-Agent: Evolution 3.50.4 (3.50.4-1.fc39) MIME-Version: 1.0 X-malware-bazaar: not-scanned X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240313_015707_115437_B3432BA5 X-CRM114-Status: UNSURE ( 7.78 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Not sure why you're CC'ing the world, but I guess adding a few more doesn't hurt ... On Wed, 2024-03-13 at 09:50 +0100, Karel Balej wrote: > > and I use iwd This is your problem, the wireless stack in the kernel doesn't use any kernel crypto code for 802.1X. I suppose iwd wants to use the kernel infrastructure but has no fallbacks to other implementations. johannes _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel