Announcement

Collapse
No announcement yet.

KRACK wi-fi vulnerability patch?

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

    KRACK wi-fi vulnerability patch?

    Is the Z-Net's wif-fi vulnerable to a WPA2 "KRACK attack", and is there a patch to update and fix any vulnerability?

    #2
    Ubuntu has updated it's stuff. Checked on the RPi forums and looks (Wheezy, Jessie and Stretch) to be updated.

    SSH to your ZNet then

    sudo apt-get update && sudo apt-get dist-upgrade -y
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

    Comment


      #3
      Raspbian releases 8 & 9 (jessie & stretch) are out; I updated one of each this AM. Doesn't look like release 7 (wheezy) is patched.

      https://raspberrypi.stackexchange.co...2-krack-attack

      https://security-tracker.debian.org/...CVE-2017-13086

      Comment


        #4
        Originally posted by Walnut2000 View Post
        Is the Z-Net's wif-fi vulnerable to a WPA2 "KRACK attack", and is there a patch to update and fix any vulnerability?
        You can confirm by SSHing into the Znet and run:

        apt search wpasupplicant

        Should be:
        wpasupplicant/oldstable,now 2.3-1+deb8u5 armhf [installed]

        Z

        Comment


          #5
          Originally posted by Pete View Post
          Ubuntu has updated it's stuff. Checked on the RPi forums and looks (Wheezy, Jessie and Stretch) to be updated.

          SSH to your ZNet then

          sudo apt-get update && sudo apt-get dist-upgrade -y
          Never had upgraded my znet, tried that and now z-wave doesn't load

          Warning Z-Wave Interface ZNET (Node 1) on Network CEBA9CCD FAILED initialization with the message: Failed to connect to interface at 192.168.1.109, will keep trying.



          Code:
          Unable to determine hardware version. I see: Hardware   : BCM2835
          ,
           - expecting BCM2708 or BCM2709.
          If this is a genuine Raspberry Pi then please report this
          to projects@drogon.net. If this is not a Raspberry Pi then you
          are on your own as wiringPi is designed to support the
          Raspberry Pi ONLY.

          Comment


            #6
            Originally posted by vasrc View Post
            You can confirm by SSHing into the Znet and run:

            apt search wpasupplicant

            Should be:
            wpasupplicant/oldstable,now 2.3-1+deb8u5 armhf [installed]

            Z
            Thanks for the info vasrc & Pete

            Mine shows: wpasupplicant/stable,now 2.3-1+deb8u3 armhf [installed]

            So I guess that means I'm a couple of updates behind where I need to be, on u3 rather than u5, but I'll wait until macrho's update is working before I start tinkering.

            Comment


              #7
              Originally posted by macrho View Post
              Never had upgraded my znet, tried that and now z-wave doesn't load

              Warning Z-Wave Interface ZNET (Node 1) on Network CEBA9CCD FAILED initialization with the message: Failed to connect to interface at 192.168.1.109, will keep trying.



              Code:
              Unable to determine hardware version. I see: Hardware   : BCM2835
              ,
               - expecting BCM2708 or BCM2709.
              If this is a genuine Raspberry Pi then please report this
              to projects@drogon.net. If this is not a Raspberry Pi then you
              are on your own as wiringPi is designed to support the
              Raspberry Pi ONLY.
              Looks like the kernal module spi-bcm2708 was replaced with it's updated spi-bcm2835 module? (Broadcom GPIO chip that interfaces with the Zwave module.). Might be due to using dist-upgrade vs upgrade. dist-upgrade removes and installs whatever it needs, upgrade only does version upgrades.

              What version of pi OS are you running?
              cat /etc/debian_version
              Also, what does this return with:
              fgrep Hardware /proc/cpuinfo | head -1 | awk '{ print $3 }'
              Should be BCM2708 or BCM2709?

              I'm assuming you don't have a backup of the SD card.

              Z

              Comment


                #8
                Originally posted by vasrc View Post
                Looks like the kernal module spi-bcm2708 was replaced with it's updated spi-bcm2835 module? (Broadcom GPIO chip that interfaces with the Zwave module.). Might be due to using dist-upgrade vs upgrade. dist-upgrade removes and installs whatever it needs, upgrade only does version upgrades.

                What version of pi OS are you running?
                cat /etc/debian_version
                Also, what does this return with:
                fgrep Hardware /proc/cpuinfo | head -1 | awk '{ print $3 }'
                Should be BCM2708 or BCM2709?

                I'm assuming you don't have a backup of the SD card.

                Z
                cat /etc/debian_version returns 8.0
                The fgrep returns BCM2835
                Correct, I don't have a backup of the SD card

                Comment


                  #9
                  Apologies....try doing a

                  sudo upgrade and see if that brings it back...
                  - Pete

                  Auto mator
                  Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                  Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                  HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                  HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                  HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                  X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                  Comment


                    #10
                    Originally posted by Pete View Post
                    Apologies....try doing a

                    sudo upgrade and see if that brings it back...
                    tried:
                    Code:
                    pi@Z-Net:~ $ sudo upgrade
                    sudo: upgrade: command not found
                    pi@Z-Net:~ $ sudo apt-get upgrade
                    Reading package lists... Done
                    Building dependency tree
                    Reading state information... Done
                    Calculating upgrade... Done
                    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

                    Comment


                      #11
                      Originally posted by macrho View Post
                      cat /etc/debian_version returns 8.0
                      The fgrep returns BCM2835
                      Correct, I don't have a backup of the SD card
                      So you're on the newer Jessie Znet and it does look like it's reporting BCM2835 which wiringPi doesn't support (hence your error msg). I don't see any update of wiringPi what supports the newer kernal module (the fgrep code came from the wiringPi github install script).

                      It's:
                      sudo apt-get upgrade

                      Hopefully that will fix things, but I suspect it will try to update the new modules instead. I don't see wiringPi anywhere, so it must be in the kernal, so I'm not sure how that's remedied. Hopefully there's someone more familiar with removing/reinstalling modules reading..

                      Worse case, HS (or some user) can send you an SD copy.

                      This is of course assuming I'm correct on the reason. YMMV

                      Z

                      Comment


                        #12
                        Originally posted by vasrc View Post
                        So you're on the newer Jessie Znet and it does look like it's reporting BCM2835 which wiringPi doesn't support (hence your error msg). I don't see any update of wiringPi what supports the newer kernal module (the fgrep code came from the wiringPi github install script).

                        It's:
                        sudo apt-get upgrade

                        Hopefully that will fix things, but I suspect it will try to update the new modules instead. I don't see wiringPi anywhere, so it must be in the kernal, so I'm not sure how that's remedied. Hopefully there's someone more familiar with removing/reinstalling modules reading..

                        Worse case, HS (or some user) can send you an SD copy.

                        This is of course assuming I'm correct on the reason. YMMV

                        Z
                        Looks like I'm probably hosed (which I think is up 2 threads above)
                        Code:
                        pi@Z-Net:~ $ sudo apt-get upgrade
                        [sudo] password for pi:
                        Reading package lists... Done
                        Building dependency tree
                        Reading state information... Done
                        Calculating upgrade... Done
                        0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                        pi@Z-Net:~ $
                        I did see that there is a way to rollback a firmware on rpi, but am not sure what the previous release was.

                        Is there anyway to restore my z-wave network to one of the usb homesteer z-wave devices (which I have one)

                        Comment


                          #13
                          You might try

                          sudo apt-get install wiringpi

                          or

                          sudo apt-get install wiringPi

                          (not sure of the case)

                          In case the znet build doesn't have wiringPi package properly installed.

                          Comment


                            #14
                            Your Z nodes will remain on the ZNet GPIO card. You can plug in your USB stick, clear it and write your ZWave network to it if post #13 doesn't work.
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                            HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                            HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                            HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                            Comment


                              #15
                              Originally posted by Pete View Post
                              Your Z nodes will remain on the ZNet GPIO card. You can plug in your USB stick, clear it and write your ZWave network to it if post #13 doesn't work.
                              Post #13 didn't work, I do have a USB stick but am unclear on how to write my ZWave network to it?

                              Comment

                              Working...
                              X