First episode of my IoT podcast. This month is about IoT maket study and how numbers can be bullshit when comes from certain analyst. We also talk about the LoRaWan world distance record.
This first episode is a test, a poor and a bit dirty (or too long) episode for testing podcast concept on my blog. It is going to be a monthly rendez-vous on IoT and especially LPWAn news.
Podcast: Play in new window | Download
Podcast (iot-decoded-fr): Play in new window | Download
The usual attack on Sigfox network is related to the “security”. Behind this large concept, for real, the only point is related to the use of clear payload over the air. As a consequence some are extending this to the possible replay after 2048 frames so regarding a standard use of Sigfox is will be about 6 month later…
That said, for real, all of this is just ignorance from these pseudo “security” experts and developer laziness. Don’t beat me for saying that, I’m part of the lazy developer, the only difference is I’m not complaining and I’m aware the solution is in my own hands.
Because, for real, the payload encryption exists as documented in the post I’ve published on May 2017 and detailed on the Feb 2017 technical security paper published by Sigfox or like in this document.
So saying the Sigfox is not proposing payload encryption is wrong and this option is also fixing any 6 months later message replay. It’s like saying WiFi is not secured because you can create an open-network.
So now, let’s see why encryption is not the default option, why a network encryption standard is not the best option and then see how to stop to be a lazy developer and make encryption working.
As I written this post for another target and it can be also useful for anyone, even if It is one more post on many of them, here are a couple of words about Meltdown and Spectre security issues. Read mode for details.
A short post to save some of the useful options for firewall-cmd:
Ghost security hole is impacting glibc under 2.18 at least. If you want to know what is your version of glibc you can type :
# ldd --version
Un nouvel outil permettant l’attaque de résaux wifi protégés par WPS est sorti. Son petit nom est reaver. Il permet de tester différentes clefs sous la forme d’une attaque de type brute force. La methode employé permet de résoudre cette attaque en un maximum de 11.000 tests, ce qui est très peu.