Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp440008ybv; Thu, 13 Feb 2020 03:26:44 -0800 (PST) X-Google-Smtp-Source: APXvYqzvwlaXYIYnjsSGR6bZk0fF0n7x0DAd2tTupgGnaMhky3Jml9HoGVl9OFYaZ4eMBELUVK3s X-Received: by 2002:aca:4c11:: with SMTP id z17mr2454413oia.104.1581593204619; Thu, 13 Feb 2020 03:26:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581593204; cv=none; d=google.com; s=arc-20160816; b=J4bbunQ/PXxXD/xJQRFrF/Y8L2tLCpvwHCRrdO6fVYYf3zFShCMu76l64qJchgI1jb VxZ5Ge1TYk5J5xqDXxRtijxyvkUgKuQlpCJ8UMbBjhuqFzdr2aa5a+suBvqDLbXSkfHG i26ady+wWuUFfIapNme6rZYYS4ejPaZVfaW/MayZSpCrdTfAQER2duPZlEXs99/L4MLN jiAbJkZe+bAtpJkSj00u6veVLYYc6xATrqtSZp14wOBg3a0l5/hlbBnl5JStrig9D2SJ nDh+0gK3VidXyQHzAJT+qtWLCBsygHjr6rz73lXfOU/fn+izPt4Hrra9BD1ux/ppC8sh ux4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=piuy77cyYc3Hbg/uCzQqaNjTcZ8dyHvY5qrHYfnNjAE=; b=DS0rA9C0gPsa5152puny1etHCpP686tzaTduqDyvRGNW8jhZjE+EWUp6Bz3emMCIGb aYCHy2yEZt6ue1IjyuDPMX9iQz5A7peSN4d5OoTuB7OE/uKHSBkKUxeb6wGc8LaJf2Lc ngAQZPRMvg2XHH6IyUkYDaz6pXGGFBjhvKjT9PO5QA40tYViY45pglKTa0DZ4w4lwv+P ZUUz5ltxntaucdXuDGVqrEeX2yVOe7J+Um0WLwd4uDv5EdeemhQOhNvRp2e8NfwRxuyX B5Mm66Y4cDko+49NXRj/Btw6Pi2svCUJ5yzpEwbPyt2nuinLuKrVBA82mm8PzDCml+k4 mPMw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p5si1019565oto.116.2020.02.13.03.26.32; Thu, 13 Feb 2020 03:26:44 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729544AbgBML00 (ORCPT + 99 others); Thu, 13 Feb 2020 06:26:26 -0500 Received: from s3.sipsolutions.net ([144.76.43.62]:33500 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726232AbgBML00 (ORCPT ); Thu, 13 Feb 2020 06:26:26 -0500 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) (envelope-from ) id 1j2CdU-008XIs-Hf; Thu, 13 Feb 2020 12:26:24 +0100 Message-ID: <98f7590498a7173e933f70c85208735a13f51792.camel@sipsolutions.net> Subject: Re: [RFC PATCH 1/2] cfg80211: skip strict validation for UDPATE_OWE command From: Johannes Berg To: Sergey Matyukevich Cc: "linux-wireless@vger.kernel.org" Date: Thu, 13 Feb 2020 12:26:23 +0100 In-Reply-To: <20200213112123.elwoei3nnk5mzkht@bars> References: <20200213090657.28841-1-sergey.matyukevich.os@quantenna.com> <20200213090657.28841-2-sergey.matyukevich.os@quantenna.com> <703b19463655cbb8a5ab9469caec5d3936dbe35d.camel@sipsolutions.net> <20200213111300.jgb3kkvwq6am3aj7@bars> <47ba092892a3762f42cac6f69a80622829e84827.camel@sipsolutions.net> <20200213112123.elwoei3nnk5mzkht@bars> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Thu, 2020-02-13 at 11:21 +0000, Sergey Matyukevich wrote: > > > > > Sure, I can fix hostapd instead. Could you point me at some good > > > starting point to look at ? Are there any user-space tools that > > > started to use strict validation ? > > > > It's not really opt-in or not, it's entirely a kernel choice. > > I mean, I don't know what userspace is supposed to do in the case, > when kernel is doing strict validation. So I was asking about any > pointers to docs or userspace tools that already do netlink > machinery appropriately. Userspace is just supposed to create well-formed messages :-) But ... it really is a kernel bug. The nl80211_policy is missing an entry for NL80211_ATTR_STATUS_CODE, so for *strict* commands, it's assumed to not be supported. Need to add something like [NL80211_ATTR_STATUS_CODE] = { .type = NLA_U16, }, to the nl80211_policy, or perhaps with a range indicating that 0 isn't valid or something. johannes