Working on my #Java obfuscator, I've realized Java has 90s-era limits: method sizes are capped at 64kB. For automated code obfuscation, this is an ancient limit that prevents modern code protection. @Oracle@java How about you remove this limit entirely?
A researcher found critical Windows zero-days.
Reported them to Microsoft.
Microsoft denied the bug bounty.
Deleted their account.
Banned them from GitHub.
Then threatened criminal charges.
The researcher dropped six zero-days in six weeks.
Three got used in real attacks within days.
Other researchers are now handing them free vulnerabilities as a gift.
Microsoft’s Digital Crimes Unit is considering legal action.
Against the person whose bugs they refused to pay for.
This is Microsoft’s bug bounty program.
If this shit is the future of Windows UI design & coding then I dunno where the hell I've been living in the past 20 years with visual designers from #Delphi and WinForms. Complete regress. #windows#microsoft#programming I miss simple WinAPI ways.
github.com/sundaramramaswamy…
LLMs have gotten good enough at reverse engineering to recover source code from obfuscated binaries with real accuracy.
So we asked the obvious next question: how fast and cheap is it to use one to build obfuscation specifically designed to beat it?
We benchmarked Claude Opus 4.6 against the Tigress obfuscator across 20 targets first, to map its strengths and failure modes. 40% solve rate. Phase 3 multi-layer combos hit 0%, with cost explosions that killed the runs.
Then we ran a dev/test/refine loop to build 3 purpose-built obfuscation variants targeting the same crackme, iterating directly against the model's known weaknesses.
The finding: LLM-targeted obfuscation is fast and cheap to develop. Context windows, budget caps, and shortcut biases are all exploitable attack surfaces.
The arms race just shifted.
Support independent software developers. Total Commander is one of the best Windows tools there is. Still developed, still upgraded. Irreplaceable.
ghisler.com/#software#tech