Unfortunately, a poorly thought through article. This article seems to only promote FUD regarding information security. I hope the overall goal of creating robust systems is not lost by calling out certain tools. Security through obscurity is not security.
How to be a hacker
31–40 of 47 posts
Re: How to be a hacker
#32Re: How to be a hacker
#33'Eye of the beholder, as always. To my grandmom, I'm an elite weapons-grade hacker because I hit Ctrl-B to bold something in MSWord rather than clicking the button for it.
Totally. For all my real life friends I am beyond comparison when it comes to computers. Reading people's comments around here or on SO makes me think I know nothing...
The only true wisdom is in knowing you know nothing.
Re: How to be a hacker
#34Real hackers know Git. If you don't know Git, you don't know Shit. Am I right fellow hackers???
Re: How to be a hacker
#35Earlier quoted context omitted.
Please enlighten me as to the point of this article then, because from my POV, it's a list of 'hacking tools' that you can use to be an entry-level 'hacker'. This notion of being a hacker due to using a tool is preposterous. The only thing the article does is perpetuate the flawed understanding of computer security and hacking for the general public.
"We started with Linux" (that's a subheading , mind you!) — "That’s crucial for hackers, because although the temptation is to focus on their tools, the job is as much art as science" — "If you can get physical access to a network"... Like, you're just not reading the article. You're just not. The fact that the OP mentions "getting physical" is an obvious counterexample to your criticism and reduction of "it's a list…
I thought it was great. Maybe I haven't heard of these tools before. Reading about them doesn't mean I know how to use them or have a thorough understanding of security, but it's a good place to start googling and learn more.
Re: How to be a hacker
#36Re: How to be a hacker
#37You're not a hacker until a hacker calls you a hacker. ( http://www.catb.org/esr/faqs/hacker-howto.html#hacker_alread... )
Then who was the first hacker?
I don't know who was the (car 'hacker) but this one was the last in the recursive tail call:
Re: How to be a hacker
#38People, take note... This article was written for Guardian readers, not the elite HN hacking corps.
Re: How to be a hacker
#39Real hackers know Git. If you don't know Git, you don't know Shit. Am I right fellow hackers???
Only if your name is Mel:
http://foldoc.org/The+Story+of+Mel,+a+Real+Programmer
http://www.wps.com/J/LGP-21/mel-the-programmer.html
The man didn't even use patch or diff! Now git off my lawn kid!
Re: How to be a hacker
#40Earlier quoted context omitted.
"We started with Linux" (that's a subheading , mind you!) — "That’s crucial for hackers, because although the temptation is to focus on their tools, the job is as much art as science" — "If you can get physical access to a network"... Like, you're just not reading the article. You're just not. The fact that the OP mentions "getting physical" is an obvious counterexample to your criticism and reduction of "it's a list…
I thought it was great. Maybe I haven't heard of these tools before. Reading about them doesn't mean I know how to use them or have a thorough understanding of security, but it's a good place to start googling and learn more.
nmap is a fairly common used tool for more than testing. So is dig netstat sockstat nc tcpdump qmail djbdns pf s(sh|cp) traceroute also read your security and tuning man pages as a great place to start.