Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1511791rwb; Tue, 29 Nov 2022 14:50:46 -0800 (PST) X-Google-Smtp-Source: AA0mqf5otKEdbYVHzZMB/5dt/AvviOSDsKXKlr55fyoXLrQSG40Rv+2XzwzTtMoAlNL7E1O1XSSk X-Received: by 2002:a17:902:ebc1:b0:186:b6aa:5646 with SMTP id p1-20020a170902ebc100b00186b6aa5646mr39284763plg.73.1669762246477; Tue, 29 Nov 2022 14:50:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669762246; cv=none; d=google.com; s=arc-20160816; b=pMLAkxIO7VHy0wDg2ZrMrC+9YcjJoOgQull0HOW7zEaIxrBV6epUWfkRdXTUcVfYo9 z0zolQ0xM8O44kt2F58V/9xEOr8Tm7qY4ZKifcahjYL5VhJm56J3CHb30J+3KaDZKUq2 qm8VTnrLiS3WydRVtjGCpN/ZHt1bkXxdtmmQFqxAwZz1vM0Gr+Om/4mdFBdVRfVNX2Qb d3LROFt9TpfLfGu0DP9Idfuk0MfMuV/2HWRuqNrJh29oCykNxbTcBxhTNeoVlUGmTj5/ qOhsEfws8XakvqpKsoQML7wsHex1xML9dPJeXBwZPY6KfqpEwKQsMMIZ6URQEpYOccFC HHOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=HGikrnX364rCVWywnwVxKwVfVWGtIZ6vltliqWh6T0Y=; b=hboI6S1rj/CQaNmahbYHQI+SorvVSM6NkBmL7MqTKR+9ye6pIZDzMj8oE0bspExYFU j819+r155b0XgnaPfoRVtL1m+YTo90wbeQ0IsOtvQhhrHkOz+pXDN4rUSwV22jhASf9W iMaIBOvvhjwxFP28kBh/9xaTPcQEjdWFcF5cyZXiW8TeRjPz7YMbmEAZspns8S6PRPmJ vLH9ouWtb4Cdj6j1KGa+FWqVH+eDdk1AWxxan2IdnK4YLwvNc+6LXX4jljVFJa5ZB7jS 84VEb5xVgaiwf6Myi4XnzpVdebZG6k+QMyWQaUul+Z7X+TAm/TOqrh1nV3ggtK748S4g ibsw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=e1YIzMNX; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z15-20020a63c04f000000b0043c1cb75c22si15879103pgi.333.2022.11.29.14.50.31; Tue, 29 Nov 2022 14:50:46 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=e1YIzMNX; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236711AbiK2WtQ (ORCPT + 67 others); Tue, 29 Nov 2022 17:49:16 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37634 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236570AbiK2WtP (ORCPT ); Tue, 29 Nov 2022 17:49:15 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CFBA02339E for ; Tue, 29 Nov 2022 14:48:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669762107; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HGikrnX364rCVWywnwVxKwVfVWGtIZ6vltliqWh6T0Y=; b=e1YIzMNX0N/4pfYxwCCeV/8Sy9uz4Bhghmcj+WsVyU0GcwrMg7U4j07rdif43qeesqRGOm rA6BSBkPQ9+t1PZNTVqpczNTukPcmwtVf1GaDLrNnGj18O0712RPiT3Fo7CHbjo6YqaNsr UmGLLTuY8ZKics3WW2lLRSRmwj1yggg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-624-jPivghd9PsO6geSKUF7Vmw-1; Tue, 29 Nov 2022 17:48:19 -0500 X-MC-Unique: jPivghd9PsO6geSKUF7Vmw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id CBC1A84ACA0; Tue, 29 Nov 2022 22:48:12 +0000 (UTC) Received: from localhost.localdomain (unknown [10.22.50.18]) by smtp.corp.redhat.com (Postfix) with ESMTP id BC26F140EBF5; Tue, 29 Nov 2022 22:48:09 +0000 (UTC) Message-ID: <8b11568a8022cdb759a43f34fdcddf33d9abc37c.camel@redhat.com> Subject: Re: [PATCH] USB: disable all RNDIS protocol drivers From: Dan Williams To: Nicolas Cavallari , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Cc: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Kalle Valo , Oleksij Rempel , Maciej =?UTF-8?Q?=C5=BBenczykowski?= , Neil Armstrong , Mauro Carvalho Chehab , Andrzej Pietrasiewicz , Jacopo Mondi , =?UTF-8?Q?=C5=81ukasz?= Stelmach , Laurent Pinchart , linux-usb@vger.kernel.org, netdev@vger.kernel.org, linux-wireless@vger.kernel.org, Ilja Van Sprundel , Joseph Tartaro Date: Tue, 29 Nov 2022 16:48:07 -0600 In-Reply-To: <04ea37cc-d97a-3e00-8a99-135ab38860f2@green-communications.fr> References: <04ea37cc-d97a-3e00-8a99-135ab38860f2@green-communications.fr> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, 2022-11-23 at 16:40 +0100, Nicolas Cavallari wrote: > On 23/11/2022 13:46, Greg Kroah-Hartman wrote: > > The Microsoft RNDIS protocol is, as designed, insecure and > > vulnerable on > > any system that uses it with untrusted hosts or devices.  Because > > the > > protocol is impossible to make secure, just disable all rndis > > drivers to > > prevent anyone from using them again. > > > > Windows only needed this for XP and newer systems, Windows systems > > older > > than that can use the normal USB class protocols instead, which do > > not > > have these problems. > > > > Android has had this disabled for many years so there should not be > > any > > real systems that still need this. > > I kind of disagree here. I have seen plenty of android devices that > only > support rndis for connection sharing, including my android 11 phone > released in Q3 2020. I suspect the qualcomm's BSP still enable it by > default. > > There are also probably cellular dongles that uses rndis by default. > Maybe ask the ModemManager people ? Yes, there are. Another class of WWAN dongles presented as USB RNDIS to the host, had an onboard DHCP server, and "bridged" that (for lack of a better term) to the WWAN. And like a home router exposed HTTP based management on 192.168.1.1 to control the WWAN stuff. https://openwrt.org/docs/guide-user/network/wan/wwan/ethernetoverusb_rndis RE Wifi, (echoing Johannes) there was one Broadcom chipset, but a bunch of devices used it. I have some though I don't actively use them. But they still work... Dan > > I'm also curious if reimplementing it in userspace would solve the > security problem. >