Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

Re: Re: Re: Re: Here is a commercial obfuscator

by Anonymous Monk
on Mar 21, 2003 at 06:53 UTC ( #244803=note: print w/replies, xml ) Need Help??

in reply to Re: Re: Re: Here is a commercial obfuscator
in thread Here is a commercial obfuscator

That's nice, but let me remind that reverse-engineering is prohibited by laws of a lot of countries (including USA). And since a sole (exclusive!) purpose of B::Deobfuscate is to break obfuscation (obviously for reverse-engineering), posting this to can hurt it (if say Stunnix guy will be smart and will bring admin of perlmonks to court). So it may be wise to move B::Deobfuscate from to somewhere else. That's nearly as posting license keys for ActiveState commercial products here..
  • Comment on Re: Re: Re: Re: Here is a commercial obfuscator

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Here is a commercial obfuscator
by herveus (Parson) on Mar 21, 2003 at 12:59 UTC

    Oh? By what theory do you construe B::Deobfuscate as reverse-engineering? It is based on the openly published (by the vendor) description of how the product achieves its claimed end. No evidence has been adduced that diotalevi has obtained and/or examined the actual product.

    Of course, you don't have any such theory. You just can't take the heat, so you try FUD. Go away.


      Independant of how B::DeObfuscate was implemented, it's sole purpose is reverse engineering of the products obfuscated with Stunnix Perl-Obfus and others (not for reverse-engineering the Perl-Obfus itself of course - please feel the difference!). You try to imply that one may use nuclear bomb for anything but bombing. Have you ever seen in US shops master keys e.g. for Volvo car's locks? B::DeObfuscate is the same.

        You are talking nonsense.

        B::DeObfuscate works on any perl code, whether run through Perl-Obfus or not. It has already been pointed out that it would work fine on other code. It's a generic deobfuscator, not specific to Perl-Obfus. You may as well try and declare perltidy and B::Deparse illegal.

        The legality of running it on a piece of code depends on the licence for that code. If I wished I could purchase Perl-Obus, run it on a piece of my code, and release the "obfuscated" code under the GPL. It would be perfectly legal for people to do whatever they like to the source.

        If I wished I could write a piece of code, release it with a restrictive licence and if somebody altered so much as a single tab they would be breaking the law.

        Contracts, licences, patents and copyright control the legality of altering code. Obfuscation is a foolish method of trying to control source code.

        If I'm going to obey the law whether the code is obfuscated or not makes no difference - I'm not going to fiddle with the source.

        If I'm going to break the law obfuscation is so trivially overcome it's not going to make a difference.

        If you're capable of making a living distributing your obfusticator - good luck to you. Just don't expect the rest of the world to agree with you.

Re: Re: Re: Re: Re: Here is a commercial obfuscator
by iguanodon (Priest) on Mar 21, 2003 at 12:54 UTC
    Awwww, come on. You asked for this by posting here and claiming your obfuscation was irreversible. You were proved wrong by someone smarter than you. Now you're playing the legal card because you lost in the technical ring?



      ...and that card is mangled and unreadable...


Re: Re: Re: Re: Re: Here is a commercial obfuscator
by zengargoyle (Deacon) on Mar 21, 2003 at 07:28 UTC


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://244803]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (6)
As of 2018-06-18 07:55 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (109 votes). Check out past polls.