Fix: system-design-doc#100
Closed
rahulk789 wants to merge 2 commits into
Closed
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the architecture overview section of the README to refine the system design diagram, clarify stages/layers, and improve categorization of the obfuscation pipeline.
Changes:
- Reworked the ASCII architecture diagram to describe a multi-stage obfuscation pipeline (pre-compilation, IR-level, compilation hardening, and post-compilation packing).
- Clarified descriptions of symbol obfuscation, string encryption, LLVM passes, and binary packing, including toolchain hardening options.
- Adjusted wording and ordering to emphasize pipeline stages and packed-binary output.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+171
to
+222
| ┌──────────────────────────────────────────────────────────────┐ | ||
| │ LLVM Obfuscator │ | ||
| ├──────────────────────────────────────────────────────────────┤ | ||
| │ │ | ||
| │ Input: source.c → [Pipeline] → Output: packed binary │ | ||
| │ │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Stage 1: Pre-compilation Obfuscation │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Layer 1: Symbol Obfuscation │ | ||
| │ ├─ Cryptographic hashing (SHA256 / BLAKE2b) │ | ||
| │ ├─ Function & variable renaming │ | ||
| │ ├─ String table anonymization │ | ||
| │ └─ Optional mapping file (debug / recovery) │ | ||
| │ │ | ||
| │ Layer 2: String Encryption │ | ||
| │ ├─ XOR / AES-based string encryption │ | ||
| │ ├─ Compile-time encryption │ | ||
| │ ├─ Runtime decryption stubs │ | ||
| │ └─ Constructor-based initialization │ | ||
| │ │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Stage 2: IR-level Obfuscation (LLVM Passes) │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Layer 3: OLLVM / Custom LLVM Passes │ | ||
| │ ├─ Control Flow Flattening │ | ||
| │ ├─ Bogus Control Flow │ | ||
| │ ├─ Instruction Substitution │ | ||
| │ ├─ Basic Block Splitting │ | ||
| │ └─ Opaque predicates │ | ||
| │ │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Stage 3: Compilation & Toolchain Hardening │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Layer 4: Compiler & Linker Hardening │ | ||
| │ ├─ Link-Time Optimization (-flto) │ | ||
| │ ├─ Symbol visibility hiding (-fvisibility=hidden) │ | ||
| │ ├─ Frame pointer omission (-fomit-frame-pointer) │ | ||
| │ ├─ Stack protections (-fstack-protector-strong) │ | ||
| │ └─ Speculative execution hardening │ | ||
| │ (-mspeculative-load-hardening) │ | ||
| │ │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Stage 4: Post-compilation Binary Protection │ | ||
| │ ───────────────────────────────────────────────────────── │ | ||
| │ Layer 5: Binary Packing & Compression │ | ||
| │ ├─ UPX packing (LZMA / NRV) │ | ||
| │ ├─ 50–70% size reduction │ | ||
| │ ├─ Additional static-analysis resistance │ | ||
| │ └─ Transparent runtime decompression │ | ||
| │ │ | ||
| └──────────────────────────────────────────────────────────────┘ |
There was a problem hiding this comment.
The updated architecture diagram is no longer wrapped in a fenced code block, whereas the previous version was. Without a code block, the ASCII diagram will render in a proportional font and may misalign across different Markdown viewers. Please wrap this diagram in a fenced code block again to preserve its monospace layout and readability.
Member
|
@rahulk789 Please update the PR by documenting all the layers, you can refer https://oaas.pointblank.club |
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.
Fixes indents and numbering along with basic categorization