3 ms·
It does until you try to tcpdump :/ 1) It's not TCP 2) It's a PITA on a 'trusted' network because there is not "encryption off" mode
by exabrial 4y ago
It does until you try to tcpdump :/
1) It's not TCP
2) It's a PITA on a 'trusted' network because there is not "encryption off" mode
- olodus 4y agoThose are very solvable problems. I work with non-TCP traffic in pcaps very often and while I agree encrypted traffic is annoying to deal with sometimes because of the extra step it can be solved with good tooling.
- zamadatix 4y agotcpdump works fine with it, and any other ethernet or IP based protocol despite the commands name, it's just 2) that's a problem (for certain perspectives of what is a problem).
- erik_seaberg 4y agoAs long as governments attack networks with impunity, it’s a mistake to trust them.
- shawnz 4y agoSee this well-known slide from the PRISM leaks as a reminder of this: https://upload.wikimedia.org/wikipedia/commons/f/f2/NSA_Muscular_Google_Cloud.jpg https://upload.wikimedia.org/wikipedia/commons/f/f2/NSA_Musc...
- KaiserPro 4y agoIts a question of choosing when and how you encrypt. For internal datacentre traffic, it depends on the value of the data. But you will need to do application level encryption. For links between datacentres, encrypting links based on rules is a sensible and not horrifically challenging thing to do. If you're big enough to have to worry about the volume of encrypted traffic, then you have rules based bandwidth priorities. for virtually everyone else, just use wireguard or some other VPN with encryption.