Post: LLVM obfuscation for imix — 587 → 0 eldritch strings - #2
Open
hulto wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New dev-blog post documenting our recent imix obfuscation work:
strings imix | grep -i eldritchwent from 587 hits to 0.The post covers:
eldritchleaks into 5 root causes (panic-locationfile!()strings, mangled symbol names, rust-embed paths, a temp-file prefix literal, and a prost-generated proto field name)eshard/obfuscator-llvmagainst LLVM 20 with-fno-rtti, loading it into a matching nightly rustc via-Z llvm-plugins/-C passes, and wiring it workspace-wide through.cargo/config.tomlcargo rustcflags only hit the final crate — useRUSTFLAGSso every dependency gets the passrustls(plugin built against distro LLVM 20 vs rustc's bundledlibLLVM-20.1-rust); load works, the pass corrupts the heapstring-encryptiononly encrypts NUL-terminated C strings (isCString()), so prost field names like[8 x i8] c"eldritch"are skipped — the sneaky final leak, which also gets MIR-inlined intolibtransport-Z location-detail=none,-C strip=symbols(the config's-Cstrip=debuginfowas shadowing the profile'sstrip=true), embedded-file rename (main.eldritch→main.svc), temp-prefix rename, and the wire-compatibleTome.eldritch→Tome.scriptfield rename in the generated Rust codeNotes
spellshift/realm) are local work-in-progress and are not part of this PR — this PR is the blog post only.Checklist
layout: post,gh-repo,gh-badge,tags,author: Hulto)YYYY-MM-DD-slug.mdnightly-2025-08-01= LLVM 20.1.8, plugin built with-fno-rtti, crash reproduced/isolated)