Sebastian Schinzel

1.3K Followers
491 Following
508 Posts
Husband, dad, mountain biker, professor of computer security at FH Münster and department lead @fraunhofersit. Private account.
Mehttps://sebastian-schinzel.de/
FH Münsterhttps://www.fh-muenster.de/de/eti/ueber-uns/personen/schinzel/

Greg Kroah-Hartman: "If you look there are thousands of unfixed CVEs in the older LTS kernels right now, and if distros or users that rely on those older branches wish to see those resolved, they need to provide working backports to us to apply, as our first attempt did not work (which is why they are unfixed in those branches.)"

Really asking for a "Pray tell us", given that nobody actually bothered disclosing the problem to downstreams and that the commit message was hiding it.

Either way, apparently the great LLM-backed patch backporting process that #NVidia is so proud of doesn't really work. Upstream doesn't really care about #LTS branches, and they should be considered insecure by default.

https://lore.kernel.org/stable/2026050114-supernova-angler-2de1@gregkh/

#Gentoo #Linux #CopyFail #security

Re: copy.fail and backport to LTS 6.12 and earlier (was: Linux 7.0.3) - Greg Kroah-Hartman

"In addition to fixing the 271 bugs identified by Claude Mythos Preview in the 150 release, we've shipped more of these fixes in 149.0.2, 150.0.1, and 150.0.2. We also continue to find bugs with other means internally, and, similar to other projects, we've seen a significant uptick in external reports in the last few months."

https://hacks.mozilla.org/2026/05/behind-the-scenes-hardening-firefox/

Our faculty uses Mattermost heavily and many lecturer use it as the primary communication channel with students. Now Mattermost changes its licensing policy and it looks like we’ll have to switch to Teams.

Any alternatives for a self-hosted simple chat app? No need for end-to-end encryption, keeping chat history complete and intact is important.

So yes, your AI can find vulnerabilities.

But can it also GENERATE NAMES, LOGOS, AND WEB SITES for it??

*check mate*

Have you ever wondered what happens with the LaTeX sources that you submit to arXiv?

In joint work with Jan, Johannes, David, and Joscha, we had a look at exactly that! Shout out to Johannes for taming 2.7 Million arXiv submissions. Jan will present the paper of our assessment of "hidden" information in arXiv source files at the IEEE Symposium on Security and Privacy 2026 (May 19, Session 3, Track 3), the leading venue for cybersecurity research (acceptance rate ~12.7%).

Our analysis highlights the prevalence of dangling files (unnecessary to create the final PDF), sensitive information in metadata (e.g., GPS locations), and a lot of irrelevant content in the form of LaTeX comments that reveals passwords, access tokens, credit card numbers, author conversations, profanity, and many more insights that were likely intended to remain private.

Many authors are unfortunately unaware that source files for arXiv submissions are in fact publicly accessible.Your submission may also be affected given that 88% feature some kind of unique details and 18% even simultaneously expose unique dangling files, unique metadata, and unique comments.

Since existing sanitization tools all have blindspots, we propose ALC-NG. It utilizes pdflatex's recorder option and a tree-sitter grammar to improve the cleaning reliability, providing a tool that helps combat "hidden" information in new arXiv submissions (or elsewhere).

Paper: https://arxiv.org/abs/2604.20927
Executive Summary: https://arxiv.comsys.rwth-aachen.de/
ALC-NG: https://github.com/COMSYS/ALC-NG/

Patent pending
Ein Leben ohne #Fahrrad ist möglich, aber sinnlos.
Because we don’t collect user data, what we know about these attacks comes from the victims of phishing. And from what victims have told us, the attacks followed a broad pattern: after tricking people into revealing their Signal credentials, attackers then used those credentials to take over their account and also frequently changed the associated phone number. 4/

A response to recent reporting in Germany, in service of clarity and accountability:

First, it’s important to be precise when it comes to critical infrastructure like Signal. Signal was not “hacked” — in that our encryption, infrastructure, and the integrity of the app’s code was not compromised. 1/

Hey speakers!

If you have some interesting app security story to share, consider submitting to the German OWASP Day CfP.

Nice community event run by fine volunteer people. This year, the OWASP Day is in Karlsruhe on September 24th. https://god.owasp.de/2026/en/cfp.html

German OWASP Day 2026