Comparing these two statements makes my head spin:

The encryption algorithm in Perl2Exe has been improved.

and

they don't guarantee any security of the source code

Why? Why? If it's just a bundler, let it be a bundler. It can never be really secure, because I can always single step the program to the point where you call the Perl interpreter's "eval" method with the now-decrypted source code.

This is looking more and more like snake oil. And since you somehow know it's been improved recently, I suspect you are an insider with the developers.

So, why did the developers bother to increase the security? Because XOR is something a customer base can understand, but "more security" isn't? Are you only reacting to the public outcry? Would you have fixed it if it didn't show up on bugtraq? Will you upgrade it even more when (not if) it gets broken again?

If it's truly secure, open up your methods to peer review.

Until then, I'll stand by my statement that perl2exe is snake oil, being sold to a naive public, and that's unethical to me.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.