in reply to Re: Re: My First Good(?) Original(?) JaPh,s
in thread My First Good(?) Original(?) JaPh,s
Doesn't seem obfuscated enough to me. Regardless even of the /ee it's pretty obvious what's going on.
I think it's important to hide the pipe for this one, otherwise while the details are not immediately obvious, the mechanics remain apparent. That's why I chose such an unusual placement of the shell quotes. The caret and dollar used to edit the incoming line also give away a lot. And don't forget that the one who started with pure tedium measures was you. :) (Remember s();..;;)
Obfuscations that rely purely on one or two arcane features don't work very well as far as I'm concerned. The trick is to hide your use of that arcane feature, and if possible even mislead the reader into thinking that something else entirely is going on. The best example I've ever seen is from Abigail: Things are not what they seem like.
As an aside, the best obfu I've ever seen is also from him:
A Japh that uses...(From his Japhs talk.)
- Computed goto.
- eval
- POD.
- A loop with only unconditional jumps....
- ... but it terminates anyway.
- Self modifying code.
- strict
- -w
- No more than one line.
- No more than 80 characters.
perl -Mstrict -we '$_ = "goto F.print chop;\n=rekcaH lreP rehtona tsuJ +";F1:eval'
Makeshifts last the longest.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re^3: My First Good(?) Original(?) JaPh,s
by sauoq (Abbot) on May 24, 2003 at 17:00 UTC |