▲ | LaTeXpOsEd: A Systematic Analysis of Information Leakage in Preprint Archives(arxiv.org) | ||||||||||||||||||||||
27 points by oldfuture 4 hours ago | 10 comments | |||||||||||||||||||||||
▲ | SiempreViernes 2 hours ago | parent | next [-] | ||||||||||||||||||||||
As far as I can tell they trawled a big archive for sensitive information, (unsurprisingly) found some, and then didn't try to contact anyone affected before telling the world "hey, there are login credentials to be found in here". | |||||||||||||||||||||||
| |||||||||||||||||||||||
▲ | mseri 2 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
Google has a great aid to reduce the attack surface: https://github.com/google-research/arxiv-latex-cleaner | |||||||||||||||||||||||
| |||||||||||||||||||||||
▲ | barthelomew an hour ago | parent | prev | next [-] | ||||||||||||||||||||||
Paper LaTeX files often contain surprising details. When a paper lacks code, looking at latex source has become a part of my reproduction workflow. The comments often reveal non-trivial insights. Often, they reveal a simpler version of the methodology section (which for poor "novelty" purposes is purposely obscured via mathematical jargon). | |||||||||||||||||||||||
| |||||||||||||||||||||||
▲ | kmm an hour ago | parent | prev [-] | ||||||||||||||||||||||
I sort of understand the reasoning on why Arxiv prefers tex to pdf[1], even though I feel it's a bit much to make it mandatory to submit the original tex file if they detect a submitted pdf was produced from one. But I've never understood what the added value is in hosting the source publicly. Though I have to admit, when I was still in academia, whenever I saw a beautiful figure or formatting in a preprint, I'd often try to take some inspiration from the source for my own work, occasionally learning a new neat trick or package. | |||||||||||||||||||||||
|