Announcement

Collapse
No announcement yet.

Linux Preparing To Disable Drivers For Microsoft's RNDIS Protocol

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux Preparing To Disable Drivers For Microsoft's RNDIS Protocol

    Phoronix: Linux Preparing To Disable Drivers For Microsoft's RNDIS Protocol

    With the next Linux kernel cycle we could see upstream disable their driver support for Microsoft's Remote Network Driver Interface Specification (RNDIS) protocol due to security concerns...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Doesn't android use RNDIS for USB tethering? IMO this is the main reason why USB tethering doesn' work with macOS.

    Comment


    • #3
      This is going to prevent the use of many USB modems and tethering from the overwhelmingly vast majority of Android phones.

      As it stands, currently the only phones that don't use RNDIS and instead use CDC NCM are the Pixel 6 and 7 lines of phones.
      Android hasn't "had this disabled for many years", there are "real systems" that rely on RNDIS: it's over 99% of Android devices.
      It's still the protocol chosen by vendors as it's the lowest common denominator. The Android developers haven't made any moves to remove or revise supported configurations so devices that are launching with Android 14 can still only implement RNDIS.

      My question is still the same as when the patch first hit the mailing list, what vulnerability is there that is so catastrophic the only solution is to slowly remove support for it while the ones still implementing it are left in the dark.
      Is it not possible to add the ability to not initialize the driver and USB interface if the device has not been trusted for that session? If it's going to be drummed on about untrusted devices being a vulnerability then why does the USB subsystem automatically trust them.

      And there still has been no response to the issues or questions brought up by the sole person that NACKed the patch, the Google network developer. If it's going to be forced through anyway then why were the incorrect statements not removed or revised.

      In the end distributions are still going to be building kernels with it, as plenty of users rely on it as the sole method of internet connection.

      Comment


      • #4
        "This is going to prevent the use of many USB modems and tethering from the overwhelmingly vast majority of Android phones."

        Based on the following, quoted in the article, I would say no.
        ​
        "Greg Kroah-Hartman on Monday created the usb.git rndis-removal branch where he is disabling all the RNDIS protocol drivers.
        .....
        'Android has had this disabled for many years so there should not be any real systems that still need this.'"

        ​

        Comment


        • #5
          Originally posted by toves View Post
          "This is going to prevent the use of many USB modems and tethering from the overwhelmingly vast majority of Android phones."

          Based on the following, quoted in the article, I would say no.
          ​
          "Greg Kroah-Hartman on Monday created the usb.git rndis-removal branch where he is disabling all the RNDIS protocol drivers.
          .....
          'Android has had this disabled for many years so there should not be any real systems that still need this.'"

          ​
          Doesn't mean vendors aren't enabling it on their releases.

          Comment


          • #6
            Isn't it up to we the people to decide to use it or not? What if we're not using it in an environment with untrusted devices?

            Comment


            • #7
              Well, Android or their distributors can always distropatch the support in as needed. But that makes clear that they are those with the obligation to support that.
              If something is not supported or maintained in the kernel, it should not be in the kernel.

              Comment


              • #8
                Originally posted by Amano View Post
                Well, Android or their distributors can always distropatch the support in as needed. But that makes clear that they are those with the obligation to support that.
                If something is not supported or maintained in the kernel, it should not be in the kernel.
                You need rndis on both Android and the Linux PC for tethering to be successful. Android handset distributors patching rndis into their kernels does jack.

                Let's see your reaction when your Android phone will no longer tether to your Linux PC because rndis is removed from the kernel.

                Comment


                • #9
                  ... waiting for a rust or microsoft developer to post, "So buy a new phone."

                  Comment


                  • #10
                    Uh, what? I don't like it but I haven't seen a phone that doesn't use this for tethering. I don't need another thing I need to patch into my kernel.

                    Comment

                    Working...
                    X