7 ms·
He searched the printer logs. Presumably when Word sends stuff to the printer, it doesn't bother with all the extraneous garbage it puts in files. Printer commu
by fooqux 4y ago
He searched the printer logs. Presumably when Word sends stuff to the printer, it doesn't bother with all the extraneous garbage it puts in files. Printer communication hasn't changed much in decades.
- moron4hire 4y agoIt is also possible he's just a lunatic who fired an innocent person.
- savanaly 4y agoWhat are the odds that he calculated a certain number of bytes, and exactly one other employee had sent a file to the printer that contained that number, but it was just a coincidence? If the method indeed doesn't work (as you suggest "is possible") it's impossible it would turn up a false positive, only a false negative.
- blarghyblarg 4y agoalmost as good as the odds that he got something pretty close, then changed the details a bit to fit the narrative. or, he stayed up for two days until he got it exactly to match by tweaking his approach a little at a time, and actually matched it to the right person. Honestly, he seems like he'd do this.
- dmix 4y agoSounds like a fun project any hacker would get distracted by.
- stavros 4y agoYou wouldn't do that though, would you? You'd type the thing up, print it, see that the printer received a 4.7 KB (or whatever) doc and look for a 4-6 KB doc the week of the leak, and then you have 100 documents to go through, rather than 100000.
- capitol_ 4y agoIt's also possible that he calculated the number of bytes, searched the logs, didn't find anything and then tweaked his numbers until something matched. And then fired that random person to make a statement and lied about how he found out who to fire.
- politician 4y agoThis approach would work in isolation, but by failing to find the true leaker would result in them being empowered to leak more over time. Is there evidence that Tesla has a lot of regular leaks?
- savanaly 4y agoI didn't mean to claim other than that anything is possible. I was just saying the original theory put forward wasn't internally logical.
- moffkalast 4y agoLooking at twitter these days I sure have a feeling this is not super unlikely.
- Workaccount2 4y agoI would assume there was also at least a minor degree of due diligence, such as "Would this person actually have had the knowledge to write letter".
- marcusverus 4y agoIt'd be even easier than that. Walk to the person's desk and ask them to bring up the document that they printed on ${printer} at ${time}. If he can't produce a document of the correct size, he's your guy.
- elliekelly 4y agoThis is a good way to fire innocent employees who had the audacity to edit a document after they’ve printed it.
- aaron695 4y ago[dead]
- mhh__ 4y agoOr lying. When you are rich or famous people or in vogue socially let you get away with these stories e.g. Consider feynmans "I'm modest but look at my genius"-isms
- tsol 4y agoYeah exactly. My thought was he probably found the leaker in a much more mundane way, but being undeniably great at PR he decided to spice up the story with this little bit of detective work. It sounds so clever you want to believe it, even if it's pretty impractical(not impossible though!). You know what they say, don't let the truth get in the way of a good story.
- VectorLock 4y agoMore important is spreading the perception he was able to sleuth down who the leaker was, to deter future leakers.
- brookst 4y agoStill. He’d have to have the same normal.dot, make the same space/tab choices, same fonts, etc. And in a large company, how many ~1 page letters get printed? What are the odds that there is only a single match in the entire company? I take this story similar to the binary coded space story: more likely to be apocryphal and promoted to deter future leakers than true stories about catching them in the past.
- Firmwarrior 4y agoCould be the case that there were only a handful of things printed at the whole company in a week, considering how obsolete paper has been getting
- lr4444lr 4y agoPerhaps it wasn't an exact byte match, but close enough to only 1 print job size within a reasonable time frame.
- barelysapient 4y agoExactly this. If you know that its around 36kb, and had to be printed between two dates, the list narrows substantially. And more than likely, the printer queue or corporate compliance tools had additional functionality that made such a search trivial. I have my own story about this: In the early 2010's I had a boss that loved to call us and check in every day. We were a remote team and he had anxiety that we were all larking off. I later learned his technique was to open the dropbox admin tools to see the location of someone before calling them. "So, BarelySapient, where are you working at today?", he'd ask in a cheerful tone. But in reality, he was testing employee truthfulness. Every call. He later fired one of my co-workers when they reported to be working from home, but dropbox reported them somewhere in the Florida keys....
- mschuster91 4y ago... and here I'm just happy about German employee and EU data protection laws. This kind of abuse would be plainly illegal here and entitle the employee to significant compensation.
- smt88 4y agoIf he had access to printer logs, he would know exactly what everyone printed and when they did it. Networked printers store a lot of information about what is being printed.
- pixl97 4y agoIn general a lot of metadata is kept, but very rarely is the full print content kept (though in some organizations it may be for security review). The difficulty here is figuring what metadata is relevant, in this case size was the most important.