Xz/liblzma: Bash-stage Obfuscation Explained
gynvael.coldwind.pl
Xz/liblzma: Bash-stage Obfuscation Explained
1–10 of 137 posts
Re: Xz/liblzma: Bash-stage Obfuscation Explained
#2Re: Xz/liblzma: Bash-stage Obfuscation Explained
#3I also saw a comment on reddit mentioning that the "sandboxing" method was sabotaged with a dot. It's on the line just after "#include " you can see a dot all the way on the left.
https://git.tukaani.org/?p=xz.git;a=commitdiff;h=328c52da8a2...
https://old.reddit.com/r/linux/comments/1brhlur/xz_utils_bac...
Re: Xz/liblzma: Bash-stage Obfuscation Explained
#4Re: Xz/liblzma: Bash-stage Obfuscation Explained
#5Did anyone search github yet for similar head | tail tricks ? I doubt it was invented just for this.
Re: Xz/liblzma: Bash-stage Obfuscation Explained
#6Thanks the simplified explanation and noisy image comparison is quite appreciated. It gives me a good grasp of what people mean by the sophistication involved. I also saw a comment on reddit mentioning that the "sandboxing" method was sabotaged with a dot. It's on the line just after "#include " you can see a dot all the way on the left. https://git.tukaani.org/?p=xz.git;a=commitdiff;h=328c52da8a2... https://old.redd…
+
+.
+
and the dot goes unnoticedRe: Xz/liblzma: Bash-stage Obfuscation Explained
#7Re: Xz/liblzma: Bash-stage Obfuscation Explained
#8Re: Xz/liblzma: Bash-stage Obfuscation Explained
#9How are the binary files passed to those stage-0 commands?