3 ms·
Some good, some pretty questionable practices. >Disable Service Set Identifier (SSID) broadcast Can easily be found anyway >Schedule routine reboots to clear
by Hikikomori 2y ago
Some good, some pretty questionable practices.
>Disable Service Set Identifier (SSID) broadcast
Can easily be found anyway
>Schedule routine reboots to clear the system memory and refresh all connections. Rebooting the router may disrupt any potential malware that may have been implanted.
Idk about that.
- helloooooooo 2y agoIf they are read only file systems it will disrupt any malware on the router. I’ve reversed routers whose file system only allows signed executables, and update packages. It’s good practice. I give the same advice to people and their phones, reboot regularly.
- Hikikomori 2y agoThen it will get infected again pretty much right away no?
- kurikuri 2y agoUnless the infector retargets the same router (i.e., the payload has to be redelivered), then no it won’t.
- lynndotpy 2y agoI think these are good recommendations. "Threat actors" in the vicinity include, say, people who have the Instagram on their phone. It can read SSIDs but can't put the networking hardware into promiscuous mode. Regularly rebooting probably isn't worth the pain, but not all compromises are persistent / rootkits.
- HeatrayEnjoyer 2y agoWhy would Instagram be able to see an SSID?
- lynndotpy 2y agoPermissions to manage network information. Apps on Android (and I believe iOS, but I'm not 100% certain) with network permissions can see broadcast SSIDs. These are often used alongside geolocation; we used to call this wardriving: https://en.wikipedia.org/Wardriving https://en.wikipedia.org/Wardriving Google also does this, and allows you to opt-out of collection from clients if you include "_nomap" at the end of your SSID: https://support.google.com/maps/answer/1725632 https://support.google.com/maps/answer/1725632