Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re^6: What happened to perlcc?

by ikegami (Pope)
on Feb 27, 2011 at 23:27 UTC ( #890476=note: print w/replies, xml ) Need Help??


in reply to Re^5: What happened to perlcc?
in thread What happened to perlcc?

Please feel free to read the code or even the docs.

Not only did I read the docs (doesn't mentioned anything on this) and the code (where I got that info), I ran the code. block contains the entire original source code, intact, not obfuscated.

If you can find any false claims that I make for perlc, I'd love to hear about them.

Like I've said many times, it doesn't obfuscate. It happily provides the entire original source code intact (after unbleach.pl if bleach is used). Aside from that, there's at least the following I didn't mention before:

  • It doesn't convert Perl to C.
  • Finally, there's an implicit claim that an executable can be made from the generated .c file, but it's not obvious how to do that.

Replies are listed 'Best First'.
Re^7: What happened to perlcc?
by daveola (Acolyte) on Feb 28, 2011 at 21:45 UTC
    It's strange, you even mention it yourself:

    Source code is also obfuscated using a simple key to avoid extracting the string from the executable.

    And in the home page, perhaps missed, was:

    Takes a single perl script, converts the block using a simple encoding with an optionally defined key.

    Which you can see from the usage involves the '-key' option.

      -key <str>         Specify key for encode/decode of embedded script

    So your claim that the source code is provided intact is false.

    And yes, it's weak encryption. Clearly if someone wants to attack an obfuscation like this, they'll do some sort of runtime attack rather than try to decode the script.

    You also state: "Finally, there's an implicit claim that an executable can be made from the generated .c file, but it's not obvious how to do that"

    And again, from the usage:

      -exe <exec>        Compile the code into an executable

    I think that's pretty simple

    But to help make it clearer, I've added the compilation command to the comments at the top of the C output.

      And in the home page, perhaps missed, was:

      Wasn't missed, just not relevant.

      And yes, it's weak encryption

      It's encoding, not encryption or obfuscation. There must be a secret for encryption.

      So your claim that the source code is provided intact is false.

      No, even when a key is specified, the code is provided intact.

      Compile the code into an executable

      I missed that, thanks.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://890476]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (2)
As of 2020-12-05 15:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How often do you use taint mode?





    Results (64 votes). Check out past polls.

    Notices?