Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The issue is not that obscurity per se is bad, but relying _only_ on obscurity is absolute the same as not having any security measures at all.

With the public ledger or not, you will still need to implement proper security measures. So it shouldn't matter if your address is public or not, in fact making it public raises the awareness for the problem. That's the argument.



> relying _only_ on obscurity

Until it gets obscure enough that we start calling it “public-key cryptography”. Guess the prime number I'm thinking of between 0 and 2↑4096 and win a fabulous prize!


If you replace "security by obscurity" with "Kerckhoffs's principle", yes, absolutely!

The problem with using regular everyday obscurity is that it usually has a small state space and makes for terrible security, but people will treat it like it is cleverly hidden and safe from attackers

If I guess the IPv4 you're thinking of between 0 and 2↑32, ready or not, you win a free port scan


As per another comment, we can scan a single port on every public IPv4 address in less than an hour.

Trying every 256bit number gets into a "slightly" larger problem.


> So it shouldn't matter if your address is public or not, in fact making it public raises the awareness for the problem. That's the argument.

Forget about the internet, we've had almost 100 years to prove we can secure identity theft. And the best thing we can do is to keep our SSN's secret -- security through obscurity. Keeping your SSN private reduces your personal attack surface.

We've had 50 years to secure the internet, and yet, we still have zero day attacks. Nuclear submarines try their best to keep their locations a secret? Why? You cannot attack something you cannot see or hear.


Well, this is a bad example, considering public/private key pairs exist,

and work for identity validation,

as long as you don't farm it out to a cheap, know-nothing vendor.


Except we are more on a chess table where we can just trivially probe each cell, unlike the vast volume of the ocean.


A game of battleship is indeed a good analogy!

Just because its a finite space that may eventually be discovered is a poor reason to announce where things are!


Battleship sounds like a good analogy, but is very different because you don't have other options to "secure your ship" besides obscurity. If you had other options, let's say a sonar or moving your ship, they would definitely be used along with obscurity.

Besides, the time to scan the whole board is too time consuming in a battleship game, but scanning the whole internet on the other hand only take a few minutes[1]

[1]: https://github.com/robertdavidgraham/masscan


You're talking IPv4 here, not IPv6. A 24 bit network has 254 addresses in IPv4. A 64bit subnet in IPv6 has 2^64.

If you can scan 1M ipv6's in a second, you can maybe scan 1 subnet in 584,942 years.

So if you're a firewall, and you notice scanning from a particular ip or network, it's easy enough to block them.

Also if you are scanning IPv4, you're not scanning addresses behind the NAT'd routers -- which is also effectively a form of obfuscation. So I would argue it's not the entire internet.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: