4 ms·
Security-wise, Wi-Fi has always been a steaming heap. And probably always will be.
by bell-cot 3y ago
Security-wise, Wi-Fi has always been a steaming heap. And probably always will be.
- para_parolu 3y agoWhat are better alternatives for wireless connectivity?
- Retr0id 3y agoAlternative is the wrong question, I think. You should* assume the wireless connection itself is compromised and use an extra layer, like wireguard. *Assuming this makes sense within your threat model. It's not something I think I should care about much, personally. Everything important I do goes over https anyway.
- dale_glass 3y agoBut that shouldn't be necessary. WiFi itself should be doing whatever wireguard adds to this setup.
- Retr0id 3y agoIt shouldn't be necessary, yet WiFi continues to show that it is.
- bell-cot 3y agoNot to claim that 99% of users would show any preference for a better standard...but that's pretty much the problem. [Edit: Retr0id is perfectly correct...but even thinking in terms of a threat model has already excluded the 99%, if not more.]
- linuxlizard 3y agoWi-Fi has the same challenges as if someone just tapped an Ethernet cable. (Except the Ethernet line can't be sniffed from the parking lot.) The amount of unsecure traffic on a basic Ethernet network makes Wi-Fi security slightly better.
- pclmulqdq 3y agoI don't think that's exactly true. Ethernet is a pretty simple physical-layer protocol only made for 1:1 connections, and you can't generally inject packets from a simple tap mid-cable. You would have to undetectably insert an active MITM device into the cable to get on the network, which is a lot more tricky to do than an undetectable tap.
- holgerschurig 3y agoWell, that is totally wrong. And I deduct that you're rather young. You think Ethernet is 10BaseT, 100BaseT and similar, i.E. Twisted Pair. But original Ethernet was designed for Coax cable, for 1:many connections. Basically you had one coax cable and run it from computer to computer. At both ends you had a terminator resistor of 50 Ohm. And at the computers you originally had vampire clamps, later T connectors. That was used until for two or maybe even three decades. First only in research, military and university (e.g. where also TCP/IP was originally was used). But later also e.g. for Novell Netware. The Terminator/RG58 cable/Network card with NE2000-clones or 3C359 cards was relatively cheap, so a lot of offices used that with some Novell Netware file server. Ethernet was designed for many clients, the CD in CSMA/CD means collision detection. With only two clients, you could do some handshake, like with RS485. But with many clients, this can become cumbersome or impossible. So Ethernet decided to detect this, and to let the senders re-send the packets after a random back-off time. On the https://en.wikipedia.org/wiki/Ethernet https://en.wikipedia.org/wiki/Ethernet after "Shared Medium" you can see a picture of this entirely not 1:1 equipment :-)
- pclmulqdq 3y agoI have actually read the Ethernet standard almost cover-to-cover, but GP was referring to Ethernet in the common use, not the technically-available options that can be tapped if your building happens to be from the 80's (or is a car). Also, at this point, a lot less of the available "Ethernets" can be tapped than you may be thinking.
- linuxlizard 3y agoAn old hub (not switch) does exactly that: all traffic forwarded down each port and I can see what everyone was doing. Even with a switch, a misbehaving device can cause all sorts of havoc on an Ethernet network. 802.1X is supposed to provide port security but isn't used often. Anyone could plug into a wall port and get access to a corporate network.
- bee_rider 3y agoOf course, the network isn’t trustworthy; giving it encryption related tasks was a bad idea.