6 ms·
People keep on getting hacked. Is it really that hard to prevent that from happening, or is this another case of widespread incompetence and "It won't happen t
by stcredzero 16y ago
People keep on getting hacked. Is it really that hard to prevent that from happening, or is this another case of widespread incompetence and "It won't happen to me" thinking?
EDIT: I've commented here before about the scary potential of the /b/ crowd if some of them ever tried to organize and become activists.
- benmathes 16y agoThe short answer is that it is that hard to fully prevent it from happening. For practical purposes, IT security's job is to make it not worth the effort to break in. And even if you've built a really secure system all it takes is one user with their daughter's name as their password to make it all moot.
- stcredzero 16y agoWhat if you only have one "user" who only logs in through SSH using port knocking and all of the server's other communication with the rest of the net is through encrypted binary data in UDP packets with fixed-size fields?
- wmf 16y agoThen you're fired because the server doesn't actually work.
- stcredzero 16y agoThen you're fired because the server doesn't actually work. If I were interviewing you, your answer would be considered nonsense and would cause you to not get hired in the first place. I actually need to write such a server for a product I'm working on. All it ever does is encrypted communications with other machines.
- wmf 16y agoOK, you're right. You'd only be fired in the other 99.9% of cases, where servers have to support standard protocols and normal users.
- bioh42_2 16y ago99.9% of cases, where servers have to support standard protocols and normal user. True. True for all small and big companies' IT. But if you are a security or even just a forensics firm, then you ought to be in the other 0.1%
- Tautologistics 16y agoOK, so then forget your "super secure" server. I would instead focus on compromising one of the admin computers that has the "special user" ssh key and the port knock sequence; or maybe I will hit one of the servers communicating with this "secure" computer and see if you remembered to bounds check all the data coming in; maybe even see if you network stack has any exploits in its tcp/udp implementations while I am at it...
- stcredzero 16y agoOK, so then forget your "super secure" server. I would instead focus on compromising one of the admin computers that has the "special user" ssh key and the port knock sequence Juicy! [making notes to buy a laptop for the express purpose of logging into the server] maybe I will hit one of the servers communicating with this "secure" computer and see if you remembered to bounds check all the data coming in All fields are fixed length.
- jbri 16y agoI have to wonder why you consider port knocking to be a useful security-usability tradeoff. If SSH alone isn't "secure" enough for you, then adding a port knock doesn't actually lift it over that boundary.
- stcredzero 16y ago
- pavel_lishin 16y agoThat sounds like a bad balance of usability to security.
- stcredzero 16y agoThe entire purpose of the machine is to manage session keys. Yes, this is part of a system that will make money. No, it's not a web app. Warning: answering programming/security questions as if web apps are the whole of computing won't win you points with everyone.
- pavel_lishin 16y agoWell, for the highly specialized purpose that I didn't know about before you explained it in this comment, your solution works.
- stcredzero 16y agoAnd for seeing if someone has the knowledge and imagination to come up with such a purpose, I think I've found a good filter.
- danilocampos 16y ago> one user with their daughter's name as their password to make it all moot. I see what you did there.
- shasta 16y ago> And even if you've built a really secure system all it takes is one user with their daughter's name as their password to make it all moot. If your security design allows anyone to SSH in to obtain significant system access using only a user selected password, it isn't "really secure."
- catshirt 16y agolikewise, you could prevent your users from creating such passwords.
- markkat 16y agoI think it really is that hard to prevent it from happening. Every organization/system is going to have vulnerabilities from time to time. If you are drawing the ire of those who want in, it's just going to be a matter of time. I really think the best way to secure yourself, is not to piss off folks like Anon.
- Seth_Kriticos 16y agoThere is nothing such as a perfectly secured system. There are just less and more secured systems. The effort put in securing the system pretty much defines how much effort and ingenuity is required to penetrate it. Kind of a cat and mouse game or chess.
- de90 16y agoNot really the answer to the question, but this was the result of social engineering -> http://pastie.org/1535735 http://pastie.org/1535735 So, even if it was secure, in this case it would have happened..
- allenp 16y agoI think if they required the use of a shibboleth or key phrase in the email they could have avoided this. http://en.wikipedia.org/wiki/Shibboleth http://en.wikipedia.org/wiki/Shibboleth http://en.wikipedia.org/wiki/List_of_shibboleths http://en.wikipedia.org/wiki/List_of_shibboleths
- JonnieCache 16y agoOr, have an agreement that all password resets will be silently ROT13'd against what is requested. So if you say "Can you reset my password to foobar" then your admin knows to actually set it to "sbbone." They can then just send a normal reply saying "ok your password has been set to 'foobar'" and then as long as both parties remember the secret protocol, you are OK. You could then also watch for login attempts using "foobar" to warn you of foul play.
- artmageddon 16y agoThat's mostly security by obscurity, in which you're bound to get burned.
- JonnieCache 16y agoCould you elaborate?
- jrockway 16y agoThe security of that system comes from hoping nbobody will guess your key exchange protocol. The security in real key exchange protocols comes from mathematics problems that would take more computer power than the universe has available to solve. So 'your way' is clearly inferior; the attacker guesses (or is told) that ROT13 is what's going on, and you're 0wned and you will never know. Problem.
- tlear 16y agoIt is difficult. In this case I am sure they knew Anon will come after them and they were SURE they were secure. But when you play with fire you gona get burned
- JoachimSchipper 16y agoUnlike benmathes, I'm going with "incompetence". The /b/ crowd hasn't shown much sophistication (yet) - then again, if this kind of straightforward social engineering works, why bother? (Seriously, a security firm that falls for "please drop the firewall and e-mail me the root password"?)
- metabrew 16y agoThis is insane and should be cause for extreme suspicion.. As a sysadmin if someone asks you to do this, the correct response is "haha not likely", and at the very least confirm their identity - call them or something. Don't sent the password over email.
- robryan 16y agoIt might be that they have never been hacked in this way before, so they don't even consider it. Probably seen older employees do it when they were new giving them the impression that it's just how thing are done.
- phrotoma 16y agoI'm reminded of the mitnick/tsutomu tales. I think Anon may be in for some hurt with a guy like Hoglund pissed at them. He's been on the front lines of security research for at least a decade.
- jinfiesto 16y agoI had the same thought. Hoglund is a bamf. It'll be interesting to see what goes down.