3 ms·
It seems here that the author has a different definition of security through obscurity to many who criticise it. The important aspect is whether the knowledge
by danpalmer 10y ago
It seems here that the author has a different definition of security through obscurity to many who criticise it.
The important aspect is whether the knowledge required to break the system is the system itself, or the key. AES is not security through obscurity because everyone can look up how it works, and it's only the key that we have to keep secret. Port knocking is the same (just with a weaker key). Moving your SSH to port 24 however is security through obscurity because if anyone knows the mechanics of how you use it, they can use it.
This differentiation is subtle, and can be somewhat of a grey area sometimes, but I find it good at differentiating between the two most of the time.
- kevincox 10y agoCouldn't you argue that the port SSH listens on is a 16 bit key? It's small and easy to brute force (among numerous other ways it is easy to discover) but I don't really see distinction you are trying to make.
- eximius 10y agoAt the information theoretic level, isn't everything? The only thing that makes this more like a 'key' is that there is a simple test for it. More complex configurations of obscurity are not really brute-forceable, just discoverable. That was less clear than I'd have like.
- danpalmer 10y agoYes, this is what I mean by it being a subtle and not always clear difference, but I think it's usually pretty easy to apply common sense to this.
- theandrewbailey 10y ago> Moving your SSH to port 24 however is security through obscurity because if anyone knows the mechanics of how you use it, they can use it. An attacker still needs to authenticate against SSH on that non-standard port. The whole world could know about it, but the security of the system is not greatly impacted.
- AstralStorm 10y agoExcept said port is not tested all the time by helpful automated test systems developed by attackers.
- PeterisP 10y agoIf you're running a real service behind that port, then those "helpful automated test systems" aren't helping you since either they don't succeed and don't do anything, or they succeed and hurt you. If you're running a honeypot behind port 22, well, that works well with putting the real service on another port or behind port knocking.
- ufo 10y agoThe author's point is that people still criticize the useful kind of obscurity as if it were the useless kind.