moderated >> Free Perl obfuscation web service

by Liraz.Siri » Wed, 02 Feb 2005 20:52:17 GMT

Perl readability keeping you up at night? Worried someone else might
one day understand your spaghetti code? Say no more! Your job security
woes are over!

I needed to obfuscate a bunch of Perl scripts a while ago. Now Perl is
famous for being naturally obfuscated, but I had something more extreme
in mind. As the thought of further obfuscating my Perl scripts by hand
horrified me, I looked around for a free automated solution.

Long story short, I didn't find anything decent, so I wrote my own.
It's pretty neat, and handles (almost) all Perl constructs. I kept
working out the bugs until it was powerful enough to obfuscate itself
recursively an arbitrary amount of passes.

Anyway, the pricing for the commercial obfuscation stuff is absolutely
outrageous:

"The Stunnix Perl-Obfus Single Developer License costs $879, and can be
purchased online in our store. May be used by the same user on any
number of machines. Full text of the license is here."

So I turned my obfuscator program into a web service anybody can use
for free:

http://liraz.org/obfus.html

Enjoy!

----- End forwarded message -----

moderated >> Free Perl obfuscation web service

by nobull@mail.com » Sat, 05 Feb 2005 03:53:01 GMT



Well I just tried a couple of what I'd consider 'tricky' constructs and
I tripped it up on the third attempt:

print '\'';

But then I assume this is only a joke anyhow.

----- End forwarded message -----

Similar Threads

1. Free perl obfuscation service - Perl

2. Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API

1. Develop a PERL WEB SERVICE that utilizes the Yahoo Web Services API's so
that you can offer a  Yahoo Search via your own perl webpage. So, you'll
have to utilize the cpan/ppm tools to install the SOAP::Lite perl module,
then, you'll need to create a web form and a perl script that will utilize
the web services provided by Yahoo. 

3. Calling .Net web service using a PERL client. - Asp.Net Web Service

4. Problem: ASP.NET/C# Console Client calls Perl Web Service (Invoke - returns NULL)

I am trying to get my C# client to connect to a 3rd Perl Web Service (SOAP 
Lite), this is the code that fails

.....
object[] results = this.Invoke("getGrossData", new object[] {week} );
return ((string)results[0]);
......

The problem:   It always return a NULL in results[0].  Why is that??

My Verficiation:
1. I have the TCP/IP Trace tool, and I can see the Perl Web Service returns 
the correct data in the HTTPResponse.  I just don't understand why .NET 
returns NULL in result[0]
2. If I connect to my own microsoft ASMX web service on IIS, result[0] 
returns what I expected
3. I even use Telnet to verify manually,  I copied and pasted the request 
manually and I got the expected data from the Web Service.
4. I even tried to   override  this and print out the HTTPResponse, and I 
was able to see the HTTPResponse from Web Service
protected override WebResponse GetWebResponse(WebRequest req)

But I don't understand why .NET returns NULL in result[0].   Please help..

Zean


5. Connecting a Perl Web Service to ASP.Net - Asp.Net Web Service

6. .Net Web Services and Perl

I am in the process of building an XML web service, using VB.Net which
will be called over the internet by clients on various platforms.

Does anyone have any experience of consuming a .Net web service using
Perl or writing a .Net web service to be consumed by Perl?  If so, I'd
like to hear of any problems you may have encountered or hints you may
have that I might learn from before I continue.

One thing in particular is, the type of data that will be returned by
the method calls.  Say a method needs to return both a numeric code
and a message; I could keep it simple and return just a string
containing both the number and message concatenated that could then be
examined by the client or I could return a serialized class with a
number and a string property.  Is one easier for the client than the
other?

Thanks in advance

Ian

7. Accessing .NET web service from Perl (SOAP::Lite) client - Asp.Net Web Service

8. Umlauts from PERL script on FreeBSD dropped by C# web service

Hi,         We wrote a Web service to put some information from forms on our 
Web site into a SQL database.  It works great.  The only problem is that 
when Germans visit our site and enter a name like "Dkheim," the entry 
shows up in our SQL table as "Drkheim."

I've verified that SQL (on the back end) and Apache/PERL (on the front end) 
all support the extended ASCII characters.  That leaves the C# web service 
(or the interaction between it and the PERL script running on FreeBSD).

As you can see from the capture of the conversation between PERL/FreeBSD and 
C#/IIS below, the " shows up on the wire as 0xfc.  Does anyone know 
whether C# (Windows 2000) should deal correctly with that encoding, or how 
to fix the problem?  We are using SOAP::Lite on the PERL side.

Thanks,
BGU

0x0380   7269 6e67 222f 3e3c 4669 7273 745f 4e61        ring"><