in reply to 1337JAPH
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: 1337JAPH
by muntfish (Chaplain) on Sep 01, 2004 at 10:56 UTC | |
Like you, I'm only just starting out in the world of obfuscation... This is just a few thoughts that came into my head when I read your code. Not necessarily criticisms! Try to avoid assigning to "real" variables like @n etc. Use perl builtin variables like $= or $; or just put the values inline. I changed your assignment of @l to a quoted string using qw;; (there are lots of options for the delimiters of quoted strings, ; is one I've been playing about with recently) - more obfu than an "English" word like split. You also had some dupes in @l which I removed. I'm not sure if they were in there on purpose (to confuse/mislead) or not. Same goes for q0, which I removed. Again this doesn't necessary make it more (or less) obfuscated but it does compact things a bit. You could also consider muddling up the list in non-alphabetic order. I re-arranged a few other things, using $1,$2 instead of $e,$r and re-ordered the print/pack code into something a little shorter, without changing the basic meaning of the code.
I hope this is useful, if only a little. Others more experienced (or with more warped minds, depending on how you look at it) may suggest more interesting ways to obfuscate your code. Perhaps you could consider changing from binary to some other more wacky pack format (maybe uuencode?). Good luck anyway. s^^unp(;75N=&9I<V@`ack(u,^;s|\(.+\`|"$`$'\"$&\"\)"|ee;/m.+h/&&print$& | [reply] [d/l] [select] |