News for hackers. Stuff that matters.
Re:Google fires employee who leaked memo on raises by mmastrac on Wednesday November 10, 2010 @09:20PM (#1892602)
Is Google using some subtle permutation on every version of the email sent out?

All it would take would be swapping "--" for "...", "ie"/"i.e."/"eg"/"e.g." You should probably compare your local copy of an email with someone else before leaking it!

Re:Google fires employee who leaked memo on raises by rflrob on Wednesday November 10, 2010 @09:26PM (#1892616)
"Hey Bob, I'm thinking about leaking my email... can I diff it with yours?"

The other problem I can see is that there's only 5 or 6 of those points, which would be enough to narrow down the leaker, but not ID them outright. Probably easier (if more evil) to check all the outgoing mail in gmail.

Re:Google fires employee who leaked memo on raises by joshu on Wednesday November 10, 2010 @09:38PM (#1892646)
You can also use trailing spaces. I have done this on the past successfully
Re:Google fires employee who leaked memo on raises by michaelhart on Wednesday November 10, 2010 @09:48PM (#1892680)
But when it's actually leaked and posted, it'll most definitely be trimmed.
Re:Google fires employee who leaked memo on raises by roel_v on Thursday November 11, 2010 @03:08AM (#1893252)
You could use a pattern of one or two spaces after each sentence. Encode an id in that. If text is copy and pasted and not processed with a s/ / /g, that most likely won't be detected by the copy-and-paster (especially when it's all done in a variable width font).
Re:Google fires employee who leaked memo on raises by roel_v on Thursday November 11, 2010 @03:54AM (#1893339)
Looks like HN does remove double spaces, what I meant was obviously s/[space][space]/[space]/g :)
Re:Google fires employee who leaked memo on raises by modeless on Thursday November 11, 2010 @05:18AM (#1893462)
It's not HN, it's a feature of HTML. All whitespace characters (including tabs and newlines) are condensed to a single space, and leading/trailing spaces are removed. So if you have a habit of double-spacing after sentences, HTML simply ignores you, unless you use <pre> or &nbsp;.
Re:Google fires employee who leaked memo on raises by roel_v on Thursday November 11, 2010 @06:19AM (#1893551)
Ah didn't know that. Well that would make the single/double space encoding of an id much harder.
Re:Google fires employee who leaked memo on raises by grncdr on Thursday November 11, 2010 @11:52AM (#1894335)
Actually, it makes it more effective if anything. The browser displays it as a single whitespace, but the source isn't altered, (and therefore easily checkable).
Re:Google fires employee who leaked memo on raises by roel_v on Thursday November 11, 2010 @12:16PM (#1894444)
Yeah but if a user copy/pastes it from his email client into his blog posting system, the double spaces are stripped, too (I checked it with Firefox, maybe other browsers work differently). It would only work I think if the single/doubles space pattern was preserved across copy/paste operations.
Re:Google fires employee who leaked memo on raises by blueben on Thursday November 11, 2010 @10:05AM (#1894001)
What is evil about checking corporate mail for corporate mail leaks?
Re:Google fires employee who leaked memo on raises by MichaelApproved on Wednesday November 10, 2010 @10:31PM (#1892781)
Or worse, the INcoming mail in gmail.
Re:Google fires employee who leaked memo on raises by vaksel on Wednesday November 10, 2010 @09:38PM (#1892645)
i doubt it's that complicated, they have full control of the mailservers, I bet the person just didn't think leaking the information was that big of a deal.
Re:Google fires employee who leaked memo on raises by tlrobinson on Wednesday November 10, 2010 @11:08PM (#1892853)
Or, you know, run a giant grep on every mail sent to or from Gmail and internal mail over the last 12 hours...
Re:Google fires employee who leaked memo on raises by olalonde on Wednesday November 10, 2010 @09:26PM (#1892615)
I doubt there are 23,300 possible permutations. Moreover, I doubt a Googler wouldn't think of this classic before leaking his e-mail. Any other theory? Perhaps no one was fired and it's just link bait?
Re:Google fires employee who leaked memo on raises by alextgordon on Wednesday November 10, 2010 @09:34PM (#1892638)
Assuming a worst case of two possibilities for each difference, that comes out as ceil(log_2(23300)) = 15 differences necessary. You could easily get that by swapping out words for synonyms (especially if you use more than two synonyms per difference).
Re:Google fires employee who leaked memo on raises by gojomo on Wednesday November 10, 2010 @11:27PM (#1892894)
Don't forget unicode homoglyphs, as well.

And even if a journalist trimmed whitespace when formatting for publication, they might not have if forwarding back to a Google rep 'for comment'.

Re:Google fires employee who leaked memo on raises by d2viant on Wednesday November 10, 2010 @09:30PM (#1892626)
Most likely somebody just forwarded it to their favorite blog, especially if they didn't think the email was confidential. Pretty easy to track outgoing email.
Re:Google fires employee who leaked memo on raises by jedc on Thursday November 11, 2010 @04:47AM (#1893418)
With "CONFIDENTIAL: INTERNAL ONLY GOOGLERS ONLY (FULL TIME AND PART TIME EMPLOYEES)" at the top it's hard to believe they might have thought it wasn't confidential.
Re:Google fires employee who leaked memo on raises by rflrob on Wednesday November 10, 2010 @09:29PM (#1892622)
I heard from a Googler before the article came out that the leaker was fired. While one could imagine a second, as-yet unleaked email about the fake firing, isn't it much simpler just to assume that the leaker was fired?
Re:Google fires employee who leaked memo on raises by barrkel on Wednesday November 10, 2010 @09:44PM (#1892669)
You'd need over 14 binary manipulation choices, but only about 9 if you had a choice of three. If you include word synonyms in the choices, with over 250 words in the memo, I don't think it's unreasonable.
Re:Google fires employee who leaked memo on raises by lhnn on Wednesday November 10, 2010 @10:28PM (#1892773)
How about summarizing a memo instead of copypasta? Then they'd have to diff the facts to mess you up.
Re:Google fires employee who leaked memo on raises by tedunangst on Wednesday November 10, 2010 @11:58PM (#1892951)
A good news source, if there are any left, probably won't run a story based solely on an anonymous tip.
Re:Google fires employee who leaked memo on raises by pyre on Thursday November 11, 2010 @12:32AM (#1892993)
Well, what if the news source only published a summary, and not the original?
Re:Google fires employee who leaked memo on raises by mfukar on Thursday November 11, 2010 @02:09AM (#1893163)
That's not journalism.

OK, it may be today's journalism, but who trusts news sources like that?

Re:Google fires employee who leaked memo on raises by chollida1 on Wednesday November 10, 2010 @09:58PM (#1892709)
With 23,000 employee's that's alot of permutations for a 3 paragraph email.