News for hackers. Stuff that matters.
Re:Data Engineer in Google Case Is Identified - author of Ne... by hkmurakami on Tuesday May 01, 2012 @12:40AM (#3913014)
>On his LinkedIn page, Mr. Milner lists his occupation as “hacker,” and under the category called “Specialties,” his entry reads, “I know more than I want to about Wi-Fi.”

I am more than moderately offended/troubled/irked by this excerpt, as it appears to deliberately depict the engineer as a "hacker" in the sense of Hollywood culture, rather than "hacker" as we know it in makers' terms.

In the wrong hands, the English language is much more potent and destructive than any programming language. An English Specialist can often cause more harm than a Wi-Fi Specialist.

Re:Data Engineer in Google Case Is Identified - author of Ne... by untog on Tuesday May 01, 2012 @01:12AM (#3913115)
I've long thought that trying to adopt "hacker" as a professional term was a bad idea. I told friends that I was going to a government hackathon once, and they thought I was going to be arrested.

Why do we have to be hackers? What was wrong with being developers?

Re:Data Engineer in Google Case Is Identified - author of Ne... by tlrobinson on Tuesday May 01, 2012 @01:31AM (#3913152)
I think it's almost like a secret handshake. If someone understands what I mean when I say "hacker" I respect them a little more.
Re:Data Engineer in Google Case Is Identified - author of Ne... by jlawer on Tuesday May 01, 2012 @03:05AM (#3913340)
Because society took both hacker and developer and changed their meaning.

Hackers became criminals and developers were Javabean coding wage slaves... given a choice criminal sounds cooler then wage slave.

Re:Data Engineer in Google Case Is Identified - author of Ne... by untog on Tuesday May 01, 2012 @10:25AM (#3914442)
Because society took both hacker and developer and changed their meaning.

But the article (and my anecdotal experiences) are proof that this hasn't actually happened. We decided to call ourselves 'hackers', but society as a whole doesn't.

given a choice criminal sounds cooler then wage slave.

I think that's my main problem with "hacker". It's an attempt to be cool.

Re:Data Engineer in Google Case Is Identified - author of Ne... by switz on Tuesday May 01, 2012 @01:27AM (#3913143)
Developer !== Hacker
Re:Data Engineer in Google Case Is Identified - author of Ne... by madiator on Tuesday May 01, 2012 @01:36AM (#3913165)
Developer != Hacker
Re:Data Engineer in Google Case Is Identified - author of Ne... by Jimmie on Tuesday May 01, 2012 @02:05AM (#3913241)
!== == Javascript programmer
Re:Data Engineer in Google Case Is Identified - author of Ne... by goodgracious on Tuesday May 01, 2012 @01:19AM (#3913132)
In the wrong hands, deep knowledge of Wi-Fi can be far more destructive than the conventional methods of a non-technical journalist. It's a new level of power in snooping.

It's a good thing journalists generally do no have Milner's level of knowledge, as surely they too would abuse it. Maybe even worse than Google. Milner's comment reflects the power of the knowledge he has. He has to take some responsibility for it.

Both Google engineers and NYT journalists do snooping on others for a living.

They are just at odds with each other, for various reasons; engineers for companies like Google generally do not like journalists and generally the same is true vice versa.

Google has a genuine PR problem. And journalists are watching their careers disintegrate with the advance of communications technology. It's an amusing little spat to watch.

Re:Data Engineer in Google Case Is Identified - author of Ne... by brudgers on Tuesday May 01, 2012 @01:04AM (#3913089)
Given that he developed a "wardriving" application, black hat connotations are not entirely unreasonable. The use of his talents to hoover up data without permission certainly doesn't offer much in the way of defense, either.
Re:Data Engineer in Google Case Is Identified - author of Ne... by magicalist on Tuesday May 01, 2012 @01:15AM (#3913122)
Ha, your parent post could almost have been written about your post too.

Looking past the scare quotes, according to the FCC report it was just Kismet, and the problem basically just came down to deciding to write the non encrypted payloads to disk. He might know too much about wifi, but probably half the regular HN posters could have implemented the same system, if they chose to.

Re:Data Engineer in Google Case Is Identified - author of Ne... by goodgracious on Tuesday May 01, 2012 @01:25AM (#3913141)
"if they chose to"

Precisely.

I know Kismet exists. I know I can install and run it. I know I can even break wi-fi encryption in some cases. But that doesn't mean I'm going to do this, for commercial purposes, for a company like Google.

Re:Data Engineer in Google Case Is Identified - author of Ne... by magicalist on Tuesday May 01, 2012 @01:35AM (#3913159)
Yes, it comes down to a choice, not scary hackers. That's what I wrote. Maybe I'm not understanding your point?
Re:Data Engineer in Google Case Is Identified - author of Ne... by goodgracious on Tuesday May 01, 2012 @01:40AM (#3913174)
My point was that I agree with what you said. Nothing more.
Re:Data Engineer in Google Case Is Identified - author of Ne... by brudgers on Tuesday May 01, 2012 @07:42AM (#3913854)
Quotation marks indicate my skepticism of the term due to its use by DOJ in building their case.

Engaging in questionable behavior which others with similar skills forgo is what distinguishes black hat from white hat hacking.