Real crypto is secure if the key is kept secret. That isn't "obscurity". Obfuscation isn't secure because you're giving out your code.
-
-
And proprietary crypto may be secure but most likely isn't because crypto is hard, and thus should be considered security through obscurity.
2 replies 0 retweets 0 likes -
Replying to @marcan42
My point on obscure ports is that they effectively increase the password bit length, increasing security. But maybe you’re saying that’s
1 reply 0 retweets 0 likes -
...not obscurity, which makes sense I suppose. I just feel obscurity can be used as an additional layer in some cases.
1 reply 0 retweets 0 likes -
Replying to @zbrogz
But they don't increase the password bit length. This is the "movie password cracking" fallacy. Multiple "passwords" != one longer password.
1 reply 0 retweets 0 likes -
A 16-bit constant that you crack *separately* adds negligible security to a strong password. It doesn't add 16 bits of entropy.
1 reply 0 retweets 0 likes -
Passwords getting cracked character is a movie thing but in the real world additional characters are multiplicative, not additive.
2 replies 0 retweets 0 likes -
Of course that doesn't mean running SSH on a nonstandard port is useless. I do it too, it cuts down on log spam. But mostly just that.
1 reply 0 retweets 0 likes -
Sure, if you get lucky you might stop or deter some attackers, but you should always assume that isn't the case.
1 reply 0 retweets 0 likes -
Replying to @marcan42
Could you determine the port separately from the password though? If yes, 2^key_size + 2^16 (negligible) If no 2^(key_size +16)
1 reply 0 retweets 0 likes
Obviously yes, you can determine the port separately from the password. Why would you think otherwise?
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.