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 X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id ABDFDC433DF for ; Sat, 23 May 2020 00:36:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7F4EA20735 for ; Sat, 23 May 2020 00:36:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="QCiD9k5K" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387461AbgEWAf7 (ORCPT ); Fri, 22 May 2020 20:35:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35366 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387456AbgEWAf7 (ORCPT ); Fri, 22 May 2020 20:35:59 -0400 Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 09DB4C061A0E for ; Fri, 22 May 2020 17:35:59 -0700 (PDT) Received: by mail-vs1-xe29.google.com with SMTP id t4so5124218vsq.0 for ; Fri, 22 May 2020 17:35:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QcO/ucQVMvQiApRZiTPxDNZkiNYiWG9EVqH96FDN/fo=; b=QCiD9k5KRoyWpcx5xQtw19B6CixFXzUtnca8lXUQsHL7mLRDcB/YIjY7O+zO8Klvxb F/7mAjh1bt/MJ+EtlcMu63VsjQ6S53xXmT9PTzifnvVZrhbvYuIJ81qPb8u5/1UnH8gH z8VM8rOVVH9tVMWmgp2GTIKQJjOBDlhMzTvktmDKIGBi3GyKDIiOnb67jQYB+r1sEwJp kenKGvtmbHvESeWUQnoenvcpAbZ8eyc/RyVinF+tMUaAXXyNSuq5WMtEzgMzenKHOMMx v2gYeCpwNGPiQW64own8/qtXHAeiklqEoRQH2V8XlAfO4UMcURadVwBQZ8VZUHOzw7q7 7MpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QcO/ucQVMvQiApRZiTPxDNZkiNYiWG9EVqH96FDN/fo=; b=PByGnp2Nl242tAiQ1j6z5vTLk14PHFe+PfS8hDQmDG7XjYCL78Q7Exwn4Q1HBF4r0z TiQsMsjfFyBWW25qUsTD5AjwIPw2v5NohDXhzF1OMz4rheF24mu2UhXQIapIeaGXX1qt RbfVZoRFSUb6g+sPc/sf/RWIraDo15mt3VEDTWg9U8T0K2bAesZtOL7IbNt1Ku7qtzf5 VOKbZ/cZCr54liapVWzc7VK2rw05ico4WOMkXO6/cgW4O6VQbBDlyUtGXFIYYvXRY3PQ Yeea4llCWEwF73o+zIUZOHbzu0REltjWF4uc/CIWAZ+s3XAgK1VCWi3hm8xn5oSlpm3z Rt6A== X-Gm-Message-State: AOAM533XfTVrSfvG3vq6UNkkdXSVoxx1GbsU011l+MufCm+LfDKjyALM lTdir2NjWoTrdbJwGdiLnXA9W3PQ/kwgRYvagw== X-Google-Smtp-Source: ABdhPJwTH+diMEXL1RcLUiBszUmg9uYllw6e+FW/b19An5Fjfm0klwoRMxhtxNBMdwlWrW2rQq+fkWhDB5C/ZlmRtMY= X-Received: by 2002:a67:6dc7:: with SMTP id i190mr12248325vsc.75.1590194157927; Fri, 22 May 2020 17:35:57 -0700 (PDT) MIME-Version: 1.0 References: <20200521124608.4b5c78f2@wiggum> <20200521134011.656381ad@wiggum> <2b22b778-2f89-9c42-93a0-5c165de26f35@lwfinger.net> <20200522121910.254aefc1@wiggum> <87a720gpfb.fsf@tynnyri.adurom.net> <8252e6a1-b83c-64eb-2503-2686374216ae@lwfinger.net> In-Reply-To: <8252e6a1-b83c-64eb-2503-2686374216ae@lwfinger.net> From: Rui Salvaterra Date: Sat, 23 May 2020 01:35:46 +0100 Message-ID: Subject: Re: [BUG?] b43: can't connect to WPA3 network (nohwcrypt=1) To: Larry Finger Cc: Kalle Valo , =?UTF-8?Q?Michael_B=C3=BCsch?= , linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 22 May 2020 at 22:06, Larry Finger wrote: > > It will do supported ciphers in hardware, and unsupported using software. The > patch tells mac80211 that we will accept the newer ciphers, then in the > set_key() callback, we tell it whether the current type will be handled in > hardware. Operations will be transparent. I will keep the nohwcrypt option just > in case someone has a hardware malfunction that prohibits hardware use for all > ciphers, but it will not be needed in cases like yours. Performance will be as > you did earlier. Wonderful, I didn't know mac80211 was that smart. But I have even better news (and it would be great if someone else could verify this): with your unconditional enablement of MFP, the CPU overhead of WPA3 is on par with WPA2, I believe it's doing hardware crypto. And it makes sense when you think of it, WPA3 Personal uses the same AES cypher as WPA2, but with SAE handshake, if I'm not mistaken. > Thanks for testing. My pleasure! Rui