In highschool, I had a friend who spent a few weeks reading the ASM for Pool of Radiance and hacked the codewheel section. He had it always display the same question, then display the answer on the screen for you to type in.

My point is that every single program that a user can get a hold of a copy of (through any means) is hackable. I mean, it has to eventually tell the CPU what to do and a human can, if sufficiently determined, figure out what is going on.

That said, there are differing levels of difficulty you can create for would-be evil-doers. Using a compiled language for stuff that users aren't supposed to edit is a good start, but Perl won't be compilable until Parrot is out. (Well, it is, but not really.)

Ultimately, the most secure system is the one that no-one can access. Once you allow access, you allow some level of insecurity. At some point, you just have to grin and bear it.

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re: Parsing/Running script from memory in embed perl by dragonchild
in thread Parsing/Running script from memory in embed perl by demode

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.