2 ms·
It isn't really secure... Because an attacker on the network can see which port you're about to connect to, and which IP you're connecting from, and connect t
by londons_explore 5y ago
It isn't really secure... Because an attacker on the network can see which port you're about to connect to, and which IP you're connecting from, and connect to the target milliseconds before you do.
I prefer to keep the word 'secure' for things that provide at least man-in-the-middle protection, which this approach doesn't.
- airhead969 5y agoSingle Packet Authorization doesn't claim to do anything about encryption, authentication, integrity, auditing, or anything else. Leave ambiguous terminology hair-splitting at the door and get to specifics. It's securing the keyhole of the padlock. No sense moving the padlock around when it can be closed to begin-with, and opened with a special knock that is extremely complicated: time, service, and identifies which user. Port knocking on top of VPN, SSL, SSH, Wireguard, or whatever. You don't do this with telnet because common sense. Duh!